Problems remaking setup after cvs update
Brian Keener
bkeener@thesoftwaresource.com
Fri Mar 9 22:50:00 GMT 2001
Brian Keener wrote:
> briank@BK_SATELLITE /build/i686-pc-cygwin/winsup/cinstall
> $ make
> /usr/lib/gcc-lib/i686-pc-cygwin/2.95.2-6/../../../../i686-pc-cygwin/bin/l
> d:/usr/
> lib/libstdc++.a: file format not recognized; treating as linker script
> /usr/lib/gcc-lib/i686-pc-cygwin/2.95.2-6/../../../../i686-pc-cygwin/bin/l
> d:/usr/
> lib/libstdc++.a:1: syntax error
> collect2: ld returned 1 exit status
> c++: file path prefix `/build/i686-pc-cygwin/newlib/' never used
> make: *** [setup.exe] Error 1
>
> briank@BK_SATELLITE /build/i686-pc-cygwin/winsup/cinstall
> $
>
Okay, I think I figured this out on my own. I got it to compile but I
think there is a problem somewhere in libstdc++.a and I don't know what to
do with it.
I think what we have here is a symbolic link problem with the make utility
that involves libstdc++.a cause when I took a closer look at the error I
saw the message about libstdc++.a. I decided to take a closer look at
libstdc++.a and saw I had two - libstdc++.a and libstdc++.a.2.10.0 but
there was a noticeable bytes size difference in the 2. I did a less on
libstdc++.a which was only 29 bytes and saw the word symlink and thought
okay maybe this is a bad symbolic link (we have been making changes to this
haven't we????) And so I renamed libstdc++.a and then copied
libstdc++.a.2.10.0 to libstdc++.a and then tried the make again and voila -
my make completed.
Got any thoughts on this. This is by the way on a Win95 Laptop using all
current versions based on setup.exe.
bk
More information about the Cygwin-developers
mailing list