From: Peter Korsgaard <peter@korsgaard.com>
To: Norbert Lange <nolange79@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/util-linux: fix detection of ncurses
Date: Wed, 06 Sep 2023 19:20:36 +0200 [thread overview]
Message-ID: <87a5tzi5gb.fsf@48ers.dk> (raw)
In-Reply-To: <20230904124334.94615-1-nolange79@gmail.com> (Norbert Lange's message of "Mon, 4 Sep 2023 14:43:33 +0200")
>>>>> "Norbert" == Norbert Lange <nolange79@gmail.com> writes:
> the configure script seems to use the NCURSES6_CONFIG variable,
> however it will still check for a system ncurses6-config and prefer
> this script if available.
Where do you see that? Looking at configure I see the normal
ac_cv_prog_FOO / check FOO / fallback to program:
if test ${ac_cv_prog_NCURSESW6_CONFIG+y}
then :
printf %s "(cached) " >&6
else $as_nop
if test -n "$NCURSESW6_CONFIG"; then
ac_cv_prog_NCURSESW6_CONFIG="$NCURSESW6_CONFIG" # Let the user override the test.
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
case $as_dir in #(((
'') as_dir=./ ;;
*/) ;;
*) as_dir=$as_dir/ ;;
esac
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir$ac_word$ac_exec_ext"; then
ac_cv_prog_NCURSESW6_CONFIG="${ac_tool_prefix}ncursesw6-config"
printf "%s\n" "$as_me:${as_lineno-$LINENO}: found $as_dir$ac_word$ac_exec_ext" >&5
break 2
fi
done
What is the error you are seeing exactly?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-09-06 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 12:43 [Buildroot] [PATCH] package/util-linux: fix detection of ncurses Norbert Lange
2023-09-06 17:20 ` Peter Korsgaard [this message]
2023-09-06 20:18 ` Norbert Lange
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=87a5tzi5gb.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=nolange79@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox