Re: poky dhcpcd failed build


Yocto
 


On 9/8/20 9:41 PM, Paul Barker wrote:
On Tue, 8 Sep 2020 at 15:17, Yocto <yocto@...> wrote:

On 9/8/20 7:57 PM, Paul Barker wrote:

On Tue, 8 Sep 2020 at 07:26, Yocto <yocto@...> wrote:

w
| collect2: error: ld returned 1 exit status
| make[1]: *** [Makefile:73: dhcpcd] Error 1
| make[1]: Leaving directory
'/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/dhcpcd/9.1.4-r0/dhcpcd-9.1.4/src'
| make: *** [Makefile:24: all] Error 2
| WARNING:
/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/dhcpcd/9.1.4-r0/temp/run.do_compile.3649983:190
exit 1 from 'exit 1'
| WARNING: Backtrace (BB generated script):
|     #1: bbfatal_log,
/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/dhcpcd/9.1.4-r0/temp/run.do_compile.3649983,
line 190
|     #2: die,
/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/dhcpcd/9.1.4-r0/temp/run.do_compile.3649983,
line 165
|     #3: oe_runmake,
/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/dhcpcd/9.1.4-r0/temp/run.do_compile.3649983,
line 160
|     #4: autotools_do_compile,
/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/dhcpcd/9.1.4-r0/temp/run.do_compile.3649983,
line 155
|     #5: do_compile,
/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/dhcpcd/9.1.4-r0/temp/run.do_compile.3649983,
line 150
|     #6: main,
/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/dhcpcd/9.1.4-r0/temp/run.do_compile.3649983,
line 194
|
| Backtrace (metadata-relative locations):
|     #1: bbfatal_log,
/var/home/dingo/overc/poky/meta/classes/logging.bbclass, line 72
|     #2: die, /var/home/dingo/overc/poky/meta/classes/base.bbclass, line 56
|     #3: oe_runmake,
/var/home/dingo/overc/poky/meta/classes/base.bbclass, line 65
|     #4: autotools_do_compile,
/var/home/dingo/overc/poky/meta/classes/autotools.bbclass, line 243
|     #5: do_compile, autogenerated, line 2
ERROR: Task
(/var/home/dingo/overc/poky/meta/recipes-connectivity/dhcpcd/dhcpcd_9.1.4.bb:do_compile)
failed with exit code '1'

Sorry to be blunt, but this email is meaningless. Please give some
context and use a name other than "Yocto". You're not likely to get
any helpful replies from an email like this.

for context, seems that the latest git commit for dhcpcd doesnt even build.

gcc/x86_64-overc-linux/10.2.0/ld: privsep-root.o: in function `ps_root_dogetifaddrs':
| /usr/src/debug/dhcpcd/9.1.4-r0/dhcpcd-9.1.4/src/privsep-root.c:374: undefined reference to `ALIGN'
| /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/dhcpcd/9.1.4-r0/recipe-sysroot-native/usr/bin/x86_64-overc-linux/../../libexec/x86_64-overc-linux/gcc/x86_64-overc-linux/10.2.0/ld: /usr/src/debug/dhcpcd/9.1.4-r0/dhcpcd-9.1.4/src/privsep-root.c:375: undefined reference to `ALIGN'
| /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/dhcpcd/9.1.4-r0/recipe-sysroot-native/usr/bin/x86_64-overc-linux/../../libexec/x86_64-overc-linux/gcc/x86_64-overc-linux/10.2.0/ld: /usr/src/debug/dhcpcd/9.1.4-r0/dhcpcd-9.1.4/src/privsep-root.c:376: undefined reference to `ALIGN'
| /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/dhcpcd/9.1.4-r0/recipe-sysroot-native/usr/bin/x86_64-overc-linux/../../libexec/x86_64-overc-linux/gcc/x86_64-overc-linux/10.2.0/ld: /usr/src/debug/dhcpcd/9.1.4-r0/dhcpcd-9.1.4/src/privsep-root.c:378: undefined reference to `ALIGN'
| /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/dhcpcd/9.1.4-r0/recipe-sysroot-native/usr/bin/x86_64-overc-linux/../../libexec/x86_64-overc-linux/gcc/x86_64-overc-linux/10.2.0/ld: /usr/src/debug/dhcpcd/9.1.4-r0/dhcpcd-9.1.4/src/privsep-root.c:380: undefined reference to `ALIGN'
| /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/dhcpcd/9.1.4-r0/recipe-sysroot-native/usr/bin/x86_64-overc-linux/../../libexec/x86_64-overc-linux/gcc/x86_64-overc-linux/10.2.0/ld: privsep-root.o:/usr/src/debug/dhcpcd/9.1.4-r0/dhcpcd-9.1.4/src/privsep-root.c:382: more undefined references to `ALIGN' follow
| collect2: error: ld returned 1 exit status
What command did you run? What's your host distro, layers and
branches/version, local.conf contents, etc? You need to give enough
info for your issue to be understood.


❯ bitbake cube-essential cube-dom0 cube-vrf cube-builder-initramfs cube-builder cube-desktop cube-server cube-k8s-node
WARNING: Host distribution "fedora-32" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
Loading cache: 100% |##########################################################################################################################################################################################################################################################################################| Time: 0:00:00
Loaded 6981 entries from dependency cache.
Parsing recipes: 100% |########################################################################################################################################################################################################################################################################################| Time: 0:00:03
Parsing of 2845 .bb files complete (2843 cached, 2 parsed). 6983 targets, 211 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION           = "1.47.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "fedora-32"
TARGET_SYS           = "x86_64-overc-linux"
MACHINE              = "intel-corei7-64"
DISTRO               = "overc"
DISTRO_VERSION       = "1.0"
TUNE_FEATURES        = "m64 corei7"
TARGET_FPU           = ""
meta                
meta-poky           
meta-yocto-bsp       = "master:c25309ecde4e7ff81fb74a74fe06991dcdbbbfc8"
meta-oe             
meta-python         
meta-networking     
meta-filesystems    
meta-multimedia     
meta-perl            = "master:b6ab91b594f10e74f86b69af956a4a3dc95570f4"
meta-overc          
meta-cube            = "master:264d1d0949fb5e9ec8e39b1f7604086d59ec2047"
meta-intel           = "master:58ce85f09cf28636a809891b254754c041c987b4"
meta-virtualization  = "master:2711b81afd489d5b458617dfdfda520d8fe61f65"
meta-cloud-services  = "master:c58fd2bea4d6ccd98d9f29bd7dcff96d7d99594d"
meta-security        = "master:fa9f747360960f6af7454d534e45263bcc15c015"
meta-selinux         = "master:15fed8756aa4828fa12a3d813754b4ca65a7607d"
meta-gnome          
meta-xfce            = "master:b6ab91b594f10e74f86b69af956a4a3dc95570f4"
meta-awnix           = "master:d9de1ff6bec994a23333fe3989329b684f22f3da"

#
# OverC updates
#

# set the machine
MACHINE = "intel-corei7-64"
#KMACHINE_genericx86-64 = "common-pc-64"
KMACHINE_corei7-64-intel-common = "intel-corei7-64"


# disto: replace the poky distro with:
DISTRO = "overc"

# IMPORTANT: remove 'image-mklibs image-prelink' from the default
#            user classes. They break lxc-autostart.
USER_CLASSES ?= "buildstats"
INSANE_SKIP_zerotier = " already-stripped"
IMAGE_FSTYPES_append = " tar.bz2"
NOISO = "1"
PACKAGE_CLASSES ?= "package_rpm"
EXTRA_IMAGE_FEATURES += " package-management "
IMAGE_INSTALL_append = " libvirt libvirt-libvirtd libvirt-virsh git htop python3-pip wireguard-tools libgomp libgomp-dev libgomp-staticdev glibc-gconvs glibc-utils nodejs nodejs-npm"
ENABLE_BINARY_LOCALE_GENERATION = "1"
CORE_IMAGE_EXTRA_INSTALL += " packagegroup-base-extended"
PACKAGE_FEED_URIS = "http://cube-repo/repo"
PACKAGE_FEED_BASE_PATHS = "rpm"
PACKAGE_FEED_ARCHS = "core2_64 genericx86_64 x86 noarch"

IMAGE_FSTYPES_remove = "hddimg wic wic.bmap"
OVERC_ESSENTIAL_MODE = "read-write"
PREFERRED_PROVIDER_virtual/kernel = "linux-yocto"



meaning dont use the name yocto@domain ?? it was just configured so all lists reguarding yocto went to a different email then personal... maybe it should be named something other then yocto... okay... but now unsub-resu to X lists... ughhhhhh

The email address is fine, just set a name other than "Yocto" in your
mail client. Using "Yocto" may confuse unfamiliar folks into thinking
you speak on behalf of the project. It also gets confusing when
multiple people set their name to "Yocto" when using these lists.

Thanks,



    

Join yocto@lists.yoctoproject.org to automatically receive all group messages.