Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: Bruno Vidal <bruno_vidal@hpfrcu03.france.hp.com>,
	parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Unable to compil gcc2.96 on L2000/11.00/64 bits
Date: Tue, 10 Oct 2000 09:00:14 -0700	[thread overview]
Message-ID: <200010101600.JAA04506@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Tue, 10 Oct 2000 20:24:52 PDT." <Pine.LNX.4.21.0010102014070.20550-100000@front.linuxcare.com.au>

Alan Modra wrote:
...
> From memory, the steps I followed were:
>   build & install binutils
>   build & install gcc using "make LANGUAGES=c; make LANGUAGES=c install"
>   build & install glibc
>   rebuild gcc

Alan,
Could you update the relevant scripts in CVS build-tools repository?
(They may not need any changes and Bruno just needs to use those)

Last year I pushed for "recipes" and those got stale pretty quickly
because the folks on the bleeding edge weren't using them. Like Bruno,
I had a hard time reproducing the success others claimed they had.
(I still chuckle over puffin's phrase: "I don't believe you")
It shouldn't be that hard to build stuff from the CVS repositories.

I've given up on the recipe's and moved to scripts instead.
Matt Taggart has contributed the build-tools/palinux-autobuilder
and recipe.linux/recipe.hpux are mine. The README file should
explain what each does.

apologies for harping on this again,
grant

Grant Grundler
Unix Systems Enablement Lab
+1.408.447.7253

      reply	other threads:[~2000-10-10 15:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-10  8:06 [parisc-linux] Unable to compil gcc2.96 on L2000/11.00/64 bits Bruno Vidal
2000-10-10  9:24 ` Alan Modra
2000-10-10 16:00   ` Grant Grundler [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=200010101600.JAA04506@milano.cup.hp.com \
    --to=grundler@cup.hp.com \
    --cc=alan@linuxcare.com.au \
    --cc=bruno_vidal@hpfrcu03.france.hp.com \
    --cc=parisc-linux@thepuffingroup.com \
    /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