Date: Sat, 29 Mar 2003 02:39:24 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [Ux2bs_Archive] No. 119 ************************************************** Friday 28 March 2003 Number 119 ************************************************** Subjects for today 1 Re: Building Perl with gcc v3.2.1 : John Poltorak 2 Building GMP (GNU MP) : John Poltorak 3 Re: Building Perl with gcc v3.2.1 : Stefan.Neis at t-online.de 4 re: Building perl with gcc-3.2.1 : sma at sohnen-moe.com 5 Re: Building READLINE : John Poltorak 6 Re: Autoconf error...? : Andreas Buening 7 Re: M4 : Andreas Buening 8 Re: Autoconf error...? : John Poltorak 9 Re: M4 : John Poltorak 10 Re: Autoconf error...? : John Poltorak 11 Re: Autoconf error...? : Andreas Buening 12 Re: M4 : Andreas Buening **= Email 1 ==========================** Date: Sat, 29 Mar 2003 10:08:20 +0000 From: John Poltorak Subject: Re: Building Perl with gcc v3.2.1 On Fri, Mar 28, 2003 at 05:10:09PM -0700, sma at sohnen-moe.com wrote: > > > >Has anyone tried building Perl with gcc v3.2.1? > > > > Here the complete diff between the log files of gcc 2.8.1 and 3.2.1: > > > [H:>diff perl-gcc321.log perl-gcc281.log > 1c1 > < Fri Mar 28 15:09:41 MST 2003 > --- > > Fri Mar 28 15:32:39 MST 2003 > 12857,12858c12857,12858 > < Fri Mar 28 15:22:05 MST 2003 > < elapsed time: 744 secs > --- > > Fri Mar 28 15:44:38 MST 2003 > > elapsed time: 719 secs > > gcc 3.2.1 is a bit slower. That is still about five times quicker than I can manage, although I never was successfull in building Perl with gcc 3.0.3. Is the installation of v3.2.1 fairly straightforward? I'm wondering whether to incorporate it into UX2BS... > Here is the test result: > Failed 35/726 test scripts, 95.18% okay. 981/68664 subtests failed, > 98.57% okay. These results don't look very good at all. You should only be getting about 5 or 6 failures instead of 35. Can you post the full summary? There's definitely something wrong. -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 2 ==========================** Date: Sat, 29 Mar 2003 10:15:26 +0000 From: John Poltorak Subject: Building GMP (GNU MP) Anyone tried building GMP? GMP is the GNU Maths Precision library and is required by Python and probably many other apps... -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 3 ==========================** Date: Sat, 29 Mar 2003 11:48:19 +0100 From: Stefan.Neis at t-online.de Subject: Re: Building Perl with gcc v3.2.1 > [H:>diff perl-gcc321.log perl-gcc281.log > 1c1 > < Fri Mar 28 15:09:41 MST 2003 > --- > > Fri Mar 28 15:32:39 MST 2003 > 12857,12858c12857,12858 > < Fri Mar 28 15:22:05 MST 2003 > < elapsed time: 744 secs > --- > > Fri Mar 28 15:44:38 MST 2003 > > elapsed time: 719 secs > > gcc 3.2.1 is a bit slower. Hm, it's a pleasant surprise that it really is only _a_bit_ slower. I've seen timings which looked _much_ worse - but then, that was C++ code, whereas Perl is plain C code. > Here is the test result: > Failed 35/726 test scripts, 95.18% okay. 981/68664 subtests failed, > 98.57% okay. That looks like some more failures than the gcc-2.8.1 compiled version produced, doesn't it? Regards, Stefan _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 4 ==========================** Date: Sat, 29 Mar 2003 13:59:02 -0700 From: sma at sohnen-moe.com Subject: re: Building perl with gcc-3.2.1 Hello, I was totally wrong about building perl with gcc v3.2.1. Arrgh! build.cmd called the original ux2_env.cmd script which overwrote the gcc321 paths needed to use gcc321. And the perl script did its own re-writing.... After fixing those, the build fails almost immediately by not even recognizing that the gcc compiler works! [...] Use which C compiler? [gcc] Uh-oh, the C compiler 'gcc' doesn't seem to be working. You need to find a working C compiler. [...] Well! Looks like some digging around in the configure script... _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 5 ==========================** Date: Sat, 29 Mar 2003 15:43:07 +0000 From: John Poltorak Subject: Re: Building READLINE On Fri, Mar 28, 2003 at 03:02:06PM -0700, sma at sohnen-moe.com wrote: > > > >Has anyone tried building READLINE? > > > >How did you get on? > > > Yes, v4.3 built with both gcc v2.8.1, and v3.2.1. It had some minor > warnings: "'XXX' discards `const' from pointer target type". Hmmm... I wonder if you are using the latest UX2BS.... It didn't work at all for me, until I took out the Posix/2 environment. It is included by default so something needs to be don to exclude it. > The main thing was to add "--disable-shared". It worked fine with this option, although I'm not sure what it does. However I needed to add readline to ps2_exc.lst before it would work. > It installed to /usr/local/. This is the default, and I usually set is specifically after I know the app will build. Where should it get installed? And what actually does get installed? -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 6 ==========================** Date: Sat, 29 Mar 2003 21:14:04 +0100 From: Andreas Buening Subject: Re: Autoconf error...? John Poltorak wrote: > > When attempting to build Python (v2.2.2), I got the following error whilst > running configure:- > > checking for uname... yes > checking for unsetenv... yes > checking for waitpid... yes > checking for _getpty... no > checking for getpriority... yes > ./configure[12809]: syntax error: `done' unexpected > > This was a configure script created by running Autoconf (v2.57) > > When I ran the configure script provided, I didn't have any problems, > which leads me to believe there must be a bug in Autoconf... > > I have had similar errors with a number of different apps. This kind of error happens very often if the autoconf macros aren't quoted accordingly in configure.in. I guess, the original configure script was generated by autoconf 2.13, wasn't it? 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 Mordor where the Shadows lie. _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 7 ==========================** Date: Sat, 29 Mar 2003 21:15:02 +0100 From: Andreas Buening Subject: Re: M4 John Poltorak wrote: [snip] > making install in doc > make[1]: Entering directory `U:/unixos2/workdir/m4-1.4/doc' > cd . && makeinfo m4.texinfo > 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. > m4.texinfo:369: warning: `.' or `,' must follow cross reference, not f. > m4.texinfo:633: warning: `.' or `,' must follow cross reference, not f. > m4.texinfo:655: warning: `.' or `,' must follow cross reference, not f. > m4.texinfo:741: warning: `.' or `,' must follow cross reference, not f. > m4.texinfo:1574: warning: `.' or `,' must follow cross reference, not f. > m4.texinfo:1625: warning: `.' or `,' must follow cross reference, not f. > m4.texinfo:2889: warning: `.' or `,' must follow cross reference, not i. Maybe m4.texinfo is defective. I don't know. Please use the procided m4.info file. > /bin/sh ./../mkinstalldirs /usr/local/info > cd . && for file in m4.info*; do \ > u:/unixos2/bin/install.exe -m 644 $file /usr/local/info/$file; \ > done > install-info --info-dir=/usr/local/info /usr/local/info/m4.info > make[1]: Leaving directory `U:/unixos2/workdir/m4-1.4/doc' > making install in lib > make[1]: Entering directory `U:/unixos2/workdir/m4-1.4/lib' > gcc -c -DHAVE_CONFIG_H -I.. -I. -Zomf -O2 -s -Zmt -D__ST_MT_ERRNO__ > getopt.c > getopt.c: In function `getopt': > getopt.c:669: argument `argv' doesn't match prototype > getopt.h:104: prototype declaration > make[1]: *** [getopt.obj] Error 1 > make[1]: Leaving directory `U:/unixos2/workdir/m4-1.4/lib' > make: *** [install] Error 1 Line 104 of getopt.h contains the "extern int getopt" declaration below: #ifdef __GNU_LIBRARY__ /* Many other libraries have conflicting prototypes for getopt, with differences in the consts, in stdlib.h. To avoid compilation errors, only prototype getopt for the GNU C library. */ extern int getopt (int argc, char *const *argv, const char *shortopts); #else /* not __GNU_LIBRARY__ */ This means you define __GNU_LIBRARY__ somewhere which sounds not really good. > In spite of this, m4.exe does get built and runs. Whether it works > correctly I'm not sure. > > AIUI the default build should not use the included regex. I don't know why > it ignores the regex library which exists in /usr/lib... There must have been a configure test for regex which you've ignored. 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 Mordor where the Shadows lie. _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 8 ==========================** Date: Sat, 29 Mar 2003 21:31:01 +0000 From: John Poltorak Subject: Re: Autoconf error...? On Sat, Mar 29, 2003 at 09:14:04PM +0100, Andreas Buening wrote: > John Poltorak wrote: > > > > When attempting to build Python (v2.2.2), I got the following error whilst > > running configure:- > > > > checking for uname... yes > > checking for unsetenv... yes > > checking for waitpid... yes > > checking for _getpty... no > > checking for getpriority... yes > > ./configure[12809]: syntax error: `done' unexpected > > > > This was a configure script created by running Autoconf (v2.57) > > > > When I ran the configure script provided, I didn't have any problems, > > which leads me to believe there must be a bug in Autoconf... > > > > I have had similar errors with a number of different apps. > > This kind of error happens very often if the autoconf macros > aren't quoted accordingly in configure.in. I guess, the original > configure script was generated by autoconf 2.13, wasn't it? Yes, in the case of Python, the provided configure script was built using autoconf 2.13, but I get a similar error with texinfo (v4.5) and this app uses the very latest autoconf - 2.57... With texinfo I get the syntax error: `done' unexpected at the end of this block here:- cat <<\_ASBOX ## ------------------------------------ ## ## Report this to bug-autoconf at gnu.org. ## ## ------------------------------------ ## _ASBOX ) | sed "s/^/$as_me: WARNING: /" >&2 ;; esac echo "$as_me:$LINENO: checking for $ac_header" >&5 echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6 if eval "test \"\${$as_ac_Header+set}\" = set"; then echo $ECHO_N "(cached) $ECHO_C" >&6 else eval "$as_ac_Header=$ac_header_preproc" fi echo "$as_me:$LINENO: result: `eval echo '${'$as_ac_Header'}'`" >&5 echo "${ECHO_T}`eval echo '${'$as_ac_Header'}'`" >&6 fi if test `eval echo '${'$as_ac_Header'}'` = yes; then cat >>confdefs.h <<_ACEOF #define `echo "HAVE_$ac_header" | $as_tr_cpp` 1 _ACEOF fi done If you installed UX2BS you would know exactly what I'm referring to if you ran:- build texinfo > > 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 Mordor where the Shadows lie. -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 9 ==========================** Date: Sat, 29 Mar 2003 22:06:22 +0000 From: John Poltorak Subject: Re: M4 On Sat, Mar 29, 2003 at 09:15:02PM +0100, Andreas Buening wrote: > John Poltorak wrote: > > [snip] > > > making install in doc > > make[1]: Entering directory `U:/unixos2/workdir/m4-1.4/doc' > > cd . && makeinfo m4.texinfo > > 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. > > m4.texinfo:369: warning: `.' or `,' must follow cross reference, not f. > > m4.texinfo:633: warning: `.' or `,' must follow cross reference, not f. > > m4.texinfo:655: warning: `.' or `,' must follow cross reference, not f. > > m4.texinfo:741: warning: `.' or `,' must follow cross reference, not f. > > m4.texinfo:1574: warning: `.' or `,' must follow cross reference, not f. > > m4.texinfo:1625: warning: `.' or `,' must follow cross reference, not f. > > m4.texinfo:2889: warning: `.' or `,' must follow cross reference, not i. > > Maybe m4.texinfo is defective. I don't know. There is no indication thatit is defective. Do you have this problem when building m4? > Please use the procided m4.info file. > > > > /bin/sh ./../mkinstalldirs /usr/local/info > > cd . && for file in m4.info*; do \ > > u:/unixos2/bin/install.exe -m 644 $file /usr/local/info/$file; \ > > done > > install-info --info-dir=/usr/local/info /usr/local/info/m4.info > > make[1]: Leaving directory `U:/unixos2/workdir/m4-1.4/doc' > > making install in lib > > make[1]: Entering directory `U:/unixos2/workdir/m4-1.4/lib' > > gcc -c -DHAVE_CONFIG_H -I.. -I. -Zomf -O2 -s -Zmt -D__ST_MT_ERRNO__ > > getopt.c > > getopt.c: In function `getopt': > > getopt.c:669: argument `argv' doesn't match prototype > > getopt.h:104: prototype declaration > > make[1]: *** [getopt.obj] Error 1 > > make[1]: Leaving directory `U:/unixos2/workdir/m4-1.4/lib' > > make: *** [install] Error 1 > > Line 104 of getopt.h contains the "extern int getopt" > declaration below: > > #ifdef __GNU_LIBRARY__ > /* Many other libraries have conflicting prototypes for getopt, with > differences in the consts, in stdlib.h. To avoid compilation > errors, only prototype getopt for the GNU C library. */ > extern int getopt (int argc, char *const *argv, const char *shortopts); > #else /* not __GNU_LIBRARY__ */ > > This means you define __GNU_LIBRARY__ somewhere which sounds > not really good. I'm only using a standard build process of running autoconf, configure and Make and not setting any specific variables. The build does include your diffs for m4 and I've tried to follow your build instructions as closely as possible. > > In spite of this, m4.exe does get built and runs. Whether it works > > correctly I'm not sure. > > > > AIUI the default build should not use the included regex. I don't know why > > it ignores the regex library which exists in /usr/lib... > > There must have been a configure test for regex which you've > ignored. This is completely reproducible under UX2BS. No manual intervention is involved. > 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 Mordor where the Shadows lie. -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 10 ==========================** Date: Sat, 29 Mar 2003 23:12:44 +0000 From: John Poltorak Subject: Re: Autoconf error...? On Sat, Mar 29, 2003 at 11:40:54PM +0100, Andreas Buening wrote: > The latest texinfo I have is 4.0. If you look into the configure.in v4.5 uses configure.ac... > file you find things like > > AC_CHECK_HEADERS(ncurses/termcap.h) > > The correct syntax would be > > AC_CHECK_HEADERS([ncurses/termcap.h]) > > If you add all those missing quotes then it should work. Do you mean I should change all the lines begining with AC_ ? What about AM_ ? How do I change this, if it needs changing:- ? AC_CHECK_FUNC(sigblock, , AC_CHECK_LIB(bsd, sigblock)) > > 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 Mordor where the Shadows lie. -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 11 ==========================** Date: Sat, 29 Mar 2003 23:40:54 +0100 From: Andreas Buening Subject: Re: Autoconf error...? John Poltorak wrote: > > On Sat, Mar 29, 2003 at 09:14:04PM +0100, Andreas Buening wrote: > > John Poltorak wrote: > > > > > > When attempting to build Python (v2.2.2), I got the following error whilst > > > running configure:- [snip] > > > ./configure[12809]: syntax error: `done' unexpected > > > > > > This was a configure script created by running Autoconf (v2.57) > > > > > > When I ran the configure script provided, I didn't have any problems, > > > which leads me to believe there must be a bug in Autoconf... > > > > > > I have had similar errors with a number of different apps. > > > > This kind of error happens very often if the autoconf macros > > aren't quoted accordingly in configure.in. I guess, the original > > configure script was generated by autoconf 2.13, wasn't it? > > Yes, in the case of Python, the provided configure script was built using > autoconf 2.13, but I get a similar error with texinfo (v4.5) and this app > uses the very latest autoconf - 2.57... > > With texinfo I get the syntax error: `done' unexpected at the end of this > block here:- [snip] > If you installed UX2BS you would know exactly what I'm referring to if you > ran:- > > build texinfo The latest texinfo I have is 4.0. If you look into the configure.in file you find things like AC_CHECK_HEADERS(ncurses/termcap.h) The correct syntax would be AC_CHECK_HEADERS([ncurses/termcap.h]) If you add all those missing quotes then it should work. 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 Mordor where the Shadows lie. _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 12 ==========================** Date: Sat, 29 Mar 2003 23:41:14 +0100 From: Andreas Buening Subject: Re: M4 John Poltorak wrote: > > On Sat, Mar 29, 2003 at 09:15:02PM +0100, Andreas Buening wrote: [snip] > > Maybe m4.texinfo is defective. I don't know. > > There is no indication thatit is defective. > > Do you have this problem when building m4? Yes. [snip] > > This means you define __GNU_LIBRARY__ somewhere which sounds > > not really good. > > I'm only using a standard build process of running autoconf, configure and > Make and not setting any specific variables. The build does include your > diffs for m4 and I've tried to follow your build instructions as closely > as possible. But somewhere you define __GNU_LIBRARY__, maybe in a header file. > > > In spite of this, m4.exe does get built and runs. Whether it works > > > correctly I'm not sure. > > > > > > AIUI the default build should not use the included regex. I don't know why > > > it ignores the regex library which exists in /usr/lib... > > > > There must have been a configure test for regex which you've > > ignored. > > This is completely reproducible under UX2BS. No manual intervention is > involved. I mean one line of configure output should tell you that no external regex could be found. 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 Mordor where the Shadows lie. _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs