From: Jonathan Nieder <jrnieder@gmail.com>
To: Richard H Lee <ricardohenrylee@gmail.com>
Cc: dash@vger.kernel.org
Subject: Re: Command parsing problem and tracefile
Date: Fri, 8 Jun 2012 12:17:30 -0500 [thread overview]
Message-ID: <20120608171730.GG10380@burratino> (raw)
In-Reply-To: <4FD22F1B.3090208@gmail.com>
Hi Richard,
Richard H Lee wrote:
> First up, when I run a configure script and it hits the following line:
> if $_pkg_config --exists --print-errors $all_libav_libs ; then
>
> with $_pkg_config being 'pkg-config --static', dash throws the
> following error:
> ./configure: 6012: ./configure: pkg-config --static: not found
Thanks for writing. Who is setting _pkg_config to 'pkg-config
--static', what are they trying to do, and can it be done another way?
This doesn't look like a dash-specific phenomenon. I get the same
result with
$ "pkg-config --static" foo bar
dash: 1: pkg-config --static: not found
which looks right to me. (You can test with 'CONFIG_SHELL=/bin/ksh
ksh ./configure'.)
[...]
> I would like to get some more info as to what in going on. IIRC, I
> saw in show.c, there was some sort for tracefile that dash to dump
> to. How do I enable this?
"dash -o debug" after a compile with DEBUG enabled. Though "dash -x"
tends to be more helpful if you are debugging a shell script rather
than trying to find a bug in dash itself.
Hope that helps,
Jonathan
next prev parent reply other threads:[~2012-06-08 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 16:58 Command parsing problem and tracefile Richard H Lee
2012-06-08 17:17 ` Jonathan Nieder [this message]
2012-06-08 21:20 ` Richard H Lee
2012-06-08 21:30 ` Jonathan Nieder
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=20120608171730.GG10380@burratino \
--to=jrnieder@gmail.com \
--cc=dash@vger.kernel.org \
--cc=ricardohenrylee@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 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.