From: Dmitry Golubovsky <golubovsky@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Two suggestions for ape (was: egrep for Plan9)
Date: Fri, 23 Oct 2009 15:54:10 +0000 [thread overview]
Message-ID: <06a0be10-d05e-47f4-bebf-c9d9512de2b8@q14g2000vbi.googlegroups.com> (raw)
In-Reply-To: <d50d7d460910230706j58181763n409b237ea4c23fb2@mail.gmail.com>
Charles,
On Oct 23, 10:40Â am, fors...@terzarima.net (Charles Forsyth) wrote:
> it's /rc/bin/ape/ls that would change, not Plan 9's ls-proper.
Of course ape's one. As well as I am proposing to add egrep to ape's
tree not Plan9's native tree.
> what does autoconf do with the `inode number'?
In fact, nothing is done with inode number.
Autoconf generates code to obtain the current directory which involves
ls -di.
Here is the macro in /usr/share/autoconf/autoconf/general.m4 that
causes the problem:
# _AC_INIT_DIRCHECK
# -----------------
# Set ac_pwd, and sanity-check it and the source and installation
directories.
#
# (This macro is AC_REQUIREd by _AC_INIT_SRCDIR, so it has to be
AC_DEFUNed.)
#
AC_DEFUN([_AC_INIT_DIRCHECK],
[m4_divert_push([PARSE_ARGS])dnl
ac_pwd=`pwd` && test -n "$ac_pwd" &&
ac_ls_di=`ls -di .` &&
ac_pwd_ls_di=`cd "$ac_pwd" && ls -di .` ||
AC_MSG_ERROR([Working directory cannot be determined])
test "X$ac_ls_di" = "X$ac_pwd_ls_di" ||
AC_MSG_ERROR([pwd does not report name of working directory])
m4_divert_pop([PARSE_ARGS])dnl
])# _AC_INIT_DIRCHECK
I have redefined the macro locally to use only ls -d, it works.
the problem is, as can be seen: ls -di is hardcoded in assumption that
every ls understands it.
I use autoconf 2.63. This macro might be different in older versions.
I am currently looking at configure in the same project archive
created with 2.59 (in 2007), I cannot see traces of this macro there,
although configure.ac was likely the same.
This test (as well as egrep test) is something autoconf uses for
internal purposes.
Jason: I understand your reasoning. However if two small fixes would
unblock execution of many projects' configure on Plan9 IMHO they are
worth making; they won't break anything.
Thanks.
Dmitry
next prev parent reply other threads:[~2009-10-23 15:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 10:43 Dimitry Golubovsky
2009-10-23 14:06 ` Jason Catena
2009-10-23 14:12 ` Charles Forsyth
2009-10-23 15:06 ` W B Hacker
2009-10-23 15:38 ` Federico G. Benavento
2009-10-23 15:54 ` Dmitry Golubovsky [this message]
2009-10-23 16:08 ` Jason Catena
2009-10-23 18:18 ` Tim Newsham
2009-10-23 18:58 ` Jason Catena
2009-10-23 21:19 ` Federico G. Benavento
2009-10-26 10:19 ` Dmitry Golubovsky
2009-10-26 13:15 ` hiro
2009-10-26 14:15 ` Dmitry Golubovsky
2009-10-26 15:06 ` [9fans] Two suggestions for ape W B Hacker
[not found] ` <636733be-5009-4311-97ab-dc81634dbd06@p15g2000vbl.googlegroups.co>
2009-10-26 20:10 ` [9fans] Two suggestions for ape (was: egrep for Plan9) erik quanstrom
2009-10-27 16:10 ` Anthony Sorace
2009-10-27 16:16 ` erik quanstrom
2009-10-27 16:25 ` ron minnich
2009-10-27 16:37 ` erik quanstrom
2009-10-27 17:56 ` tlaronde
2009-10-27 21:43 ` Tim Newsham
2009-10-27 23:14 ` Francisco J Ballesteros
2009-10-28 0:23 ` Dave Eckhardt
2009-10-28 9:45 ` tlaronde
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=06a0be10-d05e-47f4-bebf-c9d9512de2b8@q14g2000vbi.googlegroups.com \
--to=golubovsky@gmail.com \
--cc=9fans@9fans.net \
/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).