[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#240523: libc6-dev: Some note or workaround for users with custom include files



Package: libc6-dev
Version: 2.3.2.ds1-11
Severity: wishlist

Please correct me if I'm wrong, or am missing documentation out there
that covers this.  But if a user patches their kernel headers for a
custom compile (while still using kernel-package and such), is there a
recommended way of rolling those include file changes to the main system
where they won't be overriden by libc6-dev updates and such?

My main reason for this is I increased the number of file descriptors
for my system in my kernel.

include/linux/posix_types.h: __FD_SETSIZE 16384
include/linux/limits.h: NR_OPEN 16384  /  OPEN_MAX 16384
include/linux/fs.h: INR_OPEN 16384  /  NR_FILE 16384

And while the system is aware of it (ulimit and such works fine),
programs that rely on including 'sys/types.h' and such get rolled down
to 1024.  So, what would be the recommended way of doing such things in
a debian system (and if there is a best prcatices, should it be included
in a readme with libc6-dev?  As I would imagine there are a few people
who change some defines, and may not be aware that upgrades to this
package may roll the changes back)?

I would guess that using /usr/local/* would be one way to do it, and of
course you would have to edit the include path to reflect such things as
well.  Or is it feasible to symlink/copy the kernel headers to
/usr/include/linux in some way as they would not be overriden? (using
equivs in some way maybe?).


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.0
Locale: LANG=C, LC_CTYPE=C

Versions of packages libc6-dev depends on:
ii  libc6                2.3.2.ds1-11        GNU C Library: Shared libraries an
ii  linux-kernel-headers 2.5.999-test7-bk-15 Linux Kernel Headers for developme

-- no debconf information



Reply to: