Bug 457

Summary: e2fsprogs link problem
Product: buildroot Reporter: Lionel Landwerlin <llandwerlin>
Component: OtherAssignee: unassigned
Status: RESOLVED FIXED    
Severity: enhancement CC: buildroot
Priority: P5    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Host: x86-64 Target: SH4
Build:
Attachments: e2fsprogs fix for e2fsck link problem with libintl
autoreconf for libglib2

Description Lionel Landwerlin 2009-07-13 19:12:33 UTC
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
Comment 1 Lionel Landwerlin 2009-07-13 19:13:17 UTC
Created attachment 463 [details]
e2fsprogs fix for e2fsck link problem with libintl
Comment 2 Lionel Landwerlin 2009-07-17 10:13:54 UTC
Created attachment 479 [details]
autoreconf for libglib2
Comment 3 Lionel Landwerlin 2009-07-17 11:24:39 UTC
(In reply to comment #2)
> Created an attachment (id=479) [details]
> autoreconf for libglib2
> 

Hm... bugzilla... Sorry, nothing to do here...
Comment 4 Will Newton 2009-07-27 15:44:40 UTC
Comment on attachment 479 [details]
autoreconf for libglib2


This patch is not relevant for this package.
Comment 5 Peter Korsgaard 2009-08-31 08:03:55 UTC
(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.
Comment 6 Lionel Landwerlin 2009-08-31 08:30:16 UTC
(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/...).
Comment 7 Thomas Petazzoni 2010-02-21 17:59:11 UTC
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.