From: "Carlos O'Donell Jr." <carlos@megatonmonkey.net>
To: parisc-linux@parisc-linux.org
Cc: baldric-exec@baldric.uwo.ca
Subject: [parisc-linux] Glibc2.2.4-1
Date: Fri, 14 Sep 2001 11:23:53 -0400 [thread overview]
Message-ID: <20010914112352.A1491@megatonmonkey.net> (raw)
M,
Just a quick update. I've been recently inundated with the start of
school and phazing life back into a fast flowing stream is never easy ;)
Recent progression:
I finally built the full toolchain.
- Latest Binutils
- Latest GCC
- Latest Glibc 2.2.4-1
Carried out all the 0list patches by hand, in order.
x glibc-vs-gcc3
x db1-addon-enabler
x manual-texinfo4
x ldd
x glibcbug
x hurd-ldflags
x fhs-linux-paths
x pthread_create-manpage
x string2-pointer-arith
x glibc22-nss-upgrade
x glibc22-getaddrinfo
- glibc22-hppa
./sysdeps/ia64/dl-fptr.c.rej
x glibc22-eo_EO
x glibc22-m68k-compat
x glibc22-m68k-fpic
x glibc22-locales
x sparc64-fixups
x glibc22-fts
x glibc22-getdents-fix
It looks like ./sysdeps/ia64/dl-fptr.c is completely different!
I get 7 hunks failed on that file. All the reentrant ifdef's are
gone, and the structure of the file is totally different.
I've ignored those patch failures since there was no visible way
to merge them.
I also installed linuxthreads and the db1 addon.
Which mandated some minor changes to a few header includes for db1 :}
I've compiled 2.4.9-pa16 with the toolchain, and for the first time
ever... I saw a small framebuffer penguin... and it almost brought
me to tears ;)
I have 712/60's and 715/50's running the newer kernel. All of them
are doing much better, and running far faster than ever before.
-----------------------------------------------------
On to testing and building the deb for glibc 2.2.4-1
-----------------------------------------------------
I tried to apt-get -f dist-upgrade
Which again failed on "trying to install a non-directory"
(No segfaults this time around)
For future referance, you can fix this by creating a dummy directory
with the name of the directory that you are failing with.
I've fully apt-get'd my 712/60 from the baseplus tarball with
no apparent problems.
Though lately ksoftirqd seems to eat ~99% of my CPU on idle.
---
Anything I should watch for when building the deb for glibc 2.2.4-1?
It may take quite a while on my 712/60.
I'll get back you when I've finished and tested.
Cheers,
Carlos.
next reply other threads:[~2001-09-14 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-14 15:23 Carlos O'Donell Jr. [this message]
2001-09-14 16:35 ` [parisc-linux] Glibc2.2.4-1 Matthew Wilcox
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=20010914112352.A1491@megatonmonkey.net \
--to=carlos@megatonmonkey.net \
--cc=baldric-exec@baldric.uwo.ca \
--cc=parisc-linux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.