From: Rolf Eike Beer <eb@emlix.com>
To: lttng-dev@lists.lttng.org
Subject: Re: Wrong "ar" used when cross-building lttng
Date: Mon, 18 Nov 2019 09:10:13 +0100 [thread overview]
Message-ID: <8118904.6pNFUeu9c4__39084.8499302351$1574091320$gmane$org@devpool35> (raw)
In-Reply-To: <50ff7646-3ca9-0fdd-f9bf-6bfa8e63bad3@simark.ca>
[-- Attachment #1.1: Type: text/plain, Size: 2070 bytes --]
Am Freitag, 15. November 2019, 16:34:33 CET schrieb Simon Marchi:
> On 2019-11-15 3:18 a.m., Rolf Eike Beer wrote:
> > Simon Marchi wrote:
> >> On 2019-11-14 11:24 a.m., Rolf Eike Beer wrote:
> >>> 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
> >>
> >> Hmm I don't remember seeing this error, and I don't see it now.
> >>
> >> Could you please try with master? If it still happens, you can try to
> >> find from which line of the configure.ac or an m4 file this line comes
> >> from. I presume it won't be too hard to fix.
> >
> > Sorry, my fault. If I had looked a little closer I could have given you
> > the
> >
> > context:
> > checking for tput... /usr/bin/tput
> > tput: No value for $TERM and no -T specified
> >
> > ./configure: line 24663: test: -eq: unary operator expected
> >
> > When the package is built inside our automated buildsystem these variables
> > are not set because this is no interactive shell. If I build with an
> > interactive shell these warnings are in fact not there.
>
> It still sounds like the "test" command should be improved, it should not
> fail with an invalid syntax. Can you give us the relevant lines of
> configure around 24663, and if possible match them to the source lines in
> configure.ac and/or one of the m4 files in the m4 directory?
The line in configure is this:
if test -n "$PS1" && test `"$pprint_tput" colors` -eq 256 && test -t 1;
then :
Which seems to be one of these 3 lines from configure.ac:
PPRINT_INIT
PPRINT_SET_INDENT(1)
PPRINT_SET_TS(38)
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
next prev parent reply other threads:[~2019-11-18 8:10 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
[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 [this message]
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='8118904.6pNFUeu9c4__39084.8499302351$1574091320$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).