From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 2/4] libgmp: add missing with-gnu-ld
Date: Fri, 21 Mar 2014 09:53:50 +0100 [thread overview]
Message-ID: <20140321085349.GA25178@omega> (raw)
In-Reply-To: <20140321083424.GL23331@pengutronix.de>
Hi Michael,
On Fri, Mar 21, 2014 at 09:34:24AM +0100, Michael Olbrich wrote:
> On Fri, Mar 21, 2014 at 09:04:22AM +0100, Alexander Aring wrote:
> > Signed-off-by: Alexander Aring <alex.aring@gmail.com>
> > ---
> > rules/libgmp.make | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/rules/libgmp.make b/rules/libgmp.make
> > index cf36ece..6da2010 100644
> > --- a/rules/libgmp.make
> > +++ b/rules/libgmp.make
> > @@ -40,6 +40,7 @@ LIBGMP_AUTOCONF := \
> > $(CROSS_AUTOCONF_USR) \
> > --$(call ptx/endis, PTXCONF_LIBGMP_SHARED)-shared \
> > --$(call ptx/endis, PTXCONF_LIBGMP_STATIC)-static \
> > + --with-gnu-ld \
>
> Is something broken without this?
>
no I just see this always on other rules and ptxdist use normally OSELAS
Toolchain which contains the gnu linker.
I can drop this if you want.
- Alex
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-03-21 8:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 8:04 [ptxdist] [PATCH 1/4] libgmp: fix issue with missing -fPIC Alexander Aring
2014-03-21 8:04 ` [ptxdist] [PATCH 2/4] libgmp: add missing with-gnu-ld Alexander Aring
2014-03-21 8:34 ` Michael Olbrich
2014-03-21 8:53 ` Alexander Aring [this message]
2014-03-21 8:04 ` [ptxdist] [PATCH 3/4] libgmp: remove targetinstall of static lib Alexander Aring
2014-03-21 8:04 ` [ptxdist] [PATCH 4/4] libgmp: remove LIBGMP_STATIC menu entry Alexander Aring
2014-03-21 8:33 ` Michael Olbrich
2014-03-21 8:31 ` [ptxdist] [PATCH 1/4] libgmp: fix issue with missing -fPIC Michael Olbrich
2014-03-21 8:55 ` Alexander Aring
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=20140321085349.GA25178@omega \
--to=alex.aring@gmail.com \
--cc=ptxdist@pengutronix.de \
/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