This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Should I be able to build cross gcc 4.x on Cygwin?



On Dec 12, 2007, at 3:47 PM, Brian Dessent wrote:


Rick Mann wrote:

$ mkdir combined
$ cd combined
$ ln -s ../gcc-4.2.2/* .
$ ln -s ../binutils-2.17/* .
[several complaints from ln about existing links]
$ ln -s ../newlib-1.15.0/* .
[several complaints from ln about existing links]
$ cd ../..
$ mkdir testbuild
$ cd testbuild
$ ../src/combined/configure --target=xscale-elf --disable-nls --with-
newlib --prefix=/usr/local/xscale-elf-gcc --disable-newlib-supplied-
syscalls

I don't like that method at all, because it does not actually combine
anything, it simply takes the include/ dir from whatever tree you last
linked it to. In this case it looks like the include from newlib wins,
but it's not recent enough. You want to actually combine the contents
of all the include dirs in each package, not just select one.


Try the method here instead: <http://gcc.gnu.org/simtest-howto.html>.
This uses cpio to create hard links in the combined tree, which really
does create a union of the trees, rather than simply picking one version
of each directory to use.

Okay, I'll try that. However, two things:


1) The above technique works fine on Mac OS X (I'm about to try Fedora).
2) Doesn't the first ln take precedence? The subsequent ones fail if the link already exists, don't they (hence the warnings)?


Thanks for the other pointer, though.

--
Rick



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]