From: "Matthew D. Langston" <langston@SLAC.Stanford.EDU>
To: egcs <egcs@cygnus.com>
Subject: problem with genattr on i386-pc-linux-gnulibc
Date: Wed, 03 Dec 1997 15:32:00 -0000 [thread overview]
Message-ID: <3485B0DB.D3249E62@SLAC.Stanford.EDU> (raw)
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
make[2]: *** [stamp-attr] Error 126
make[2]: Leaving directory `/home/work/projects/rpm/BUILD/egcs-1.0/gcc'
make[1]: *** [bootstrap-lean] Error 2
make[1]: Leaving directory `/home/work/projects/rpm/BUILD/egcs-1.0/gcc'
make: *** [bootstrap-lean] Error 2
*** End error message ***
I configured and built egcs-1.0 *in the egcs-1.0
source directory* as follows:
langston@seto$ ./configure --prefix=/usr/local --enable-shared i386-pc-linux-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').
I am building RedHat RPMs of egcs-1.0 for my site, so
I must pass the `i386' target type to configure.
Also, since I am building RedHat RPMs, I must build
egcs-1.0 in the source directory. This is contrary to
the advice given at
http://www.cygnus.com/egcs/install/configure.html , but
since I am building RPMs I have no choice but to build
in the source directory.
Can anyone offer insight into this problem?
--
Matt Langston
SLD, Stanford Linear Accelerator Center
langston@SLAC.Stanford.EDU
next reply other threads:[~1997-12-03 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-03 15:32 Matthew D. Langston [this message]
1997-12-03 21:10 ` Joseph H. Buehler
1997-12-03 23:52 ` Jeffrey A Law
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=3485B0DB.D3249E62@SLAC.Stanford.EDU \
--to=langston@slac.stanford.edu \
--cc=egcs@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).