12 Nov
2016
12 Nov
'16
11:54 p.m.
On Sun, 13 Nov 2016 09:27:47 +1100, Erik de Castro Lopo wrote:
Ralf Mardorf wrote:
"Pretty sure"?
As already pointed out, the Arch package does use the source from
upstream. It is not patched.
The only changes are:
sed -i 's|#!/usr/bin/python|#!/usr/bin/python2|' src/binheader_writef_check.py
\
src/create_symbols_file.py programs/test-sndfile-metadata-set.py
sed -i 's|python|&2|' src/Makefile.am
And it's configured with:
./configure --prefix=/usr --disable-sqlite
See:
https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packa…
The default flags - not necessarily used by the package maintainer -
are:
#########################################################################
# ARCHITECTURE, COMPILE FLAGS
#########################################################################
#
CARCH="@CARCH@"
CHOST="@CHOST@"
#-- Compiler and Linker Flags
# -march (or -mcpu) builds exclusively for an architecture
# -mtune optimizes for an architecture, but builds for whole processor family
CPPFLAGS="-D_FORTIFY_SOURCE=2"
CFLAGS="@CARCHFLAGS@ -mtune=generic -O2 -pipe -fstack-protector-strong"
CXXFLAGS="@CARCHFLAGS@ -mtune=generic -O2 -pipe -fstack-protector-strong"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro"
#-- Make Flags: change this for DistCC/SMP systems
#MAKEFLAGS="-j2"
#-- Debugging flags
DEBUG_CFLAGS="-g -fvar-tracking-assignments"
DEBUG_CXXFLAGS="-g -fvar-tracking-assignments"
See:
https://git.archlinux.org/svntogit/packages.git/tree/trunk/makepkg.conf?h=p…
Regards,
Ralf
Since Kjetil guess seems to be plausible, I would
try adding
"-D_FILE_OFFSET_BITS=64"
to the flags in makepkg.conf. I don't know, if it belongs there, but
since it doesn't take much time to test it, I wouldn't wait for a
reply, how to handle this and simply test it.
That may not help, because to get libsndfile to built on a 32 bit
system *without* large file support, I'm pretty sure they would have
had to patch the libsndfile sources.