From: Earnie Boyd <earnie_boyd@yahoo.com>
To: Andre Oliveira da Costa <costa@cade.com.br>,
Cygwin <cygwin@sourceware.cygnus.com>
Subject: RE: Linking problems
Date: Thu, 27 Jan 2000 14:16:00 -0000 [thread overview]
Message-ID: <20000127213815.17917.qmail@web118.yahoomail.com> (raw)
--- Andre Oliveira da Costa <costa@cade.com.br> wrote:
> > Get a binutils snapshot from Mumit's ftp site or rename collect2
> > so that it's
> > not found and ld is used directly.
>
> Mmmh... been there, but the snapshots seem to be older than the binutils
> package shipped with gcc-2.95.2:
>
> (contents of directory /pub/khan/gnu-win32/cygb20/snapshots)
>
> binutils-19990808/ dlltool/ gcc-2.95-19990715/
> binutils-19990818/ gcc-2.95-19990609/ libstdc++-v3-19990717/
> binutils-19990911/ gcc-2.95-19990626/ libstdc++-v3-2.90.7/
>
> I am trying to download binutils-000127.tar.bz2 directly from
> ftp://sourceware.cygnus.com , but I'm not sure I should use one of Mumit's
> snapshots instead. Could you (or Mumit, or anybody ;) ) shed some light
> here? In the meantime, I renamed collect2 to _collect2, and now I got the
> good old message
Can't help on this. Never tried a binutils build.
>
> foo.c: undefined reference to xxxx
>
> back. Odd thing: the linker output message appears slowly on my terminal,
> one char at a time (the rest of the output appears normally). Is this caused
> by the absence of collect2?
>
Copy ld.exe from the bin directory to the same directory as collect2. Modify
the specs file and substitute collect2 to ld.
=====
Earnie Boyd < mailto:earnie_boyd@yahoo.com >
Cygwin Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-01-27 14:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-27 14:16 Earnie Boyd [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-01 17:39 Sean LeBlanc
2004-02-01 23:17 ` Larry Hall
2004-02-02 0:32 ` Sean LeBlanc
2004-02-02 1:12 ` Larry Hall
2000-01-27 9:00 Earnie Boyd
2000-01-27 9:58 ` Andre Oliveira da Costa
2000-01-26 15:05 Earnie Boyd
2000-01-27 5:35 ` Andre Oliveira da Costa
2000-01-26 4:31 Andre Oliveira da Costa
2000-01-26 14:35 ` Andre Oliveira da Costa
1999-08-10 5:28 LInking problems MR. S.CHANDER
1999-08-11 11:27 ` Mumit Khan
1999-08-12 7:52 ` MR. S.CHANDER
1999-08-12 8:08 ` Mumit Khan
1999-08-13 6:03 ` MR. S.CHANDER
1999-08-31 23:49 ` MR. S.CHANDER
1999-08-31 23:49 ` Mumit Khan
1999-08-31 23:49 ` MR. S.CHANDER
1999-08-31 23:49 ` Mumit Khan
1999-08-31 23:49 ` MR. S.CHANDER
1998-07-23 8:33 Linking problems Aaron Schweiger
1998-07-24 0:25 ` Mumit Khan
1997-09-18 6:41 Ernest Clayton Cordell, Jr.
1997-09-17 21:11 Colin Peters
1997-09-17 4:35 Fredrik Eldh
1997-09-17 12:30 ` Mikey
1997-07-07 7:09 Jon Thackray
1997-07-07 12:07 ` Jon Thackray
1997-06-30 5:58 linking problems Wei Ku
1997-06-27 1:29 Berenice LOPEZ
1997-06-17 7:47 Linking problems Manmathan Muthukumarapillai
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=20000127213815.17917.qmail@web118.yahoomail.com \
--to=earnie_boyd@yahoo.com \
--cc=costa@cade.com.br \
--cc=cygwin@sourceware.cygnus.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).