public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* problem with genattr on i386-pc-linux-gnulibc
@ 1997-12-03 15:32 Matthew D. Langston
  1997-12-03 21:10 ` Joseph H. Buehler
  1997-12-03 23:52 ` Jeffrey A Law
  0 siblings, 2 replies; 3+ messages in thread
From: Matthew D. Langston @ 1997-12-03 15:32 UTC (permalink / raw)
  To: egcs

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: problem with genattr on i386-pc-linux-gnulibc
  1997-12-03 15:32 problem with genattr on i386-pc-linux-gnulibc Matthew D. Langston
@ 1997-12-03 21:10 ` Joseph H. Buehler
  1997-12-03 23:52 ` Jeffrey A Law
  1 sibling, 0 replies; 3+ messages in thread
From: Joseph H. Buehler @ 1997-12-03 21:10 UTC (permalink / raw)
  To: egcs

"Matthew D. Langston" <langston@SLAC.Stanford.EDU> writes:

> 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 am having similar problems with i686-pc-linux-gnulibc1 under redhat
4.2, though using 971201, not egcs-1.0 (yet).  You don't show a core
dump message, but in my case, the linker is coredumping with a SEGV.

> 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'll have to try omitting --host, maybe it will fix my problems.

> 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.

I build with a shell script, here is what it does, maybe you can do
the same thing in your .spec file:

    : unpack tar &&
    : cd top-level source directory &&
    mkdir .src &&
    mv * .src &&
    mv .src src &&
    mkdir build &&
    cd build &&
    : configure, make, etc.

Joe Buehler

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: problem with genattr on i386-pc-linux-gnulibc
  1997-12-03 15:32 problem with genattr on i386-pc-linux-gnulibc Matthew D. Langston
  1997-12-03 21:10 ` Joseph H. Buehler
@ 1997-12-03 23:52 ` Jeffrey A Law
  1 sibling, 0 replies; 3+ messages in thread
From: Jeffrey A Law @ 1997-12-03 23:52 UTC (permalink / raw)
  To: langston; +Cc: egcs

  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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~1997-12-03 23:52 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1997-12-03 15:32 problem with genattr on i386-pc-linux-gnulibc Matthew D. Langston
1997-12-03 21:10 ` Joseph H. Buehler
1997-12-03 23:52 ` Jeffrey A Law

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).