From: Markos Chandras <Markos.Chandras@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] sawman: Link using gcc instead of ld
Date: Tue, 10 Dec 2013 09:36:57 +0000 [thread overview]
Message-ID: <52A6E0B9.6040305@imgtec.com> (raw)
In-Reply-To: <20131209185731.6ba10101@skate>
On 12/09/2013 05:57 PM, Thomas Petazzoni wrote:
> Dear Markos Chandras,
>
> On Mon, 9 Dec 2013 16:48:53 +0000, Markos Chandras wrote:
>
>>> Adding:
>>>
>>> LD = $(CC) -nostdlib
>>>
>>> to Makefile.am and also:
>>>
>>> SAWMAN_AUTORECONF = YES
>>>
>>> to sawman.mk fixes the problem.
>>>
>>> What do you think about this solution?
>>
>> Yes this is preferred. You should patch configure.ac or Makefile.am (if
>> they are available) and run autoreconf as suggested.
>
> I definitely agree that patching the Makefile.am and using
> <pkg>_AUTORECONF is the preferred way.
>
> However, I find it weird that we need to add LD = $(CC) -nostdlib in
> the Makefile.am. There are plenty of other autotools-based packages
> that generate libraries, including private libraries, and they work
> just fine. Isn't there a better fix that can hopefully be upstreamed?
>
> Best regards,
>
> Thomas
>
Hi Thomas,
I am not familiar with the code. I haven't examined the Makefiles to be
honest. A better fix would be to identify the direct use of $(LD) in the
Makefile for linking and replace it with $(CC). I did something similar
for directfb
http://git.buildroot.net/buildroot/tree/package/directfb/directfb-use-gcc-link.patch
--
markos
prev parent reply other threads:[~2013-12-10 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 16:30 [Buildroot] [PATCH] sawman: Link using gcc instead of ld Vicente Olivert Riera
2013-12-06 18:08 ` Thomas Petazzoni
2013-12-09 11:47 ` Vicente Olivert Riera
2013-12-09 11:58 ` Vicente Olivert Riera
2013-12-09 16:48 ` Markos Chandras
2013-12-09 17:57 ` Thomas Petazzoni
2013-12-10 9:36 ` Markos Chandras [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=52A6E0B9.6040305@imgtec.com \
--to=markos.chandras@imgtec.com \
--cc=buildroot@busybox.net \
/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.