From: Markos Chandras <Markos.Chandras@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] sawman: Link using gcc instead of ld
Date: Mon, 9 Dec 2013 16:48:53 +0000 [thread overview]
Message-ID: <52A5F475.6030303@imgtec.com> (raw)
In-Reply-To: <52A5B06E.60204@imgtec.com>
On 12/09/2013 11:58 AM, Vicente Olivert Riera wrote:
> On 12/09/2013 11:47 AM, Vicente Olivert Riera wrote:
>> On 12/06/2013 06:08 PM, Thomas Petazzoni wrote:
>>> Dear Vicente Olivert Riera,
>>>
>>> On Fri, 6 Dec 2013 16:30:28 +0000, Vicente Olivert Riera wrote:
>>>
>>>> +--- SaWMan-1.6.3/wm/sawman/Makefile.in.orig 2013-12-06
>>>> 14:22:22.675409826 +0000
>>>> ++++ SaWMan-1.6.3/wm/sawman/Makefile.in 2013-12-06
>>>> 16:04:03.383752843 +0000
>>>
>>> Makefile.in is generated from Makefile.am. So we shouldn't be fixing
>>> Makefile.in, but instead Makefile.am or the process that generates
>>> Makefile.in from Makefile.am.
>>>
>>> What happens if you simply add:
>>>
>>> SAWMAN_AUTORECONF = YES
>>>
>>> ?
>>
>> You still have the same problem.
>>
>>> Best regards,
>>>
>>> Thomas
>>>
>>
>>
>
> 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.
--
markos
next prev parent reply other threads:[~2013-12-09 16:48 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 [this message]
2013-12-09 17:57 ` Thomas Petazzoni
2013-12-10 9:36 ` Markos Chandras
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=52A5F475.6030303@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.