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.
Please CC me on responses.
Dennis
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
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.
Dennis
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