From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Sun, 23 Nov 2003 14:16:00 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 249 ************************************************** Saturday 22 November 2003 Number 249 ************************************************** Subjects for today 1 Fetchmail : John Poltorak 2 Re: Posix/2 header problem? : Stefan Neis 3 Perl and -Zomf : Lyn St George" 4 Re: Perl and -Zomf : John Poltorak 5 Re: Perl and -Zomf : Henry Sobotka 6 Re: Perl and -Zomf : Lyn St George" **= Email 1 ==========================** Date: Sun, 23 Nov 2003 11:09:16 +0000 From: John Poltorak Subject: Fetchmail Does anyone have any notes for building FETCHMAIL on OS/2? -- John **= Email 2 ==========================** Date: Sun, 23 Nov 2003 19:23:20 +0100 (CET) From: Stefan Neis Subject: Re: Posix/2 header problem? On Sat, 22 Nov 2003, John Poltorak wrote: > Yes, you're right. There is a paths.h within bogofilter, but it is > included by using:- > > #include "paths.h" > > Is this a problem with search paths? Yes... > Where do "*.h" files expect to be found? Just the current directory? I don't know exactly. IIRC, it's current directory + everything given by -I flags. However, that not quite relevant. The real problem is that sys/syslog.h apparently gets bogofilter's paths.h by using "#include " which looks like a path problem. I suppose the Makefile is passing "-Isomething" to the compiler which then takes precedence for finding the includes given by <...>. If bogofilter's paths.h is actually found in the current directory, you could try to remove a potentially existing "-I.", otherwise the only possible fix is to rename the header file and change the includes in bogofilter's source code accordingly. Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 3 ==========================** Date: Sun, 23 Nov 2003 20:16:50 +0000 From: "Lyn St George" Subject: Perl and -Zomf Hallo all I'm trying to build perl 5.8.2 and have just found that I've screwed up the emxomf versions (a failed install of gcc .3.21, reverted to pgcc 2.95). While the system built BerkeleyDB yesterday it now refuses on perl "gcc doesn't seem to be working". Taking -Zomf out of the args when running that test manually allows the 'try.exe' to build and run OK. emxomf.exe is now from gcc 2.95, as are all the libs I can find, but it still won't build with 'configure'. Is there something else that -Zomf needs apart from emxomf.exe? - Cheers Lyn St George +--------------------------------------------------------------------------------- + http://www.zolotek.net .. eCommerce hosting, consulting +---------------------------------------------------------------------------------- **= Email 4 ==========================** Date: Sun, 23 Nov 2003 21:02:08 +0000 From: John Poltorak Subject: Re: Perl and -Zomf On Sun, Nov 23, 2003 at 08:16:50PM +0000, Lyn St George wrote: > Hallo all > > I'm trying to build perl 5.8.2 and have just found that I've screwed > up the emxomf versions (a failed install of gcc .3.21, reverted to > pgcc 2.95). While the system built BerkeleyDB yesterday it now > refuses on perl "gcc doesn't seem to be working". > > Taking -Zomf out of the args when running that test manually allows > the 'try.exe' to build and run OK. emxomf.exe is now from gcc 2.95, as > are all the libs I can find, but it still won't build with 'configure'. Configure can be a little tricky to run sometimes and will produce all sorts of entirely spurious msgs sometimes. How about posting some of the output Configure produces when it show these errors? > > - > Cheers > Lyn St George > +--------------------------------------------------------------------------------- > + http://www.zolotek.net .. eCommerce hosting, consulting > +---------------------------------------------------------------------------------- > -- John **= Email 5 ==========================** Date: Sun, 23 Nov 2003 21:34:33 -0500 From: Henry Sobotka Subject: Re: Perl and -Zomf Lyn St George wrote: > > Just found this in the popuplog.os2: > > F:\USR\TEST\BIN\CPP.EXE > CPP->IBERTY._sch_istable > 127 > > cpp.exe, iberty.a and iberty.dll are from gcc2.95 and have just > been refreshed. 127 means mismatched DLLs, in this case iberty. Try running "which -al iberty". h~ **= Email 6 ==========================** Date: Sun, 23 Nov 2003 23:42:37 +0000 From: "Lyn St George" Subject: Re: Perl and -Zomf On Sun, 23 Nov 2003 21:02:08 +0000, John Poltorak wrote: >On Sun, Nov 23, 2003 at 08:16:50PM +0000, Lyn St George wrote: >> Hallo all >> >> I'm trying to build perl 5.8.2 and have just found that I've screwed >> up the emxomf versions (a failed install of gcc .3.21, reverted to >> pgcc 2.95). While the system built BerkeleyDB yesterday it now >> refuses on perl "gcc doesn't seem to be working". >> >> Taking -Zomf out of the args when running that test manually allows >> the 'try.exe' to build and run OK. emxomf.exe is now from gcc 2.95, as >> are all the libs I can find, but it still won't build with 'configure'. > > >Configure can be a little tricky to run sometimes and will produce all >sorts of entirely spurious msgs sometimes. > >How about posting some of the output Configure produces when it show these >errors? I run 'sh Configure -des -Dprefix=/usr' and when it gets to the gcc test it reports: "Uh-oh, the C compiler 'gcc' doesn't seem to be working." This test creates a tiny 'try.c' and then runs: $cc -o try $ccflags $ldflags try.c where both sets of flags are taken from hints/os2.sh (written by Ilya Z) and where both contain -Zomf. If I run this test compile manually but without the -Zomf then try.exe builds and tests OK. This process is identical to that from perl 5.8.0 which used to build correctly on this system. Since then I tried to install gcc3.2.1 but it failed ('couldn't find as.exe') so I reverted to gcc2.95. My config.site used to have -Zomf in the ldflags entry, but I found when building BerkeleyDB the other day that this caused that infamous "gcc can't create an executable" error and so removed it. While I *think* I've removed all traces of gcc3.2.1, in particular the emx executables and libs, it seems pretty obvious that something is still there. The trouble is that I can't find it - I've spent the whole day looking and now I'm stuck ... I'm just hoping that someone has seen this before, or has some better clues for me to chase ... - Cheers Lyn St George +--------------------------------------------------------------------------------- + http://www.zolotek.net .. eCommerce hosting, consulting +----------------------------------------------------------------------------------