Re: poky dhcpcd failed build


 

On Tue, 8 Sep 2020 at 15:17, Yocto <yocto@optimcloud.com> wrote:


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

On Tue, 8 Sep 2020 at 07:26, Yocto <yocto@optimcloud.com> 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.


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,

--
Paul Barker
Konsulko Group

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