From: "Joel Soete" <soete.joel@tiscali.be>
To: "Carlos O'Donell" <carlos@baldric.uwo.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] RE: New glibc patches 2004-03-08, fixes GLRO changes.
Date: Wed, 10 Mar 2004 15:47:09 +0100 [thread overview]
Message-ID: <404EC1C600000B2D@ocpmta1.freegates.net> (raw)
In-Reply-To: <20040309150318.GD22721@baldric.uwo.ca>
Hi Carlos,
Here are the news:
(first of all sorry for delay but I have temporarely have to exchange my
N4k for a b180 so it take a bit more time)
The glibc cvs 2.3.3 cvs dated 20040308 + your patch compiles well (just this
time I enable profiling) :).
I also install it on /mnt/chroot (according James method, just to test).
As I foreseen to use this disk to other test on the N4k, I grab the list
of packages installed (dpkg --get-selection > /mnt/chroot/var/tmp/Selection.doc)
and chroot to /mnt/chroot to install previously mentioned pkg list. All works
fine (just 3 pkg failled to install because no /proc available in chroot).
In the same time I drive a make -k check and just get additional Errors:
[...]
make[2]: *** [/Develop/parisc-linux/build/glibc/libio/tst-mmap-eofsync.out]
Error 1
make[2]: *** [/Develop/parisc-linux/build/glibc/libio/tst-mmap-fflushsync.out]
Error 1
make[1]: *** [libio/tests] Error 2
make[2]: [/Develop/parisc-linux/build/glibc/posix/annexc.out] Error 1 (ignored)
make[2]: *** [/Develop/parisc-linux/build/glibc/elf/multiload.o] Error 1
make[2]: *** [/Develop/parisc-linux/build/glibc/elf/origtest.o] Error 1
[...]
I have two hypothesis:
a. it is the first time I added enable-profile;
b. I forget to build first gcc(3.3) tool with your gcc patch (gcc/config/pa/fptr.c)
Now, 2.6.4-rc3-pa0 is just available, I will so try first to build it in
the chroot disk...
hth,
Joel
----------------------------------------------------------------------------------------
Tiscali ADSL: 19,50 /mois, pendant 3 mois! L'Internet rapide, c'est pour
tout le monde.
http://reg.tiscali.be/default.asp?lg=fr
next prev parent reply other threads:[~2004-03-10 14:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 13:05 [parisc-linux] glibc cvs: additional patche Joel Soete
2004-03-07 21:23 ` [parisc-linux] " Carlos O'Donell
2004-03-08 7:27 ` Joel Soete
2004-03-08 17:49 ` [parisc-linux] New glibc patches 2004-03-08, fixes GLRO changes Carlos O'Donell
2004-03-09 9:04 ` [parisc-linux] " Joel Soete
2004-03-09 13:49 ` Joel Soete
2004-03-09 15:03 ` Carlos O'Donell
2004-03-09 15:41 ` Joel Soete
2004-03-10 14:47 ` Joel Soete [this message]
2004-03-10 18:21 ` Joel Soete
2004-03-11 18:42 ` Carlos O'Donell
2004-03-12 15:32 ` Joel Soete
2004-03-12 16:41 ` Carlos O'Donell
2004-03-12 17:33 ` Joel Soete
2004-03-12 21:20 ` Carlos O'Donell
2004-03-13 18:59 ` Joel Soete
2004-03-14 19:32 ` Carlos O'Donell
2004-03-14 19:40 ` Carlos O'Donell
2004-03-14 19:59 ` Joel Soete
2004-03-14 20:12 ` James Morrison
2004-03-15 6:31 ` Joel Soete
2004-03-16 14:57 ` James Morrison
2004-03-15 17:38 ` Joel Soete
2004-03-15 18:51 ` Carlos O'Donell
2004-03-16 9:43 ` Joel Soete
2004-03-16 21:09 ` Carlos O'Donell
2004-03-17 8:30 ` Joel Soete
2004-03-18 17:59 ` Carlos O'Donell
2004-03-23 7:07 ` Joel Soete
2004-03-23 17:06 ` Carlos O'Donell
2004-04-01 15:14 ` Joel Soete
2004-04-02 5:51 ` Carlos O'Donell
2004-03-09 15:07 ` James Morrison
2004-03-09 15:09 ` Carlos O'Donell
2004-03-09 15:39 ` James Morrison
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=404EC1C600000B2D@ocpmta1.freegates.net \
--to=soete.joel@tiscali.be \
--cc=carlos@baldric.uwo.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