public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.org>
To: Arnaud Charlet <charlet@adacore.com>
Cc: Matthias Klose <doko@ubuntu.com>, gcc@gcc.gnu.org
Subject: Re: Building gcc on Ubuntu 11.10
Date: Thu, 09 Feb 2012 20:23:00 -0000	[thread overview]
Message-ID: <4F341DCE.2030500@moene.org> (raw)
In-Reply-To: <20120209181615.GA52526@adacore.com>

On 02/09/2012 07:16 PM, Arnaud Charlet wrote:

>>> Yes.  Debian moved everything for some reason.  It's a problem that must
>>> be addressed somehow before gcc 4.7 is released.
>>>
>>> It's extremely unfortunate that this will make it impossible to build
>>> older releases of gcc on newer Debian installations.
>
> Note that there's a simple work around:
> export LIBRARY_PATH=/usr/lib/x86_64-linux-gnu
>
> So this shouldn't block GCC 4.7.

I tried that, and it is not enough (it was for a while after August, 2011).

-- 
Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
At home: http://moene.org/~toon/; weather: http://moene.org/~hirlam/
Progress of GNU Fortran: http://gcc.gnu.org/wiki/GFortran#news

  reply	other threads:[~2012-02-09 19:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09  6:33 Nenad Vukicevic
2012-02-09 10:21 ` Ian Lance Taylor
2012-02-09 10:35   ` Richard Guenther
2012-02-09 18:16   ` Matthias Klose
2012-02-09 19:17     ` Arnaud Charlet
2012-02-09 20:23       ` Toon Moene [this message]
2012-02-15 14:56         ` Martin Jambor
2012-02-16  0:43           ` Toon Moene
2012-02-09 22:05   ` Russ Allbery
2012-02-09 23:14     ` Ian Lance Taylor
2012-02-09 23:53       ` Russ Allbery
2012-02-10 10:42         ` Andreas Schwab
2012-02-10 10:43           ` Andrew Haley
2012-02-10 19:01           ` Russ Allbery
2012-02-10 21:09             ` Toon Moene
2012-02-10 21:40               ` Russ Allbery

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=4F341DCE.2030500@moene.org \
    --to=toon@moene.org \
    --cc=charlet@adacore.com \
    --cc=doko@ubuntu.com \
    --cc=gcc@gcc.gnu.org \
    /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).