Feature Requests item #1735177, was opened at 2007-06-11 19:38
Message generated for change (Comment added) made by bagder
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350976&aid=1735177&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: libcurl
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Patrick MONNERAT (monnerat)
Assigned to: Daniel Stenberg (bagder)
Summary: Porting to OS/400

Initial Comment:
A port of the library to OS/400 would be great.
I started doing it, using an ASCII runtime (on an EBCDIC machine). The library compiles and runs providing you apply the attached patch (against CVS 11 june 2007).

It is quite long, since it maps tabs to spaces, trims right spaces and limits line length to 80 chars.

In addition there are a few files added. All these changes were needed for the OS/400... which is not standard at all.

For the moment, there is no SSL support (SSL on OS/400 is not OpenSSL), and no EBCDIC support. I plan to do it...

This is a work in progress and if it please you (the development team!), a write access to CVS would be of great benefit for it ...

Thanks in advance for a reply !

----------------------------------------------------------------------

>Comment By: Daniel Stenberg (bagder)
Date: 2007-06-11 22:25

Message:
Logged In: YES
user_id=1110
Originator: NO

I second the objection to all the unnecessary white spaces changes.

Further, why are so many Curl_* functions mentioned in the
libcurl-os400.bndsrc file? The ones with uppercase C are library internal
only.

Also, I suggest you subscribe to the curl-library list and continue this
effort there. Post patches and discuss approach with the lot there, as it
offers a better way for discussions within the entire libcurl community.

----------------------------------------------------------------------

Comment By: Dan Fandrich (dfandrich)
Date: 2007-06-11 21:14

Message:
Logged In: YES
user_id=236775
Originator: NO

Are the whitespace and 80 column limit changes strictly necessary for
OS/400? Those completely hide within the diff the actual changes necessary
for OS/400 support. The 80 column limit especially can really reduce the
readability of the code on all platforms. If the OS/400 compiler is so
truly broken as to not accept the code otherwise, then those changes could
be done in a preprocessing phase using indent(1) and expand(1).

For the libcurl-os400.bndsrc file, isn't there some way to generate it at
compile time? I'm assuming it's just a list of libcurl exports that are
already marked with CURL_EXTERN in the source. Similarly, the file
Makefile.inc ought to be used instead of hard-coding the source files into
makefile-os400.sh. Both these changes will future-proof the OS/400 build
mechanism from future libcurl changes. It's too bad the autotools won't
work (I assume).

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350976&aid=1735177&group_id=976
Received on 2007-06-11