Date: Thu, 22 Apr 2004 00:04:21 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 356 ************************************************** Wednesday 21 April 2004 Number 356 ************************************************** Subjects for today 1 --prefix : John Poltorak 2 Re: cygpath: not found : Andreas Buening 3 Re: _wait3 : Andreas Buening 4 Re: --prefix : Andreas Buening 5 Re: _wait3 : John Poltorak 6 Re: cygpath: not found : John Poltorak 7 BYACC : John Poltorak 8 Re: cygpath: not found : Andreas Buening 9 Re: BYACC : Andreas Buening 10 Re: BYACC : John Poltorak 11 Re: cygpath: not found : Jeff Robinson 12 Re: _wait3 : Dave Yeo" 13 Re: _wait3 : Dave Yeo" 14 Re: BYACC : Dave Yeo" 15 Re: BYACC : Stefan.Neis at t-online.de 16 test -f foo.[cmd|exe] : John Poltorak 17 Re: BYACC : John Poltorak 18 Building wxWindows : John Poltorak 19 Re: Vile build error : John Poltorak 20 Re: BYACC : Andrew MacIntyre **= Email 1 ==========================** Date: Tue, 20 Apr 2004 19:33:21 +0100 From: John Poltorak Subject: --prefix Which takes precedence for the definition of prefix, a config.site setting or --prefix on the configure command line? I would have expected the configure command line, but that doesn't appear to be the case. -- John **= Email 2 ==========================** Date: Tue, 20 Apr 2004 21:02:44 +0200 From: Andreas Buening Subject: Re: cygpath: not found John Poltorak wrote: > > On Mon, Apr 19, 2004 at 09:46:31PM +0200, Andreas Buening wrote: > > That's an old automake bug fixed in (roughly estimated) 1.7.x. > > It happens only if you use .obj files. > > So, I guess I need to run automake (1.7.6) before autoconf... I'd suggest the latest version you've installed. > What about aclocal? Should I run that too? If in doubt, yes. Btw, I think we need something like a ux2bs FAQ or "known Bugs" site since this kind of problem arises every few months. Bye, Andreas **= Email 3 ==========================** Date: Tue, 20 Apr 2004 21:02:28 +0200 From: Andreas Buening Subject: Re: _wait3 Dave Yeo wrote: > > Trying to build TightVNC I get a bunch of unresolved symbols. I know how to redefine most but not _wait3. Any ideas? Good question. I can link wait3() but it seems to be declared nowhere (emx). > Also get this error which I've never seen before though I often have -lshm in programs > /usr/X11R6/lib/shm.a(shm.o): Undefined symbol DosAllocSharedMem referenced from text segment > /usr/X11R6/lib/shm.a(shm.o): Undefined symbol DosGetSharedMem referenced from text segment > /usr/X11R6/lib/shm.a(shm.o): Undefined symbol DosFreeMem referenced from text segment Should be in one of the standard libraries (-los2?). Which gcc do you use? Bye, Andreas **= Email 4 ==========================** Date: Tue, 20 Apr 2004 21:21:18 +0200 From: Andreas Buening Subject: Re: --prefix John Poltorak wrote: > > Which takes precedence for the definition of prefix, a config.site setting > or --prefix on the configure command line? > > I would have expected the configure command line, but that doesn't appear > to be the case. I think in best case this behaviour is undefined, so don't use $prefix or any other installdir variable in config.site. This can break much more than it could be worth. Use "make prefix=..." if you really want to overwrite the command line of configure. Bye, Andreas **= Email 5 ==========================** Date: Tue, 20 Apr 2004 20:39:13 +0100 From: John Poltorak Subject: Re: _wait3 On Tue, Apr 20, 2004 at 09:02:28PM +0200, Andreas Buening wrote: > Dave Yeo wrote: > > > > Trying to build TightVNC I get a bunch of unresolved symbols. I know how to redefine most but not _wait3. Any ideas? > > Good question. I can link wait3() but it seems to be declared nowhere (emx). > > > Also get this error which I've never seen before though I often have -lshm in programs > > /usr/X11R6/lib/shm.a(shm.o): Undefined symbol DosAllocSharedMem referenced from text segment > > /usr/X11R6/lib/shm.a(shm.o): Undefined symbol DosGetSharedMem referenced from text segment > > /usr/X11R6/lib/shm.a(shm.o): Undefined symbol DosFreeMem referenced from text segment > > Should be in one of the standard libraries (-los2?). Which gcc do you use? Where is the original source for SHM? > Bye, > Andreas -- John **= Email 6 ==========================** Date: Tue, 20 Apr 2004 20:42:27 +0100 From: John Poltorak Subject: Re: cygpath: not found On Tue, Apr 20, 2004 at 09:02:44PM +0200, Andreas Buening wrote: > John Poltorak wrote: > > > > On Mon, Apr 19, 2004 at 09:46:31PM +0200, Andreas Buening wrote: > > > So, I guess I need to run automake (1.7.6) before autoconf... > > I'd suggest the latest version you've installed. I did try 1.8.3 but have had a few problems with it... > Btw, I think we need something like a ux2bs FAQ or "known Bugs" > site since this kind of problem arises every few months. A FAQ would be an excellent idea, but I wouldn't know where to start with one... > Bye, > Andreas -- John **= Email 7 ==========================** Date: Tue, 20 Apr 2004 20:37:31 +0100 From: John Poltorak Subject: BYACC I've just become aware of a new version of BYACC which is available from:- ftp://invisible-island.net/byacc/byacc-20040328.tgz This one comes ready made for a normal GNU build & install, which I'm happy to report works perfectly well on OS/2. One difference I have made in my own environment is the addition of:- CFLAGS=-Zomf -O2 -s -Zmt -D__ST_MT_ERRNO__ LDFLAGS=-Zcrtdll -Zlinker /exepack:2 -Zlinker /pm:vio This results in yacc.exe being 37kB instead of 82kB. Is there any reason not to have the *FLAGS as a above? Any alternative suggestions for *FLAGS would be appreciated. -- John **= Email 8 ==========================** Date: Tue, 20 Apr 2004 22:59:15 +0200 From: Andreas Buening Subject: Re: cygpath: not found John Poltorak wrote: > A FAQ would be an excellent idea, but I wouldn't know where to start with > one... Every time you (or anybody else) raises a question that can be answered generally and could be also interesting for other people in the future the problem should be documented. E.g., ask Jeff to add a site like

Known bugs of the build system

....
  • cygpath not found

    • Fixed bugs

    ....

    cygpath not found

    Problem: I'm trying to compile package xyz and make prints a message about cygpath not found which looks like the following: 

    insert John's original posting _here_

    Reason: This is a known automake bug which was fixed with automake 1.7.x. It occurrs if you have set the compilation flags so that .obj files are produced. Therefore, automake assumes that you are using cygwin on Winxy and tries to use the cygpath tool.

    Rerun automake and maybe the other autotools on your source package (more information on the autotools)

    Bye, Andreas **= Email 9 ==========================** Date: Tue, 20 Apr 2004 22:59:40 +0200 From: Andreas Buening Subject: Re: BYACC John Poltorak wrote: > > I've just become aware of a new version of BYACC which is available from:- > > ftp://invisible-island.net/byacc/byacc-20040328.tgz > > This one comes ready made for a normal GNU build & install, which I'm > happy to report works perfectly well on OS/2. > > One difference I have made in my own environment is the addition of:- > > CFLAGS=-Zomf -O2 -s -Zmt -D__ST_MT_ERRNO__ > LDFLAGS=-Zcrtdll -Zlinker /exepack:2 -Zlinker /pm:vio > > This results in yacc.exe being 37kB instead of 82kB. > > Is there any reason not to have the *FLAGS as a above? > > Any alternative suggestions for *FLAGS would be appreciated. -Os instead of -O2 produces even slightly smaller files (only gcc 2.9.x or higher) Don't forget -Zstack. Many applications will crash occasionally without a reasonable stack. Formally, -D... is a preprocessor command and -s a linker command, so CPPFLAGS=-D__ST_MT_ERRNO__ CFLAGS=-Zomf -O2 -Zmt LDFLAGS=-s -Zcrtdll -Zlinker /exepack:2 -Zlinker /pm:vio -Zstack 0x6000 might be intended. Bye, Andreas **= Email 10 ==========================** Date: Tue, 20 Apr 2004 22:35:25 +0100 From: John Poltorak Subject: Re: BYACC On Tue, Apr 20, 2004 at 10:59:40PM +0200, Andreas Buening wrote: > John Poltorak wrote: > > > > I've just become aware of a new version of BYACC which is available from:- > > > > ftp://invisible-island.net/byacc/byacc-20040328.tgz > > > > This one comes ready made for a normal GNU build & install, which I'm > > happy to report works perfectly well on OS/2. > > > > One difference I have made in my own environment is the addition of:- > > > > CFLAGS=-Zomf -O2 -s -Zmt -D__ST_MT_ERRNO__ > > LDFLAGS=-Zcrtdll -Zlinker /exepack:2 -Zlinker /pm:vio > > > > This results in yacc.exe being 37kB instead of 82kB. > > > > Is there any reason not to have the *FLAGS as a above? > > > > Any alternative suggestions for *FLAGS would be appreciated. > > -Os instead of -O2 produces even slightly smaller files > (only gcc 2.9.x or higher) I've standardised on 2.8.1 at the moment, although hope to go to 3.2.2 in a few months time, once my build environment has built as many apps as it can handle. > Don't forget -Zstack. Many applications will crash occasionally > without a reasonable stack. I thought the default stacksize was 8MB if nothing was specified... I also read that you could specify a stacksize using GCCOPT=-Zstack=1000 so what would be wrong with setting it globally if the default was not appropriate? Stacksize itself is one of the great unknowns to me and I have no idea how to determine the optimum value for any app. > Formally, -D... is a preprocessor command I often see all these values defined under DEFS... > and -s a linker command, so > CPPFLAGS=-D__ST_MT_ERRNO__ > CFLAGS=-Zomf -O2 -Zmt > LDFLAGS=-s -Zcrtdll -Zlinker /exepack:2 -Zlinker /pm:vio -Zstack 0x6000 > might be intended. Well it would certainly be nice to set some standards. I'll incorporate these into my BYACC build, although I wonder if the /pm:vio could be set globally somehow. > > > Bye, > Andreas -- John **= Email 11 ==========================** Date: Tue, 20 Apr 2004 17:54:09 -0500 From: Jeff Robinson Subject: Re: cygpath: not found I'd be quite happy to maintain something like this... just this morning I updated the UnixOS2 pages somewhat and would like to expand it to have more information about UX2BS as well. I think it makes sense to keep everything more or less together, even if they are "separate" projects. On my last revision of the site I had made provisions for adding more information to each piece of software. ( Such as http://unixos2.com/pages/packages/GnuPG/index.html ). The only problem being that my time is somewhat limited right now so I don't always catch in the list what might need to be in the "Known Issues" portion for each piece of software. I'm interested in having the pages be a lot more helpful and hopefully take some of the load off people asking questions over and over. Jeff Andreas Buening wrote: > John Poltorak wrote: > > >>A FAQ would be an excellent idea, but I wouldn't know where to start with >>one... > > > Every time you (or anybody else) raises a question that can > be answered generally and could be also interesting for other > people in the future the problem should be documented. > > E.g., ask Jeff to add a site like > >

    Known bugs of the build system

    > > ... > >
  • cygpath not found
    • > > > > >

    Fixed bugs

    > > ... > >

    cygpath not found

    > >

    > Problem: I'm trying to compile package xyz and make prints a message > about cygpath not found which looks like the following: >

    > > 
    > insert John's original posting _here_
>
    > >

    > Reason: This is a known automake bug which was fixed with automake > 1.7.x. It occurrs if you have set the compilation flags so that .obj > files are produced. Therefore, automake assumes that you are using > cygwin on Winxy and tries to use the cygpath tool. >

    > >

    > Rerun automake and maybe the other autotools on your source package > (more information on the autotools) >

    > > > > Bye, > Andreas -- ---------------- Whatza JamochaMUD? http://jamochamud.anecho.mb.ca Or other stuff: http://www.anecho.mb.ca/~jeffnik ----------------------------------------------------------- **= Email 12 ==========================** Date: Tue, 20 Apr 2004 17:42:49 -0800 From: "Dave Yeo" Subject: Re: _wait3 On Tue, 20 Apr 2004 21:02:28 +0200, Andreas Buening wrote: >Dave Yeo wrote: >> >> Trying to build TightVNC I get a bunch of unresolved symbols. I know how to redefine most but not _wait3. Any ideas? > >Good question. I can link wait3() but it seems to be declared nowhere (emx). Hmm it doesn't link here and I can't find it declared anywhere. Its purpose is wait3(), wait4(). wait for process to terminate or stop and this is the code /* reap any zombies */ int status, pid; while ((pid= wait3(&status, WNOHANG, (struct rusage *)0))>0); Wonder if I can just comment it out? > >> Also get this error which I've never seen before though I often have -lshm in programs >> /usr/X11R6/lib/shm.a(shm.o): Undefined symbol DosAllocSharedMem referenced from text segment >> /usr/X11R6/lib/shm.a(shm.o): Undefined symbol DosGetSharedMem referenced from text segment >> /usr/X11R6/lib/shm.a(shm.o): Undefined symbol DosFreeMem referenced from text segment > >Should be in one of the standard libraries (-los2?). Which gcc do you use? I had changed shm.a (static link?) with one I have no memory of getting. Upon reverting to older shm.a the error vanished. Dave **= Email 13 ==========================** Date: Tue, 20 Apr 2004 17:51:18 -0800 From: "Dave Yeo" Subject: Re: _wait3 On Tue, 20 Apr 2004 20:39:13 +0100, John Poltorak wrote: >Where is the original source for SHM? http://os2ports.com/ftp/pub/os2/unix/xfree86/ports/libs/shm.zip Dave **= Email 14 ==========================** Date: Tue, 20 Apr 2004 18:07:40 -0800 From: "Dave Yeo" Subject: Re: BYACC On Tue, 20 Apr 2004 20:37:31 +0100, John Poltorak wrote: >One difference I have made in my own environment is the addition of:- > >CFLAGS=-Zomf -O2 -s -Zmt -D__ST_MT_ERRNO__ >LDFLAGS=-Zcrtdll -Zlinker /exepack:2 -Zlinker /pm:vio > >This results in yacc.exe being 37kB instead of 82kB. > >Is there any reason not to have the *FLAGS as a above? > >Any alternative suggestions for *FLAGS would be appreciated. The /exepack:2 is much the same as running lxlite on a binary. I'd suggest usually using -Zbin-files. This forces files to be opened in binary mode and often solves problems with ctrl-L vs ctrl-L+ctrl-M line endings For what its worth XFree86 imakefiles end up something like this CFLAGS=-D__UNIXOS2__ -O2 -fstrength-reduce -fpcc-struct-return -D__ST_MT_ERRNO -Zmtd -Zsysv-signals LDFLAGS=-D__UNIXOS2__ -O2 -fstrength-reduce -fpcc-struct-return -D__ST_MT_ERRNO -Zmtd -Zsysv-signals -Zbin-files. Some of these may be for debugging Also don't forget that -Zomf files have problems with forking. Dave **= Email 15 ==========================** Date: Wed, 21 Apr 2004 11:39:24 +0100 From: Stefan.Neis at t-online.de Subject: Re: BYACC Hi, > The /exepack:2 is much the same as running lxlite on a binary. I'd > suggest usually using -Zbin-files. This forces files to be opened in > binary mode and often solves problems with ctrl-L vs ctrl-L+ctrl-M line > endings. I'd rather _not_ add that by default. AFAIK, that results in just replacing one kind of problems with the other kind of problems - possibly less problems with files written by the program (if they are to be processed by other software) and more problems with files you try to read (if they've been modified with a "native" editor). Regards, Stefan **= Email 16 ==========================** Date: Wed, 21 Apr 2004 11:15:18 +0100 From: John Poltorak Subject: test -f foo.[cmd|exe] Does anyone know if I can use an expression like foo.[cmd|exe] with test to see if either foo.cmd or foo.exe exists? -- John **= Email 17 ==========================** Date: Wed, 21 Apr 2004 11:20:22 +0100 From: John Poltorak Subject: Re: BYACC On Tue, Apr 20, 2004 at 06:07:40PM -0800, Dave Yeo wrote: > >Any alternative suggestions for *FLAGS would be appreciated. > > The /exepack:2 is much the same as running lxlite on a binary. I'd suggest usually using -Zbin-files. This > forces files to be opened in binary mode and often solves problems with ctrl-L vs ctrl-L+ctrl-M line endings > For what its worth XFree86 imakefiles end up something like this > CFLAGS=-D__UNIXOS2__ -O2 -fstrength-reduce -fpcc-struct-return -D__ST_MT_ERRNO -Zmtd > -Zsysv-signals > LDFLAGS=-D__UNIXOS2__ -O2 -fstrength-reduce -fpcc-struct-return -D__ST_MT_ERRNO -Zmtd > -Zsysv-signals -Zbin-files. > Some of these may be for debugging Arghhh!!! Soooooo many options! > Also don't forget that -Zomf files have problems with forking. How do I know whether a program uses fork? If I do use -Zomf will the program fail to build or will it just not work as intended? > Dave -- John **= Email 18 ==========================** Date: Wed, 21 Apr 2004 12:54:15 +0100 From: John Poltorak Subject: Building wxWindows I've never managed to build wxWindows so I gave it another try today... Configure does not get rebuilt when using Autoconf v2.59 - this error occurs:- g:/ux2bs/workdir/wxBase-2.5.1 wxBase-2.5.1 Using:- autoconf (GNU Autoconf) 2.59 (release for OS/2) configure.in:5906: g:/ux2bs/bin/m4: Cannot open autoconf_inc.m4: No such file or directory autom4te: g:/ux2bs/bin/m4.exe failed with exit status: 1 Where does autoconf_inc.m4 originate? Since the provided configure script was already built with that version I guess it's no big deal. Configure runs OK and creates a Makefile, but when this runs it stops with:- make CHANGES.txt COPYING.LIB LICENCE.txt Makefile Makefile.in README.txt aclocal.m4 autom4te.cache bk-deps config.guess config.log config.status config.sub configarg.cache configure configure.in descrip.mms include install-sh lib locale mkinstalldirs samples setup.h.in setup.h_vms src version-script version-script.in wx-config wx-config.in wxBase.spec wxbase-2.5-config wxwin.m4 BUILDING with no parms CHANGES.txt COPYING.LIB LICENCE.txt Makefile Makefile.in README.txt aclocal.m4 autom4te.cache bk-deps config.guess config.log config.status config.sub configarg.cache configure configure.in descrip.mms include install-sh lib locale mkinstalldirs samples setup.h.in setup.h_vms src version-script version-script.in wx-config wx-config.in wxBase.spec wxbase-2.5-config wxwin.m4 ../bk-deps gcc -c -o wxzlib_adler32.o -Ilib/wx/include/base-2.5 -I./include -O2 -Zmt -D__ST_MT_ERRNO__ -Wall src/zlib/adler32.c SYS1034: The system cannot find the command processor in the path specified. OS/2 Command Interpreter version 4.5 I've seen something similar occur previously with other apps but can't think why. Does anyone know what is wrong here? -- John **= Email 19 ==========================** Date: Wed, 21 Apr 2004 14:05:52 +0100 From: John Poltorak Subject: Re: Vile build error On Mon, Apr 19, 2004 at 08:33:03PM +0100, John Poltorak wrote: > Is the latest version of VILE (9.4) buildableon OS/2? > > I just tried the usual autoconf/configure/make routine and it failed to > build vile.exe although 64 executables do get created in the FILTERS > directory. > > This is the error at the time that the build falls over:- > spawn.c: In function `bktoshell': > spawn.c:228: too many arguments to function `getpgrp' > make: *** [spawn.o] Error 1 I've tried building it again, this time without Posix/2 and it does work now. It looks like Posix/2 has a problem with [set|get]pgrp... -- John **= Email 20 ==========================** Date: Wed, 21 Apr 2004 20:20:44 +1000 (EST) From: Andrew MacIntyre Subject: Re: BYACC On Tue, 20 Apr 2004, John Poltorak wrote: > > Don't forget -Zstack. Many applications will crash occasionally > > without a reasonable stack. > > I thought the default stacksize was 8MB if nothing was specified... Only for a.out. Its much smaller (4k or 8k I think) for -Zomf. -- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andymac at bullseye.apana.org.au (pref) | Snail: PO Box 370 andymac at pcug.org.au (alt) | Belconnen ACT 2616 Web: http://www.andymac.org/ | Australia