From: Richard Earnshaw <rearnsha@gcc.gnu.org>
To: Paul Brook <paul@codesourcery.com>
Cc: gcc@gcc.gnu.org, Mark Mitchell <mark@codesourcery.com>,
Toon Moene <toon@moene.indiv.nluug.nl>
Subject: Re: Mainline in regression-fix mode after Thanksgiving
Date: Mon, 29 Nov 2004 14:06:00 -0000 [thread overview]
Message-ID: <1101735554.1585.14.camel@pc960.cambridge.arm.com> (raw)
In-Reply-To: <200411291329.01550.paul@codesourcery.com>
On Mon, 2004-11-29 at 13:29, Paul Brook wrote:
> On Monday 29 November 2004 09:55, Richard Earnshaw wrote:
> > Whilst on the issue of g77 vs g95. I still regard the fact that you
> > have to build and install (in a system directory) a non-standard build
> > of a non-standard library (gmp with mpf) as a major build bug. This
> > makes it impossible for folks who don't have root access on their
> > machines to build and install the fortran compiler unless they are
> > prepared to set LD_LIBRARY_PATH (or whatever) every time they want to
> > run the resulting compiler.
>
> Not impossible. It should work if you build/link a static libgmp.a.
> I agree it's a problem though.
Default builds of these libraries on most platforms will produce DSO
versions of the libraries.
Defaults builds of gcc that link against these will link to the DSO
instances.
You pretty much need to be an expert to work around this. There's
certainly no configure-time option that I'm aware of that will do all
this for you -- it requires, at the least, changes to the make system.
R.
next prev parent reply other threads:[~2004-11-29 13:43 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 1:16 Mark Mitchell
2004-11-23 1:21 ` Kazu Hirata
2004-11-23 1:28 ` Diego Novillo
2004-11-23 1:31 ` Mark Mitchell
2004-11-23 1:37 ` Diego Novillo
2004-11-23 11:46 ` Nathan Sidwell
2004-11-23 16:09 ` Mark Mitchell
2004-11-23 2:15 ` Mike Stump
2004-11-23 2:31 ` Mark Mitchell
2004-11-23 3:00 ` Giovanni Bajo
2004-11-23 8:17 ` Daniel Berlin
2004-11-23 8:39 ` H. J. Lu
2004-11-23 17:19 ` Janis Johnson
2004-11-23 17:23 ` Giovanni Bajo
2004-11-23 18:02 ` Mark Mitchell
2004-11-23 18:20 ` Joe Buck
2004-11-23 18:34 ` Giovanni Bajo
2004-11-23 19:01 ` Joe Buck
2004-11-25 15:47 ` Gerald Pfeifer
2004-11-23 18:03 ` Janis Johnson
2004-11-23 22:14 ` Mike Stump
[not found] ` <41A3B68A.5020408@cs.york.ac.uk>
2004-11-23 23:52 ` Mike Stump
2004-11-24 18:49 ` Giovanni Bajo
2004-11-24 19:39 ` Joe Buck
2004-11-24 18:44 ` Giovanni Bajo
2004-11-25 12:41 ` Richard Sandiford
2004-11-25 18:03 ` Mike Stump
2004-11-28 13:02 ` Toon Moene
2004-11-24 17:29 ` Joseph S. Myers
2004-11-24 17:32 ` Mark Mitchell
2004-11-24 17:38 ` Gabriel Dos Reis
2004-11-28 12:59 ` Toon Moene
2004-11-29 5:02 ` Mark Mitchell
2004-11-29 11:30 ` Richard Earnshaw
2004-11-29 13:53 ` Paul Brook
2004-11-29 14:06 ` Richard Earnshaw [this message]
2004-11-29 16:07 ` Andreas Schwab
2004-11-29 21:47 ` Phil Edwards
2004-11-29 21:59 ` Paul Brook
2004-11-29 23:27 ` Phil Edwards
2004-11-30 22:49 ` Gerald Pfeifer
2004-11-23 20:05 Richard Kenner
2004-11-28 13:41 Richard Kenner
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=1101735554.1585.14.camel@pc960.cambridge.arm.com \
--to=rearnsha@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=paul@codesourcery.com \
--cc=toon@moene.indiv.nluug.nl \
/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).