On 06/11/2013 04:18 PM, Philip Nienhuis wrote:
On my list is finding out how to build using mxe-octave on Windows 7
64-bit,
I'm starting to try the same thing now, so maybe we can help each other
and make it work.
> as that runs on my fastest dev box (the build I referred to runs
on an older Core Duo desktop).
I consistently get configure messages that "gcc cannot build
executables", with the log mentioning that ld cannot find a.o.,
-ladvapi32. Now, advapi32.dll and friends are in the C:\Windows\system32
dir which *is* in the MinGW PATH as /c/windows/system32. I've
experimented with LDFLAGS and other tricks to no avail :-) Google didn't
turn up a solution yet.
I think this is a very MinGW-specific issue.
This is with the 64-bit mingw and tools? Why is it trying to link with
advapi32? If that is normal, then where is that dependency coming from?
Is it explicitly listed in some Makefiles?