On 7/9/2010 01:09, Dave Korn wrote:
On 07/07/2010 02:47, JonY wrote:
I'm working on the mingw-w64 GCC package on Cygwin. Normally, anything
cygwin gets installed to /usr, however, with gcc 4.6, the locales data
clashes.
Yaakov suggested installing to /usr, but there are some problems with it.
This makes GCC look in /usr/mingw regardless of what the toolchain
target is (anything matching mingw*), bad idea if we want a gcc 4
mingw.org cross toolchain later. It can be fixed, but I'm not too sure
how yet.
Hmm, does this even happen when it is being built as a cross- rather than
native- compiler? That would be a GCC bug if so; cross-compilers are meant
not to look in the standard system directories as if they were native, see the
docs for LOCAL_INCLUDE_DIR, SYSTEM_INCLUDE_DIR, STANDARD_INCLUDE_DIR and
INCLUDE_DEFAULTS(*) for full details.
Well, cross GCC looks in /sysroot/mingw if that is what you mean.
Locale data is also conflicting.
So can't it just go in $prefix/$target/share instead of $prefix/share after
a bit of fiddling with configure options?
It could.
