Daniel P. Berrange wrote:
> Tested-by: Daniel P. Berrange
>
>
> Confirmed it fixes the failure on Fedora 28, and does not cause a regression
> on Fedora 26 with older glibc.
Thanks. Pushing it:
2017-10-09 Bruno Haible
getopt-posix: Fix build failure when using ac_cv_header_getopt_
On Fri, Oct 06, 2017 at 07:59:13PM +0200, Bruno Haible wrote:
> Daniel P. Berrange wrote:
> > From my own F28 rawhide install with glibc-2.26.90-16.fc28.x86_64
> >
> > >
> > > 1) The output of
> > > $ nm test-getopt-posix | grep getopt
> >
> > $ nm test-getopt-posix | grep getopt
> >
Daniel P. Berrange wrote:
> From my own F28 rawhide install with glibc-2.26.90-16.fc28.x86_64
>
> >
> > 1) The output of
> > $ nm test-getopt-posix | grep getopt
>
> $ nm test-getopt-posix | grep getopt
> U getopt@@GLIBC_2.2.5
> 00400ab0 t getopt_loop.constprop.0
Hi,
Christian Ehrhardt wrote:
> > Fedora 26 only has glibc 2.25 - you need to have Fedora rawhide to get
> > the broken behaviour, as that has glibc 2.26.90
> As Daniel said at least glibc 2.26 as in Fedora rawhide or Ubuntu Artful.
This tip is not helpful: I spent two hours trying Fedora Rawhide
On 09/29/2017 05:02 AM, Christian Ehrhardt wrote:
Here [1] a log of your commands on such a system showing the issue.
Thanks, but I still don't understand what the bug is. With those
commands, the test programs use Gnulib-supplied getopt, not the glibc
getopt. So why would any change in glibc
On Fri, Sep 29, 2017 at 10:45 AM, Daniel P. Berrange
wrote:
> On Thu, Sep 28, 2017 at 04:41:37PM -0700, Paul Eggert wrote:
> > That patch essentially negates the point of the test, which is that
> getopt
> > should be visible from unistd.h. I'd rather fix the problem than nuke the
> > test.
> >
>
On Thu, Sep 28, 2017 at 04:41:37PM -0700, Paul Eggert wrote:
> That patch essentially negates the point of the test, which is that getopt
> should be visible from unistd.h. I'd rather fix the problem than nuke the
> test.
>
> Could you explain what the Gnulib problem is here? I can't really see it
That patch essentially negates the point of the test, which is that
getopt should be visible from unistd.h. I'd rather fix the problem than
nuke the test.
Could you explain what the Gnulib problem is here? I can't really see it
in your email. A self-contained example would help.
For what it'
On Thu, Sep 28, 2017 at 2:05 PM, Christian Ehrhardt <
christian.ehrha...@canonical.com> wrote:
>
>
> On Thu, Sep 28, 2017 at 12:25 AM, Eric Blake wrote:
>
>> [adding gnulib]
>>
>
> [...]
>
>>
> then libvirt needs to pick up the
>> updated gnulib.
>
>
> I copied in current gnulib from git and it
On Thu, Sep 28, 2017 at 12:25 AM, Eric Blake wrote:
> [adding gnulib]
>
> On 09/27/2017 04:36 PM, Christian Ehrhardt wrote:
> > Hi,
> > there seems to be an incompatibility to the last glibc due to [1].
>
> Gnulib needs to be updated to track the glibc changes (it looks like
> that is actually un
[adding gnulib]
On 09/27/2017 04:36 PM, Christian Ehrhardt wrote:
> Hi,
> there seems to be an incompatibility to the last glibc due to [1].
Gnulib needs to be updated to track the glibc changes (it looks like
that is actually under way already), then libvirt needs to pick up the
updated gnulib.
11 matches
Mail list logo