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

[Rick Mann <rmann at latencyzero dot com>]

On Dec 12, 2007, at 4:06 PM, Brian Dessent wrote:

> Rick Mann wrote:
>
> > 1) The above technique works fine on Mac OS X (I'm about to try  
> > Fedora).
>
> I don't know why that is off hand.  It could be a difference between  
> ln
> in Darwin and ln in GNU coreutils.
>
> > 2) Doesn't the first ln take precedence? The subsequent ones fail if
> > the link already exists, don't they (hence the warnings)?
>
> You're probably right, and that's exactly the problem: the include/ in
> gcc is not sufficient, it only contains a small subset of what the
> include/ in src contains, so that is bound to fail if the gcc one is
> used.


I used the following to make the combined dir. It seemed to work on  
Mac OS X, still trying on Cygwin. Do you see anything wrong with it? I  
have three top-level dirs: src (containing gcc-4.2.2/, binutils-2.17/,  
and newlib-1.15.0/), combined, work. My find requires no "-print" (but  
I'll use that in Cygwin).

 1643  rm -rf combined/
 1644  ls
 1645  cd src/newlib-1.15.0/
 1646  find . | cpio -pdlu ../../combined
 1647  cd ../binutils-2.17/
 1648  find . | cpio -pdlu ../../combined
 1649  cd ../gcc-4.2.2/
 1650  find . | cpio -pdlu ../../combined
 1651  cd ../..
 1653  cd work
 1654  rm -rf *
 1655  ../combined/configure --target=xscale-elf --disable-nls --with- 
newlib --prefix=/usr/local/gcc-xscale-elf --disable-newlib-supplied- 
syscalls
 1656  make


Does the order look good to you?

Thanks!

--
Rick