How to stop GCC from searching for components in --prefix on Windows host?
Dave Korn
dk@artimi.com
Wed Sep 22 17:48:00 GMT 2004
> -----Original Message-----
> From: gcc-owner On Behalf Of E. Weddington
> Sent: 22 September 2004 17:29
> Hello!
>
> I regularly build GCC for the AVR target on a Windows host
> (--host=mingw32) usually with some configured --prefix=X. The binary
> toolset is redistributed to other users who typically don't
> install it in X.
The error is with your users, not gcc! Heh, well, it's fair enough to say
that it's a limitation of gcc that it gets hard-coded install paths built
into it.
> There have been some problems where X on the build machine is on a
> particular drive, and on the install machine X is on a drive with
> removable media, then GCC sometimes craps out and doesn't properly
> locate all the components. Is there some way to get GCC to *not* search
> for components in the configured prefix, but preserve its
> other search rules?
How about supplying a dummy path to the --prefix argument when you build
your releases, something that points to C:\ or whatever, something that's
pretty much guaranteed to be there on every system you need to support but
also pretty much guaranteed not to contain any executables that would get in
the way?
cheers,
DaveK
--
Can't think of a witty .sigline today....
More information about the Gcc
mailing list