[9fans] Two suggestions for ape (was: egrep for Plan9)
Great, thanks Russ. I have two suggestions for ape minor additions arising from my recent attempts to run configure scripts on Plan9 1. Add this script (suggested by Russ) as /rc/bin/ape/egrep #!/bin/rc if(~ $1 -E) shift exec grep $* 2. Make ls accept -i option (if inode numbers do not exists in Plan9 then it could print some numeric hash of file path, whatever) These things are needed by autoconf. For the former, the script above worked fine as egrep. For the latter, autoconf supplies code using ls -di when checking the current directory. I had to redefine the corresponding function locally to get around this. Looks like these things are hardwired in the autoconf macro library. Thanks. -- Dimitry Golubovsky Anywhere on the Web
Re: [9fans] So quiet!
On Thu Oct 22 22:54:41 EDT 2009, eri...@gmail.com wrote: Everyone is busy drinking and debating protocol semantics. I think we've managed to empty the coraid fridge of beer. skip, sorry about that. we drank all your beer. - erik
Re: [9fans] So quiet!
In the cloud architecture it's Services all the way down at least till mack sneezes. - erik
Re: [9fans] So quiet!
erik quanstrom wrote: On Thu Oct 22 22:54:41 EDT 2009, eri...@gmail.com wrote: Everyone is busy drinking and debating protocol semantics. I think we've managed to empty the coraid fridge of beer. skip, sorry about that. we drank all your beer. - erik Tsk, Tsk, ..and here some of us thought that Plan9 team were all pointy-haired ivory-tower types who drank only white wine... ;-) ..ducks and waddles offstage... Bill
Re: [9fans] Two suggestions for ape (was: egrep for Plan9)
it's /rc/bin/ape/ls that would change, not Plan 9's ls-proper. what does autoconf do with the `inode number'?
Re: [9fans] So quiet!
on the contrary... I have always equated the plan 9 crowd as the most punkrock of the alternative OS crowd. On 10/23/09, W B Hacker w...@conducive.org wrote: erik quanstrom wrote: On Thu Oct 22 22:54:41 EDT 2009, eri...@gmail.com wrote: Everyone is busy drinking and debating protocol semantics. I think we've managed to empty the coraid fridge of beer. skip, sorry about that. we drank all your beer. - erik Tsk, Tsk, ..and here some of us thought that Plan9 team were all pointy-haired ivory-tower types who drank only white wine... ;-) ..ducks and waddles offstage... Bill
Re: [9fans] So quiet!
David Leimbach wrote: on the contrary... I have always equated the plan 9 crowd as the most punkrock of the alternative OS crowd. On 10/23/09, W B Hacker w...@conducive.org wrote: erik quanstrom wrote: On Thu Oct 22 22:54:41 EDT 2009, eri...@gmail.com wrote: Everyone is busy drinking and debating protocol semantics. I think we've managed to empty the coraid fridge of beer. skip, sorry about that. we drank all your beer. - erik Tsk, Tsk, ..and here some of us thought that Plan9 team were all pointy-haired ivory-tower types who drank only white wine... ;-) ..ducks and waddles offstage... Bill 'most punkrock'? NFW! The very endurance of Acme/Rio vs psuedo-3D and weird cube-rotation, bouncing 3-D'ish icons, warping and 'Genie' effects, tells me that by and large Plan9'ers can still read. Moreover, probably would rather read a dead-tree book than watch what passes for cinema these days - all gasoline bombs and special-effects - whether on big screen or desktop. A 'Game-Boy' or XBox crowd it ain't... Bill
Re: [9fans] So quiet!
skip, sorry about that. we drank all your beer. - erik fantastic!
Re: [9fans] Two suggestions for ape (was: egrep for Plan9)
Charles Forsyth wrote: it's /rc/bin/ape/ls that would change, not Plan 9's ls-proper. what does autoconf do with the `inode number'? Haven't you heard of the elephant that escaped from a traveling circus and wandered into the vegetable garden of a lady who had never seen an elephant in her life? Not even in pictures. She called the local sheriff and reported a great grey-skinned beast was pulling up all her carrots with its ..tail. Puzzled sheriff asked what it was DOING with the carrots thereafter... She said, Sheriff, you wouldn't believe me if I told you.. So, too, autoconf and those inode numbers... ;-) Bill
Re: [9fans] So quiet!
You even bought Oberon beer. It was good! iPhone email On Oct 23, 2009, at 11:02 AM, Skip Tavakkolian 9...@9netics.com wrote: skip, sorry about that. we drank all your beer. - erik fantastic!
Re: [9fans] Two suggestions for ape (was: egrep for Plan9)
I have no idea, but I know that removing the -i switch from configure gets it going, so just ignoring it should be good enough On Fri, Oct 23, 2009 at 12:12 PM, Charles Forsyth fors...@terzarima.net wrote: it's /rc/bin/ape/ls that would change, not Plan 9's ls-proper. what does autoconf do with the `inode number'? -- Federico G. Benavento
Re: [9fans] Two suggestions for ape (was: egrep for Plan9)
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
Re: [9fans] Two suggestions for ape (was: egrep for Plan9)
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. I wasn't going to comment again on this, since it's ape's tools, not the plan9 versions. I was obviously mistaken in assuming that you suggested changing plan9's version. I still personally feel that for plan9 to mean something, additional options and tools should be considered on their own merits and because they fit the plan9 philosophy, not because some random tool uses them and ignores them. From what's been described here autoconf should not have the expectation that it gets -i, just to ignore it. For ape that's fine, but from what I've had rejected I believe the core of plan9 is held to a higher standard. Dmitry Jason Catena
Re: [9fans] So quiet!
I'm so envious :-( Sent from the hotel in China :-) On Fri, Oct 23, 2009 at 10:52 AM, Eric Van Hensbergen eri...@gmail.com wrote: Everyone is busy drinking and debating protocol semantics. I think we've managed to empty the coraid fridge of beer. Sent from my iPhone On Oct 22, 2009, at 10:35 PM, Michaelian Ennis michaelian.en...@gmail.com wrote: ;) Ian
Re: [9fans] Two suggestions for ape (was: egrep for Plan9)
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. What if you just made a command gnuconfig which rewrote the configure script, fixing the minor defects, and ran the result? Or bound in a dummy ls and egrep before executing the real configure script? Lets keep the infection contained. Thanks. Dmitry Tim Newsham http://www.thenewsh.com/~newsham/
Re: [9fans] Two suggestions for ape (was: egrep for Plan9)
What if you just made a command gnuconfig which rewrote the configure script, fixing the minor defects, and ran the result? I wrote an rc script (vary http://codereview.appspot.com/117087/diff/1/2) which generally applies a sam script to a file (via ssam http://codereview.appspot.com/95076/diff/9038/10015) and runs the result. For configure, it would be called something like vary -x plan9port.sam configure --configure-opt which would create a new variation of the configure script, called configure.plan9port, and run it. Tim Newsham Jason Catena
Re: [9fans] So quiet!
On Fri, Oct 23, 2009 at 11:02 AM, Skip Tavakkolian 9...@9netics.com wrote: skip, sorry about that. we drank all your beer. - erik fantastic! Thanks for the beer Skip!
Re: [9fans] Two suggestions for ape (was: egrep for Plan9)
http://plan9.bell-labs.com/sources/contrib/fgb/rc/config hacks configure and mostly gets it going for egrep and fgrep aux/stub /bin/egrep bind /bin/grep /bin/egrep On Fri, Oct 23, 2009 at 4:18 PM, Tim Newsham news...@lava.net wrote: 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. What if you just made a command gnuconfig which rewrote the configure script, fixing the minor defects, and ran the result? Or bound in a dummy ls and egrep before executing the real configure script? Lets keep the infection contained. Thanks. Dmitry Tim Newsham http://www.thenewsh.com/~newsham/ -- Federico G. Benavento
Re: [9fans] iwp9 video (was: iwp9 deadline extension)
eric, thanks for broadcasting it On Thu, Oct 22, 2009 at 1:19 AM, Eric Van Hensbergen eri...@gmail.com wrote: Okay - still not sure there is going to be enough bandwidth to pull off livestreaming, but I'm going to attempt it. The URL to check will be http://www.livestream.com/iwp9 starting at 9pm US EST. I'll be recording the sessions to tape as well and depending on the quality of the livestream will post the taped versions at some later date. -eric On Mon, Oct 19, 2009 at 5:32 PM, Tim Newsham tim.news...@gmail.com wrote: Is video streaming going to happen? On Fri, Aug 28, 2009 at 12:13 PM, erik quanstrom quans...@quanstro.net wrote: If we've got 320kbps we can easily do the presentation via justin.tv or something similar. Alternatively, if we just want to set up e.g. an mpeg stream, I have machines that can proxy that. Though Erik will have to confirm / deny the existence of any amount of bandwidth in the first place. i'll try to get this information on monday. i'll only be able to quote the bandwidth claimed. - erik -- Federico G. Benavento
Re: [9fans] So quiet!
I would suggest that we're the most eclectic. Try having a conversation with a bunch of 9fans that doesn't encompass several millennia of culture, technology etc. Also I'm fairly certain that a disproportionately large number of 9fans aren't CS grads. As with Un*x, it's the people who recognise the power and simplicity who are the fans, not the academic dogmatists and fashionistas. D On 23 Oct 2009, at 15:06, David Leimbach wrote: on the contrary... I have always equated the plan 9 crowd as the most punkrock of the alternative OS crowd. On 10/23/09, W B Hacker w...@conducive.org wrote: erik quanstrom wrote: On Thu Oct 22 22:54:41 EDT 2009, eri...@gmail.com wrote: Everyone is busy drinking and debating protocol semantics. I think we've managed to empty the coraid fridge of beer. skip, sorry about that. we drank all your beer. - erik Tsk, Tsk, ..and here some of us thought that Plan9 team were all pointy-haired ivory-tower types who drank only white wine... ;-) ..ducks and waddles offstage... Bill
Re: [9fans] So quiet!
That basically encompasses what I meant by punkrock :-). On Fri, Oct 23, 2009 at 3:31 PM, dav...@mac.com wrote: I would suggest that we're the most eclectic. Try having a conversation with a bunch of 9fans that doesn't encompass several millennia of culture, technology etc. Also I'm fairly certain that a disproportionately large number of 9fans aren't CS grads. As with Un*x, it's the people who recognise the power and simplicity who are the fans, not the academic dogmatists and fashionistas. D On 23 Oct 2009, at 15:06, David Leimbach wrote: on the contrary... I have always equated the plan 9 crowd as the most punkrock of the alternative OS crowd. On 10/23/09, W B Hacker w...@conducive.org wrote: erik quanstrom wrote: On Thu Oct 22 22:54:41 EDT 2009, eri...@gmail.com wrote: Everyone is busy drinking and debating protocol semantics. I think we've managed to empty the coraid fridge of beer. skip, sorry about that. we drank all your beer. - erik Tsk, Tsk, ..and here some of us thought that Plan9 team were all pointy-haired ivory-tower types who drank only white wine... ;-) ..ducks and waddles offstage... Bill
Re: [9fans] iwp9 video (was: iwp9 deadline extension)
Agreed, much appreciated. I got the flu after booking the entire trip, it was to be my first time at iwp9 :(. At least I was able to see. Will the sessions be available for download? =jt On 2009-10-23, Federico G. Benavento benave...@gmail.com wrote: eric, thanks for broadcasting it On Thu, Oct 22, 2009 at 1:19 AM, Eric Van Hensbergen eri...@gmail.com wrote: Okay - still not sure there is going to be enough bandwidth to pull off livestreaming, but I'm going to attempt it. The URL to check will be http://www.livestream.com/iwp9 starting at 9pm US EST. I'll be recording the sessions to tape as well and depending on the quality of the livestream will post the taped versions at some later date. -eric On Mon, Oct 19, 2009 at 5:32 PM, Tim Newsham tim.news...@gmail.com wrote: Is video streaming going to happen? On Fri, Aug 28, 2009 at 12:13 PM, erik quanstrom quans...@quanstro.net wrote: If we've got 320kbps we can easily do the presentation via justin.tv or something similar. Alternatively, if we just want to set up e.g. an mpeg stream, I have machines that can proxy that. Though Erik will have to confirm / deny the existence of any amount of bandwidth in the first place. i'll try to get this information on monday. i'll only be able to quote the bandwidth claimed. - erik -- Federico G. Benavento
[9fans] Plan9 awk vs. GNU awk
Hi,
Working through the autoconf stuff I came across another issue: Plan9
awk does not seem to recognize a regexp that GNU awk does. This
results in config.status not properly creating config.h file based on
the configure's findings. The regexp in the test program was extracted
from config.status. Can anybody see anything wrong with this regexp?
The test program named `rxtest' (long regexp should match a #define or
#undef statement, if matched the whole line is printed):
#!/bin/sh
# (or /bin/rc for Plan9)
awk '
/^[\t ]*#[\t ]*(define|undef)[\t
]+[_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ][_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789]*([\t
(]|$)/ {
line = $ 0
print line }
'
The source file (config.h.in), top portion of it:
/* src/config.h.in. Generated from configure.ac by autoheader. */
/* platform-specific defines */
#include platform.h
/* Define to 1 if you want to use the primitives which let you examine Hugs
bytecodes (requires INTERNAL_PRIMS). */
#undef BYTECODE_PRIMS
/* Define to 1 to use a Char encoding determined by the locale. */
#undef CHAR_ENCODING_LOCALE
/* Define to 1 to use the UTF-8 Char encoding. */
#undef CHAR_ENCODING_UTF8
/* Define to 1 if you want to perform runtime tag-checks as an internal
consistency check. This makes Hugs run very slowly - but is very effective
at detecting and locating subtle bugs. */
#undef CHECK_TAGS
/* Define to one of `_getb67', `GETB67', `getb67' for Cray-2 and Cray-YMP
systems. This function is required for `alloca.c' support on those systems.
*/
#undef CRAY_STACKSEG_END
/* Define to 1 if using `alloca.c'. */
#undef C_ALLOCA
/* Define to 1 if debugging generated bytecodes or the bytecode interpreter.
*/
#undef DEBUG_CODE
Result under Linux (top portion):
$ cat src/config.h.in | rxtest | head
#undef BYTECODE_PRIMS
#undef CHAR_ENCODING_LOCALE
#undef CHAR_ENCODING_UTF8
#undef CHECK_TAGS
#undef CRAY_STACKSEG_END
#undef C_ALLOCA
#undef DEBUG_CODE
that is, all lines matched.
awk used was:
awk --version
GNU Awk 3.1.6
Copyright (C) 1989, 1991-2007 Free Software Foundation.
Result under Plan9:
term% cat src/config.h.in | rxtest
term%
Nothing: Plan9 awk does not match this regexp and source file's lines.
Not sure which version Plan9 awk is, the binary is dated:
term% ls -l /bin/awk
total 1000
-rwxr-xr-x 1 dima users 327504 Feb 4 2009 /bin/awk
/sys/src/cmd/awk/main.c contains:
char*version = version 19990602;
Thanks.
--
Dimitry Golubovsky
Anywhere on the Web
Re: [9fans] Plan9 awk vs. GNU awk
try using [_a-zA-Z][_a-zA-Z0-9] rather than the expanded form. i
didn't track it down to be sure, but plan 9 awk seem to have a limit
34 characters inside square brackets. a rather odd number
cpu% echo hello | awk '/^[abcdefghijklmnopqrstuvwxyzABCDEFGH].+/ {
line = $0 ; print line }'
cpu% echo hello | awk '/^[abcdefghijklmnopqrstuvwxyzABCDEFG].+/ { line
= $0 ; print line }'
hello
