public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: assakhof <assakhof@mimos.my>
To: gcc-help@gcc.gnu.org
Subject: Re: gnu gcc in BSDI 4.0.1
Date: Fri, 28 Jul 2000 18:05:00 -0000	[thread overview]
Message-ID: <4.3.2.7.2.20000729085744.00ab8100@ew.mimos.my> (raw)
In-Reply-To: <oraef2l8a4.fsf@guarana.lsd.ic.unicamp.br>

At 10:00 AM 7/28/2000 -0300, Alexandre Oliva wrote:
>On Jul 28, 2000, assakhof <assakhof@mimos.my> wrote:
>
> > /var/tmp/ccVb72jg.s:121: Error: Alignment not a power of 2
>
>Incompatibility between GCC and the assembler.  Which assembler are
>you using?

# as -V
GNU assembler version 2.8.1 (bsd/os), using BFD version 2.8.1

> > Do I need to install GNU binutils ?
>
>Maybe.

I get binutils-2.10, so I decide to install it. But then I got this error 
(during binutils installation):

trad-core.c: In function `trad_unix_core_file_p':
trad-core.c:188: `USRSTACK' undeclared (first use this function)
trad-core.c:188: (Each undeclared identifier is reported only once
trad-core.c:188: for each function it appears in.)
make[3]: *** [trad-core.lo] Error 1
make[3]: Leaving directory `/var/src/binutils-2.10/bfd'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/src/binutils-2.10/bfd'
make[1]: *** [all-recursive-am] Error 2
make[1]: Leaving directory `/var/src/binutils-2.10/bfd'
make: *** [all-bfd] Error 2

But there were no word USRSTACK in trad-core.c ... It make me confuse.

FYI, I used GNU make-3.79 . Any help greatly appreciated.

Rgds,

--assakhof

  reply	other threads:[~2000-07-28 18:05 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
2000-07-28  5:50                         ` assakhof
2000-07-28  6:00                           ` Alexandre Oliva
2000-07-28 18:05                             ` assakhof [this message]
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=4.3.2.7.2.20000729085744.00ab8100@ew.mimos.my \
    --to=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).