[PATCH] Apache 1.3.21-dev for NetWare builds (1)

[Pavel Novy <no...@feld.cvut.cz>]

Hi all,

I've succeded with builds of the Apache 1.3.21-dev for NetWare a few
months ago. I am able to compile almost whole set of NLM modules using
the GNU utilities (make, gcc, ..., nlmconv) on Linux and Win32
platforms. Unfortunatelly, there are some fixes in the sources needed to
get it work. I am currently doing this by a set of patches applied to
the latest CVS sources. It's a big problem to me to hold these patches
up-to-date due to changes in the sources they are sometimes occuring.

My primary target is to make builds of the Apache (and any of
Apache-related modules) for NetWare platform possible with the GNU
stuff, Watcom and CodeWarrior by default, without no additional changes
in the sources. Only CodeWarrior from Metrowerks can be currently used.

Here is a list of known problems I will propose to be fixed:

1. import/export files format issues
2. a _getch macro definition issue
3. redefinition of types issues
4. an uninitialized data issues
5. CodeWarrior bitfields alignment (compatibility) issue
6. ...

An explanation for #1 issues follows. If I will get some covetable
response in this mailing list, then I will post the next ones.

a) There is a problem with import/export files in the CVS sources files
if linking NLMs with a nlmconv utility from the GNU binutils package. It
expects at least one delimiter (space, tab) before symbol name on each
line. All import/export files included in Novell NDK are using this
convention, so no problem with these files when building the Apache for
NetWare with the GNU stuff.

b) There is a problem with import/export files in the CVS sources if
linking NLMs with a wlink linker (from Watcom SDK) - it expects that all
symbols are separated by a comma. All import/export files included in
Novell NDK are using this convention, so no problem with these files
when building the Apache for NetWare with Watcom.

Attached patches for all files affected by the issues. If these files
are generated automatically by some scripts, those scripts should be
fixed too. I suppose that CodeWarrior has no problem with this
"NDK-like" format.

Regards,
Pavel Novy

Re: [PATCH] Apache 1.3.21-dev for NetWare builds (1)

["William A. Rowe, Jr." <wr...@rowe-clan.net>]

From: "Pavel Novy" <no...@feld.cvut.cz>
Sent: Wednesday, August 01, 2001 8:00 AM


> Hi all,
> 
> I've succeded with builds of the Apache 1.3.21-dev for NetWare a few
> months ago. I am able to compile almost whole set of NLM modules using
> the GNU utilities (make, gcc, ..., nlmconv) on Linux and Win32
> platforms. Unfortunatelly, there are some fixes in the sources needed to
> get it work. I am currently doing this by a set of patches applied to
> the latest CVS sources. It's a big problem to me to hold these patches
> up-to-date due to changes in the sources they are sometimes occuring.
> 
> My primary target is to make builds of the Apache (and any of
> Apache-related modules) for NetWare platform possible with the GNU
> stuff, Watcom and CodeWarrior by default, without no additional changes
> in the sources. Only CodeWarrior from Metrowerks can be currently used.
> 
> Here is a list of known problems I will propose to be fixed:
> 
> 1. import/export files format issues
> 
> An explanation for #1 issues follows. If I will get some covetable
> response in this mailing list, then I will post the next ones.
> 
> a) There is a problem with import/export files in the CVS sources files
> if linking NLMs with a nlmconv utility from the GNU binutils package. It
> expects at least one delimiter (space, tab) before symbol name on each
> line. All import/export files included in Novell NDK are using this
> convention, so no problem with these files when building the Apache for
> NetWare with the GNU stuff.
> 
> b) There is a problem with import/export files in the CVS sources if
> linking NLMs with a wlink linker (from Watcom SDK) - it expects that all
> symbols are separated by a comma. All import/export files included in
> Novell NDK are using this convention, so no problem with these files
> when building the Apache for NetWare with Watcom.
> 
> Attached patches for all files affected by the issues. If these files
> are generated automatically by some scripts, those scripts should be
> fixed too. I suppose that CodeWarrior has no problem with this
> "NDK-like" format.

> --- src/support/httpd.exp Tue Feb  6 05:17:00 2001
> +++ src_gcc/support/httpd.exp Wed Aug  1 13:10:18 2001
> @@ -1,424 +1,424 @@
>  #! .
> -ap_MD5Encode 
...
> + ap_MD5Encode,
...

These changes would likely confuse some other platform, since (all but the one
ApacheCore.exp example) are shared by several.  For Apache 1.3.x, can I
suggest you drop a fixexp.pl script somewhere in the tree (I'd suggest build/)
that would allow -t or -c args, to insert tabs and/or comments, as needed, in
all of the .exp/.imp files scattered throughout the tree?  The httpd.exp especially
worries me on AIX.

In Apache 2.0, exports are generated by script.  It should be possible to add
the same level of 'control' to the generation, so you are spared this headache
based on a ./Configure flag.  Since that port is just beginning, I'm sure Brad
Nicholes will make a mental note to introduce this option :)

Bill

[and yes... we are interested in the other patches/rationals.  Try to keep each
as focused and limited in scope as you did with this patch - it helps!  Brad has
pretty much the final word on what does/doesn't go into the os/netware branch.]