public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Markus Sicheneder <sichen@studbox.uni-stuttgart.de>
To: egcs@cygnus.com
Subject: Re: egcs-1.0.2 installation (still problems)
Date: Thu, 16 Apr 1998 13:53:00 -0000	[thread overview]
Message-ID: <35362A72.B89DC37C@studbox.uni-stuttgart.de> (raw)
In-Reply-To: <13844.892695417@hurl.cygnus.com>

hello,

sorry to bother you guys again, but i still have problems with the
compilation of egcs-1.0.2 on my i586 linux system (just) with the shared
libs.

thanks for the answers so far; your suggestion to avoid the problems
was:

> Try building totally outside of the source directory, not as
> a subdir of the source tree.

so i have the following directorys now:
	/usr/src/egcs-1.0.2
and	/usr/src/egcs-obj

according to the INSTALL guide i did a:
	../egcs-1.0.2/configure --prefix=/usr/egcs --enable-shared
and	make bootstrap-lean (also tried: make bootstrap)
both in the /usr/src/egcs-obj dir.

here is the output of the configure command:
--- snip ----
sichen:/usr/src/egcs-obj # ../egcs-1.0.2/configure --prefix=/usr/egcs
--enable-shared
Configuring for a i586-pc-linux-gnulibc1 host.
Created "Makefile" in /usr/src/egcs-obj using
"../egcs-1.0.2/config/mh-x86pic" and "../egcs-1.0.2/config/mt-x86pic"
./config.status is unchanged
Links are now set up to build a native compiler for
i586-pc-linux-gnulibc1
sichen:/usr/src/egcs-obj # 
--- snip ----

i guess the realtive paths are ok as they are also used in the example
of the INSTALL guide.
well the problem i encounter is still the same; here the output:

------ snip ------
[...]
make[3]: Entering directory `/usr/src/egcs-obj/libraries/libio'
make[3]: `iostream.list' is up to date.
make[3]: Leaving directory `/usr/src/egcs-obj/libraries/libio'
/usr/src/egcs-obj/gcc/xgcc -B/usr/src/egcs-obj/gcc/ -g -O2
-fno-implicit-templates -Wl,-soname,libstdc++.so.`echo 2.8.0 | sed
's/\([0-9][.][0-9]\).*/\1/'` -shared -o libstdc++.so.2.8.0 `cat piclist`
-lm
xgcc: pic/cmathi.o: No such file or directory
xgcc: pic/cstdlibi.o: No such file or directory
xgcc: pic/cstringi.o: No such file or directory
xgcc: pic/cstrio.o: No such file or directory
xgcc: pic/cstrmain.o: No such file or directory
xgcc: pic/dcomio.o: No such file or directory
xgcc: pic/dcomplex.o: No such file or directory
xgcc: pic/fcomio.o: No such file or directory
xgcc: pic/fcomplex.o: No such file or directory
xgcc: pic/ldcomio.o: No such file or directory
xgcc: pic/ldcomplex.o: No such file or directory
xgcc: pic/stdexcepti.o: No such file or directory
xgcc: pic/stlinst.o: No such file or directory
make[2]: *** [libstdc++.so.2.8.0] Error 1
make[2]: Leaving directory `/usr/src/egcs-obj/libraries/libstdc++'
make[1]: *** [all-target-libstdc++] Error 2
make[1]: Leaving directory `/usr/src/egcs-obj'
make: *** [bootstrap-lean] Error 2
sichen:/usr/src/egcs-obj # ls
---- snip ----

actually i cant find a pic directory -- and my compiler neighter ?!

i am using:\x18
	gcc-2.7.2.1
	bin utilities 2.7.0.3
	make-3.76.1

well, i was able to compile gcc 2.8.0; but as far as i can remember the
shared libraries were compiled indepentendly (this is about 3-4 months
ago -- so i am not absolutely sure). so i think my system isnt really
the problem.

cu,
	markus

  reply	other threads:[~1998-04-16 13:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-15  2:25 egcs-1.0.2 installation Markus Sicheneder
1998-04-15 11:37 ` Jeffrey A Law
1998-04-15 15:09   ` Markus Sicheneder
1998-04-15 19:57     ` Jeffrey A Law
1998-04-16 13:53       ` Markus Sicheneder [this message]
1998-04-15 23:03     ` Gerald Pfeifer
1998-04-16 10:51       ` Craig Burley
1998-04-18  1:43         ` Jeffrey A Law
1998-04-17 23:53           ` Craig Burley
1998-04-19  1:49           ` Gerald Pfeifer
1998-05-07  6:52         ` PATCH: htdocs/install/configure.html Gerald Pfeifer
1998-05-08 13:02           ` Jeffrey A Law
1998-04-16  2:26     ` egcs-1.0.2 installation Manfred Hollstein US/EPB3 60/1F/110 #40283
1998-04-16 10:51     ` Horst von Brand
1998-04-16 18:39       ` Markus Sicheneder
1998-04-17 22:05         ` 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=35362A72.B89DC37C@studbox.uni-stuttgart.de \
    --to=sichen@studbox.uni-stuttgart.de \
    --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).