lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: Rolf Eike Beer <eb@emlix.com>
To: lttng-dev@lists.lttng.org
Subject: Re: Wrong "ar" used when cross-building lttng
Date: Thu, 14 Nov 2019 17:24:38 +0100	[thread overview]
Message-ID: <3241563.NbJrRt7XGO__24461.2829572119$1573748789$gmane$org@devpool35> (raw)
In-Reply-To: <2e655403-71d2-ee11-3675-d9ad81d6fe85@simark.ca>


[-- Attachment #1.1: Type: text/plain, Size: 1518 bytes --]

Simon Marchi wrote:
> On 2019-11-14 2:58 a.m., Rolf Eike Beer wrote:
> > The unprefixed version of "ar" is being used, leading to this error:
> > 
> > arm-unknown-linux-gnueabi-gcc  -I. -Wall -I../../../include/ -I../../../
> > include/ \
> > 
> >         -O2 -g -march=armv7-a -mtune=cortex-a9 -mfpu=neon-fp16 -mfloat-
> > 
> > abi=hard -mthumb-interwork -pipe
> > -Wl,--no-copy-dt-needed-entries,--as-needed - Wl,--build-id -Wdate-time
> > -c -o lttng-ust-provider-hello.o tp.c
> > ar -rc lttng-ust-provider-hello.a lttng-ust-provider-hello.o
> > make[4]: ar: Command not found
> > 
> > I fixed it for the moment with "make AR=arm-unknown-linux-gnueabi-ar", but
> > ideally this would not be needed.
> > 
> > Greetings,
> > 
> > Eike
> 
> Hi Rofl,
> 
> Indeed, I can see the problem.
> 
> Can you please try the patch below?  It adds an autoconf check for ar and
> then passes it as an environment variable to the Makefiles of doc/examples.

Works for me.

I have not checked latest git, but maybe you may want to fix this warning, 
too?

With 2.11.0 release tarball:

-./configure: line 24663: test: -eq: unary operator expected

Greetings,

Eike
-- 
Rolf Eike Beer, emlix GmbH, http://www.emlix.com
Fon +49 551 30664-0, Fax +49 551 30664-11
Gothaer Platz 3, 37083 Göttingen, Germany
Sitz der Gesellschaft: Göttingen, Amtsgericht Göttingen HR B 3160
Geschäftsführung: Heike Jordan, Dr. Uwe Kracke – Ust-IdNr.: DE 205 198 055

emlix - smart embedded open source

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 313 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

  parent reply	other threads:[~2019-11-14 16:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2357817.GzqeBO7jDX@devpool35>
2019-11-14 16:01 ` Wrong "ar" used when cross-building lttng Simon Marchi
     [not found] ` <2e655403-71d2-ee11-3675-d9ad81d6fe85@simark.ca>
2019-11-14 16:24   ` Rolf Eike Beer [this message]
     [not found]   ` <3241563.NbJrRt7XGO@devpool35>
2019-11-14 16:43     ` Simon Marchi
     [not found]     ` <3c62ba15-bb2d-702e-86f4-90e8decc9fb1@simark.ca>
2019-11-15  8:18       ` Rolf Eike Beer
     [not found]       ` <4096513.X5kWAsihKE@devpool35>
2019-11-15 15:34         ` Simon Marchi
     [not found]         ` <50ff7646-3ca9-0fdd-f9bf-6bfa8e63bad3@simark.ca>
2019-11-18  8:10           ` Rolf Eike Beer
2019-11-14  7:58 Rolf Eike Beer

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='3241563.NbJrRt7XGO__24461.2829572119$1573748789$gmane$org@devpool35' \
    --to=eb@emlix.com \
    --cc=lttng-dev@lists.lttng.org \
    /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;
as well as URLs for NNTP newsgroup(s).