Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Mallon <rmallon@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libsndfile: Add -D_FILE_OFFSET_BITS=64 to configuration
Date: Tue, 18 Sep 2012 06:37:09 +1000	[thread overview]
Message-ID: <505789F5.7090506@gmail.com> (raw)
In-Reply-To: <20120917190500.5a1ab662@skate>

On 18/09/12 03:05, Thomas Petazzoni wrote:

> Dear Ryan Mallon,
> 
> On Mon, 17 Sep 2012 16:48:14 +1000, Ryan Mallon wrote:
>> libsndfile requires sizeof(sf_count_t) == 8, where sf_count_t is a
>> typedef alias for off_t. This is not true by default for all
>> tool-chains, which leads to a runtime assert failure in binaries
>> compiled against libsndfile. See:
>>     
>>   http://permalink.gmane.org/gmane.comp.audio.libsndfile.devel/229
>>    
>> Add -D_FILE_OFFSET_BITS=64 to the configuration for libsndfile to
>> ensure that off_t is the correct size.
>>     
>> Signed-off-by: Ryan Mallon <rmallon@gmail.com>
>> ---
>>
>> diff --git a/package/libsndfile/libsndfile.mk
>> b/package/libsndfile/libsndfile.m index e5fbb5e..5e39aca 100644
>> --- a/package/libsndfile/libsndfile.mk
>> +++ b/package/libsndfile/libsndfile.mk
>> @@ -7,5 +7,7 @@
>>  LIBSNDFILE_VERSION = 1.0.25
>>  LIBSNDFILE_SITE = http://www.mega-nerd.com/libsndfile/files
>>  LIBSNDFILE_INSTALL_STAGING = YES
>> +LIBSNDFILE_CFLAGS = $(TARGET_CFLAGS) -D_FILE_OFFSET_BITS=64
>> +LIBSNDFILE_CONF_ENV += CFLAGS="$(LIBSNDFILE_CFLAGS)"
> 
> This looks strange: Buildroot already automatically passes
> -D_FILE_OFFSET_BITS=64 when BR2_LARGEFILE=y, see package/Makefile.in.


Okay, I didn't realise that. libsndfile should either depend on or
select (probably the latter) that package then. I will post a follow up.

Thanks,
~Ryan

      reply	other threads:[~2012-09-17 20:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-17  6:48 [Buildroot] [PATCH] libsndfile: Add -D_FILE_OFFSET_BITS=64 to configuration Ryan Mallon
2012-09-17 17:05 ` Thomas Petazzoni
2012-09-17 20:37   ` Ryan Mallon [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=505789F5.7090506@gmail.com \
    --to=rmallon@gmail.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