public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Brian Dessent <brian@dessent.net>
To: Tim Prince <tprince@computer.org>
Cc: Thomas Mittelstaedt <T.Mittelstaedt@cadenas.de>,  	gcc-help@gcc.gnu.org
Subject: Re: Problem building gcc-4.2.2 on 64-bit ubuntu linux
Date: Thu, 20 Dec 2007 06:17:00 -0000	[thread overview]
Message-ID: <476A08C9.76332F9B@dessent.net> (raw)
In-Reply-To: <4769CBC8.8060705@computer.org>

Tim Prince wrote:

> Ubuntu decided to find a 64- vs 32- bit setup incompatible with
> predecessor distros.

Not just Ubuntu, but Debian (and anything based on Debian.)  You make it
out to seem like the Debian maintainers did this because they just felt
like being different, but I'm sure they had their own good reasons. 
After all, they had to maintain a local patch in their gcc trees to make
it work, so it's not like they didn't also feel the burden of this.  If
the distro maintainers thought that the tradeoff of making tens of
thousands of packages easier for their team of maintainers to manage
warrants a two line change in some gcc configury, then that's their
right.

> Presumably, there is an ubuntu patch set for this,
> but it's quite inconvenient that they chose to break the scheme chosen
> by their predecessors.  The scheme chosen by everyone else is to put the
> 64-bit stuff in /usr/lib64, and the 32-bit stuff in /usr/lib.

The patch to make this alternative layout work has been in mainline gcc
for more than 2 months:
<http://gcc.gnu.org/viewcvs?view=rev&revision=128845> so the issue is
now moot, or at least it will be before too long.

> Pretty
> much the kind of mess Bill Gates wanted to see the alternatives get into.

And this is relevant how?!?  Yes, it sure does suck that you can't
install gcc in Debian.  Oh wait, you can: "apt-get install gcc".

The fact that Debian maintainers go out of their way to modify and
"Debianize" many software packages sometimes does mean that occasionally
patches are required to get upstream sources to work.  This is a feature
not a bug, and it's one of the reasons why I happen to cherish Debian
based systems above all others.  If you want something that's just a
bunch of software thrown together without any patches (= without any
cohesion), by all means run far and fast from Debian; it will drive you
crazy.

Brian

  reply	other threads:[~2007-12-20  6:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19  9:09 Thomas Mittelstaedt
2007-12-19 12:36 ` John (Eljay) Love-Jensen
2007-12-19 13:34   ` Thomas Mittelstaedt
2007-12-19 14:32     ` Thomas Mittelstaedt
2007-12-19 15:00       ` Kai Ruottu
2007-12-19 15:14         ` Kai Ruottu
2007-12-19 15:03       ` Thomas Mittelstaedt
2007-12-19 16:55         ` Thomas Mittelstaedt
2007-12-20  1:56           ` Tim Prince
2007-12-20  6:17             ` Brian Dessent [this message]
2007-12-20 13:33               ` Problem building gcc-4.2.2 on 64-bit ubuntu linux, SUCCESS!! Thomas Mittelstaedt
2007-12-20  7:21             ` Problem building gcc-4.2.2 on 64-bit ubuntu linux Fabian Cenedese

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=476A08C9.76332F9B@dessent.net \
    --to=brian@dessent.net \
    --cc=T.Mittelstaedt@cadenas.de \
    --cc=gcc-help@gcc.gnu.org \
    --cc=tprince@computer.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).