From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/lz4: fix static build
Date: Sun, 30 Oct 2022 12:09:41 +0100 [thread overview]
Message-ID: <20221030120941.06aa98ac@windsurf> (raw)
In-Reply-To: <20221028164800.16655-1-fontaine.fabrice@gmail.com>
On Fri, 28 Oct 2022 18:48:00 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fix the following static build failure raised since bump to version
> 1.9.4 in commit 1f54af8c4f814bfc0993756b82575ad581ce5318:
>
> compiling dynamic library 1.9.4
> /home/giuliobenetti/autobuild/run/instance-0/output-1/host/opt/ext-toolchain/m68k-buildroot-uclinux-uclibc/bin/ld.real: /home/giuliobenetti/autobuild/run/instance-0/output-1/host/m68k-buildroot-uclinux-uclibc/sysroot/usr/lib/crt1.o: in function `_start':
> (.text+0x1c): undefined reference to `main'
>
> Fixes:
> - http://autobuild.buildroot.org/results/9187852fb7a869bf5595275d47929632659a4407
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> .../0001-build-Support-BUILD_SHARED-no.patch | 42 +++++++++++++++++++
> 1 file changed, 42 insertions(+)
> create mode 100644 package/lz4/0001-build-Support-BUILD_SHARED-no.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-10-30 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 16:48 [Buildroot] [PATCH 1/1] package/lz4: fix static build Fabrice Fontaine
2022-10-30 11:09 ` Thomas Petazzoni via buildroot [this message]
2022-11-08 19:56 ` Peter Korsgaard
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=20221030120941.06aa98ac@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.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