Gerrit P. Haase wrote:
Dave Korn wrote:
Yep, that's got to be the source of the problem.
% ls /lib/gcc/i686-pc-mingw32
3.4.1
Gcc normally lives under "/lib/gcc-lib/....", rather than
"/lib/gcc/...";
someone's been playing around with all the various individual
--*-prefix=DIR
and --*dir= options at configure time, and got an inconsistent set.
BTW, the options used are
--prefix=/usr --exec-prefix=/usr \
--libdir=/usr/lib --libexecdir=/usr/lib
The path under lib and libexec is gcc controled. I just use
--libexecdir=/usr/lib because I dislike to have executables under
/usr/share/gcc/... where they put it nowadays.
With --libdir=/usr/lib --libexecdir=/usr/lib we have only one path,
/usr/lib/gcc/... else there are two, /usr/lib/gcc and /usr/share/gcc/...
one with the runtime libraries and one with the executables.
The gcc-lib path was used in pre 3.4 gcc releases.
Gerrit
--
=^..^=
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
