[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tinycc-devel] test failure on Linux
From: |
Thomas Preud'homme |
Subject: |
Re: [Tinycc-devel] test failure on Linux |
Date: |
Thu, 14 Feb 2013 23:22:27 +0100 |
User-agent: |
KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; ) |
Le jeudi 14 février 2013 20:21:30, Ramsay Jones a écrit :
> Thomas Preud'homme wrote:
> > Le mercredi 13 février 2013 19:08:37, Thomas Preud'homme a écrit :
> >> Le mercredi 13 février 2013 17:16:28, Thomas Preud'homme a écrit :
> >>> On Wed, 13 Feb 2013 08:30:14 -0700, address@hidden wrote:
> >>>> "Thomas Preud'homme" <address@hidden> wrote:
> >>>>> Why not but strike multiarch from that as I don't see how we could
> >>>>> detect it by compiling a C program.
> >>>>
> >>>> Use the output of ldd to tell you where the C library is.
> >>>
> >>> Yep true, I thought about it last night and forgot about it in the
> >>> morning. However I just pushed a commit using checking where is crti.o
> >>> before reading your mail. It's a one line test so I think the solution
> >>> is not too bad but you can prove me wrong of course.
> >>
> >> Thanks a lot for the suggestion. Thinking about it a bit I managed to
> >> come up with a much better patch. It's not totally done though but I
> >> have to leave. I'll push it tonight. Stay tuned.
> >
> > Pushed. And the diffstat from the original situation (before my 2 commits
> > to
>
> > reorganize) is also better. See for yourself:
> OK, despite what I said, I fetched commit e298f608 ("Create config-print
> program to test $cc", 13-02-2013) last night in order to test it.
> [Sorry for not reporting the results last night, but I desperately
> needed to get some sleep!]
Of course, no need to be sorry for that.
>
> Unfortunately, the news is not good! :( Using ldd has broken the build
> again and my x86 is apparently a bigendian machine! :-P
This should be fixed by grischka's commit:
944627c479f01d919f10f9d9dd807cca43bf7aba
Best regards,
Thomas
signature.asc
Description: This is a digitally signed message part.
- Re: [Tinycc-devel] test failure on Linux, (continued)
- Re: [Tinycc-devel] test failure on Linux, Thomas Preud'homme, 2013/02/13
- Re: [Tinycc-devel] test failure on Linux, Thomas Preud'homme, 2013/02/13
- Re: [Tinycc-devel] test failure on Linux, grischka, 2013/02/13
- Re: [Tinycc-devel] test failure on Linux, Thomas Preud'homme, 2013/02/13
- Re: [Tinycc-devel] test failure on Linux, arnold, 2013/02/13
- Re: [Tinycc-devel] test failure on Linux, Domingo Alvarez Duarte, 2013/02/13
- Re: [Tinycc-devel] test failure on Linux, Thomas Preud'homme, 2013/02/13
- Re: [Tinycc-devel] test failure on Linux, Thomas Preud'homme, 2013/02/13
- Re: [Tinycc-devel] test failure on Linux, Thomas Preud'homme, 2013/02/13
- Re: [Tinycc-devel] test failure on Linux, Ramsay Jones, 2013/02/14
- Re: [Tinycc-devel] test failure on Linux,
Thomas Preud'homme <=
- Re: [Tinycc-devel] test failure on Linux, Ramsay Jones, 2013/02/14
- Re: [Tinycc-devel] test failure on Linux, Ramsay Jones, 2013/02/13
- Re: [Tinycc-devel] test failure on Linux, Thomas Preud'homme, 2013/02/13
- Re: [Tinycc-devel] test failure on Linux, grischka, 2013/02/13
- Re: [Tinycc-devel] test failure on Linux, Christian Jullien, 2013/02/13
- Re: [Tinycc-devel] test failure on Linux, Thomas Preud'homme, 2013/02/13
- Re: [Tinycc-devel] test failure on Linux, Thomas Preud'homme, 2013/02/13
- Re: [Tinycc-devel] test failure on Linux, Thomas Preud'homme, 2013/02/13
- Re: [Tinycc-devel] test failure on Linux, grischka, 2013/02/13
- Re: [Tinycc-devel] test failure on Linux, Thomas Preud'homme, 2013/02/13