On Sat, 17 Dec 2011, Thorsten Glaser wrote:
Finn Thain dixit:
It might be worth running the tests on physical hardware instead of an
emulator.
You just volunteered.
You just promoted me to Debian Developer.
Finn
--
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
with
On Thu, Dec 15, 2011 at 12:47:10PM +, Thorsten Glaser wrote:
Just FYI, maybe you can do something with it (or not).
I built the latest eglibc 2.13-23 without nocheck.
I have just included it as the expected tests results. I have to say the
list of failure seems to say that m68k is not
On Sat, 17 Dec 2011, Aurelien Jarno wrote:
On Thu, Dec 15, 2011 at 12:47:10PM +, Thorsten Glaser wrote:
Just FYI, maybe you can do something with it (or not).
I built the latest eglibc 2.13-23 without nocheck.
I have just included it as the expected tests results. I have to say
Finn Thain dixit:
I have just included it as the expected tests results. I have to say the
list of failure seems to say that m68k is not really in a good state.
Mh. I’m just the builder.
It might be worth running the tests on physical hardware instead of an
emulator.
You just volunteered.
Just FYI, maybe you can do something with it (or not).
I built the latest eglibc 2.13-23 without nocheck.
make[1]: Leaving directory `/tmp/buildd/eglibc-2.13/build-tree/m68k-libc'
#
# Testsuite failures, someone should be working towards
# fixing these! They are listed here for the purpose of
#
On Thu, 15 Dec 2011, Thorsten Glaser wrote:
Just FYI, maybe you can do something with it (or not).
I built the latest eglibc 2.13-23 without nocheck.
It might be helpful to do the same with gcc 4.4.
Finn
make[1]: Leaving directory `/tmp/buildd/eglibc-2.13/build-tree/m68k-libc'
#
#
Finn Thain dixit:
It might be helpful to do the same with gcc 4.4.
That was with gcc 4.4 (which src:eglibc forces).
bye,
//mirabilos
--
“Having a smoking section in a restaurant is like having
a peeing section in a swimming pool.”
--
7 matches
Mail list logo
