From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: Michael Abbott <michael@araneidae.co.uk>
Cc: crossgcc@sourceware.org, Joachim Nilsson <joachim.nilsson@vmlinux.org>
Subject: Re: crosstool-ng libncurses check in configure
Date: Mon, 11 May 2009 18:13:00 -0000 [thread overview]
Message-ID: <200905112013.18558.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <Pine.LNX.4.64.0905111822380.19340@venus.araneidae.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1459 bytes --]
Michael,
Joachim,
All,
On Monday 11 May 2009 19:26:54 Michael Abbott wrote:
> Not a patch ... but how about:
> lib="$(
> for l in ncursesw ncurses curses; do
> for x in so a dylib; do
> echo -n "lib$l.$x "
> done
> done)"
Yeah! Nice. See attached patch. Will be comitted soonish.
> ? You probably don't need the -n (then you don't need the "... " either),
> but I'm not actually looking at the useage here, just the one line.
See The Open Group Base Specifications Issue 7:
http://www.opengroup.org/onlinepubs/9699919799/utilities/echo.html
OK, seems clear enough: echo has *not* option! Will be using printf instead,
which is strongly recommended in the "Application Usage" section.
> Actually, if the order matters you need to swap the for lines around, but
> again I don't suppose it does.
Yes, the order matters (we prefer ncursesw, then ncurses, then curses), but
you got it right! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +0/33 662376056 | Software Designer | \ / CAMPAIGN | ___ |
| --==< ^_^ >==-- `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
`------------------------------^-------^------------------^--------------------'
[-- Attachment #2: configure-POSIX-compliance.patch --]
[-- Type: text/x-diff, Size: 912 bytes --]
Index: ct-ng.trunk/configure
===================================================================
--- ct-ng.trunk/configure (revision 1515)
+++ ct-ng.trunk/configure (working copy)
@@ -350,7 +350,13 @@
has_or_abort inc="ncurses/ncurses.h ncurses/curses.h ncurses.h curses.h" \
err="'ncurses' headers files were not found"
-has_or_abort lib="$( echo lib{ncursesw,ncurses,curses}.{so,a,dylib} )" \
+ncurses_libs="$( for l in ncursesw ncurses curses; do \
+ for x in so a dylib; do \
+ printf "lib$l.$x "; \
+ done; \
+ done \
+ )"
+has_or_abort lib="${ncurses_libs}" \
err="'ncurses' library was not found"
#---------------------------------------------------------------------
[-- Attachment #3: Type: text/plain, Size: 71 bytes --]
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2009-05-11 18:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-10 14:31 Joachim Nilsson
2009-05-11 17:03 ` Yann E. MORIN
2009-05-11 17:27 ` Michael Abbott
2009-05-11 18:13 ` Yann E. MORIN [this message]
2009-05-11 20:48 ` Yann E. MORIN
2009-05-12 15:26 ` Paul Smith
2009-05-12 16:33 ` Yann E. MORIN
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=200905112013.18558.yann.morin.1998@anciens.enib.fr \
--to=yann.morin.1998@anciens.enib.fr \
--cc=crossgcc@sourceware.org \
--cc=joachim.nilsson@vmlinux.org \
--cc=michael@araneidae.co.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).