<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>
<blockquote type="cite"> I've seen these compiler defining
constants come and go and mutate over the decades</blockquote>
Nah, _WIN32 and _WIN64 have always been the standard definitions.
_WIN32 is always defined, and _WIN64 is additionally defined for
64-bit targets. But some toolchains used their own non-standard
definitions (e.g. MinGW defined "WIN32")</p>
<p>
<blockquote type="cite">Platform: Unknown</blockquote>
I think there might be a problem ;-)<br>
</p>
<p>
<blockquote type="cite">usr/lib/gcc/x86_64-pc-msys/10.2.0/</blockquote>
These paths are wrong. The toolchain should be in the "mingw32"
resp. "mingw64" folder.<br>
</p>
<p>Just a quick check: did you follow all the steps in
<a class="moz-txt-link-freetext" href="https://github.com/pure-data/pure-data/blob/master/INSTALL.txt">https://github.com/pure-data/pure-data/blob/master/INSTALL.txt</a>?</p>
<p>Especially, did you install the necessary toolchains and do you
run your commands from the "MINGW32" shell resp. the "MINGW64"
shell? Don't use the "MSYS" shell for compiling!<br>
</p>
<p>Christof<br>
</p>
<p>On 09.12.2020 16:22, David Rush wrote:<br>
</p>
<blockquote type="cite"
cite="mid:CAA_wS4UuYtGbXwRBBDB+7h0s=i9Rab2z_gY0PwAkoC2WfyFbEQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">On Wed, 9 Dec 2020 at 14:53, Christof Ressi <<a
href="mailto:info@christofressi.com" moz-do-not-send="true">info@christofressi.com</a>>
wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div>
<p> </p>
<blockquote type="cite"> indicating that _WIN32 is not
defined.</blockquote>
<blockquote type="cite">So if I instead build with
CFLAGS=-D_WIN32, I get a different set of errors while
building s_inter.c</blockquote>
<p> If "_WIN32" is not defined by the compiler, something
is going very wrong...</p>
</div>
</blockquote>
<div>Well...-ish. I've seen these compiler defining constants
come and go and mutate over the decades and versions. Even
u$oft did it in VS a couple of versions ago. I had to go
back and twiddle SO MANY bits of code that all had slightly
different ways of detecting OS and machine details. </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div>
<p> </p>
<blockquote type="cite">usr/lib/gcc/x86_64-pc-msys/10.2.0/../../../../x86_64-pc-msys/bin/ld:
pd-s_audio_oss.o: in function `oss_open_audio':</blockquote>
This files should never be built on Windows in the first
place. Can you post the full output of the "./configure"
and "make" command and attach them as text files?<br>
</div>
</blockquote>
<div><br>
However, I did find this odd. My configure output ends with</div>
<div><br>
</div>
configure:<br>
<br>
pd 0.51.3 is now configured<br>
<br>
Platform: Unknown<br>
Debug build: no<br>
Universal build: no<br>
Localizations: yes<br>
Source directory: .<br>
Installation prefix: /usr<br>
<br>
Compiler: gcc<br>
CPPFLAGS:<br>
CFLAGS: -ffast-math -funroll-loops
-fomit-frame-pointer -O3<br>
LDFLAGS:<br>
INCLUDES:<br>
LIBS: -lpthread -ldl<br>
<br>
External extension:<br>
External CFLAGS:<br>
External LDFLAGS:<br>
<br>
fftw: no<br>
wish(tcl/tk): wish<br>
audio APIs: OSS<br>
midi APIs: OSS<br>
<br>
<div>and yet, I still see portaudio/portmidi being built. I
wonder if the configure process is actually what is going
wrong here?</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div>
<p>Just for the record, can you successfully build other
software with Msys2? Just to rule out a general problem
with your Msys2 installation.</p>
</div>
</blockquote>
<div>PD (and my externals) are the only software of substance
I am currently building with Msys2. Mostly I work in Scheme
and Haskell when doing my own hacking, and VS C++ for money.<br>
<br>
</div>
<div>Logs &cet attached </div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Pd-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Pd-dev@lists.iem.at">Pd-dev@lists.iem.at</a>
<a class="moz-txt-link-freetext" href="https://lists.puredata.info/listinfo/pd-dev">https://lists.puredata.info/listinfo/pd-dev</a>
</pre>
</blockquote>
</body>
</html>