Jonathan Nieder wrote:
For example, dpkg itself doesn't seem to have
large-file support.
... in squeeze. Looks like aspects of this were fixed in version
1.16.0. I'm not sure yet why the squeeze dpkg binary here has a
reference to the (32-bit) open() function --- another pitfall for
the
On Sat, Sep 24, 2011 at 03:49:11PM -0500, Jonathan Nieder wrote:
Three cheers for the new dpkg-buildflags interface!
I would like to suggest an addition to the default flags: the output of
getconf LFS_CFLAGS should be included in the CFLAGS/CXXFLAGS variables. On
32-bit archs, this
Steve Langasek wrote:
On Sat, Sep 24, 2011 at 03:49:11PM -0500, Jonathan Nieder wrote:
It also has a negative side-effect that Debian would no longer be doing
its part to get
#define _LARGEFILE_SOURCE
#define _FILE_OFFSET_BITS 64
put directly in upstream's config.h when appropriate.
Hi!
On Sat, 2011-09-24 at 15:55:12 -0500, Jonathan Nieder wrote:
Jonathan Nieder wrote:
For example, dpkg itself doesn't seem to have
large-file support.
... in squeeze. Looks like aspects of this were fixed in version
1.16.0. I'm not sure yet why the squeeze dpkg binary here has a
tag 642573 wontfix
thanks
Hi!
On Sat, 2011-09-24 at 14:25:44 -0700, Steve Langasek wrote:
On Sat, Sep 24, 2011 at 03:49:11PM -0500, Jonathan Nieder wrote:
I would like to suggest an addition to the default flags: the output of
getconf LFS_CFLAGS should be included in the CFLAGS/CXXFLAGS
Processing commands for cont...@bugs.debian.org:
tag 642573 wontfix
Bug #642573 [dpkg] dpkg-buildflags: include $(getconf LFS_CFLAGS)?
Added tag(s) wontfix.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
642573:
found 629480 dpkg/1.16.1
quit
Roger Leigh wrote:
dpkg currently supports
Build-Depends (arch all and any)
Build-Depends-Indep (arch all)
and the same Build-Conflicts.
This patch adds
Build-Depends-Arch (arch any)
and Build-Conflicts-Arch.
Sorry for the slow reply. Let’s see.
7 matches
Mail list logo