From: "Yocto" <yocto@optimcloud.com>
To: yocto@lists.yoctoproject.org
Subject: Re: [yocto] poky dhcpcd failed build
Date: Tue, 8 Sep 2020 21:16:00 +0700 [thread overview]
Message-ID: <d8bdfc43-e204-3eab-4582-af06b2309e2c@optimcloud.com> (raw)
In-Reply-To: <CAM9ZRVsrMHicRmLPBeGefSS=WZgVEp+-joU95sZ_=WwJaf9zzg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4382 bytes --]
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
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
>
>
[-- Attachment #2: Type: text/html, Size: 5507 bytes --]
next prev parent reply other threads:[~2020-09-08 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 6:24 poky dhcpcd failed build Yocto
2020-09-08 12:57 ` [yocto] " Paul Barker
2020-09-08 14:16 ` Yocto [this message]
2020-09-08 14:41 ` Paul Barker
2020-09-08 14:45 ` Yocto
2020-09-09 4:17 ` akuster
[not found] <1632BAF241A18982.9948@lists.yoctoproject.org>
2020-09-08 6:27 ` Yocto
2020-09-09 23:58 ` Khem Raj
2020-09-10 3:19 ` Yocto
[not found] ` <16334DF9E2497D60.23670@lists.yoctoproject.org>
2020-09-13 2:02 ` Yocto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d8bdfc43-e204-3eab-4582-af06b2309e2c@optimcloud.com \
--to=yocto@optimcloud.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.