From: Alexandre Oliva <aoliva@redhat.com>
To: assakhof <assakhof@mimos.my>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gnu gcc in BSDI 4.0.1
Date: Fri, 28 Jul 2000 00:09:00 -0000 [thread overview]
Message-ID: <orlmymn33m.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <4.3.2.7.2.20000728104326.00adc770@jaring.my>
On Jul 28, 2000, assakhof <assakhof@mimos.my> wrote:
> /var/src/gcc-2.95.2/gcc/f/fini.c:713: undefined reference to `__eprintf'
> Anybody 've an idea to solve this ?
Try `make bootstrap', in case you didn't, as per the installation
instructions.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2000-07-28 0:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Gregory>
[not found] ` <P.>
[not found] ` <Sherwood"'s>
[not found] ` <message>
[not found] ` <of>
[not found] ` <"Fri,>
[not found] ` <28>
[not found] ` <04>
[not found] ` <Feb>
[not found] ` <2000>
[not found] ` <09:33:58>
[not found] ` <-0800>
2000-02-04 9:31 ` GCC Build Gregory P. Sherwood
2000-02-06 19:06 ` Alexandre Oliva
2000-02-07 9:20 ` Gregory P. Sherwood
2000-04-01 0:00 ` Gregory P. Sherwood
2000-04-01 0:00 ` Alexandre Oliva
2000-04-01 0:00 ` Gregory P. Sherwood
[not found] ` <15:11:10>
[not found] ` <+0800>
2000-07-28 0:03 ` gnu gcc in BSDI 4.0.1 assakhof
2000-07-28 0:09 ` Alexandre Oliva [this message]
2000-07-28 5:50 ` assakhof
2000-07-28 6:00 ` Alexandre Oliva
2000-07-28 18:05 ` assakhof
2000-07-29 10:51 ` Alexandre Oliva
[not found] ` <"Wed,>
[not found] ` <15>
[not found] ` <Aug>
[not found] ` <2001>
[not found] ` <23:41:29>
[not found] ` <-0700>
2001-08-15 23:46 ` code broken by gcc 3.0 Brent Phillips
2001-08-16 18:18 ` Alexandre Oliva
2001-08-16 22:05 ` Brent Phillips
[not found] <Brent>
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=orlmymn33m.fsf@guarana.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=assakhof@mimos.my \
--cc=gcc-help@gcc.gnu.org \
/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).