From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] package/unixodbc: new package
Date: Fri, 13 Mar 2015 22:03:51 +0100 [thread overview]
Message-ID: <20150313220351.5dce9aa3@free-electrons.com> (raw)
In-Reply-To: <1426278306-21589-1-git-send-email-bernd.kuhls@t-online.de>
Dear Bernd Kuhls,
On Fri, 13 Mar 2015 21:25:06 +0100, Bernd Kuhls wrote:
> diff --git a/package/unixodbc/0001-fix-nopthread.patch b/package/unixodbc/0001-fix-nopthread.patch
> new file mode 100644
> index 0000000..45933e5
> --- /dev/null
> +++ b/package/unixodbc/0001-fix-nopthread.patch
> @@ -0,0 +1,39 @@
> +Fix pthread detection
> +
> +configure.in always calls AC_CHECK_COMP_OPT(pthread) which succeeds with the
> +toolchain used although it does not contain thread support:
> +
> +checking for mutex_lock in -lthread ... no
> +checking for pthread_mutex_lock in -lpthread... no
> +checking for pthread_mutex_lock in -lc... no
> +checking if compiler accepts -pthread... yes
> +checking for pthread_mutex_lock in -lc... no
> +checking for pthread_mutex_lock in -lpthread... no
> +
> +This positive configure check leads to
> +
> + CFLAGS="$CFLAGS -pthread"
> +
> +in ./configure, line 15757 which causes a compilation bug
> +/home/br/br4/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-buildroot-linux-uclibcgnueabi/4.8.3/../../../../arm-buildroot-linux-uclibcgnueab
> +
> +using this defconfig
> +http://autobuild.buildroot.net/results/e86/e86e97ff7887f1bdc6bf913498392ff50f56ea88/defconfig
> +
> +This patch disables the freebsd-only code path. Patching configure directly
> +prevents the need for autoreconf.
> +
> +Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
Hum, could we instead get a solution that could potentially be
upstreamed? Like using AC_CACHE_CHECK(), or something like that.
Also, any reason to patch configure directly? We normally don't do
that, and always prefer to patch configure.{in,ac}.
That being said, if you don't care about no-thread support in unixodbc,
I would personally be fine if you decided to add 'depends on
BR2_TOOLCHAIN_HAS_THREADS' in Config.in.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-13 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 20:25 [Buildroot] [PATCH v3 1/1] package/unixodbc: new package Bernd Kuhls
2015-03-13 21:03 ` Thomas Petazzoni [this message]
2015-03-13 21:19 ` Bernd Kuhls
2015-03-13 21:27 ` Thomas Petazzoni
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=20150313220351.5dce9aa3@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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