Date: Fri, 14 Feb 2003 02:34:47 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [Ux2bs_Archive] No. 77 ************************************************** Thursday 13 February 2003 Number 77 ************************************************** Subjects for today 1 Re: perl module problem : Henry Sobotka 2 Re: Building UNZIP : Stefan.Neis at t-online.de 3 Re: Building UNZIP : John Poltorak 4 Re: perl module problem : Henry Sobotka 5 Unzip550, "bug" in os2/makefile.os2 : Stefan.Neis at t-online.de 6 Unzip550, "bug" in os2/makefile.os2 : Stefan.Neis at t-online.de 7 Unzip550, "bug" in os2/makefile.os2 : Stefan.Neis at t-online.de 8 Unzip550, "bug" in os2/makefile.os2 : Stefan.Neis at t-online.de 9 perl module problem : Dave Saville" 10 Re: Building UNZIP : Stefan.Neis at t-online.de 11 Building An Open-Source Application : Hakan" 12 Re: Building An Open-Source Application : Hakan" 13 Re: perl module problem : Dave Saville" 14 Re: Building UNZIP : John Poltorak 15 Re: perl module problem : Henry Sobotka 16 Re: CVS : John Poltorak 17 Re: perl module problem : Dave Saville" 18 Re: Building An Open-Source Application : John Poltorak 19 Re: Building An Open-Source Application : John Poltorak 20 Re: CVS : Andrew Belov" **= Email 1 ==========================** Date: Fri, 14 Feb 2003 09:26:58 -0500 From: Henry Sobotka Subject: Re: perl module problem Try using: at SET PERLLIB_PREFIX=e:/usr/lib/perl/lib;D:\usr\lib\perl\lib (slashes for original build, backslashes for new location). h~ _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 2 ==========================** Date: Fri, 14 Feb 2003 11:43:48 +0100 From: Stefan.Neis at t-online.de Subject: Re: Building UNZIP Hi, > gcc -Zomf -O -I. -c -Wall -DOS2 -DASM_CRC DLLFLAG= -DFUNZIP -ocryptf.obj crypt.c > gcc: cannot specify -o with -c and multiple compilations That one really does look like a an error in makefile.os2, all those lines containing OUT="-o" \ for gcc have to read OUT="-o " \ (Note the additional space!). With that change, the above command line expands to gcc -Zomf .... -o cryptf.obj crypt.c which gcc will treat as an "-o filename" option instead of parsing it as "-o_and_several_other_options". Regards, Stefan _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 3 ==========================** Date: Fri, 14 Feb 2003 11:43:53 +0000 From: John Poltorak Subject: Re: Building UNZIP On Fri, Feb 14, 2003 at 11:43:48AM +0100, Stefan.Neis at t-online.de wrote: > Hi, > > > gcc -Zomf -O -I. -c -Wall -DOS2 -DASM_CRC DLLFLAG= -DFUNZIP -ocryptf.obj crypt.c > > gcc: cannot specify -o with -c and multiple compilations > > That one really does look like a an error in makefile.os2, One wonders if it was ever tested. > all those lines > containing > OUT="-o" \ > for gcc have to read > OUT="-o " \ (Note the additional space!). > With that change, the above command line expands to > gcc -Zomf .... -o cryptf.obj crypt.c > which gcc will treat as an "-o filename" option instead of parsing it as > "-o_and_several_other_options". I don't think that is the error. When I rearranged the targets and put UNZIPSFX.EXE first, that built OK. This is what happened:- make -f os2/makefile.os2 all \ CC="gcc -Zomf -O -I." \ CFLAGS="-Wall -DOS2 -DASM_CRC " \ NFLAGS="" \ DLLFLAG="" \ AS="gcc -Zomf" \ ASFLAGS="-Di386" \ LDFLAGS="-o ./" \ LDFLAGS2="-Zsmall-conv -Zstack 320 -Zsys -s" \ OUT="-o" \ OBJ=".obj" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ CRC32X="crc_gcc" \ DEF="os2/unzip.def" make[1]: Entering directory `U:/unixos2/workdir/unzip-5.50' gcc -Zomf -O -I. -c -Wall -DOS2 -DASM_CRC -DSFX -ounzipsf_.obj unzip.c gcc -Zomf -O -I. -c -Wall -DOS2 -DASM_CRC -DSFX -ocrctab_.obj crctab.c gcc -Zomf -O -I. -c -Wall -DOS2 -DASM_CRC -DSFX -ocrypt_.obj crypt.c gcc -Zomf -O -I. -c -Wall -DOS2 -DASM_CRC -DSFX -oextract_.obj extract.c gcc -Zomf -O -I. -c -Wall -DOS2 -DASM_CRC -DSFX -ofileio_.obj fileio.c gcc -Zomf -O -I. -c -Wall -DOS2 -DASM_CRC -DSFX -oglobals_.obj globals.c gcc -Zomf -O -I. -c -Wall -DOS2 -DASM_CRC -DSFX -oinflate_.obj inflate.c gcc -Zomf -O -I. -c -Wall -DOS2 -DASM_CRC -DSFX -omatch_.obj match.c gcc -Zomf -O -I. -c -Wall -DOS2 -DASM_CRC -DSFX -oprocess_.obj process.c gcc -Zomf -O -I. -c -Wall -DOS2 -DASM_CRC -DSFX -ottyio_.obj ttyio.c gcc -Zomf -O -I. -c -Wall -DOS2 -DASM_CRC -DSFX -oos2_.obj os2/os2.c gcc -Zomf -O -I. -c -Wall -DOS2 -DASM_CRC -DSFX -oos2acl_.obj os2/os2acl.c gcc -Zomf -O -I. -o ./unzipsfx.exe os2/unzip.def unzipsf_.obj crc_gcc.obj crctab_.obj crypt_.obj extract_.obj fileio_.obj globals_.obj inflate_.obj match_.obj process_.obj ttyio_.obj os2_.obj os2acl_.obj -Zsmall-conv -Zstack 320 -Zsys -s gcc -Zomf -O -I. -c -Wall -DOS2 -DASM_CRC DLLFLAG= -DFUNZIP -ocryptf.obj crypt.c gcc: cannot specify -o with -c and multiple compilations make[1]: *** [cryptf.obj] Error 1 make[1]: Leaving directory `U:/unixos2/workdir/unzip-5.50' make: *** [gcc] Error 2 To me, it looks like the 'DLLFLAG=' string is misplaced, but don't understand how this could have arisen... > Regards, > Stefan -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 4 ==========================** Date: Fri, 14 Feb 2003 12:16:44 -0500 From: Henry Sobotka Subject: Re: perl module problem Dave Saville wrote: > > No difference Have you run the testperl.cmd that came with earlier versions of Perl? It might turn up a clue to what the problem is. h~ _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 5 ==========================** Date: Fri, 14 Feb 2003 12:23:39 +0100 From: Stefan.Neis at t-online.de Subject: Unzip550, "bug" in os2/makefile.os2 Hi there, In case nobody noted/reported it yet, it looks like os2/makefile.os2 in unzip550.zip got caught in a famous trap for supporting multiple compilers, namely that specifying an output file name requires spaces between flag and output file name on some compilers (notably gcc: -o filename) and disallows space for other compilers(namely any MSC based thing: /Fofilename) So when you're using $(OUT)$ at in the build rules, the "obvious" work-around is to include the space in the definition of the makefile variable OUT. Unfortunately, this doesn't happen in os2/makefile.os2 for any target using gcc. There are two possible fixes: Ommit $(OUT)$ at completely (at least gcc is clever enough to figure out the name of the object file itself and $(OUT)$ at isn't even consistently used anyway), or changing the "wrong" definitions of OUT (adding a space at the end). I slightly prefer the latter, so I'm adding the trivial patch to that effect to this mail. Kind regards and keep up the good work, Stefan Neis ------- Patch for os2/makefile.os2 ------------------- --- makefile.org Sat Nov 10 22:19:00 2001 +++ makefile.os2 Fri Feb 14 12:08:12 2003 at at -399,7 +399,7 at at ASFLAGS="-Di386" \ LDFLAGS="-o ./" \ LDFLAGS2="-Zsmall-conv -Zstack 320 -Zsys -s" \ - OUT="-o" \ + OUT="-o " \ OBJ=".obj" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ at at -417,7 +417,7 at at ASFLAGS="-Di386" \ LDFLAGS="-o ./" \ LDFLAGS2="-Zstack 320 -Zcrtdll -s" \ - OUT="-o" \ + OUT="-o " \ OBJ=".obj" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ at at -435,7 +435,7 at at ASFLAGS="-Di386" \ LDFLAGS="-o ./" \ LDFLAGS2="-Zsmall-conv" \ - OUT="-o" \ + OUT="-o " \ OBJ=".o" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ at at -452,7 +452,7 at at ASFLAGS="-Di386" \ LDFLAGS="-o ./" \ LDFLAGS2="-Zsmall-conv -s" \ - OUT="-o" \ + OUT="-o " \ OBJ=".o" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ at at -472,7 +472,7 at at ASFLAGS="-Di386" \ LDFLAGS="-Zsys -o ./" \ LDFLAGS2="-ladvapi32 -Zsmall-conv -s" \ - OUT="-o" \ + OUT="-o " \ OBJ=".o" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ cc: ux2bs at powerusersbbs.net _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 6 ==========================** Date: Fri, 14 Feb 2003 12:23:39 +0100 From: Stefan.Neis at t-online.de Subject: Unzip550, "bug" in os2/makefile.os2 Hi there, In case nobody noted/reported it yet, it looks like os2/makefile.os2 in unzip550.zip got caught in a famous trap for supporting multiple compilers, namely that specifying an output file name requires spaces between flag and output file name on some compilers (notably gcc: -o filename) and disallows space for other compilers(namely any MSC based thing: /Fofilename) So when you're using $(OUT)$ at in the build rules, the "obvious" work-around is to include the space in the definition of the makefile variable OUT. Unfortunately, this doesn't happen in os2/makefile.os2 for any target using gcc. There are two possible fixes: Ommit $(OUT)$ at completely (at least gcc is clever enough to figure out the name of the object file itself and $(OUT)$ at isn't even consistently used anyway), or changing the "wrong" definitions of OUT (adding a space at the end). I slightly prefer the latter, so I'm adding the trivial patch to that effect to this mail. Kind regards and keep up the good work, Stefan Neis ------- Patch for os2/makefile.os2 ------------------- --- makefile.org Sat Nov 10 22:19:00 2001 +++ makefile.os2 Fri Feb 14 12:08:12 2003 at at -399,7 +399,7 at at ASFLAGS="-Di386" \ LDFLAGS="-o ./" \ LDFLAGS2="-Zsmall-conv -Zstack 320 -Zsys -s" \ - OUT="-o" \ + OUT="-o " \ OBJ=".obj" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ at at -417,7 +417,7 at at ASFLAGS="-Di386" \ LDFLAGS="-o ./" \ LDFLAGS2="-Zstack 320 -Zcrtdll -s" \ - OUT="-o" \ + OUT="-o " \ OBJ=".obj" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ at at -435,7 +435,7 at at ASFLAGS="-Di386" \ LDFLAGS="-o ./" \ LDFLAGS2="-Zsmall-conv" \ - OUT="-o" \ + OUT="-o " \ OBJ=".o" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ at at -452,7 +452,7 at at ASFLAGS="-Di386" \ LDFLAGS="-o ./" \ LDFLAGS2="-Zsmall-conv -s" \ - OUT="-o" \ + OUT="-o " \ OBJ=".o" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ at at -472,7 +472,7 at at ASFLAGS="-Di386" \ LDFLAGS="-Zsys -o ./" \ LDFLAGS2="-ladvapi32 -Zsmall-conv -s" \ - OUT="-o" \ + OUT="-o " \ OBJ=".o" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ cc: ux2bs at powerusersbbs.net _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 7 ==========================** Date: Fri, 14 Feb 2003 12:23:39 +0100 From: Stefan.Neis at t-online.de Subject: Unzip550, "bug" in os2/makefile.os2 Hi there, In case nobody noted/reported it yet, it looks like os2/makefile.os2 in unzip550.zip got caught in a famous trap for supporting multiple compilers, namely that specifying an output file name requires spaces between flag and output file name on some compilers (notably gcc: -o filename) and disallows space for other compilers(namely any MSC based thing: /Fofilename) So when you're using $(OUT)$ at in the build rules, the "obvious" work-around is to include the space in the definition of the makefile variable OUT. Unfortunately, this doesn't happen in os2/makefile.os2 for any target using gcc. There are two possible fixes: Ommit $(OUT)$ at completely (at least gcc is clever enough to figure out the name of the object file itself and $(OUT)$ at isn't even consistently used anyway), or changing the "wrong" definitions of OUT (adding a space at the end). I slightly prefer the latter, so I'm adding the trivial patch to that effect to this mail. Kind regards and keep up the good work, Stefan Neis ------- Patch for os2/makefile.os2 ------------------- --- makefile.org Sat Nov 10 22:19:00 2001 +++ makefile.os2 Fri Feb 14 12:08:12 2003 at at -399,7 +399,7 at at ASFLAGS="-Di386" \ LDFLAGS="-o ./" \ LDFLAGS2="-Zsmall-conv -Zstack 320 -Zsys -s" \ - OUT="-o" \ + OUT="-o " \ OBJ=".obj" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ at at -417,7 +417,7 at at ASFLAGS="-Di386" \ LDFLAGS="-o ./" \ LDFLAGS2="-Zstack 320 -Zcrtdll -s" \ - OUT="-o" \ + OUT="-o " \ OBJ=".obj" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ at at -435,7 +435,7 at at ASFLAGS="-Di386" \ LDFLAGS="-o ./" \ LDFLAGS2="-Zsmall-conv" \ - OUT="-o" \ + OUT="-o " \ OBJ=".o" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ at at -452,7 +452,7 at at ASFLAGS="-Di386" \ LDFLAGS="-o ./" \ LDFLAGS2="-Zsmall-conv -s" \ - OUT="-o" \ + OUT="-o " \ OBJ=".o" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ at at -472,7 +472,7 at at ASFLAGS="-Di386" \ LDFLAGS="-Zsys -o ./" \ LDFLAGS2="-ladvapi32 -Zsmall-conv -s" \ - OUT="-o" \ + OUT="-o " \ OBJ=".o" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ cc: ux2bs at powerusersbbs.net _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 8 ==========================** Date: Fri, 14 Feb 2003 12:23:39 +0100 From: Stefan.Neis at t-online.de Subject: Unzip550, "bug" in os2/makefile.os2 Hi there, In case nobody noted/reported it yet, it looks like os2/makefile.os2 in unzip550.zip got caught in a famous trap for supporting multiple compilers, namely that specifying an output file name requires spaces between flag and output file name on some compilers (notably gcc: -o filename) and disallows space for other compilers(namely any MSC based thing: /Fofilename) So when you're using $(OUT)$ at in the build rules, the "obvious" work-around is to include the space in the definition of the makefile variable OUT. Unfortunately, this doesn't happen in os2/makefile.os2 for any target using gcc. There are two possible fixes: Ommit $(OUT)$ at completely (at least gcc is clever enough to figure out the name of the object file itself and $(OUT)$ at isn't even consistently used anyway), or changing the "wrong" definitions of OUT (adding a space at the end). I slightly prefer the latter, so I'm adding the trivial patch to that effect to this mail. Kind regards and keep up the good work, Stefan Neis ------- Patch for os2/makefile.os2 ------------------- --- makefile.org Sat Nov 10 22:19:00 2001 +++ makefile.os2 Fri Feb 14 12:08:12 2003 at at -399,7 +399,7 at at ASFLAGS="-Di386" \ LDFLAGS="-o ./" \ LDFLAGS2="-Zsmall-conv -Zstack 320 -Zsys -s" \ - OUT="-o" \ + OUT="-o " \ OBJ=".obj" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ at at -417,7 +417,7 at at ASFLAGS="-Di386" \ LDFLAGS="-o ./" \ LDFLAGS2="-Zstack 320 -Zcrtdll -s" \ - OUT="-o" \ + OUT="-o " \ OBJ=".obj" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ at at -435,7 +435,7 at at ASFLAGS="-Di386" \ LDFLAGS="-o ./" \ LDFLAGS2="-Zsmall-conv" \ - OUT="-o" \ + OUT="-o " \ OBJ=".o" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ at at -452,7 +452,7 at at ASFLAGS="-Di386" \ LDFLAGS="-o ./" \ LDFLAGS2="-Zsmall-conv -s" \ - OUT="-o" \ + OUT="-o " \ OBJ=".o" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ at at -472,7 +472,7 at at ASFLAGS="-Di386" \ LDFLAGS="-Zsys -o ./" \ LDFLAGS2="-ladvapi32 -Zsmall-conv -s" \ - OUT="-o" \ + OUT="-o " \ OBJ=".o" \ CRC32="crc_gcc" \ CRC32F="crc_gcc" \ cc: ux2bs at powerusersbbs.net _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 9 ==========================** Date: Fri, 14 Feb 2003 13:10:39 +0000 (GMT) From: "Dave Saville" Subject: perl module problem I am trying to use the newly built perl to install a perl module. I copied the perl tree onto my prod drive. So it is on D: not E: Here is the command I run to get perl580 (I have two versions of perl installed) at SET PERLLIB_PREFIX=e:/usr/lib/perl/lib;D:/usr/lib/perl/lib at SET PERLLIB=d:/usr/lib/perl/lib/5.8.0/os2;d:/usr/lib/perl/lib/5.8.0;d:/usr /lib/perl/lib/site_perl/5.8.0/os2;d:/usr/lib/perl/lib/site_perl/5.8.0; d:/usr/lib/perl/lib/site_perl at SET PERL_SH_DIR=D:\BIN perl.exe %1 %2 %3 %4 %5 %6 %7 %8 %9 Now when I run perl58,cmd makefile.pl I get: [D:\home\db\Programming\C\ClipBoard\perl]perl58 makefile.pl [D:\home\db\Programming\C\ClipBoard\perl]perl.exe makefile.pl Unable to find a perl 5 (by these names: D:/USR/BIN/PERL.EXE perl.exe perl5.exe perl5.8.0.exe miniperl.exe, in these dirs: C:/MPTN/BIN C:/IBMCOM D:/apps/NETSCAPE/PROGRAM C:/IBMLAN/NETPROG C:/MUGLIB C:/OS2C:/OS2/SYSTEM C:/OS2/MDOS/WINOS2 C:/OS2/INSTALL C:/ C:/OS2/MDOS C:/OS2/APPS C:/MMOS2 C:/NSC C:/tcpip/bin C:/tcpip/pcomos2 D:/BIN D:/USR/BIN D:/USR/LOCAL/BIN D:/EMX/BIN /APPS/PGP D:/PROGRAMMING/REXX/VREXX2 D:/XFREE86/BIN D:/APPS/READIBM2 D:/apps/ure/Toolkit/Beta/Bin C:/SIO2k D:/Apps/Office51 C:/JAVA11/ICATJAVA/BIN C:/JAVA11/BIN C:/ODIN32/SYSTEM32 d:/apps/norman/nvc/bin D:/apps/watchcat e:/usr/lib/perl/bin) Have d:/usr/lib/perl/lib/5.8.0/os2/Config.pm expected e:/usr/lib/perl/lib/5.8.0/os2/Config.pm Your perl and your Config.pm seem to have different ideas about the architecture they are running on. Perl thinks: [os2] Config says: [os2] This may or may not cause problems. Please check your installation of perl if you have problems building this extension. Unrecognized argument in LIBS ignored: 'user32.lib' Note (probably harmless): No library found for -lsocket Note (probably harmless): No library found for -lm Note (probably harmless): No library found for -lbsd Running '0 "-Ie:/usr/lib/perl/lib/5.8.0" e:/usr/lib/perl/lib/5.8.0/ExtUtils/xsub pp -v 2>&1' exits with status 16777215 at d:/usr/lib/perl/lib/5.8.0/ExtUtils/MM_ Unix.pm line 3826. Running '0 e:/usr/lib/perl/lib/5.8.0/ExtUtils/xsubpp temp000 2>&1' exits with st atus 16777215 at d:/usr/lib/perl/lib/5.8.0/ExtUtils/MM_Unix.pm line 3852. Here is makefile.PL - I am trying to port the windows clipboard module to OS/2 use ExtUtils::MakeMaker; use Config; WriteMakefile( 'NAME' => 'OS2::Clipboard', 'VERSION_FROM' => 'Clipboard.pm', 'dist' => { COMPRESS => 'gzip -9f', SUFFIX => 'gz'}, 'XS' => { 'Clipboard.xs' => 'Clipboard.cpp' }, 'LIBS' => ( $BORLAND ? 'import32.lib cw32mti.lib' : 'user32.lib' ), ($] < 5.005 ? () : ( 'AUTHOR' => 'Dave Saville 'Interaction with the Windows clipboard based on Win32::Clipboard by Aldo Calpini ', )), ); sub MY::xs_c { ' .xs.cpp: $(PERL) -I$(PERL_ARCHLIB) -I$(PERL_LIB) $(XSUBPP) $(XSPROTOARG)$(XSUBPPARGS) $*.xs >xstmp.c && $(MV) xstmp.c $*.cpp '; } And no I don't know what I am doing :-) -- Regards Dave Saville _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 10 ==========================** Date: Fri, 14 Feb 2003 13:20:03 +0100 From: Stefan.Neis at t-online.de Subject: Re: Building UNZIP > gcc -Zomf -O -I. -c -Wall -DOS2 -DASM_CRC DLLFLAG= -DFUNZIP -ocryptf.obj > crypt.c > gcc: cannot specify -o with -c and multiple compilations > > To me, it looks like the 'DLLFLAG=' string is misplaced, but don't > understand how this could have arisen... Exactly. Sorry, I didn't note that one (no such problem over here!) and apparently gcc is perfectly able to cope without the space between "-o" and the filename - at least on OS/2. My only guess is that your make (which version?) has a bug and doesn't interpret > NFLAGS="" \ > DLLFLAG="" \ as setting both the variable NFLAGS and DLLFLAG to nothing but as setting NFLAGS to the string "DLLFLAG=" (as $(NFLAGS) is occuring in precisely that rule at the location where "DLLFLAG=" mysteriously appears. The only "fix" I see is trying a different version of make (old GNUmake 3.75 works for me). (Or you can simply remove $(NFLAGS) from the rules for building crypt$(OBJ), cryptf$(OBJ) and ttyiof$(OBJ) as that flag is supposed to work around a "IBM C++ Set" specific bug, so it's not really relevant for us. That should improve things as well). Andreas, any suggestions/ideas? Regards, Stefan _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 11 ==========================** Date: Fri, 14 Feb 2003 13:23:42 -0500 (EST) From: "Hakan" Subject: Building An Open-Source Application I would like to try my hand at building an open-source application which has not been made available for OS/2 (swish-e version 2) but being new to this environment, I need some help to get started. According to the docs for this app, I should first run ./CONFIGURE and then make etc. What is ./CONFIGURE, what does it do, what is the OS/2 substitute and what do I need to do? TIA. Hakan _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 12 ==========================** Date: Fri, 14 Feb 2003 14:04:34 -0500 (EST) From: "Hakan" Subject: Re: Building An Open-Source Application On Fri, 14 Feb 2003 18:44:37 +0000, John Poltorak wrote: >On Fri, Feb 14, 2003 at 01:23:42PM -0500, Hakan wrote: >> I would like to try my hand at building an open-source application >> which has not been made available for OS/2 (swish-e version 2) but >> being new to this environment, I need some help to get started. > >Do you have a source for this app? Yes, the website is www.swish-e.org. Version 1 of swish-e has been ported to OS/2 and I am running it successfully, version 2, however, does not seem to have been ported. >> According to the docs for this app, I should first run ./CONFIGURE and >> then make etc. What is ./CONFIGURE, what does it do, what is the OS/2 >> substitute and what do I need to do? > >On Unix you normally only have to run configure, make and make install. > >This mailing list is basically about producing an environment which allows >you to build things on OS/2 just as easily, and in many case things do >build with no trouble at all. > >Currently, most configure scripts are not capable of running correctly on >OS/2, so they need to be recreated by running autoconf. > >Essentially the UnixOS/2 Build System is simply a wrapper which runs >autoconf, configure, make and make install, when you run:- > >build APPLICATION > >Unfortunately, not all apps follow this process, so there is quite a bit >of exception handling built. > >If you have been following things on the list and have managed to build >Perl successfully, you are well on the way to having a reasonable build >environment. The next thing you need to do after building Perl is to run >update_base.cmd which ought to build a number of missing pieces from the >jigsaw. If that runs successfully, then you will have installed autoconf >and automake and you will be ready to tackle most other apps. OK, will try update_base.cmd as the next step. Thanks. Hakan >> TIA. >> >> Hakan > > >-- >John > > > > >_______________________________________________ >UX2BS mailing list >UX2BS at powerusersbbs.net >http://powerusersbbs.net/mailman/listinfo/ux2bs > > _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 13 ==========================** Date: Fri, 14 Feb 2003 14:46:31 +0000 (GMT) From: "Dave Saville" Subject: Re: perl module problem On Fri, 14 Feb 2003 09:26:58 -0500, Henry Sobotka wrote: > at SET PERLLIB_PREFIX=e:/usr/lib/perl/lib;D:\usr\lib\perl\lib No difference -- Regards Dave Saville _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 14 ==========================** Date: Fri, 14 Feb 2003 15:09:33 +0000 From: John Poltorak Subject: Re: Building UNZIP On Fri, Feb 14, 2003 at 01:20:03PM +0100, Stefan.Neis at t-online.de wrote: > > gcc -Zomf -O -I. -c -Wall -DOS2 -DASM_CRC DLLFLAG= -DFUNZIP -ocryptf.obj > > crypt.c > > gcc: cannot specify -o with -c and multiple compilations > > > > To me, it looks like the 'DLLFLAG=' string is misplaced, but don't > > understand how this could have arisen... > > Exactly. Sorry, I didn't note that one (no such problem over here!) and > apparently gcc is perfectly able to cope without the space between > "-o" and the filename - at least on OS/2. > My only guess is that your make (which version?) has a bug and doesn't > interpret > > NFLAGS="" \ > > DLLFLAG="" \ Just tried with Make v3.76.1 and it's OK, so it looks as though there is a bug in Make v3.79.1. > Andreas, any suggestions/ideas? Maybe Andreas can confirm this... > Regards, > Stefan > -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 15 ==========================** Date: Fri, 14 Feb 2003 15:47:06 -0500 From: Henry Sobotka Subject: Re: perl module problem Dave Saville wrote: > > What the *% at ! is it doing running MM_Unix.pm? Surely it should be > MM_OS2.pm? MM_OS2.pm overrides some of the methods in MM_Unix.pm; the problem is likely occurring in one that doesn't get overridden, and it may just be a side-effect of not being able to find perl in the first place. h~ _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 16 ==========================** Date: Fri, 14 Feb 2003 16:23:22 +0000 From: John Poltorak Subject: Re: CVS On Mon, Feb 03, 2003 at 10:23:23PM +0300, Andrew Belov wrote: > On Mon, 3 Feb 2003 17:50:22 +0000, John Poltorak wrote: > > >> The "EMX-new" CVS v 1.11.5 compiles fine now. > > > >What steps did you go through to compile it? > > Basically I just applied the 1.11 EMX-new patches - but there were some > conflicts so upgrading to 1.11.5 is not as trivial as it seems to be. I have just had a look at it and am very confused... It looks as though many of the patches in DIFFS are related to CONFIGURE, but they wouldn't be required is starting from Autoconf... Also there are patches for Changelog which I would expect to be in the original source along with changes relating to zlib. I don't understand why they are necessary. Also, are the patches meant to provide a means of building everything which is in src\emx-new.ZIP? (BTW BUILD mentions emx-new.arj). Is there any documentation on the version of RSHD provided? How does it differ from IBM's RSHD.EXE? Can it be used as a replacement? IBM's RSHD is a single threaded app AFAIK, so it only supports one remote shell at a time. Is this one the same? There is some mention of needing to use TOUCH.EXE from GNU File Utils v4, although you do provide a copy. What are the nature of this newer time format? -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 17 ==========================** Date: Fri, 14 Feb 2003 17:32:41 +0000 (GMT) From: "Dave Saville" Subject: Re: perl module problem I am getting somewhere. Fixed perllib_prefix and did a global change down config.pm to change E: to D: Now I get [D:\home\db\Programming\C\ClipBoard\perl]perl.exe makefile.pl Unable to find a perl 5 (by these names: D:/USR/BIN/PERL.EXE perl.exe perl5.exe perl5.8.0.exe miniperl.exe, in these dirs: C:/MPTN/BIN C:/IBMCOM D:/apps/NETSCAP E/PROGRAM C:/IBMLAN/NETPROG C:/MUGLIB C:/OS2 C:/OS2/SYSTEM C:/OS2/MDOS/WINOS2 C: /OS2/INSTALL C:/ C:/OS2/MDOS C:/OS2/APPS C:/MMOS2 C:/NSC C:/tcpip/bin C:/tcpip/p comos2 D:/BIN D:/USR/BIN D:/USR/LOCAL/BIN D:/EMX/BIN /APPS/PGP D:/PROGRAMMING/RE XX/VREXX2 D:/XFREE86/BIN D:/APPS/READIBM2 D:/apps/ure/Toolkit/Beta/Bin C:/SIO2k D:/Apps/Office51 C:/JAVA11/ICATJAVA/BIN C:/JAVA11/BIN C:/ODIN32/SYSTEM32 d:/apps /norman/nvc/bin D:/apps/watchcat D:/usr/lib/perl/bin) Running '0 "-ID:/usr/lib/perl/lib/5.8.0" D:/usr/lib/perl/lib/5.8.0/ExtUtils/xsub pp -v 2>&1' exits with status 16777215 at D:/usr/lib/perl/lib/5.8.0/ExtUtils/MM_ Unix.pm line 3826. Running '0 D:/usr/lib/perl/lib/5.8.0/ExtUtils/xsubpp temp000 2>&1' exits with st atus 16777215 at D:/usr/lib/perl/lib/5.8.0/ExtUtils/MM_Unix.pm line 3852. Writing Makefile for OS2::Clipboard What the *% at ! is it doing running MM_Unix.pm? Surely it should be MM_OS2.pm? -- Regards Dave Saville _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 18 ==========================** Date: Fri, 14 Feb 2003 18:44:37 +0000 From: John Poltorak Subject: Re: Building An Open-Source Application On Fri, Feb 14, 2003 at 01:23:42PM -0500, Hakan wrote: > I would like to try my hand at building an open-source application > which has not been made available for OS/2 (swish-e version 2) but > being new to this environment, I need some help to get started. Do you have a source for this app? > According to the docs for this app, I should first run ./CONFIGURE and > then make etc. What is ./CONFIGURE, what does it do, what is the OS/2 > substitute and what do I need to do? On Unix you normally only have to run configure, make and make install. This mailing list is basically about producing an environment which allows you to build things on OS/2 just as easily, and in many case things do build with no trouble at all. Currently, most configure scripts are not capable of running correctly on OS/2, so they need to be recreated by running autoconf. Essentially the UnixOS/2 Build System is simply a wrapper which runs autoconf, configure, make and make install, when you run:- build APPLICATION Unfortunately, not all apps follow this process, so there is quite a bit of exception handling built. If you have been following things on the list and have managed to build Perl successfully, you are well on the way to having a reasonable build environment. The next thing you need to do after building Perl is to run update_base.cmd which ought to build a number of missing pieces from the jigsaw. If that runs successfully, then you will have installed autoconf and automake and you will be ready to tackle most other apps. > TIA. > > Hakan -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 19 ==========================** Date: Fri, 14 Feb 2003 19:30:13 +0000 From: John Poltorak Subject: Re: Building An Open-Source Application On Fri, Feb 14, 2003 at 02:04:34PM -0500, Hakan wrote: > On Fri, 14 Feb 2003 18:44:37 +0000, John Poltorak wrote: > > >On Fri, Feb 14, 2003 at 01:23:42PM -0500, Hakan wrote: > >> I would like to try my hand at building an open-source application > >> which has not been made available for OS/2 (swish-e version 2) but > >> being new to this environment, I need some help to get started. > > > >Do you have a source for this app? > > Yes, the website is www.swish-e.org. Version 1 of swish-e has been > ported to OS/2 and I am running it successfully, version 2, however, > does not seem to have been ported. Are there any patches available for it? Sometimes the source code may need to be changed, although many patches I see are more related to configure scripts or Makefiles rather than the actual program source. > >If you have been following things on the list and have managed to build > >Perl successfully, you are well on the way to having a reasonable build > >environment. The next thing you need to do after building Perl is to run > >update_base.cmd which ought to build a number of missing pieces from the > >jigsaw. If that runs successfully, then you will have installed autoconf > >and automake and you will be ready to tackle most other apps. > > OK, will try update_base.cmd as the next step. I just tried swish-e and it doesn't build. If I run autoconf first, then it creates a configure script which aborts. This has happened a few times recently, and may well be due to a bug in Autoconf... Just running the supplied configure results in failure because there is no regex.h. That is something which a number of apps require, so I will need to build regex as part of update_base.cmd at some point soon. > Thanks. > > Hakan -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 20 ==========================** Date: Fri, 14 Feb 2003 22:42:01 +0300 (MSK) From: "Andrew Belov" Subject: Re: CVS On Fri 14 Feb 03, 16:23:22 +0000, John Poltorak wrote: >I have just had a look at it and am very confused... > >It looks as though many of the patches in DIFFS are related to CONFIGURE, >but they wouldn't be required is starting from Autoconf... Well, this is due to the fact that CVS is developed using CVS itself. Two "vendor branches" are running and the patches are created by comparing the "cvs-os2" branch against a tagged revision of the original code, so everything that differs would flow into the patch file. >Also there are patches for Changelog which I would expect to be in the >original source along with changes relating to zlib. I don't understand >why they are necessary. That's normal - given that only the "$Id$" markers mismatch. Obviously, they may be selectively disabled with "-kkv", but I don't see much advantage in hunting for "$Id$"`s. >Also, are the patches meant to provide a means of building everything >which is in src\emx-new.ZIP? (BTW BUILD mentions emx-new.arj). CVS is packed with ARJ for the purpose of local distribution; I only repackage it with ZIP when I intend to upload it to public OS/2 sites. ARJ has gone GPL open-source last year, so it may be freely downloaded from http://arj.sourceforge.net. >Is there any documentation on the version of RSHD provided? How does it >differ from IBM's RSHD.EXE? Can it be used as a replacement? IBM's RSHD is >a single threaded app AFAIK, so it only supports one remote shell at a >time. Is this one the same? Little is known about its origins, remember that I'm already the 3rd or 4th maintainer of the EMX-new branch. It's designed to be interchangeable with IBM's RSHD when deployed by means of INETD. This way it imposes no restrictions on the number of sessions served simultaneosly. It uses the same initialization files. >There is some mention of needing to use TOUCH.EXE from GNU File Utils v4, >although you do provide a copy. What are the nature of this newer time >format? Later releases of Fileutils were updated for compliance to the SUSv2. This is the particular difference that demands a newer TOUCH for the sanity script: CVS v 1.11/fileutils v 3.16: touch 1225180134 cdir/cfile CVS v 1.12/fileutils v 4.x: touch -t 203412251801 cdir/cfile _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs