From: Jim Wilson <wilson@cygnus.com>
To: Kjartan Maraas <kmaraas@fib.hl.no>
Cc: "gnome-list@gnome.org" <gnome-list@gnome.org>,
"egcs@cygnus.com" <egcs@cygnus.com>
Subject: Re: Compiling problems (egcs)
Date: Tue, 24 Mar 1998 14:49:00 -0000 [thread overview]
Message-ID: <199803242049.MAA23824@rtl.cygnus.com> (raw)
In-Reply-To: <35122646.60AF116D@fib.hl.no>
It turned out that there were references
to the egcs-build-directory, in my case /usr/local/src/egcs-build, in
the libf2c.a library in /usr/local/lib (at least I think this was the
culprit). These references also ended up in my gnome-libs and after
deleting the egcs-build directory compiling barfed.
`references' and `compiling barfed' are not very descriptive. You need to
report exactly what commands you typed and exactly what problems you saw.
Some references from the source tree are unavoidable, because the libraries
are compiled with -g, and the debugging info contains the source file names.
Jim
prev parent reply other threads:[~1998-03-24 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-20 8:45 Kjartan Maraas
1998-03-24 14:49 ` Jim Wilson [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=199803242049.MAA23824@rtl.cygnus.com \
--to=wilson@cygnus.com \
--cc=egcs@cygnus.com \
--cc=gnome-list@gnome.org \
--cc=kmaraas@fib.hl.no \
/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).