Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: Kieran Bingham <kieran.bingham@ideasonboard.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-11-26
Date: Mon, 28 Nov 2022 19:57:50 +0100	[thread overview]
Message-ID: <20221128195750.196cfe66@gmx.net> (raw)
In-Reply-To: <20221128190024.5380be46@gmx.net>

Hello Kieran,

On Mon, 28 Nov 2022 19:00:49 +0100, Peter Seiderer <ps.report@gmx.net> wrote:

> Hello Kieran,
>
> On Mon, 28 Nov 2022 09:03:44 +0000, Kieran Bingham <kieran.bingham@ideasonboard.com> wrote:
>
> > Hi Thomas,
> >
> > + Buildroot list
> >
> > Quoting Thomas Petazzoni (2022-11-27 07:39:11)
> > > Hello,
> > >
> > > Autobuilder failures
> > > ====================
> > >
> > > Below is a list of build failures reported by the Buildroot autobuilders
> > > in relation to packages or CPU architectures you are in charge of.
> > > Please help us improving the quality of Buildroot by investigating those
> > > build failures and sending patches to fix them.
> > >
> > > Results for the '2022.02.x' branch
> > > ----------------------------------
> > >
> > > Build failures related to your packages:
> > >
> > >     arch     |             reason             |                                       url
> > > -------------+--------------------------------+---------------------------------------------------------------------------------
> > >   aarch64    | libcamera-1966b9a58436fab51... | http://autobuild.buildroot.net/results/5ea8f180e4909f8157565238b25f567fcf1f3beb
> >
> > Upon a quick examination I can see the following highlights in
> > build-end.log here:
> >
> > ...
> > Run-time dependency GTest found: YES 1.11.0
> > ...
> >     lc-compliance application: YES
> > ...
> >     lc-compliance            : enabled
> > ...
> > [117/121] Linking target src/lc-compliance/lc-compliance
> > FAILED: src/lc-compliance/lc-compliance
> > /home/buildroot/autobuild/run/instance-3/output-1/host/bin/aarch64-linux-gnu-g++  -o src/lc-compliance/lc-compliance src/lc-compliance/lc-compliance.p/.._cam_event_loop.cpp.o src/lc-compliance/lc-compliance.p/.._cam_options.cpp.o src/lc-compliance/lc-compliance.p/environment.cpp.o src/lc-compliance/lc-compliance.p/main.cpp.o src/lc-compliance/lc-compliance.p/simple_capture.cpp.o src/lc-compliance/lc-compliance.p/capture_test.cpp.o -Wl,--as-needed -Wl,--no-undefined -Wl,--start-group -lstdc++fs -Wshadow -include config.h '-Wl,-rpath,$ORIGIN/../libcamera:$ORIGIN/../libcamera/base:/home/buildroot/autobuild/run/instance-3/output-1/host/aarch64-buildroot-linux-gnu/sysroot/usr/lib/../lib64' -Wl,-rpath-link,/home/buildroot/autobuild/run/instance-3/output-1/build/libcamera-1966b9a58436fab51f8270aad6a228b935e4fac4/build/src/libcamera -Wl,-rpath-link,/home/buildroot/autobuild/run/instance-3/output-1/build/libcamera-1966b9a58436fab51f8270aad6a228b935e4fac4/build/src/libcamera/base -Wl,-rpat
 h-
>  li
> >  nk,/home/buildroot/autobuild/run/instance-3/output-1/host/aarch64-buildroot-linux-gnu/sysroot/usr/lib/../lib64 src/libcamera/libcamera.so.0.0.0 src/libcamera/base/libcamera-base.so.0.0.0 -latomic /home/buildroot/autobuild/run/instance-3/output-1/host/aarch64-buildroot-linux-gnu/sysroot/usr/lib/libevent_pthreads.so /home/buildroot/autobuild/run/instance-3/output-1/host/aarch64-buildroot-linux-gnu/sysroot/usr/lib/libevent.so -lpthread -L/home/buildroot/autobuild/run/instance-3/output-1/host/aarch64-buildroot-linux-gnu/sysroot/usr/lib -lgtestd -Wl,--end-group
> > /home/buildroot/autobuild/run/instance-3/output-1/host/opt/ext-toolchain/bin/../lib/gcc/aarch64-linux-gnu/7.3.1/../../../../aarch64-linux-gnu/bin/ld: cannot find -lgtestd
> > collect2: error: ld returned 1 exit status
> >
> > I don't think we've changed anything (on the libcamera side) regarding
> > gtest/lc-compliance in quite some time ... so I'm surprised to see this
> > error pop up?
>
> The following patch/hack fixes the problem here:
>
> 	$ diff -u ./host/aarch64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/gtest.pc_orig ./host/aarch64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/gtest.pc
> --- ./host/aarch64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/gtest.pc_orig	2022-11-28 18:44:57.547871537 +0100
> +++ ./host/aarch64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/gtest.pc	2022-11-28 18:45:06.676052468 +0100
> @@ -5,5 +5,5 @@
>  Description: GoogleTest (without main() function)
>  Version: 1.11.0
>  URL: https://github.com/google/googletest
> -Libs: -L${libdir} -lgtestd -lpthread
> +Libs: -L${libdir} -lgtest -lpthread
>  Cflags: -I${includedir} -DGTEST_HAS_PTHREAD=1
>
>
> More of an gtest package problem than a libcamera one, mind the
> libgtestd vs. libgtest, the other way round was fixed by 'package/gtest:
> fix gtest.pc/gmock.pc library names for the debug build' ([1]), seems
> something changed since the introduction of the patch (or the conditional
> introduced by the patch is wrong)....

Seems package/gtest/0001-pkg-config-fix-gtest.pc-gmock.pc-library-names-for-t.patch
is no longer needed since the bump of gtest to 1.22 ([2], see gtest commit [3])...

Regards,
Peter


[2] https://git.buildroot.net/buildroot/commit/?h=2022.02.x&id=c59eee8118a2da55002ae16e416e3700ce4c60f4
[3] https://github.com/google/googletest/commit/ca3ffd90f2726f6c0c6e790f05c7c88491a16466


>
> The given .config sets:
>
> # BR2_ENABLE_DEBUG is not set
> BR2_ENABLE_RUNTIME_DEBUG=y
>
> Regards,
> Peter
>
> [1] https://git.buildroot.net/buildroot/commit/?id=1afea0b11b140a6d50aff726f2570702cc984a6e
>
> >
> > --
> > Kieran
> >
> >
> > > Thanks for your contribution to Buildroot!
> > >
> > > --
> > > http://autobuild.buildroot.net
> > _______________________________________________
> > buildroot mailing list
> > buildroot@buildroot.org
> > https://lists.buildroot.org/mailman/listinfo/buildroot
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-11-28 18:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <notmuch-sha1-bd80a5e4a125bbe0e62e6253fdfa7610e4834e90>
2022-11-28  9:03 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-11-26 Kieran Bingham
2022-11-28 18:00   ` Peter Seiderer
2022-11-28 18:57     ` Peter Seiderer [this message]

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=20221128195750.196cfe66@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@buildroot.org \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox