>Number: 3341 >Category: config >Synopsis: When I try to compile Apache it don't recognizes my os. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Wed Nov 4 11:10:01 PST 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.3 >Environment: I'm running Win95 (Pentium II 266MHz)and used GCC for Win32 to compile the program. I don't know the version of GCC but it is downloaded within three weeks from now. >Description: This is what happens when I run GCC.
BASH.EXE-2.01$ configure Using config file: Configuration Creating Makefile hostinfo: not found Sorry, but we cannot grok "i586-whatever-CYGWIN32_95|4.0|19.0" uname -m i586 uname -r 4.0 uname -s CYGWIN32_95 uname -v 19.0 uname -X uname: invalid option -- X Try `uname --help' for more information. Ideally, read the file PORTING, do what it says, and send the resulting patches to The Apache Group by filling out a report form at http://www.apache.org/bug_report.html. If you don't wish to do the port yourself, please submit this output rather than the patches. Thank you. Pressing on with the build process, but all bets are off. Do not be surprised if it fails. If it works, and even if it does not, please contact the above address. + configured for Unknown and unsupported OS platform + setting C compiler to gcc + setting C pre-processor to gcc -E + checking for system header files + adding selected modules + doing sanity check on compiler and options Creating Makefile in support Creating Makefile in main Creating Makefile in ap Creating Makefile in regex Creating Makefile in os/unix Creating Makefile in modules/standard BASH.EXE-2.01$ >How-To-Repeat: Just try to compile it on a Win95 with GCC for Win32. >Fix: I know that there already is a precompiled version of Apache for Win32 compiling it gives one the advantage of choosing the components. >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]
