linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Dennis Gilmore <dennis@ausil.us>
Cc: linux-ext4@vger.kernel.org
Subject: Re: PATCH: use CFLAGS when linking always
Date: Sun, 6 May 2007 09:54:31 -0400	[thread overview]
Message-ID: <20070506135431.GA4004@thunk.org> (raw)
In-Reply-To: <200705052206.08371.dennis@ausil.us>

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

      reply	other threads:[~2007-05-06 13:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-05 14:20 PATCH: use CFLAGS when linking always Dennis Gilmore
2007-05-05 19:26 ` Theodore Tso
2007-05-06  3:06   ` Dennis Gilmore
2007-05-06 13:54     ` Theodore Tso [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070506135431.GA4004@thunk.org \
    --to=tytso@mit.edu \
    --cc=dennis@ausil.us \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).