Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Joel Soete <soete.joel@scarlet.be>
To: "Carlos O'Donell" <carlos@systemhalted.org>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
	Alan Mock <alan.mock@gmail.com>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Trouble Building GCC
Date: Thu, 02 Nov 2006 20:17:45 +0000	[thread overview]
Message-ID: <454A5269.8020800@scarlet.be> (raw)
In-Reply-To: <119aab440611021000i5c283d29mdda5682afdf2b2c8@mail.gmail.com>



Carlos O'Donell wrote:
> On 11/1/06, John David Anglin <dave@hiauly1.hia.nrc.ca> wrote:
>> Using debian and I believe gentoo, GCC 4.1 packages are available.
>> So, you really shouldn't have to build GCC unless you are interested
>> in working on or learning about GCC.  4.2 and 4.3 aren't ready for
>> prime time.
> 
> I recommended he start by learning to build the compiler.
> 
imho, a good source of information for that was for me the learning the way the debian packages (gcc-4.1 and gcc-4.2 aka 
gcc-snapshot) are build (verbose build and log the stuff was helpfull). More over, for me, those pakages are particulary 
well design: uptream sources, debian patches, ... and consequently easy to understand ;-)

Ciao,
	Joel
> Cheers,
> Carlos.
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
> 
> 
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

      parent reply	other threads:[~2006-11-02 20:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-02  0:38 [parisc-linux] Trouble Building GCC Alan Mock
2006-11-02  1:17 ` John David Anglin
     [not found]   ` <119aab440611021000i5c283d29mdda5682afdf2b2c8@mail.gmail.com>
2006-11-02 20:17     ` Joel Soete [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=454A5269.8020800@scarlet.be \
    --to=soete.joel@scarlet.be \
    --cc=alan.mock@gmail.com \
    --cc=carlos@systemhalted.org \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@lists.parisc-linux.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