Bug 406609

Summary:	sys-apps/e2fsprogs fails when using old glibc with new kernel headers due to missing fallocate()
Product:	Gentoo Linux	Reporter:	Ortwin Glueck <odi>
Component:	[OLD] Core system	Assignee:	Gentoo's Team for Core System packages <base-system>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Ortwin Glueck 2012-03-02 15:36:06 UTC

It requires the fallocate syscall which is only supported from glibc-2.10. I encountered that when upgrading a dated Gentoo installation with glibc-2.9. e2fsprogs should force a glibc upgrade.

../lib/libext2fs.so: undefined reference to `fallocate'
collect2: ld returned 1 exit status
make[2]: *** [e2fsck] Error 1
make[2]: Leaving directory `/var/tmp/portage/sys-fs/e2fsprogs-1.42/work/e2fsprogs-1.42/e2fsck'
make[1]: *** [all-progs-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/sys-fs/e2fsprogs-1.42/work/e2fsprogs-1.42'
make: *** [all] Error 2
emake failed


Reproducible: Always

Comment 1 SpanKY gentoo-dev

2012-03-05 05:27:45 UTC

no, it shouldn't.  it has logic for dealing with missing fallocate(), but the logic goes wrong when you have new kernel headers.

Comment 2 SpanKY gentoo-dev

2012-03-05 05:41:10 UTC

should be all set now in the tree; thanks for the report!

Commit message: Fix building on older glibcs w/out fallocate
http://sources.gentoo.org/sys-fs/e2fsprogs/e2fsprogs-1.42.1.ebuild?r1=1.2&r2=1.3
http://sources.gentoo.org/sys-fs/e2fsprogs/e2fsprogs-1.42.ebuild?r1=1.8&r2=1.9
http://sources.gentoo.org/sys-fs/e2fsprogs/files/e2fsprogs-1.42-no-fallocate.patch?rev=1.1