Robert Blair | 1 Nov 01:41 2008
Picon

Re: buildenv problem

** Reply to message from "Dave Yeo" <daveryeo <at> telus.net> on Fri, 31 Oct 2008
15:39:02 -0700

> Never tried to run autoconf with ash before, just took it for granted
> that it would work. Trying now I get the same error. I'd suggest
> downloading
> http://hobbes.nmsu.edu/download/pub/os2/util/shell/pdksh-5.2.14-bin-2.zi
> p and installing it and using sh.exe to run configure, autoconf etc.
> Look in Paul's setup files for instances of ash (or ash.exe) and change
> them to sh (sh.exe or /bin/sh.exe).
> These should be things like makeshell=, shell=, etc.
> Then try running configure like sh ./configure, or for autoconf, sh
> autoconf

That appears to help considerably.

Now there are complaints about grep.  sh./configure quits with.

checking for grep that handles long lines and -e... configure: error: no
acceptable grep could be found in (entire PATH)

There is a grep in F:/MOZTOOLS but apparently not up to specs.

I downloaded a version of grep from HOBBES but still get the same error.  Do
you know where there is a good version of grep?

--

-- 
Robert Blair
Stefan.Neis | 1 Nov 01:41 2008
Picon

Re: buildenv problem

        Hi,

> FWIW, I've never needed to follow the recommendation to use ash.  I've not
> had any problems I can attribute to sh.exe.

Basically I made the same observation, or rather I even saw things working with
sh.exe that wouldn't work with ash. However, whenever ash is sufficient, it seems
to process shell scripts _much_ faster than pdksh's sh.exe, at least in the cases
where I actually did a timing for both (something like 25 seconds vs.
40 seconds, IIRC), so my first try always is ash ...

        Regards,
	        Stefan	
Robert Blair | 1 Nov 05:22 2008
Picon

Re: buildenv problem

** Reply to message from "Steven Levine" <steve53 <at> earthlink.net> on Fri, 31 Oct
2008 16:47:51 -0700

> >Now there are complaints about grep.  sh./configure quits with.
> 
> >checking for grep that handles long lines and -e... configure: error: no
> >acceptable grep could be found in (entire PATH)
> 
> >There is a grep in F:/MOZTOOLS but apparently not up to specs.
> 
> Are you sure you are using this grep?  You should be able to force
> configure to use a specific grep with

That is the only grep.exe on my system.

>   export EGREP=f:/moztools/egrep
> 
> or
> 
>   export EGREP='f:/moztools/grep -E'
> 
> depending on what you have.
> 
> >Do you know where there is a good version of grep?
> 
> What version of grep did you download?

2.5.1a (which I have deleted)

I just checked the version in moztools, it is 2.5.1
(Continue reading)

Dave Yeo | 1 Nov 04:24 2008
Picon

Re: buildenv problem

On Sat, 1 Nov 2008 01:41:27 +0100, Stefan.Neis <at> t-online.de wrote:

>> FWIW, I've never needed to follow the recommendation to use ash.  I've not
>> had any problems I can attribute to sh.exe.
>
>Basically I made the same observation, or rather I even saw things working with
>sh.exe that wouldn't work with ash. However, whenever ash is sufficient, it seems
>to process shell scripts _much_ faster than pdksh's sh.exe, at least in the cases
>where I actually did a timing for both (something like 25 seconds vs.
>40 seconds, IIRC), so my first try always is ash ...

Are you sure you were using the sh.exe from
http://hobbes.nmsu.edu/download/pub/os2/util/shell/pdksh-5.2.14-bin-2.zi
p? and not from some bash package?
I just tested running FFmpeg's configure. Looking at some pages in
Seamonkey while test was running (not loading pages but did change tabs
once or twice). Three runs each gave (number of seconds)

ash=
93.57
94.61
97.81

sh=
79.54
76.19
79.47

so here sh.exe is somewhat faster.
The Mozilla team figured that ash built mozilla twice as fast as bash.
(Continue reading)

Dave Yeo | 1 Nov 04:27 2008
Picon

Re: buildenv problem

On Fri, 31 Oct 2008 16:47:51 -0700, Steven Levine wrote:

>Are you sure you are using this grep?  You should be able to force
>configure to use a specific grep with
>
>  export EGREP=f:/moztools/egrep
>
>or
>
>  export EGREP='f:/moztools/grep -E'
>
>depending on what you have.

Or from cmd.exe etc
set EGREP='f:/moztools/grep -E"
or
set EGREP=f:/moztools/egrep

Generally when configure can't find something you can set an enviroment
variable to point at it.
Dave
Dave Yeo | 1 Nov 04:36 2008
Picon

Re: buildenv problem

On Fri, 31 Oct 2008 16:38:26 -0700, Steven Levine wrote:

>
>In <19740414223344.639F2637343F9680 <at> priv-edmwaa07.telusplanet.net>, on
>10/31/08
>   at 03:39 PM, "Dave Yeo" <daveryeo <at> telus.net> said:
>
>>Never tried to run autoconf with ash before, just took it for granted
>>that it would work.
>
>Sorta surprised me too.  I knew ash was pretty minimum function, but I
>didn't know it lacked the ability to search the path for scripts on the
>command line.

This could be the famous %PATH% bug in ash. Basically ash disregards
the first entry in %PATH%. Workaround is to set PATH=/foo;%PATH%

>
>>http://hobbes.nmsu.edu/download/pub/os2/util/shell/pdksh-5.2.14-bin-2.zi
>>p and installing it and using sh.exe to run configure, autoconf etc.
>
>Based on what Paul appears to be doing, he appears to be using bash for
>everything but make.

There are a lot of bash ports floating around. Some work fairly well
running configure scripts and some don't. They are all slow.

>
>>These should be things like makeshell=, shell=, etc.
>>Then try running configure like sh ./configure, or for autoconf, sh
(Continue reading)

Dave Yeo | 1 Nov 04:41 2008
Picon

Re: buildenv problem

On Fri, 31 Oct 2008 21:22:15 -0700, Robert Blair wrote:

>
>I just noticed this -DSYSCONFDIR=\"/usr/local/etc\" there is no etc directory
>in /usr/local/.  Any idea what this should be?

Those are strange errors. What program is this? Googling only found a
program to control your X10 firecracker :)
Dave
Robert Blair | 1 Nov 06:34 2008
Picon

Re: buildenv problem

** Reply to message from "Robert Blair" <libc-z03fbokz <at> listemail.net> on Fri,
31 Oct 2008 21:22:15 -0700

> The output of make follows
> 
> make.exe  all-am
> make.exe[1]: Entering directory `F:/dev/flipit'
> source='flipit.c' object='flipit.o' libtool=no \
> depfile='.deps/flipit.Po' tmpdepfile='.deps/flipit.TPo' \
> depmode=gcc3 sh.exe ./depcomp \
> gcc -DHAVE_CONFIG_H -I. -I. -I.  -DSYSCONFDIR=\"/usr/local/etc\"   -D__EMX__
> -DOS2 -D__ST_MT_ERRNO__ -O2 -c `test -f 'flipit.c' || echo './'`flipit.c
> flipit.c:89:18: pasting "SYSCONFDIR" and ""/flipit.conf"" does not give a valid
> preprocessing token
> flipit.c:89:31: pasting "SYSCONFDIR" and ""/flipit.conf"" does not give a valid
> preprocessing token
> flipit.c:159:25: pasting "SYSCONFDIR" and ""/flipit.conf"" does not give a
> valid preprocessing token
> make.exe[1]: *** [flipit.o] Error 1
> make.exe[1]: Leaving directory `F:/dev/flipit'
> make: *** [all] Error 2
> 
> I just noticed this -DSYSCONFDIR=\"/usr/local/etc\" there is no etc directory
> in /usr/local/.  Any idea what this should be?

I deleted the flipit directory again and reloaded it.  This time when I ran
configure I added the "--sysconfdir=/dev/flipit" parameter.  It did not change
anything.

--

-- 
(Continue reading)

Robert Blair | 1 Nov 08:57 2008
Picon

Re: buildenv problem

** Reply to message from "Robert Blair" <libc-z03fbokz <at> listemail.net> on Fri,
31 Oct 2008 22:34:13 -0700

> > flipit.c:89:18: pasting "SYSCONFDIR" and ""/flipit.conf"" does not give a valid
> > preprocessing token

I found what the problem is.  It appears that something was changed in the
newer versions of the GCC compiler.  Searching google for "does not give a
valid preprocessing token" got the answer.

Removing the ## in conf.h line 33
#define SYSCONFFILE SYSCONFDIR  ## "/flipit.conf"
solved that problem.

--

-- 
Robert Blair
John Small | 11 Nov 14:45 2008
Picon

Built grep 2.5.3 successfully, or not?

In my continuing efforts to figure out how to port software I keep 
trying new source code packages to see if I can get anything to build.
Most end in failure and I have not been able to figure out if the 
problem is
- my build environment (Smedley's)
  - am I missing something?
  - do I have the wrong version of something?
  - which shell should I be using?
  - do I have all the necessary env. vars. set correctly?
- my configuration
  - which options, if any, should I be passing to the configure 
scripts?
  - which "can't find" messages during configure are acceptable and 
which ones indicate an error which needs to be fixed.
  - which "checking for/whether xyz... no" messages during configure 
are acceptable and which ones indicate an error which needs to be 
fixed.
- the source code itself
  - are there changes necessary to make it build under/for OS/2?

I finally ran across some source which may have built successfully, 
grep-2.5.3 (<ftp://aeneas.mit.edu/pub/gnu/grep/grep-2.5.3.tar.bz2>):
- running the configure script completes without any obvious-to-me, 
fatal errors
- running "make" completes without any obvious-to-me, fatal errors

But then when I run "make check" I get some failures. I see many 
"FAIL" messages but at the end the summary says:
  3 of 13 tests failed
  (1 tests were not run)
(Continue reading)


Gmane