Date: Sat, 30 Aug 2003 02:48:19 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [Ux2bs_Archive] No. 187 ************************************************** Friday 29 August 2003 Number 187 ************************************************** Subjects for today 1 Re: autoconf v2.57 build : Dave Saville" 2 Re: Re: dumps of g++ verbose and search dirs : James Moe" 3 Re: Re: dumps of g++ verbose and search dirs : Henry Sobotka 4 Re: Re: dumps of g++ verbose and search dirs : James Moe" 5 Re: additional packages : Andreas Buening 6 Re: autoconf v2.57 build : Andreas Buening 7 Re: Re: GCC builds : Andreas Buening **= Email 1 ==========================** Date: Sat, 30 Aug 2003 08:06:01 +0100 (BST) From: "Dave Saville" Subject: Re: autoconf v2.57 build On Fri, 29 Aug 2003 13:24:07 -0700 (MST), James Moe wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >On Fri, 29 Aug 2003 19:58:54 +0100, John Poltorak wrote: > >>You ought to be able to build this version of autoconf just by running >>build autoconf >> > Yes, that is what I did. I also remember it building on the previous version of >ux2bs. > >autoconf-2.57 >..Using autoconf (GNU Autoconf) 2.50 (release 3 for OS/2) >./aclocal.m4:46: error: Autoconf version 2.54 or higher is required for this script >./aclocal.m4:46: the top level >..autoconf failed. > >autoconf-2.54 >..Using autoconf (GNU Autoconf) 2.50 (release 3 for OS/2) >./aclocal.m4:46: error: Autoconf version 2.53b or higher is required for this script >./aclocal.m4:46: the top level >..autoconf failed: 1. > And that needs 2.52, and 2.50 won't build that because it gets errors which I previously posted. -- Regards Dave Saville _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 2 ==========================** Date: Sat, 30 Aug 2003 11:27:40 -0700 (MST) From: "James Moe" Subject: Re: Re: dumps of g++ verbose and search dirs -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 30 Aug 2003 12:37:02 -0400, Henry Sobotka wrote: > >emx/include/c++ does exist and du reports usage at 1.9MB. > Would you archive that directory and send it to me? My current investigation is in the /emx/include/c++/3.2.1/bits directory. When I unset cplus_include_path, a bunch of this type of error shows up: g:/emx/include/c++/3.2.1/cctype:59: `isalnum' not declared Looking at /emx/include/c++/3.2.1/bits/localfwd.h, is included which unsets the isalnum macro (and others) then declares the c++ version, "using ::isalnum;". But those versions have not been defined yet since that is the purpose of localefwd.h. But must exist first to unset the macro versions.... So I am thinking there may be a header problem in one of the distributions. Maybe. - -- jimoe at sohnen-moe dot com pgp/gpg public key: http://www.keyserver.net/en/ -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0 OS/2 for non-commercial use Comment: PGP 5.0 for OS/2 Charset: cp850 wj8DBQE/UOycsxxMki0foKoRArNQAJ909mK6yPPABKNmrFQXy1Zei8ftVQCfd+Uu QXq4FWWqRN0yJHif5AOjr88= =M+ci -----END PGP SIGNATURE----- _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 3 ==========================** Date: Sat, 30 Aug 2003 12:37:02 -0400 From: Henry Sobotka Subject: Re: Re: dumps of g++ verbose and search dirs James Moe wrote: > > When you compile using --verbose, does one of the search paths look like: > /emx/include/c++ > If so, does it actually exist? And is there anything in it? > Also does "/emx/include/cpp/" show in the list? > (I am looking at what is different among those who have a working compiler, and those > that do not.) Before unsetting CPLUS_INCLUDE_PATH (linkage fails): #include "..." search starts here: #include <...> search starts here: D:/emx/include/cpp D:/emx/include d:/emx/include/c++/3.2.1 d:/emx/include/c++/3.2.1/i386-pc-os2-emx d:/emx/include/c++/3.2.1/backward d:/emx/lib/gcc-lib/i386-pc-os2-emx/3.2.1/include D:/EMX/include/c++/3.2.1 D:/EMX/include/c++/3.2.1/i386-pc-os2-emx D:/EMX/include/c++/3.2.1/backward D:/EMX/lib/gcc-lib/i386-pc-os2-emx/3.2.1/include D:/EMX/include End of search list. After unsetting (clean build): #include "..." search starts here: #include <...> search starts here: d:/emx/include/c++/3.2.1 d:/emx/include/c++/3.2.1/i386-pc-os2-emx d:/emx/include/c++/3.2.1/backward d:/emx/lib/gcc-lib/i386-pc-os2-emx/3.2.1/include D:/EMX/include/c++/3.2.1 D:/EMX/include/c++/3.2.1/i386-pc-os2-emx D:/EMX/include/c++/3.2.1/backward D:/EMX/lib/gcc-lib/i386-pc-os2-emx/3.2.1/include D:/EMX/include End of search list. emx/include/c++ does exist and du reports usage at 1.9MB. After building with --save-temps, a look at hello.ii shows that, when linkage fails, it's reading emx/include/cpp and, in hello.s calling __Z4endlR7ostream, _cout and __ZN7ostreamlsEPKc. Going into emx/include/c++ first, those calls become __ZSt4endlIcSt11char_traitsIcEERSt13basic_ostreamIT_T0_ES6_, __ZSt4cout and __ZStlsISt11char_traitsIcEERSt13basic_ostreamIcT_ES5_PKc. Although in this case I unset CPLUS_INCLUDE_PATH completely, the failure stems from having emx/include/cpp and emx/include there because those envar paths get searched first and the wrong headers used. With 3.2.1, CPLUS_INCLUDE_PATH just has to be set to paths gcc doesn't know about (e.g. XFree86/include, toolkit/include) that might be necessary. If you want, James, I can email you the temps. A hello.ii comparison might turn up why you're getting the isalnum etc. errors. h~ _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 4 ==========================** Date: Sat, 30 Aug 2003 15:41:59 -0700 (MST) From: "James Moe" Subject: Re: Re: dumps of g++ verbose and search dirs -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 30 Aug 2003 14:50:04 -0400, Henry Sobotka wrote: >> >> Would you archive that directory and send it to me? >Attached. > Sigh. That is not it either. I get the same failures. The more I look at this, the more I am convinced it is a header or header ordering problem. I can't figure out how localefwd.h and cctype is supposed to work. Our distributions appear the same and yours works; mine does not. So what is different? - -- jimoe at sohnen-moe dot com pgp/gpg public key: http://www.keyserver.net/en/ -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0 OS/2 for non-commercial use Comment: PGP 5.0 for OS/2 Charset: cp850 wj8DBQE/USg3sxxMki0foKoRAvb1AKDSACM3Ms0oHlZQV9c/7c29S+ZUzwCeIvhP e7exeLTnWzsDmUi8S+Gvk3o= =iG8I -----END PGP SIGNATURE----- _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 5 ==========================** Date: Sat, 30 Aug 2003 17:35:25 +0200 From: Andreas Buening Subject: Re: additional packages T.Sikora wrote: > > I added the following ux2 packages: > > elvis.zip > vim.zip > mc.zip > xbin.zip > > Unix editors and Midnight Commander were sorely missing. MC is a must > have in my book. I didn't want to add XFree86 but mc relied on the xbin > package. You can always deinstall with removepkg what you don't want. Has there been any proposal what's the distinction between the UnixOS/2 distro and the ux2 build system? I mean, Midnight Commander and vi are user programs that are not necessary for the build system. Bye, Andreas _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 6 ==========================** Date: Sat, 30 Aug 2003 17:35:35 +0200 From: Andreas Buening Subject: Re: autoconf v2.57 build Stefan.Neis at t-online.de wrote: > > Hi, > > > Is there a trick to building autoconf v2.57? > > > autoconf-2.57 > > ..Using autoconf (GNU Autoconf) 2.50 (release 3 for > > OS/2) > > ./aclocal.m4:46: error: Autoconf version 2.54 or higher > > is required for this script > > Maybe try without running autoconf first? Yes, that's true. You have to use the provided configure to install autoconf the first time. After that you can autoconf. Btw, I put the latest version onto http://unix.os2site.com/pub/... Bye, Andreas _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 7 ==========================** Date: Sat, 30 Aug 2003 17:36:09 +0200 From: Andreas Buening Subject: Re: Re: GCC builds T.Sikora wrote: [snip] > I setup gcc_config and ux2_config with: > > REM ** AUTOCONF VERSION SETTINGS ** > REM ** Uncomment each section for the version desired ** > > REM ** (Default) AUTOCONF SETTINGS ** > SET ACLOCAL=${ACLOCAL-"${UXRT}/usr/bin/aclocal"} > SET AUTOCONF=${AUTOCONF-"${UXRT}/usr/bin/autoconf"} > SET AUTOMAKE=${AUTOMAKE-"${UXRT}/usr/bin/automake"} > SET AUTOHEADER=${AUTOHEADER-"${UXRT}/usr/bin/autoheader"} [...] > The older autoconf works fine with EMX and the newer one breaks some > port builds.... actually a whole lot of them. So maybe putting the newer > autoconf in /usr/local and defining which one to use through the config > files is a good compromise? No. Let's keep the directories clean. There should be no reason why we still need 2.50 or 2.52. If any of my packages breaks, please, tell me which one and I'll fix it. Bye, Andreas _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs