Bug#993380: lxc FTCBFS: compilation error in non-default code path

2023-08-18 Thread Mathias Gibbens
Looking at http://crossqa.debian.net/src/lxc, it appears that this was fixed in version 4.0.11. Helmut, can you confirm? If so, let's close this bug. Mathias signature.asc Description: This is a digitally signed message part

Bug#993380: [pkg-lxc-devel] Bug#993380: lxc FTCBFS: compilation error in non-default code path

2021-09-02 Thread Helmut Grohne
Control: tags -1 + upstream Control: forwarded -1 https://github.com/lxc/lxc/issues/3961 On Thu, Sep 02, 2021 at 12:21:08AM +0200, Pierre-Elliott Bécue wrote: > Would you like me to forward the bug to their github issue tracker? If > you prefer I'm eager to do it. But to be honest, as you did the

Bug#993380: [pkg-lxc-devel] Bug#993380: lxc FTCBFS: compilation error in non-default code path

2021-09-01 Thread Pierre-Elliott Bécue
Helmut Grohne writes: > Source: lxc > Version: 1:4.0.10-1 > User: debian-cr...@lists.debian.org > Usertags: ftcbfs > > lxc used to cross build successfully, but no longer does. A build > includes the following snippet: > > | libtool: compile: powerpc64le-linux-gnu-gcc -DHAVE_CONFIG_H -I. >

Bug#993380: lxc FTCBFS: compilation error in non-default code path

2021-08-31 Thread Helmut Grohne
Source: lxc Version: 1:4.0.10-1 User: debian-cr...@lists.debian.org Usertags: ftcbfs lxc used to cross build successfully, but no longer does. A build includes the following snippet: | libtool: compile: powerpc64le-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../../src -Wdate-time -D_FORTIFY_SOURCE=2