From: Stefan Seyfried <stefan.seyfried@googlemail.com>
To: poky@yoctoproject.org
Subject: ac_cv_sizeof_off_t breaks curl compilation
Date: Sun, 08 Dec 2013 13:42:29 +0100 [thread overview]
Message-ID: <52A46935.8090803@message-id.googlemail.com> (raw)
Hi all,
I investigated why I get a libcurl5 package (libcurl.so.5) out of curl
with poky (branch dora, building for ARM and powerpc32).
Basically, libcurl.so.5 (instead of libcurl.so.4) means "you are doing
it wrong". curl configure detects that the ABI is broken (because off_t
is not 64bits) and bumps the SONAME, see lib/README.curl_off_t in the
curl source.
After a long and hard debugging session, I found out that the following
files set ac_cv_sizeof_off_t to 4:
meta/site/arm-linux:ac_cv_sizeof_off_t=${ac_cv_sizeof_off_t=4}
meta/site/ix86-common:ac_cv_sizeof_off_t=${ac_cv_sizeof_off_t=4}
meta/site/powerpc32-linux:ac_cv_sizeof_off_t=${ac_cv_sizeof_off_t=4}
Now this is true for some cases, but only if e.g. _FILE_OFFSET_BITS is
not set to 64 (which curl does).
Curl does use AC_CHECK_SIZEOF(off_t) which works correctly, but only if
ac_cv_sizeof_off_t is not preset to the wrong value.
I'm now wondering how many other packages silently compile with wrong
features etc because of this. Curl is just very vocal about this issue,
so that it was easy to notify.
If this is not the right list to report such issues, please point me
into the right direction.
Thanks,
Stefan
--
Stefan Seyfried
Linux Consultant & Developer -- GPG Key: 0x731B665B
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
reply other threads:[~2013-12-08 12:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52A46935.8090803@message-id.googlemail.com \
--to=stefan.seyfried@googlemail.com \
--cc=poky@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.