Re: getconf(1) interface considered cross-harmful

2017-10-30 Thread Guillem Jover
On Thu, 2017-10-19 at 10:51:30 +0100, Simon McVittie wrote: > On Thu, 19 Oct 2017 at 10:50:36 +0200, Guillem Jover wrote: > > When it comes to LFS, starting with dpkg 1.19.0 you can now use the > > new «lfs» feature from the «future» feature area > > ... or if your upstream uses Autotools, ask

Re: getconf(1) interface considered cross-harmful

2017-10-19 Thread Simon McVittie
On Thu, 19 Oct 2017 at 10:50:36 +0200, Guillem Jover wrote: > When it comes to LFS, starting with dpkg 1.19.0 you can now use the > new «lfs» feature from the «future» feature area ... or if your upstream uses Autotools, ask them to add AC_SYS_LARGEFILE to configure.ac, which as far as I can tell

getconf(1) interface considered cross-harmful

2017-10-19 Thread Guillem Jover
Hi! I recently noticed that the getconf(1) interface is broken by design when it comes to cross-compiling. It always returns the information for the build system (GNU/dpkg terms), via the build system libc. This means that any package using getconf(1) to get build-specific information such as