cross compiling patches
Wed Mar 29 16:42:00 GMT 2000
> >One remaining (and yet uncommented) problem is that the second level
> > - libiberty
> > - include
> >of our cvs repository are not compatible to the current state of
> >the net release preview. I think it's due to the fact that
> >binutils in the repository is a 199909.. version while the net
> >release binutils is the 19990818-1 version.
> >I only want let this as an aid to memory.
> This has already been commented on in the cygwin-developers mailing
> list and DJ is looking into this.
My current thinking is to remove all the libiberty.a files and other
shared development files (bfd, opcodes) from the three tarballs that
shouldn't have them (gcc, binutils, gdb) as those packages really
shouldn't be exporting those libraries to other packages (yes,
binutils/bfd is an exception, but...). They are often incompatible
between packages, and there isn't really anything we can do about
them. Plus, any source package that needs them usually includes the
right version itself.
I did find that the only differences between the *.h files was that
gdb's had CR/LF and binutils's had NL. Except, that assert from gcc
and from cygwin are totally different but either should work just
c++filt is another example of two packages owning the same tool. I
don't know who has the master copy.
More information about the Cygwin-patches