From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC] [PATCH v2] lib32: Add support for linking 32bit programs on 64bit
Date: Fri, 7 Apr 2017 11:19:45 +0200 [thread overview]
Message-ID: <20170407091945.GA536@rei.lan> (raw)
In-Reply-To: <20170407105832.6f9d811a@linux-v3j5>
Hi!
> > +ifeq ($(filter -m32,$(CFLAGS)),)
> > +$(MAKE_TARGETS): LDFLAGS += -L$(top_builddir)/lib$(subst -m,,$(filter -m32,$(CFLAGS)))
> > +else
> > +LDFLAGS += -L$(top_builddir)/lib
> > +endif
>
> I think this breaks the build if you do 'make CFLAGS+=-m32' or './configure
> CFLAGS=-m32' to build everything in compatability mode. Am I doing it wrong or
> is this an issue?
If -m32 is in CFLAGS the $(filter -m32,$(CFLAGS)) is nonempty and we
will add -L$(top_builddir)/lib regardless. We will build the lib32 as
well but never use it.
And you have to pass LDLAGS=-m32 to the configure script as well, since
the implicit rule to build an executable from list of object files is:
$(CC) $(LDFLAGS) n.o $(LOADLIBES) $(LDLIBS)
Hence if you pass -m32 only to CFLAGS the compiler will fail to link the
ltp-pan binary.
Passing -m32 in CFLAGS only works for testcases though, since they are
compiled and linked in one try and hence use both LDFLAGS and CFLAGS.
> > +#
> > +# You should have received a copy of the GNU General Public License along
> > +# with this program; if not, write to the Free Software Foundation, Inc.,
> > +# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
> > +#
>
> Minor nit: should be e-mail.
Ok. I guess that we should use recent enough headers...
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-04-07 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 12:46 [LTP] [RFC] [PATCH v2] lib32: Add support for linking 32bit programs on 64bit Cyril Hrubis
2017-04-07 8:58 ` Richard Palethorpe
2017-04-07 9:19 ` Cyril Hrubis [this message]
2017-04-07 11:32 ` Richard Palethorpe
2017-04-07 11:44 ` Cyril Hrubis
2017-05-16 8:38 ` Richard Palethorpe
2017-05-16 16:00 ` Jiri Jaburek
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=20170407091945.GA536@rei.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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