All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Lukichev <alexander.lukichev@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] i686-buildroot-linux-gnu-as  does not work
Date: Mon, 27 Jan 2014 13:47:49 +0200	[thread overview]
Message-ID: <52E64765.5010803@gmail.com> (raw)
In-Reply-To: <255977954.4763389.1390820376074.JavaMail.root@openwide.fr>

Hi Romain, Kirill,

On 01/27/2014 12:59 PM, Romain Naour wrote:
> I had the same problem with infozip and I fixed this error by patching unix/Makefile like this:
(...)
> match.o: match.S
>   $(CPP) match.S > _match.s
> - $(AS) _match.s
> - mv _match.o match.o
> - rm -f _match.s
> + $(AS) _match.s -o match.o
(...)
> (Ok, this patch is really weird...)
Why?

To me it seems that $(AS) should not be expected to output by default to <basename>.o, as is
apparently expected in the infozip's unix/Makefile. GNU as outputs to a.out by default.

If I build the package in my host environment, it picks "$(CC) -c" as the value for $(AS) and
works OK but when called from Buildroot, the value for $(AS) is set to invoke the toolchain's
as directly, and the output of it goes to a.out.

Am I totally wrong in believing that your patch is the right way to produce match.o rather
than original way of doing it?

--
Best regards,
  Alexander Lukichev

  reply	other threads:[~2014-01-27 11:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-25 10:23 [Buildroot] i686-buildroot-linux-gnu-as does not work Кирилл Луценко
2014-01-26 17:12 ` Alexander Lukichev
2014-01-26 19:33   ` Кирилл Луценко
2014-01-27  7:37     ` Кирилл Луценко
2014-01-27 10:59       ` Romain Naour
2014-01-27 11:47         ` Alexander Lukichev [this message]
2014-01-27 12:48           ` Romain Naour
2014-01-27 22:23             ` Arnout Vandecappelle
2014-01-30 22:20               ` Romain Naour

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=52E64765.5010803@gmail.com \
    --to=alexander.lukichev@gmail.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.