Date: Sat, 10 Jan 2004 00:04:06 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 288 ************************************************** Friday 09 January 2004 Number 288 ************************************************** Subjects for today 1 Re: NetPBM : Andreas Buening 2 Re: OpenLDAP : Andreas Buening 3 Re: gocr : Andreas Buening 4 Re: gocr : Thomas Dickey **= Email 1 ==========================** Date: Fri, 09 Jan 2004 01:15:55 +0100 From: Andreas Buening Subject: Re: NetPBM Franz Bakan wrote: > > On Tue, 6 Jan 2004 15:12:46 +0000, John Poltorak wrote: > > >If you've tried building GOCR, don't you get a problem when running Make > >because of the included make.bat ? > > You have to delete make.bat Alternatively, it should be possible to call "make.exe" explicitely instead of just "make". Bye, Andreas **= Email 2 ==========================** Date: Fri, 09 Jan 2004 01:15:43 +0100 From: Andreas Buening Subject: Re: OpenLDAP Bart van Leeuwen wrote: [snip] > checking for a BSD compatible install... c:/unixos2/bin/install.exe > checking for ar... no > checking for gar... no > configure: error: Unable to locate ar(1) or suitable replacement. Check > PATH or > set AR. > > I think I mis configured something ar is executable on the command line.. The most popular reasons: Do you use '/' instead of '\' in your PATH before you run configure? Have you set ac_executable_extensions=".exe"? Some old versions might have used EXEEXT or ac_exeext but this should be obsolete. The AC_EXEEXT macro is obsolete for new autoconf versions. Otherwise, I have no idea. Bye, Andreas **= Email 3 ==========================** Date: Fri, 09 Jan 2004 01:17:10 +0100 From: Andreas Buening Subject: Re: gocr John Poltorak wrote: > > I've managed to build GOCR fairly easily from the distributed source with > a couple of very minor changes, but I need to run EMXBIND to create an > OS/2 .exe. > > I'd like to have it built automatically and I think I should be able to > achieve this by the use of EXEEXT. I'm never clear about whether I need to > change configure.in or Makefile.in or both. Can someone remind me? AC_EXEEXT was for configure.in but it's obsolete now. "EXEEXT = at EXEEXT at " should be put into Makefile.in automatically. A real problem is that in many cases $(EXEEXT) isn't used at all places in Makefile.am where it should be. Bye, Andreas **= Email 4 ==========================** Date: Thu, 8 Jan 2004 19:29:45 -0500 (EST) From: Thomas Dickey Subject: Re: gocr On Fri, 9 Jan 2004, Andreas Buening wrote: > John Poltorak wrote: > > > > I've managed to build GOCR fairly easily from the distributed source with > > a couple of very minor changes, but I need to run EMXBIND to create an > > OS/2 .exe. > > > > I'd like to have it built automatically and I think I should be able to > > achieve this by the use of EXEEXT. I'm never clear about whether I need to > > change configure.in or Makefile.in or both. Can someone remind me? > > AC_EXEEXT was for configure.in but it's obsolete now. Not if one chooses to not use automake. > "EXEEXT = at EXEEXT at " should be put into Makefile.in automatically. > A real problem is that in many cases $(EXEEXT) isn't used at all > places in Makefile.am where it should be. > > > Bye, > Andreas > > -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net