From: hjl@lucon.org (H.J. Lu)
To: chadg@redrose.net (Chad Gatesman)
Cc: leei@ai.sri.com, oliva@dcc.unicamp.br, egcs@cygnus.com,
egcs-bugs@cygnus.com
Subject: Re: -frepo not working?
Date: Wed, 16 Dec 1998 12:25:00 -0000 [thread overview]
Message-ID: <m0zqNUq-00038tC@ocean.lucon.org> (raw)
In-Reply-To: <98Dec16.150359est.26887@gateway.bristol.com>
> Yes. I understood you, and I am saying it still does not work for me if I put -frepo on the link line. Here are the versions
> I am using. Could it possibly be a problem there, or maybe a platform specific bug? I am using Linux 2.1.129 on an Intel
> Pentium using libc.so.5.4.46.
>
>
> chad:/tmp> g++ -v
> Reading specs from /usr/local/lib/gcc-lib/i586-pc-linux-gnulibc1/pgcc-2.91.60/specs
> gcc version pgcc-2.91.60 19981201 (egcs-1.1.1 release)
> chad:/tmp> ld -v
> GNU ld version 2.9.1 (with BFD 2.9.1)
If you use Linux, you should use my binutils. The
current one is 2.9.1.0.19a.
>
> chad:/tmp> g++ -frepo -c repo-fail.cc
> chad:/tmp> g++ -frepo -o repo-fail repo-fail.o
# uname -a
Linux ocean.lucon.org 2.1.131 #1 SMP Tue Dec 15 19:35:46 PST 1998 i686 unknown
# g++ -frepo -c repo-fail.cc
# g++ -o repo-fail repo-fail.o
collect: recompiling repo-fail.cc
collect: relinking
BTW, I am using glibc 2.0.7.
H.J.
next prev parent reply other threads:[~1998-12-16 12:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-14 11:13 Chad Gatesman
1998-12-16 0:41 ` Alexandre Oliva
1998-12-16 9:55 ` Chad Gatesman
1998-12-16 11:07 ` Lee Iverson
1998-12-16 11:20 ` Chad Gatesman
1998-12-16 11:33 ` Lee Iverson
1998-12-16 12:04 ` Chad Gatesman
1998-12-16 12:25 ` H.J. Lu [this message]
1998-12-16 15:37 ` Chad Gatesman
1999-01-22 9:26 ` Swen Thuemmler
1999-01-22 10:54 ` Chad Gatesman
1999-01-31 23:58 ` Chad Gatesman
1999-01-31 23:58 ` Swen Thuemmler
1998-12-17 8:21 ` Chad Gatesman
1998-12-17 8:06 ` Horst von Brand
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=m0zqNUq-00038tC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=chadg@redrose.net \
--cc=egcs-bugs@cygnus.com \
--cc=egcs@cygnus.com \
--cc=leei@ai.sri.com \
--cc=oliva@dcc.unicamp.br \
/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).