From: Charles Wilson <cwilson@ece.gatech.edu>
To: cygwin@cygwin.com
Subject: Re: Available for test: gcc-3.1.1-2 gcc2-2.95.3-8
Date: Thu, 11 Jul 2002 23:59:00 -0000 [thread overview]
Message-ID: <3D2E51ED.3080902@ece.gatech.edu> (raw)
In-Reply-To: <20020712000601.GA11148@redhat.com>
Christopher Faylor wrote:
> On Thu, Jul 11, 2002 at 01:19:03PM -0400, Charles Wilson wrote:
>
>>attempt to open /usr/lib/mingw/libstdc++-2.a succeeded
>>
>
> This is suspicious. It almost looks like libstdc++-2.a is empty.
> Otherwise, you would have seen some symbols being loaded here.
>
> I just tried this with the copy of libstdc++-2.a that I'd been
> using for setup builds and it seems to work ok.
>
> Could you do a "nm" on this file and make sure that it is not
> corrupted? Or maybe you need to do a ranlib on it?
It had symbols.
> I've put the copy of libstdc++-2.a that I'm using at
>
> ftp://cygwin.com/pub/cygwin/tmp/libstdc++-2.a.bz2
>
> if you want to try it.
DOH!
gcc-3.1.1 (or maybe gcc-mingw-3_1-20020516-1) clobbered my old
gcc-2.95.3 (mingw) version of /usr/lib/mingw/libstdc++.a.
I copied it to libstdc++-2.a AFTER installing gcc-3.1.1. After
restoring my original file (to libstdc++-2.a), everything worked.
Sorry for the confusion (boy, I feel silly).
So,
3.1.1:
gcc works
gcc -mno-cygwin works
g++ works
g++ -mno-cygwin works
g77 works
g77 -mno-cygwin works
2.95.3-8:
gcc-2 works
gcc-2 -mno-cygwin works
g++-2 works
g++-2 -mno-cygwin works (provided one installs libstdc++.a from mingw's
gcc as /usr/lib/mingw/libstdc++-2.a)
g77-2 breaks:
/usr/lib/libcygwin.a(libcmain.o)(.text+0x81): undefined reference to
`WinMain@16'
g77-2 -mno-cygwin breaks:
/usr/lib/mingw/libmingw32.a(main.o)(.text+0x8d):main.c: undefined
reference to `WinMain@16'
>> I'm probably doing something very stupid, which will occur to me 2
>>seconds after I send this, but could I ask you to wipe out your current
>>gcc2 installation, reinstall it, and see what happens?
>
>
> Sorry. I was slow. It took me about twenty seconds.
>
> You can disregard this email.
I gather you figured out what was "wrong" with g77-2 in gcc2-2.95.3-8 ?
--Chuck
P.S. Now, my tests are very very simple. Consider them "basic"
functionality tests. We still need more "real world" testing before
these are ready to go, IMO.
Also, I'm thinking that the files in
/usr/include/g++-3/ (including _G_config.h)
should go into a
gcc2-mingw-2.95_YYYYMMDD-X
package (perhaps along with
usr/lib/mingw/libg2c.a
usr/lib/mingw/libgcc.a
usr/lib/mingw/libobjc.a
usr/lib/mingw/libstdc++.a from mingw's gcc, appropriately '-2' renamed)
Hey, wait a minute -- maybe that's why g77-2 is failing? It's linking
against libg2c.a from 3.1? Yep, seems so!
--Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-07-12 3:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 2:19 Christopher Faylor
2002-07-11 3:47 ` Charles Wilson
2002-07-11 3:49 ` Charles Wilson
2002-07-11 6:47 ` Nicholas Wourms
2002-07-11 8:26 ` Charles Wilson
2002-07-11 20:26 ` Christopher Faylor
2002-07-11 20:50 ` Christopher Faylor
2002-07-11 10:19 ` Christopher Faylor
2002-07-11 11:56 ` Charles Wilson
2002-07-11 21:09 ` Christopher Faylor
2002-07-11 21:33 ` Unscrible--liangalei@CS.SJTU.EDU.CN liangalei
2002-07-11 23:59 ` Charles Wilson [this message]
2002-07-12 0:27 ` Available for test: gcc-3.1.1-2 gcc2-2.95.3-8 Christopher Faylor
2002-07-12 0:31 ` Charles Wilson
2002-07-12 1:32 ` Christopher Faylor
2002-07-12 2:54 ` Charles Wilson
2002-07-12 4:40 ` Christopher Faylor
2002-07-12 9:22 ` Charles Wilson
2002-07-12 18:46 ` Christopher Faylor
2002-07-12 7:27 ` Nicholas Wourms
2002-07-15 0:55 ` Charles Wilson
2002-07-15 1:09 ` Christopher Faylor
2002-07-15 8:02 ` Nicholas Wourms
2002-07-15 11:56 ` Charles Wilson
2002-07-15 12:36 ` Nicholas Wourms
2002-07-11 7:19 ` Nicholas Wourms
2002-07-11 9:05 ` Christopher Faylor
2002-07-11 14:26 ` Nicholas Wourms
2002-07-11 8:49 ` Pavel Tsekov
2002-07-12 2:38 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D2E51ED.3080902@ece.gatech.edu \
--to=cwilson@ece.gatech.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).