linux-ext4 - Re: PATCH: use CFLAGS when linking always

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 6 May 2007 09:54:31 -0400
From:	Theodore Tso <tytso@....edu>
To:	Dennis Gilmore <dennis@...il.us>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: PATCH: use CFLAGS when linking always

On Sat, May 05, 2007 at 10:06:01PM -0500, Dennis Gilmore wrote:
> Once upon a time Saturday 05 May 2007, Theodore Tso wrote:
> > On Sat, May 05, 2007 at 09:20:47AM -0500, Dennis Gilmore wrote:
> > > for multilib archs default CFLAGS may be inappropriate  and reslut in
> > > binaries unable to be linked.  since e2fsprogs uses gcc for linking I
> > > noticed this while building for sparc64.  patch has been tested and
> > > applied in Aurora SPARC Linux.
> >
> > What options do you need, and why don't you just specify them via:
> >
> > configure --with-ldopts="--foo-ld-flag"
> >
> > 					- Ted
> 
> defaults on sparc64  result in 64 bit objects  but gcc trying to create a 32 
> bit binary.  as a result the build blows up horribly.  the patch ensures that 
> CFLAGS is used in linking.  since gcc is used to link it is needed.
> 

What CFLAGS are you passing to configure, exactly?  And why can't you
also pass them to configure via --with-ldopts?

						- Ted


-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html