Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Carlos O'Donell Jr." <carlos@megatonmonkey.net>
To: Matthew Wilcox <willy@debian.org>,
	parisc-linux@lists.parisc-linux.org, baldric-exec@baldric.uwo.ca
Subject: Re: [parisc-linux] Building from scratch.
Date: Tue, 28 Aug 2001 11:06:14 -0400	[thread overview]
Message-ID: <20010828110614.A30657@megatonmonkey.net> (raw)
In-Reply-To: <20010828071743.A1289@megatonmonkey.net>; from carlos@megatonmonkey.net on Tue, Aug 28, 2001 at 07:17:43AM -0400

> > 
> > I have no enthusiasm for working on glibc.  Please, someone, take it
> > off my hands.
> > 
> > -- 
> > Revolutions do not require corporate support.
> >

Wow, do I feel like a knuckle head :}

So after allowing myself to sip a good cup of straight black joe,
I think I found _the_ problem with my setup.

I use a makefile + perl to automate the download/setup/install of
the toolchain and associated files (atleast that's what I'm working 
on...)

I noticed the following error in my makefile:

 --prefix=$(DEST)/hppa-linux\
--with-headers=$(SRC)/linux/include \

Which is definately not a good thing! Since both get concatenated
into a single --prefix. My apologies Matthew, I did not want to waste
your time or mine on something so trivial. Sadly, when trying for the
eleventybazillionth time ... you might miss the _missing_ space in
the configure line.

Please forgive me... once I finish the setup, would you like me to send
the list a new ./toolchain/index.html for the site?

Some things I've noticed that I will add to index.html:

a) Must remember to set CC to hppa-linux-gcc (It hurts when you forget)
	= glibc's configure always seeks out gcc and there seems to
	= be no --with-cc=?? option
	= The wrong gcc also hurts because configure adds 
	= -isystem /your/local/gcc/include rather than the proper one.

b) Must remember to add $DEST/bin to path (needed for building gcc)
	= gcc is the first complainer since it needs hppa-linux-ar.

c) If not running debian, must run:

[glibc-2.2.4]sh ./debian/patches/glibc22-hppa.dpatctch -patch /your/hppa/glibc
(This patch touches some ia64 stuff?)

I wonder how many people build the toolchain from source?
I love this crosscompiler! Especially since our dual PIII box can still
compile the pants of any of our HPPA boxes (especially the 715/50's ;)

<Carlos looks back at the compile, still chugging, much father!>

OH MY GOD!
It compiled with 0 errors and 0 warnings...

I'm estatic!

I'm too frenetic to actually attempt to xc something and test out glibc :}


I'll bet you lied about the patch failing just to taunt me!
I bested you! ;)


Cheers,
Carlos.

      parent reply	other threads:[~2001-08-28 15:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-26 20:27 [parisc-linux] Building from scratch Carlos O'Donell Jr.
2001-08-27 19:38 ` Matthew Wilcox
2001-08-28  3:54   ` Carlos O'Donell Jr.
2001-08-28  4:39   ` Carlos O'Donell Jr.
2001-08-28  5:10     ` Matthew Wilcox
2001-08-28 11:17       ` Carlos O'Donell Jr.
2001-08-28 14:56         ` Matthew Wilcox
2001-08-28 15:29           ` Carlos O'Donell Jr.
2001-08-28 18:47             ` Matthew Wilcox
2001-08-28 19:22               ` Carlos O'Donell Jr.
2001-08-28 19:44                 ` Matthew Wilcox
2001-08-28 20:36                   ` Carlos O'Donell Jr.
2001-08-28 20:47                     ` Matthew Wilcox
2001-08-28 15:06         ` Carlos O'Donell Jr. [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=20010828110614.A30657@megatonmonkey.net \
    --to=carlos@megatonmonkey.net \
    --cc=baldric-exec@baldric.uwo.ca \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=willy@debian.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