[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 2.2.8 testsuite failures on mac os x 10.6.3 with gcc-4.5
From: |
Ralf Wildenhues |
Subject: |
Re: 2.2.8 testsuite failures on mac os x 10.6.3 with gcc-4.5 |
Date: |
Mon, 7 Jun 2010 21:16:23 +0200 |
User-agent: |
Mutt/1.5.20 (2009-10-28) |
* Peter O'Gorman wrote on Mon, Jun 07, 2010 at 12:17:13AM CEST:
> On 06/06/2010 04:05 AM, Ralf Wildenhues wrote:
> >>
> >>Do we really want to test this with no object files?
>
> >I think the workaround we used at the time for compilers like this was
> >to empty whole_archive_flag_spec, although cheaper workaround could in
> >principle be used (add dummy object, extract only the first convenience
> >archive). It bothers me to see that GCC reintroduces this bug, however.
>
> Ugh, well, I am not going to remove the -force_load support from
> libtool, it's the best way to get debugging working with convenience
> archives. I'll look at adding a dummy object if there is no other
> object on the link line (but I don't think it's urgent for an OS
> that does not ship with an affected compiler).
Does passing /dev/null as object work?
Otherwise, we can also just ignore the failure for now.
> On another topic - do we care about test failures that only happen
> with SElinux in enforcing mode (at least tests/demo-exec.test fails
> on Fedora 13)?
What's the nature of the failure? In general, we care about letting our
testsuite skip for cases it cannot reasonably pass, but only in those
cases. Can we detect it reliably?
Cheers,
Ralf
Re: 2.2.8 testsuite failures on mac os x 10.6.3 with gcc-4.5, Gary V. Vaughan, 2010/06/06