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 07:17:43 -0400 [thread overview]
Message-ID: <20010828071743.A1289@megatonmonkey.net> (raw)
In-Reply-To: <20010828061037.A13332@parcelfarce.linux.theplanet.co.uk>; from willy@debian.org on Tue, Aug 28, 2001 at 06:10:37AM +0100
> > And applied glibc_2.2.4-1.diff from same directory.
>
> 2.2.4-1 doesn't build. I haven't investigated in any detail, but it gets
> further than your build error indicates. Use dpkg-buildpackage to build
> it... and you need to uncomment the hppa-specific patch in 0list... and
> you need to edit the patch anyway to get it to apply...
>
> I have no enthusiasm for working on glibc. Please, someone, take it
> off my hands.
>
> --
> Revolutions do not require corporate support.
>
I have also tried building 2.2.4 without the diff, but with no success.
What would be the responsibilities of said maintianer?
The small fact that "uncomment the hppa-specific patch in 0list" means
little to nothing to me ;) ... is probably an indication that I'm not
experienced enough to take on glibc.
Seeing as you are the current glibc maintainer, my question would be:
What type of process do you follow for maintaining glibc?
a) Kick machine until glibc works.
b) Throw machines out window until glibc works.
c) Wait. Glibc will fix itself.
d) Who nees glibc? PARISC ASM!
e) Stay up many hours extracting those pesky pieces that don't work with HPPA.
Thanks for all the invaluable help Matthew! :}
I promise to try and stop doing crazy things like building the toolchain
by hand ;)
Cheers,
Carlos
next prev parent reply other threads:[~2001-08-28 11:17 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. [this message]
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.
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=20010828071743.A1289@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