From: "Orn E. Hansen" <oe.hansen@oehansen.pp.se>
To: egcs@cygnus.com
Subject: Building breaks on shared libs
Date: Tue, 02 Dec 1997 22:54:00 -0000 [thread overview]
Message-ID: <199712030123.CAA26318@oehansen.pp.se> (raw)
I've applied the patches for the December 1st snapshot, and
configured it with '--enable-shared' and '--enable-thread'. After
having given the command:
make bootstrap-lean
The build successfully built the compiler and utilities, and went on
to the stdc++, finishing with making a static one 'libstdc++.a'. But
breaks on making the shared 'libstdc++.so.2.8.0'. It gives errors on
several files that are referred to under the 'libio' tree. Thinking
that some of these files were non-existant. However, taking a quick
look under the 'libio', those files were there. Maybe the links to
these files, for the making of shared libs, are given relative to the
wrong root tree?
The system I build it on, is Debian, with glibc 2.0.5c. I've
successfully used the egcs compiler with the static library, without
any problems. I also installed only the 'egcs-core' and 'egcs-c++'
parts of egcs (I don't need fortran :-)
next reply other threads:[~1997-12-02 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-02 22:54 Orn E. Hansen [this message]
1997-12-03 8:36 ` Jeffrey A Law
1997-12-03 12:54 ` Orn E. Hansen
1997-12-05 9:20 ` Jeffrey A Law
1997-12-05 10:44 ` Orn E. Hansen
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=199712030123.CAA26318@oehansen.pp.se \
--to=oe.hansen@oehansen.pp.se \
--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).