On Thu, Mar 10, 2022 at 9:58 AM Jeremy Puhlman <jpuhl...@mvista.com> wrote:
>
> Adding -ldl should resolve it. It corrected the issue on ubuntu-18.04 +
> extended-buildtools and with out. Lemme check centos as well.
>

Thanks Jeremy
Since, I merged the patch. Please send and incremental fix.


>
> On 3/10/2022 9:04 AM, Khem Raj wrote:
> > sadly I am seeing this failure
> >
> > https://errors.yoctoproject.org/Errors/Details/651342/
> >
> > On Wed, Mar 9, 2022 at 12:31 PM Jeremy Puhlman <jpuhl...@mvista.com> wrote:
> >>
> >>
> >> On 3/9/2022 12:06 PM, Khem Raj wrote:
> >>> Thanks Jeremy
> >>>
> >>> I wonder why we don't see it failing on AB or in my local testing. is
> >>> it specific to some build host distro ?
> >> I am seeing the same issue reported on ubuntu 18.04, centos 7 and 8, but
> >> its only with the extended buildtools.
> >>
> >>> On Wed, Mar 9, 2022 at 11:41 AM Jeremy Puhlman <jpuhl...@mvista.com> 
> >>> wrote:
> >>>> From: Jeremy Puhlman <jpuhl...@mvista.com>
> >>>>
> >>>> gcc   abstract.o -Xlinker -L../../dist/lib -lplc4 -L../../dist/lib 
> >>>> -lnspr4 -lpthread -o abstract
> >>>> /build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/11.2.0/../../../../x86_64-pokysdk-linux/bin/ld:
> >>>>  /lib64/librt.so.1: undefined reference to `__libc_dlsym@GLIBC_PRIVATE'
> >>>> /build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/11.2.0/../../../../x86_64-pokysdk-linux/bin/ld:
> >>>>  /lib64/librt.so.1: undefined reference to 
> >>>> `__pthread_unwind@GLIBC_PRIVATE'
> >>>> /build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/11.2.0/../../../../x86_64-pokysdk-linux/bin/ld:
> >>>>  /lib64/librt.so.1: undefined reference to 
> >>>> `__libc_dlopen_mode@GLIBC_PRIVATE'
> >>>> /build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/11.2.0/../../../../x86_64-pokysdk-linux/bin/ld:
> >>>>  /lib64/librt.so.1: undefined reference to 
> >>>> `__clock_getcpuclockid@GLIBC_PRIVATE'
> >>>> /build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/11.2.0/../../../../x86_64-pokysdk-linux/bin/ld:
> >>>>  /lib64/librt.so.1: undefined reference to 
> >>>> `__clock_nanosleep@GLIBC_PRIVATE'
> >>>> /build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/11.2.0/../../../../x86_64-pokysdk-linux/bin/ld:
> >>>>  /lib64/librt.so.1: undefined reference to 
> >>>> `__clock_settime@GLIBC_PRIVATE'
> >>>> /build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/11.2.0/../../../../x86_64-pokysdk-linux/bin/ld:
> >>>>  /lib64/librt.so.1: undefined reference to `__clock_getres@GLIBC_PRIVATE'
> >>>>
> >>>> The linker is not correctly pulling in lrt as needed.
> >>>>
> >>>> Signed-off-by: Jeremy Puhlman <jpuhl...@mvista.com>
> >>>> ---
> >>>>    meta-oe/recipes-support/nspr/nspr_4.29.bb | 2 ++
> >>>>    1 file changed, 2 insertions(+)
> >>>>
> >>>> diff --git a/meta-oe/recipes-support/nspr/nspr_4.29.bb 
> >>>> b/meta-oe/recipes-support/nspr/nspr_4.29.bb
> >>>> index f224bcd34..2717f37bc 100644
> >>>> --- a/meta-oe/recipes-support/nspr/nspr_4.29.bb
> >>>> +++ b/meta-oe/recipes-support/nspr/nspr_4.29.bb
> >>>> @@ -160,6 +160,8 @@ PACKAGECONFIG[ipv6] = "--enable-ipv6,--disable-ipv6,"
> >>>>    # preferred path upstream.
> >>>>    EXTRA_OECONF += "--includedir=${includedir}/nspr"
> >>>>
> >>>> +EXTRA_OEMAKE:append:class-native = " EXTRA_LIBS='-lpthread -lrt'"
> >>>> +
> >>>>    do_compile:prepend() {
> >>>>           oe_runmake CROSS_COMPILE=1 CFLAGS="-DXP_UNIX ${BUILD_CFLAGS}" 
> >>>> LDFLAGS="" CC="${BUILD_CC}" -C config export
> >>>>    }
> >>>> --
> >>>> 2.31.1
> >>>>
> >>>>
> >>>> 
> >>>>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#95938): 
https://lists.openembedded.org/g/openembedded-devel/message/95938
Mute This Topic: https://lists.openembedded.org/mt/89670512/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to