All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Alexandre Courbot <gnurou@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH v2 0/3] tools/gpio: switch to tools buildsystem
Date: Sun, 19 Jun 2016 16:52:26 +0300	[thread overview]
Message-ID: <1466344346.30123.165.camel@linux.intel.com> (raw)
In-Reply-To: <CAAVeFu+81cpK9-kAZhfyhhZc1AkegxaeCQ7omxDoRctSyboyFg@mail.gmail.com>

On Sun, 2016-06-19 at 22:07 +0900, Alexandre Courbot wrote:
> On Sun, Jun 19, 2016 at 12:24 AM, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > Current environment is not allowed to easily build the tools.
> > Move to tools buildsystem to allow user build gpio tools using only
> > existing
> > kernel sources. Besides that support O=/path/to/build/dir option.
> 
> Very good idea. I just have a few issues with the current patchset:
> 
> 1) I think patch 1 and 2 should be merged, otherwise we would have one
> commit where the GPIO tools are not available anymore

No objection!

> 2) When trying to cross-compile the tools, I am hitting the following
> error:
> 
>   arm-linux-gnueabihf-gcc -Wp,-MD,./.lsgpio.o.d,-MT,lsgpio.o -O2 -Wall
> -g -D_GNU_SOURCE -Iinclude -D"BUILD_STR(s)=#s"   -c -o lsgpio.o
> lsgpio.c
>   arm-linux-gnueabihf-gcc -Wp,-MD,./.gpio-utils.o.d,-MT,gpio-utils.o
> -O2 -Wall -g -D_GNU_SOURCE -Iinclude -D"BUILD_STR(s)=#s"   -c -o
> gpio-utils.o gpio-utils.c
>    ld -r -o lsgpio-in.o  lsgpio.o gpio-utils.o
> lsgpio.o: error adding symbols: File in wrong format
> 
> Looks like the host linker is invoked instead of the target one.

Can you try to add

LD = $(CROSS_COMPILE)ld

into Makefile and re-run?

-- 

Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-06-19 13:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-18 15:24 [PATCH v2 0/3] tools/gpio: switch to tools buildsystem Andy Shevchenko
2016-06-18 15:24 ` [PATCH v2 1/3] tools/gpio: remove old Makefile Andy Shevchenko
2016-06-18 15:24 ` [PATCH v2 2/3] tools/gpio: move to tools buildsystem Andy Shevchenko
2016-06-18 15:24 ` [PATCH v2 3/3] tools/gpio: add install section Andy Shevchenko
2016-06-19 13:07 ` [PATCH v2 0/3] tools/gpio: switch to tools buildsystem Alexandre Courbot
2016-06-19 13:52   ` Andy Shevchenko [this message]
2016-06-19 14:00     ` Alexandre Courbot

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=1466344346.30123.165.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=gnurou@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    /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.