All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC] [PATCH] lib32: Add support for linking 32bit programs on 64bit
Date: Tue, 28 Mar 2017 17:33:47 +0200	[thread overview]
Message-ID: <20170328153347.GJ1045@rei> (raw)
In-Reply-To: <20170328165536.741d14e5@linux-v3j5>

Hi!
> > * The directory lib32 contains symlinks of minimal set of sources
> >   needed to link newlib testcase + Makefile.
> 
> Apparently missing safe_socket which is required for cve-2016-4997.c, but that
> is easy to fix I suppose.

That is just one symlink away...

> > * The testcases.mk builds 32bit library as well if
> >   32bit compiler was installed (-m32 configure test was succesful)
> > 
> > * And finally the env_post.mk switches between lib and lib32 depeding
> >   on if -m32 was passed in the CFLAGS
> 
> I added "cve-2016-4997: CFLAGS += -m32" and it still tried to look in
> "../../lib"

Hmm, that is not easy to fix, since this is target specific variable and
we simply do not see the -m32 in the CFLAGS in the condition below.

We would have to set the LDFLAGS per target and I'm not sure if we can
easily do that.

> > +ifeq ($(filter -m32,$(CFLAGS)),)
> >  LDFLAGS				+= -L$(top_builddir)/lib
> > +else
> > +LDFLAGS				+= -L$(top_builddir)/lib32
> > +endif
> 
> I was able to remove the if statement (i.e. put both dirs on the search path)
> and the 64-bit tests still compiled fine and so did the 32-bit test, although
> maybe not all linkers can be trusted to ignore libs with the wrong number of
> bits.

While this works mostly fine it produces warnings I would like to avoid.

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2017-03-28 15:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 10:01 [LTP] [RFC] [PATCH] lib32: Add support for linking 32bit programs on 64bit Cyril Hrubis
2017-03-28 14:55 ` Richard Palethorpe
2017-03-28 15:33   ` Cyril Hrubis [this message]
2017-03-28 15:46     ` Cyril Hrubis
2017-03-29  9:37       ` Richard Palethorpe
2017-03-29  8:36 ` Jan Stancek
2017-03-29  9:12   ` Cyril Hrubis
2017-03-29 12:48 ` Richard Palethorpe
2017-03-29 14:56   ` Richard Palethorpe

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=20170328153347.GJ1045@rei \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.