Author Topic: What is the future of this platform?  (Read 11491 times)

DougB

  • Sr. Member
  • ****
  • Posts: 407
    • View Profile
Re: What is the future of this platform?
« Reply #75 on: 2012.09.28, 22:03:08 »
Well, now I am running into configuration problems. For some reason, Paul's build seems to want to configure to build a Mozilla derivative, and it wants to use U:\moztools\config.site-gcc335b4. That file is from a release of moztools, as released by Dave Yeo, not too long ago. It bears no relation, at all, to my system, and a number of the entries don't make sense, to me. I don't think it should be using that anyway.

So, I removed the environment variables for MOZILLA, and CONFIG_SITE. Then, I get some reasonable output from:
Code: [Select]
ash ./configurebut it seems to want a different GREP than what is available. The error lines, from config.log are;
Code: [Select]
configure:5382: checking for grep that handles long lines and -e
configure:5433: error: no acceptable grep could be found in U:\foo;U:\usr\bin;U:\usr\local\bin;U:\GLIBIDL335\GLIB\gcc\bin;U:\GLIBIDL335\LIBIDL\gcc\bin;u:\PERL\bin;u:\bin;U:\MOZTOOLS;U:\EMX\bin;u:\extras\bin;u:\dev\qt\trunk\bin;U:\python25;M:\MPTN\BIN;M:\IBMCOM;M:\ECS\SYSTEM\Samba;M:\ECS\BIN;M:\TCPIP\BIN;W:\PROGRAMS\EMX\BIN;M:\IBMGSK50\BIN;M:\IBMGSK40\BIN;M:\IBMGSK\BIN;M:\OS2;M:\OS2\SYSTEM;M:\OS2\INSTALL;M:\;M:\OS2\MDOS;M:\OS2\APPS;M:\ECS\KLIBC\BIN;W:\PROGRAMS\JAVA142\BIN;M:\MMOS2\FREEDB;M:\MMOS2;M:\MMOS2\MMPLAYER;W:\PROGRAMS\4OS2;W:\PROGRAMS\OPENSSH;W:\UTILITY;W:\APPS\WGET\BIN;W:\TOOLS\dfsee\bin;W:\ODIN\SYSTEM32;W:\LOTUSW4\COMPNENT;W:\LOTUSW4\ORGANIZE;W:\LOTUSW4\APPROACH;W:\LOTUSW4\FLG;W:\LOTUSW4\WORDPRO;W:\APPS\BA2KWS;W:\PROGRAMS\qt4\bin;W:\APPS\EMBLSH;M:\ecs\ACPI\UTIL;U:\WATCOM\BINP;U:\WATCOM\BINW;U:\VISPRORX;;;/usr/xpg4/bin

Question: What is that all about?

Paul Smedley

  • Sr. Member
  • ****
  • Posts: 322
    • View Profile
Re: What is the future of this platform?
« Reply #76 on: 2012.09.29, 07:19:27 »
Well, now I am running into configuration problems. For some reason, Paul's build seems to want to configure to build a Mozilla derivative, and it wants to use U:\moztools\config.site-gcc335b4. That file is from a release of moztools, as released by Dave Yeo, not too long ago. It bears no relation, at all, to my system, and a number of the entries don't make sense, to me. I don't think it should be using that anyway.

So, I removed the environment variables for MOZILLA, and CONFIG_SITE. Then, I get some reasonable output from:
Code: [Select]
ash ./configurebut it seems to want a different GREP than what is available. The error lines, from config.log are;
Code: [Select]
configure:5382: checking for grep that handles long lines and -e
configure:5433: error: no acceptable grep could be found in U:\foo;U:\usr\bin;U:\usr\local\bin;U:\GLIBIDL335\GLIB\gcc\bin;U:\GLIBIDL335\LIBIDL\gcc\bin;u:\PERL\bin;u:\bin;U:\MOZTOOLS;U:\EMX\bin;u:\extras\bin;u:\dev\qt\trunk\bin;U:\python25;M:\MPTN\BIN;M:\IBMCOM;M:\ECS\SYSTEM\Samba;M:\ECS\BIN;M:\TCPIP\BIN;W:\PROGRAMS\EMX\BIN;M:\IBMGSK50\BIN;M:\IBMGSK40\BIN;M:\IBMGSK\BIN;M:\OS2;M:\OS2\SYSTEM;M:\OS2\INSTALL;M:\;M:\OS2\MDOS;M:\OS2\APPS;M:\ECS\KLIBC\BIN;W:\PROGRAMS\JAVA142\BIN;M:\MMOS2\FREEDB;M:\MMOS2;M:\MMOS2\MMPLAYER;W:\PROGRAMS\4OS2;W:\PROGRAMS\OPENSSH;W:\UTILITY;W:\APPS\WGET\BIN;W:\TOOLS\dfsee\bin;W:\ODIN\SYSTEM32;W:\LOTUSW4\COMPNENT;W:\LOTUSW4\ORGANIZE;W:\LOTUSW4\APPROACH;W:\LOTUSW4\FLG;W:\LOTUSW4\WORDPRO;W:\APPS\BA2KWS;W:\PROGRAMS\qt4\bin;W:\APPS\EMBLSH;M:\ecs\ACPI\UTIL;U:\WATCOM\BINP;U:\WATCOM\BINW;U:\VISPRORX;;;/usr/xpg4/bin

Question: What is that all about?

FWIW - I don't recommend removing the CONFIG_SITE reference.  Yes the config.site is located in a /moztools directory, and yes, it started life as a version used to build mozilla, but it's progressed a long way from that, and contains many things that 'help' configure - including grep.

Another way around the grep issue is to run:
'set grep=grep.exe' before running ./configure

dryeo

  • Newbie
  • *
  • Posts: 45
    • View Profile
Re: What is the future of this platform?
« Reply #77 on: 2012.09.29, 07:27:01 »
Quote
I think it may help if someone can write some article on the EDM/2 on how to set up Paul's environment.
[...]

The download file contains a directory (wget-1.14). Put that on the same drive as Paul's build environment. Then, click on the icon that you built to launch paul's build environment. That should get you to a command line. Change to the wget-1.14 directory, and now we need to figure out how to build it. Paul's instructions are a little confusing at this point (and somewhat incomplete in some more complicated cases).

Since I am tired, I will quit here, and hopefully, somebody will make this a little easier. I am not at all sure if I still have the original setup files, or if I have messed around with them. I don't normally use the setup as Paul supplied it (which seems to be set up to build a mozilla derivative, and I do not have the latest version), so I am somewhat lost here. I am sure that most people will have the same problem.

What I'd do (I don't have Pauls environment) is open EPM,  and open a shell within EPM. (Command --> Create command shell). Now we have a scrolling window for reviewing output.
Start out by doing sh configure --help (I use [pdk]sh.exe, substitute ash if you prefer) and examine the output. Of interest are options such as --enable-threads={posix|solaris|pth|windows} --disable-ipv6, ssl options, libiconv, libintl and whether to support nls options. We'll come back to this if configure makes mistakes in configuring for the build system.
Then try sh configure and watch the configure script figure out the build environment, what tools we have installed and what our libc supports.
Eventually here configure errors out with,

Code: [Select]
checking for libgnutls... no
configure: error: --with-ssl was given, but GNUTLS is not available

So we have to decide whether to use openssl. (Openssl has an incompatible license with GPL v2 ). For our first test build we'll disable it, so rerun configure as sh configure --without-ssl.
Eventually configure ends by creating a bunch of makefiles, so now we can do
make
and after a bunch of output make dies with
Code: [Select]
epbase=`echo spawn-pipe.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
gcc.exe -DHAVE_CONFIG_H -I. -I../src   -I/usr/local/include  -O2 -Wall -MT spawn-pipe.o -MD -MP -MF $depbase.Tpo -c -o spawn-pipe.o spawn-pipe.c &&\
mv -f $depbase.Tpo $depbase.Po
In file included from ./spawn.h:37,
                 from spawn-pipe.c:47:
./sched.h:43: error: redefinition of 'struct sched_param'
So need to examine what is different between lib\spawn.h and lib\sched.h and how they relate to our headers.
Search \usr\include for sched_param, we find it in spawn.h with a comment, todo implement sched.h.
Perhaps configure got confused by not finding sched.h? As we have sched_param we should be able to ignore the one included by lib\spawn.h. Best seems to try to change line 35 in spawn.h.in from
#if !(defined __GLIBC__ && !defined __UCLIBC__)
to
#if !(defined __GLIBC__ && !defined __UCLIBC__ || defined __OS2__)
and try again.
This time make finishes by building src\wget.exe so see if it runs by cd src && wget --version and it seems to work.
Now to test by doing make check which unluckily dies here due to perl issues. These can probably be fixed or can test wget by downloading things and seeing if they work.
Ideally after the build error is to contact the authours of wget for advice on the best way to fix the problem and get a fix into the code so the next version builds out of the box.

dryeo

  • Newbie
  • *
  • Posts: 45
    • View Profile
Re: What is the future of this platform?
« Reply #78 on: 2012.09.29, 07:39:34 »
Well, now I am running into configuration problems. For some reason, Paul's build seems to want to configure to build a Mozilla derivative, and it wants to use U:\moztools\config.site-gcc335b4. That file is from a release of moztools, as released by Dave Yeo, not too long ago. It bears no relation, at all, to my system, and a number of the entries don't make sense, to me. I don't think it should be using that anyway.

So, I removed the environment variables for MOZILLA, and CONFIG_SITE. Then, I get some reasonable output from:
Code: [Select]
ash ./configurebut it seems to want a different GREP than what is available. The error lines, from config.log are;
Code: [Select]
configure:5382: checking for grep that handles long lines and -e
configure:5433: error: no acceptable grep could be found in U:\foo;U:\usr\bin;U:\usr\local\bin;U:\GLIBIDL335\GLIB\gcc\bin;U:\GLIBIDL335\LIBIDL\gcc\bin;u:\PERL\bin;u:\bin;U:\MOZTOOLS;U:\EMX\bin;u:\extras\bin;u:\dev\qt\trunk\bin;U:\python25;M:\MPTN\BIN;M:\IBMCOM;M:\ECS\SYSTEM\Samba;M:\ECS\BIN;M:\TCPIP\BIN;W:\PROGRAMS\EMX\BIN;M:\IBMGSK50\BIN;M:\IBMGSK40\BIN;M:\IBMGSK\BIN;M:\OS2;M:\OS2\SYSTEM;M:\OS2\INSTALL;M:\;M:\OS2\MDOS;M:\OS2\APPS;M:\ECS\KLIBC\BIN;W:\PROGRAMS\JAVA142\BIN;M:\MMOS2\FREEDB;M:\MMOS2;M:\MMOS2\MMPLAYER;W:\PROGRAMS\4OS2;W:\PROGRAMS\OPENSSH;W:\UTILITY;W:\APPS\WGET\BIN;W:\TOOLS\dfsee\bin;W:\ODIN\SYSTEM32;W:\LOTUSW4\COMPNENT;W:\LOTUSW4\ORGANIZE;W:\LOTUSW4\APPROACH;W:\LOTUSW4\FLG;W:\LOTUSW4\WORDPRO;W:\APPS\BA2KWS;W:\PROGRAMS\qt4\bin;W:\APPS\EMBLSH;M:\ecs\ACPI\UTIL;U:\WATCOM\BINP;U:\WATCOM\BINW;U:\VISPRORX;;;/usr/xpg4/bin

Question: What is that all about?

As Paul hinted, it is looking for grep instead of grep.exe. You need exeext=.exe or/and ac_executable_extensions=.exe in your environment, preferably in config.site or set GREP=grep.exe, then perhaps PERL=perl.exe and so on.
BTW, I didn't release that moztools though it is basically the same as the one I use.

DougB

  • Sr. Member
  • ****
  • Posts: 407
    • View Profile
Re: What is the future of this platform?
« Reply #79 on: 2012.09.29, 17:42:02 »
Thanks guys. This will take a bit of study, and experimenting, and I don't have time at the moment.

Quote
BTW, I didn't release that moztools though it is basically the same as the one I use.

Sorry, I was thinking of MZFNTCFGFT.

I suppose that I really should get a new copy of Paul's build environment, but what I have is working well for what I actually use it for so I hate to upset the apple cart.

More, when I find the time...

DougB

  • Sr. Member
  • ****
  • Posts: 407
    • View Profile
Re: What is the future of this platform?
« Reply #80 on: 2012.09.30, 18:28:16 »
Paul:

Quote
FWIW - I don't recommend removing the CONFIG_SITE reference.

Well, I get a LOT further without it, than I do with it. It always stops with:
Code: [Select]
configure.:3322: error: in `U:/wget-1.14':
configure.:3325: error: failed to load site script u:/moztools/config.site-gcc335b4
See `config.log' for more details

When I look in config.log, the only relevant thing that I see, are these three lines, which tell me nothing.

If I REM the site entry in GCC335.cmd (I also added set grep=grep.exe), I get a lot of output, that looks pretty reasonable, then it stops at:
Code: [Select]
./configure.lineno: 6947: Syntax error: "!" unexpected

If I look in the configure file (which I have to assume this is working with), line 6947 is blank. I have no idea what it wants.

Dave: I haven't got around to trying anything that you suggested, yet. More when I find the time.