From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Sun, 30 Jun 2002 04:29:05 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 258 ************************************************** Saturday 29 June 2002 Number 258 ************************************************** Subjects for today 1 Re: UnixOS/2 Build System : James Cannon 2 Re: Perl 5.73 and perl212F.dll : John Poltorak 3 Re: Texinfo bug - no! m4 bug (RTFM) : Thomas Hoffmann 4 Re: PID files : Thomas Hoffmann 5 Re: UnixOS/2 Build System : Thomas Hoffmann 6 Re: UnixOS/2 Build System : John Poltorak 7 Re: UnixOS/2 Build System : Stefan Neis 8 Re: UnixOS/2 Build System : Sebastian Wittmeier (ShadoW)" 9 Re: libtool : Andreas Buening 10 Re: Gettext : Andreas Buening 11 Re: Building SED using new Autoconf : Andreas Buening 12 Re: Building SED using new Autoconf : John Poltorak **= Email 1 ==========================** Date: Sun, 30 Jun 2002 08:46:16 -0700 (PDT) From: James Cannon Subject: Re: UnixOS/2 Build System GNU INFO should be able to be converted to a format more suitable to you. Perhaps other list members can provide recommendations ... --- John Poltorak wrote: > On Sun, Jun 30, 2002 at 01:24:15PM +0100, Thomas > Hoffmann wrote: > > wget.info says: > > I need to start using GNU INFO regularly, but it > seems to awkward and I > can't get the hang of it... > > > > > You can also encode your username and password > within a URL: > > > > ftp://user:password at host/path > > http://user:password at host/path > > > > Either USER or PASSWORD, or both, may be left > out. If you leave out > > either the HTTP username or password, no > authentication will be sent. > > If you leave out the FTP username, `anonymous' > will be used. If you > > leave out the FTP password, your email address > will be supplied as a > > default password.(1) > > Thanks for that. > > Here is how to get a specific file: > > wget > ftp://unixos2: at 213.152.37.92/pub/unixos2/build_system/lib/build.cmd > > I'm not sure how to retreive the whole directory > tree. Wildcards don't > seem to work... > > I'm not sure if anyone has tried it, but one of the > problems in > establishing the correct '-p' value for patch has > been fixed with this > handy bit of AWK code:- > > if test -f $PATCHFILE; then > { > > patch -p`awk 'BEGIN { > min_p = 1234567 > } > > $1 == "+++" || $1 == "***" { > gsub (ARCHIVE ".*", "", $2) > gsub (/[^/]/, "", $2) > if (length($2) < min_p) min_p = length($2) > } > > END { > print min_p + 1 > }' ARCHIVE=$ARCHIVE $PATCHFILE` < $PATCHFILE > > } > > > Wish I understood it... :-) > > There was a problem with the previous code, but this > seems to work. > > > > -- > > Thomas Hoffmann > Telephone: > > 49-351-4598831 > > thoffman at zappa.sax.de > Dresden, > > Germany > > > > ..sig under construction ... > > > -- > John > > ===== Sincerely, James Cannon Using OS/2 Warp in the beautiful Wine Country of Northern California! __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com **= Email 2 ==========================** Date: Sun, 30 Jun 2002 11:20:36 +0100 From: John Poltorak Subject: Re: Perl 5.73 and perl212F.dll On Sat, Jun 29, 2002 at 10:27:22PM +0300, Andrew Belov wrote: > On Sat, 29 Jun 2002 16:42:56 +0200 (CEST), Stefan Neis wrote: > > >> Here is what I get when it fails: > >> > >> PERL212F.DLL 0001:000bb5eb > >> P1=00000001 P2=00000000 P3=XXXXXXXX P4=XXXXXXXX > >> EAX=00000000 EBX=040cb024 ECX=11f982b0 EDX=0432c650 > >(snipp) > >> > >> If it can help... > > > >Anybody cares to explain to a nosy individual how one extracts useful > >information from this kind of dump? I know that core files are handled > >by gdb (and how), but which program is extracting something useful from > >those register dumps and how much information do you really get? > > Using a tool like HIEW, For anyone, like me, who has never even heard of HIEW you can get it here:- http://hobbes.nmsu.edu/pub/os2/dev/util/hiew604.zip I've just downloaded it and will see if I can make any sense of it. -- John **= Email 3 ==========================** Date: Sun, 30 Jun 2002 12:57:06 +0100 From: Thomas Hoffmann Subject: Re: Texinfo bug - no! m4 bug (RTFM) Folks, you have described at length the phenomenology of this so called bug, but nobody seems to have bothered to have a look at text of the error msg. Otherwise, you would have found in m4.texinfo line 282 and 352: 282: at xref{Compatibility} for more details. 352: functions. at xref{Debug Levels} for more details on the format and As you can see, "for" follows the at xref command (...and begins with the "f" from the "not f" part of the error msg. Now a look into the texinfo docs provides: *Please note:* A period or comma *must* follow the closing brace of an ` at xref'. It is required to terminate the cross reference. This period or comma will appear in the output, both in the Info file and in the printed manual. So, to fix this one simply should add the needed periods or commata in m4.texinfo (m4 "bug" is a bit of an exaggeration, maybe the texinfo syntax has changed. But the above paragraph can already be found in texi.tex in emx's gnudoc.zip from 1995). John Poltorak schrieb: > > On Thu, Jun 27, 2002 at 11:08:19PM +0200, Andreas Buening wrote: > > John Poltorak wrote: > > > > > > When I use MAKEINFO from TEXINFO v4.0 I get the following msgs when > > > creating the info docs for M4:- > > > > > > m4.texinfo:282: warning: `.' or `,' must follow cross reference, not f. > > > m4.texinfo:352: warning: `.' or `,' must follow cross reference, not f. > > > m4.texinfo:358: warning: `.' or `,' must follow cross reference, not f. > > > m4.texinfo:363: warning: `.' or `,' must follow cross reference, not f. > > > > > > This does not occur with older versions of MAKEINFO. > > > > > > Can anyone confirm this behaviour? > > > > Yes. But it's only a warning. > > It also seems to be a standard feature of the original. > > > > > bye, > > Andreas > > > > -- > > One OS to rule them all, One OS to find them, > > One OS to bring them all and in the darkness bind them > > In the Land of Redmond where the Shadows lie. > > -- > John -- Thomas Hoffmann Telephone: 49-351-4598831 thoffman at zappa.sax.de Dresden, Germany ..sig under construction ... **= Email 4 ==========================** Date: Sun, 30 Jun 2002 13:16:05 +0100 From: Thomas Hoffmann Subject: Re: PID files You are right. The FHS 2.1 doc says in 5.10: .... Process identifier (PID) files, which were originally placed in /etc,should be placed in /var/run.The naming convention for PID files is .pid.For example, the crond PID file is named /var/run/crond.pid. The internal format of PID files remains unchanged. The file should consist of the process identifier in ASCII-encoded decimal, followed by a newline character.For example, if crond was process number 25, /var/run/crond.pid would contain three characters: two, five, and newline. Programs that read PID files should be somewhat flexible in what they accept; i.e., they should ignore extra whitespace, leading zeroes, absence of the trailing newline, or additional lines in the PID file. Programs that create PID files should use the simple specification located in the above paragraph. .... John Poltorak schrieb: > > Is there a standard, or recommended location for PID files? > > If I have a choice, I tend to put mine in /var/run > > Does this seem a reasonable standard for UnixOS/2? > > -- > John -- Thomas Hoffmann Telephone: 49-351-4598831 thoffman at zappa.sax.de Dresden, Germany ..sig under construction ... **= Email 5 ==========================** Date: Sun, 30 Jun 2002 13:24:15 +0100 From: Thomas Hoffmann Subject: Re: UnixOS/2 Build System wget.info says: You can also encode your username and password within a URL: ftp://user:password at host/path http://user:password at host/path Either USER or PASSWORD, or both, may be left out. If you leave out either the HTTP username or password, no authentication will be sent. If you leave out the FTP username, `anonymous' will be used. If you leave out the FTP password, your email address will be supplied as a default password.(1) John Poltorak schrieb: > > I suppose it would be easiest to download the whole thing using wget, but > I can't remember the syntax for logging on as a particular user. Can > anyone remind me? > > -- > John -- Thomas Hoffmann Telephone: 49-351-4598831 thoffman at zappa.sax.de Dresden, Germany ..sig under construction ... **= Email 6 ==========================** Date: Sun, 30 Jun 2002 16:26:29 +0100 From: John Poltorak Subject: Re: UnixOS/2 Build System On Sun, Jun 30, 2002 at 01:24:15PM +0100, Thomas Hoffmann wrote: > wget.info says: I need to start using GNU INFO regularly, but it seems to awkward and I can't get the hang of it... > You can also encode your username and password within a URL: > > ftp://user:password at host/path > http://user:password at host/path > > Either USER or PASSWORD, or both, may be left out. If you leave out > either the HTTP username or password, no authentication will be sent. > If you leave out the FTP username, `anonymous' will be used. If you > leave out the FTP password, your email address will be supplied as a > default password.(1) Thanks for that. Here is how to get a specific file: wget ftp://unixos2: at 213.152.37.92/pub/unixos2/build_system/lib/build.cmd I'm not sure how to retreive the whole directory tree. Wildcards don't seem to work... I'm not sure if anyone has tried it, but one of the problems in establishing the correct '-p' value for patch has been fixed with this handy bit of AWK code:- if test -f $PATCHFILE; then { patch -p`awk 'BEGIN { min_p = 1234567 } $1 == "+++" || $1 == "***" { gsub (ARCHIVE ".*", "", $2) gsub (/[^/]/, "", $2) if (length($2) < min_p) min_p = length($2) } END { print min_p + 1 }' ARCHIVE=$ARCHIVE $PATCHFILE` < $PATCHFILE } Wish I understood it... :-) There was a problem with the previous code, but this seems to work. > -- > Thomas Hoffmann Telephone: > 49-351-4598831 > thoffman at zappa.sax.de Dresden, > Germany > > ..sig under construction ... -- John **= Email 7 ==========================** Date: Sun, 30 Jun 2002 18:14:04 +0200 (CEST) From: Stefan Neis Subject: Re: UnixOS/2 Build System On Sun, 30 Jun 2002, John Poltorak wrote: > wget ftp://unixos2: at 213.152.37.92/pub/unixos2/build_system/lib/build.cmd > > I'm not sure how to retreive the whole directory tree. Wildcards don't > seem to work... wget --recursive should help. Use with care, though ... Stefan **= Email 8 ==========================** Date: Sun, 30 Jun 2002 21:26:10 +0200 (CEST) From: "Sebastian Wittmeier (ShadoW)" Subject: Re: UnixOS/2 Build System On Sun, 30 Jun 2002 18:14:04 +0200 (CEST), Stefan Neis wrote: >On Sun, 30 Jun 2002, John Poltorak wrote: > >> wget ftp://unixos2: at 213.152.37.92/pub/unixos2/build_system/lib/build.cmd >> >> I'm not sure how to retreive the whole directory tree. Wildcards don't >> seem to work... > >wget --recursive should help. Use with care, though ... And with "-g=on" wget recognizes wildcards. Sebastian **= Email 9 ==========================** Date: Sun, 30 Jun 2002 21:53:49 +0200 From: Andreas Buening Subject: Re: libtool John Poltorak wrote: > > Has anyone managed to install the latest libtool? > > What did you need to do? How can you tell whether it is installed > correctly? > > I tried building the latest version straight from GNU and have libtool > and libtoolize shell scripts in c:\usr\local\bin which is on the path when > I make builds, and there is also a c:\usr\local\share\libtool dir with > assorted files, but when I try building an app which looks for libtool, it > can't find it, so it looks as though the install may have missed out some > step. Good question. At least some applications seem to ignore the external libtool stuff. You may have to "libtoolize" your package (for the case that works). bye, Andreas -- One OS to rule them all, One OS to find them, One OS to bring them all and in the darkness bind them In the Land of Redmond where the Shadows lie. **= Email 10 ==========================** Date: Sun, 30 Jun 2002 21:54:30 +0200 From: Andreas Buening Subject: Re: Gettext John Poltorak wrote: > > If anyone has succeeded in building gettext v0.11.2 especially in > 'masochist' mode, I'd like to know exactly what you did because I always > fail miserably when trying to do this, and I have tried many many times. > > There seem to be soooooo many dependencies to getting this right and > gettext seems to be such a key part to so many GNU apps that it is > essential to have it installed. The good news is that (the code of) gettext 0.11.2 seems to work as an _internal_ library of gawk 3.1.1. I'm going to find out how to get configure working soon. bye, Andreas -- One OS to rule them all, One OS to find them, One OS to bring them all and in the darkness bind them In the Land of Redmond where the Shadows lie. **= Email 11 ==========================** Date: Sun, 30 Jun 2002 21:54:58 +0200 From: Andreas Buening Subject: Re: Building SED using new Autoconf John Poltorak wrote: > > On Mon, Jun 24, 2002 at 08:41:47PM +0200, Andreas Buening wrote: > > John Poltorak wrote: > > > > > > In an attempt to rebuild as many apps from scatch as possible using the > > > new Autoconf, I thought I would start with SED. Okay, I've looked closer into that problem for sed, grep and textutil packages. If you want to make build scripts that start from scratch (i.e. from ftp.gnu.org ;-) ) you have to do the following: - Apply the patches/files/whatever as mentioned in the INSTALL.OS2 files. - Apply additional patches/files for autoconf 2.53/automake 1-6-2 (see below) - Run the auto* tools, i.e. "aclocal" or "aclocal -I m4" automake autoconf Additional patches/whatever: sed: cp -p /usr/share/automake-1.6/depcomp . grep: mv m4/init.m4 m4/init.m4.old touch m4/init.m4 mv m4/header.m4 m4/header.m4.old touch m4/header.m4 replace m4/progtest.m4 by a newer version (see below) textutils: cp -p /usr/share/automake-1.6/depcomp . replace m4/progtest.m4 by a newer version (see below) replace m4/chown.m4 by a newer version (see below) Some notes: If you directly start from the gnu sources (I've started from the patched sources) you may still get a message that is outdated. In this case you can find somewhere in /usr/share/auto*. Currently I don't plan to upload a new "release" with those minor changes because a) you still get the same binaries and b) it would increase confusion if there were packages of the same software but created by different autoconf versions. ----------------------------- --- gnu/textutils-2.0/configure.in Sat Oct 20 17:35:24 2001 +++ test/textutils-2.0/configure.in Sat Jun 29 01:02:02 2002 at at -66,11 +66,11 at at AC_FUNC_VPRINTF AC_REPLACE_FUNCS(memcpy memset stpcpy strpbrk strtol strtoul) -AM_FUNC_STRTOD +AC_FUNC_STRTOD AC_SUBST(POW_LIBM) test $am_cv_func_strtod_needs_libm = yes && POW_LIBM=-lm -AM_FUNC_ERROR_AT_LINE +AC_FUNC_ERROR_AT_LINE AC_CHECK_FUNCS(nl_langinfo) AC_CHECK_HEADERS(langinfo.h) ----------------------------- ----------------------------- --- gnu/textutils-2.0/m4/chown.m4 Sat Dec 1 21:41:50 2001 +++ test/textutils-2.0/m4/chown.m4 Sat Jun 29 01:34:22 2002 at at -51,6 +51,9 at at fi ]) dnl end AC_CHECK_FUNC(chown, ...) +AH_TOP([#include]) +AH_TOP([#include]) + AH_VERBATIM([z_EMX_REPLACE_CHOWN], [/* If libc does not support chown(), replace it by a dummy function */ #if !HAVE_CHOWN && !defined chown ----------------------------- --------------------------------- ----- progtest.m4 --------------- --------------------------------- # Search path for a program which passes the given test. # Ulrich Drepper , 1996. # # This file can be copied and used freely without restrictions. It can # be used in projects which are not available under the GNU General Public # License but which still want to provide support for the GNU gettext # functionality. # Please note that the actual code of GNU gettext is covered by the GNU # General Public License and is *not* in the public domain. # serial 2 dnl AM_PATH_PROG_WITH_TEST(VARIABLE, PROG-TO-CHECK-FOR, dnl TEST-PERFORMED-ON-FOUND_PROGRAM [, VALUE-IF-NOT-FOUND [, PATH]]) AC_DEFUN([AM_PATH_PROG_WITH_TEST], [# Extract the first word of "$2", so it can be a program name with args. set dummy $2; ac_word=[$]2 AC_MSG_CHECKING([for $ac_word]) AC_CACHE_VAL(ac_cv_path_$1, [case "[$]$1" in /*) ac_cv_path_$1="[$]$1" # Let the user override the test with a path. ;; *) unset ac_cv_path_$1 ac_save_IFS=$IFS; IFS="${PATH_SEPARATOR-:}" for ac_dir in ifelse([$5], , $PATH, [$5]); do IFS=$ac_save_IFS test -z "$ac_dir" && ac_dir=. for ac_exec_ext in '' $ac_executable_extensions; do if $as_executable_p $ac_dir/$ac_word$ac_exec_ext; then if [$3]; then ac_cv_path_$1="$ac_dir/$ac_word" break fi fi done test -z [$]ac_cv_path_$1 || break done dnl If no 4th arg is given, leave the cache variable unset, dnl so AC_PATH_PROGS will keep looking. ifelse([$4], , , [ test -z "[$]ac_cv_path_$1" && ac_cv_path_$1="$4" ])dnl ;; esac])dnl $1="$ac_cv_path_$1" if test ifelse([$4], , [-n "[$]$1"], ["[$]$1" != "$4"]); then AC_MSG_RESULT([$]$1) else AC_MSG_RESULT(no) fi AC_SUBST($1)dnl ]) --------------------------------- bye, Andreas -- One OS to rule them all, One OS to find them, One OS to bring them all and in the darkness bind them In the Land of Redmond where the Shadows lie. **= Email 12 ==========================** Date: Sun, 30 Jun 2002 23:35:09 +0100 From: John Poltorak Subject: Re: Building SED using new Autoconf On Sun, Jun 30, 2002 at 09:54:58PM +0200, Andreas Buening wrote: > John Poltorak wrote: > > > > On Mon, Jun 24, 2002 at 08:41:47PM +0200, Andreas Buening wrote: > > > John Poltorak wrote: > > > > > > > > In an attempt to rebuild as many apps from scatch as possible using the > > > > new Autoconf, I thought I would start with SED. > > Okay, I've looked closer into that problem for sed, grep > and textutil packages. If you want to make build scripts > that start from scratch (i.e. from ftp.gnu.org ;-) ) > you have to do the following: Many thanks, I'll try this out over the next few days and try and integrate it into my build framework > - Apply the patches/files/whatever as mentioned in the > INSTALL.OS2 files. > - Apply additional patches/files for autoconf 2.53/automake 1-6-2 > (see below) > - Run the auto* tools, i.e. > "aclocal" or "aclocal -I m4" > automake > autoconf > > > Additional patches/whatever: > sed: Just to clarify matters... I should do this first:- > cp -p /usr/share/automake-1.6/depcomp . and then run each of these aclocal automake autoconf autoheader before configure.... I found I managed to build a SED.EXE but had to miss out the doc directory which had the following errors: Making install in doc make[1]: Entering directory `C:/unixos2/workdir/sed-3.02/doc' ./mdate-sh[60]: shift: nothing to shift Updating ./version.texi cd . \ && makeinfo \ `echo sed.texi | sed 's,.*/,,'` ./version.texi:71: Unknown command `(#)PD'. sed.texi:99: warning: at sc argument all uppercase, thus no effect. sed.texi:244: warning: at sc argument all uppercase, thus no effect. sed.texi:282: warning: at sc argument all uppercase, thus no effect. sed.texi:427: warning: at sc argument all uppercase, thus no effect. sed.texi:594: warning: at sc argument all uppercase, thus no effect. sed.texi:670: warning: Info cannot handle `:' in index entry `: (label) command'. sed.texi:713: warning: at sc argument all uppercase, thus no effect. sed.texi:705: warning: at sc argument all uppercase, thus no effect. sed.texi:429: warning: at sc argument all uppercase, thus no effect. sed.texi:281: warning: at sc argument all uppercase, thus no effect. sed.texi:243: warning: at sc argument all uppercase, thus no effect. makeinfo: Removing output file `C:/unixos2/workdir/sed-3.02/doc/sed.info' due to errors; use --force to preserve. make[1]: *** [sed.info] Error 2 make[1]: Leaving directory `C:/unixos2/workdir/sed-3.02/doc' make: *** [install-recursive] Error 1 Does anyone else get this error? I see these msgs are only warnings, so I'm not sure why the make process halts at this point instead of carrying on. I'm using Makeinfo v4.1, BTW. > bye, > Andreas > > -- > One OS to rule them all, One OS to find them, > One OS to bring them all and in the darkness bind them > In the Land of Redmond where the Shadows lie. -- John