Hi, when link e2fsck from the e2fsprogs package, you might experience a problem at the link. e2fsck is looking for -lintl. Please find a fix as attachment. Regards, Lionel
Created attachment 463 [details] e2fsprogs fix for e2fsck link problem with libintl
Created attachment 479 [details] autoreconf for libglib2
(In reply to comment #2) > Created an attachment (id=479) [details] > autoreconf for libglib2 > Hm... bugzilla... Sorry, nothing to do here...
Comment on attachment 479 [details] autoreconf for libglib2 This patch is not relevant for this package.
(In reply to comment #0) > Hi, > > when link e2fsck from the e2fsprogs package, you might experience a problem at > the link. e2fsck is looking for -lintl. > > Please find a fix as attachment. What problem is your patch fixing exactly? It doesn't look like e2fsprogs uses libintl.
(In reply to comment #5) > (In reply to comment #0) > > Hi, > > > > when link e2fsck from the e2fsprogs package, you might experience a problem at > > the link. e2fsck is looking for -lintl. > > > > Please find a fix as attachment. > > What problem is your patch fixing exactly? It doesn't look like e2fsprogs uses > libintl. > It adds the --sysroot option when linking. This problem only appears with an external toolchain when sysroot is the staging directory instead of the original sysroot of the toolchain (for me its in /opt/STM/STLinux-2.3/...).
The package has been switched to the autotools infrastructure since then, and with the autotools infrastructure, $(TARGET_CONFIGURE_ENV) is passed to the ./configure script, and this variable contains LDFLAGS. So this bug is fixed.