From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] package/libv4l: bump version to 1.18.0
Date: Wed, 2 Oct 2019 22:57:53 +0200 [thread overview]
Message-ID: <20191002225753.10192fd9@gmx.net> (raw)
In-Reply-To: <20191002223511.2f98969c@windsurf.home>
Hello Thomas,
On Wed, 2 Oct 2019 22:35:11 +0200, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> On Wed, 2 Oct 2019 22:25:16 +0200
> Peter Seiderer <ps.report@gmx.net> wrote:
>
> > > On Wed, 2 Oct 2019 21:43:16 +0200
> > > Peter Seiderer <ps.report@gmx.net> wrote:
> > >
> > > > - remove 0001-fixup-lfs-mismatch-in-preload-libraries.patch
> > > > (Upstream applied [1])
> > > > - remove 0002-keytable-fix-EVIOCSCLOCKID-related-compile-failure.patch
> > > > (Upstream applied [2])
> > > > - remove 0003-Build-sdlcam-only-if-jpeg-is-enabled.patch
> > > > (Upstream applied [3])
> > > > - remove 0004-v4l2-compliance-needs-fork.patch
> > > > (Upstream applied [4])
> > >
> > > Since there are no patch left, do we still need AUTORECONF = YES and
> > > the dependency on host-gettext ?
> >
> > Good catch (autoreconf/host-gettext) was added with the 0003-Build-sdlcam-only-if-jpeg-is-enabled.patch
> > patch ([5]), but without autoreconf I get the following build error (using the config from [6]):
> >
> > .../host/opt/ext-toolchain/bin/../lib/gcc/sparc-buildroot-linux-uclibc/7.4.0/../../../../sparc-buildroot-linux-uclibc/bin/ld: qv4l2-qv4l2.o: undefined reference to symbol '__atomic_fetch_add_4@@LIBATOMIC_1.0'
> > .../host/opt/ext-toolchain/bin/../lib/gcc/sparc-buildroot-linux-uclibc/7.4.0/../../../../sparc-buildroot-linux-uclibc/bin/ld: /home/seiderer/Work/Buildroot/build_sparc_qt5multimedia_001/host/sparc-buildroot-linux-uclibc/sysroot/lib/libatomic.so.1: error adding symbols: DSO missing from command line
>
> How come this is related to autoreconf ? On SPARC, you need to link
> with -latomic, so this build failure is not too surprising. What is
> surprising is that an autoreconf fixes it. Do you think you could
> investigate this ?
Can (try) to investigate, the difference seems to be how the qt compile/link flags
are generated with/without autoreconf, the bug fixed with 'package/qt5base: fix libtool
la file dependency_libs entries' ([6]) was only triggered on libv4l/utils/qv4l with
autoreconf enabled too...
Regards,
Peter
[6] https://git.buildroot.net/buildroot/commit/?id=4ad73bf5e6326f7a414ecc94dbac0c79f5d33b31
>
> Thomas
next prev parent reply other threads:[~2019-10-02 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 19:43 [Buildroot] [PATCH v1] package/libv4l: bump version to 1.18.0 Peter Seiderer
2019-10-02 19:53 ` Thomas Petazzoni
2019-10-02 20:25 ` Peter Seiderer
2019-10-02 20:35 ` Thomas Petazzoni
2019-10-02 20:57 ` Peter Seiderer [this message]
2019-10-03 16:25 ` Peter Seiderer
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=20191002225753.10192fd9@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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