From: Jeffrey A Law <law@cygnus.com>
To: langston@SLAC.Stanford.EDU
Cc: egcs <egcs@cygnus.com>
Subject: Re: problem with genattr on i386-pc-linux-gnulibc
Date: Wed, 03 Dec 1997 23:52:00 -0000 [thread overview]
Message-ID: <3850.881221745@hurl.cygnus.com> (raw)
In-Reply-To: <3485B0DB.D3249E62@SLAC.Stanford.EDU>
In message < 3485B0DB.D3249E62@SLAC.Stanford.EDU >you write:
> I received the following error when building egcs-1.0
> on a PentiumII running vanilla RedHat 4.2 Linux.
> *** Begin error message ***
> stage1/xgcc -Bstage1/ -DIN_GCC -O2 -g -O2 -DHAVE_CONFIG_H -o genattr
> \
> genattr.o rtl.o ` case "obstack.o" in ?*) echo obstack.o ;; esac ` ` case
> "" in ?*) echo ;; esac ` ` case "" in ?*) echo ;; esac `
> ./genattr ./config/i386/i386.md > tmp-attr.h
> /bin/sh: ./genattr: No such file or directory
Hmmm, this does not look like a problem with egcs -- it looks more
like a system error of some kind.
> langston@seto$ ./configure --prefix=/usr/local --enable-shared i386-pc-li
> nux-gnulibc
> langston@seto$ make bootstrap-lean
>
> However, egcs-1.0 builds absolutely fine when I don't
> pass `configure' a target name (which, in my case,
> defaults to `i686-pc-linux-gnulibc1').
You should never have to provide a target name for native builds;
if rpms are requiring that, then the rpms need to be fixed.
> Can anyone offer insight into this problem?
Avoid the rpms and just build egcs without them.
jeff
prev parent reply other threads:[~1997-12-03 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-03 15:32 Matthew D. Langston
1997-12-03 21:10 ` Joseph H. Buehler
1997-12-03 23:52 ` Jeffrey A Law [this message]
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=3850.881221745@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=langston@SLAC.Stanford.EDU \
/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).