You are not logged in.
Hope this is right place to ask. I am trying to build current systemd package in a clean environment (using clean-chroot-manager) and the build is failing, with the following compilation errors:
In file included from src/shared/firewall-util.c:24:0:
/usr/include/linux/if.h:71:2: error: redeclaration of enumerator 'IFF_UP'
IFF_UP = 1<<0, /* sysfs */
^
/usr/include/net/if.h:44:5: note: previous definition of 'IFF_UP' was here
IFF_UP = 0x1, /* Interface is up. */
^~~~~~
/usr/include/linux/if.h:72:2: error: redeclaration of enumerator 'IFF_BROADCAST'
IFF_BROADCAST = 1<<1, /* __volatile__ */
^
/usr/include/net/if.h:46:5: note: previous definition of 'IFF_BROADCAST' was here
IFF_BROADCAST = 0x2, /* Broadcast address valid. */
^~~~~~~~~~~~~
/usr/include/linux/if.h:73:2: error: redeclaration of enumerator 'IFF_DEBUG'
IFF_DEBUG = 1<<2, /* sysfs */
. . . etc . . .
Conflicting files /usr/include/linux/if.h and /usr/include/net/if.h came from the following packages:
$ sudo arch-chroot /scratch/chroot64/maker bash
[root@gdansk /]# pacman -Qo /usr/include/linux/if.h
/usr/include/linux/if.h is owned by linux-api-headers 4.5.2-1
[root@gdansk /]# pacman -Qo /usr/include/net/if.h
/usr/include/net/if.h is owned by glibc 2.23-4
Anyone else experiencing this problem? Last time I tried this on 6th May (I regularly rebuild small selection of packages), with no issues.
Offline
Not a pacman issue, moving to Creating and Modifying Packages.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Fails for me as well in a clean chroot. Dunno if the bbs is the right place for this... perhaps a flyspray?
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
There was a bug in linux headers, fixed here. This was merged to 4.5.5 (and 4.4.11 and few others too, I suppose)
Offline
There was a bug in linux headers, fixed here. This was merged to 4.5.5 (and 4.4.11 and few others too, I suppose)
I don't believe that linux-headers is a requirement to build systemd.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Somehow systemd build included both glibc and linux headers, error message is pretty clear about this. So there must be a dependency somewhere, either direct or indirect.
Offline
Try enabling [testing] which contains linux-4.6.0 and building... errors out.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Just checked this again - there is linux-api-headers and there is linux-headers. The former is userland headers, it is a dependency of glibc and is included in base-devel. That's where the breakage comes from. I am surprised there's been so little impact from this. Anyway if someone would kindly upgrade linux-api-headers (and, I suppose kernel as well) package to 4.5.5 , the breakage would be fixed.
I am not sure how to override clean-chroot-manager package selection, probably just need to make it "unclean" and manually edit /etc/pacman.conf in the chroot ?
Last edited by Bronek (2016-05-19 19:51:56)
Offline
@Bronek - You can enable [testing] and try building as I did...
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
@graysky - I did that, but apparently linux-api-headers package in testing is still at 4.5.2-1 , so no change there.
EDIT: there is no linux-api-headers in testing at all.
EDIT2: I "fixed" this for my own package build, by adding to maker's /etc/pacman.conf
[chroot_local]
SigLevel = Never
Server = file:///repo
... and then installing linux-api-headers 4.4.11 package which I have built myself (in the same clean chroot). After this I need to be careful to avoid using "sudo ccm s" and use "sudo ccm S" (capital letter) instead, as not to replace linux-api-headers 4.4.11 with official version 4.5.2
Last edited by Bronek (2016-05-19 20:22:03)
Offline
FWIW, systemd-230 has a workaround for this error.
Offline