[arch-dev-public] Current [core] repo packages build failures
Hi, I am doing a local rebuild of all [core] packages to test if there are any issues with the upcoming glibc-2.16 before it gets released. As a baseline, I built the [core] repo using the current glibc. All failures are from the latest package in [testing]/[core] with building with testing-x86_64 FAIL: automake Various testsuite failures - I think related to warning output with perl-5.16 FAIL: b43-fwcutter curl: (6) Could not resolve host: bu3sch.de; No address associated with hostname FAIL: heirloom-mailx make: /bin/install: Command not found FAIL: libarchive 107: test_read_format_mtree FAIL FAIL: libmpc autoreconf: automake failed with exit status: 1 FAIL: licenses w3c.html ... FAILED FAIL: syslinux /usr/include/linux/ext2_fs.h:178:41: error: unknown type name 'umode_t' FAIL: vi make: /bin/install: Command not found Allan
Le 2012-06-01 05:56, Allan McRae a écrit :
FAIL: heirloom-mailx make: /bin/install: Command not found
Fixed in trunk. Stéphane
On Fri, Jun 1, 2012 at 6:50 AM, Stéphane Gaudreault <stephane@archlinux.org> wrote:
Le 2012-06-01 05:56, Allan McRae a écrit :
FAIL: heirloom-mailx make: /bin/install: Command not found
Fixed in trunk.
You might want to run archrelease to get these fix picked up by ABS, especially if they don't modify the package content like in this case. At least, that's what I did for vi.
Stéphane
Le 2012-06-01 14:44, Eric Bélanger a écrit :
On Fri, Jun 1, 2012 at 6:50 AM, Stéphane Gaudreault <stephane@archlinux.org> wrote:
Le 2012-06-01 05:56, Allan McRae a écrit :
FAIL: heirloom-mailx make: /bin/install: Command not found Fixed in trunk. You might want to run archrelease to get these fix picked up by ABS, especially if they don't modify the package content like in this case. At least, that's what I did for vi.
Done, thanks for the tip. Stéphane
On Fri, Jun 1, 2012 at 5:56 AM, Allan McRae <allan@archlinux.org> wrote:
Hi,
I am doing a local rebuild of all [core] packages to test if there are any issues with the upcoming glibc-2.16 before it gets released. As a baseline, I built the [core] repo using the current glibc. All failures are from the latest package in [testing]/[core] with building with testing-x86_64
FAIL: vi make: /bin/install: Command not found
fixed
Allan
Am 01.06.2012 11:56, schrieb Allan McRae:
I am doing a local rebuild of all [core] packages to test if there are any issues with the upcoming glibc-2.16 before it gets released. As a baseline, I built the [core] repo using the current glibc. All failures are from the latest package in [testing]/[core] with building with testing-x86_64
FAIL: syslinux /usr/include/linux/ext2_fs.h:178:41: error: unknown type name 'umode_t'
Sounds weird. I'll look into it.
On 04/06/12 18:15, Thomas Bächler wrote:
Am 01.06.2012 11:56, schrieb Allan McRae:
I am doing a local rebuild of all [core] packages to test if there are any issues with the upcoming glibc-2.16 before it gets released. As a baseline, I built the [core] repo using the current glibc. All failures are from the latest package in [testing]/[core] with building with testing-x86_64
FAIL: syslinux /usr/include/linux/ext2_fs.h:178:41: error: unknown type name 'umode_t'
Sounds weird. I'll look into it.
Don't look to hard. It is due to the header being broken. I reported it to the kernel bugtracker but the response was basically do not use that header... The syslinux dev knows about it. Allan
Am 04.06.2012 10:24, schrieb Allan McRae:
FAIL: syslinux /usr/include/linux/ext2_fs.h:178:41: error: unknown type name 'umode_t'
Sounds weird. I'll look into it.
Don't look to hard. It is due to the header being broken. I reported it to the kernel bugtracker but the response was basically do not use that header... The syslinux dev knows about it.
Allan
There's also https://bugs.archlinux.org/task/30084.
participants (4)
-
Allan McRae
-
Eric Bélanger
-
Stéphane Gaudreault
-
Thomas Bächler