From: "Rolland Wong" <rolland@linkmark-tech.com>
To: <gnu@gnu.org>
Subject: some question about ANSI C
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <200001031518.KAA15506@mescaline.gnu.org> (raw)
Message-ID: <20000401000000.AkLFiJl4LuT1dVVJrGGASh3WBQo1JX6_peej4SM4Tjw@z> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1553 bytes --]
Dear Sir/ Madam,
Â
   I'm not sure if I wrote to a right
party..  Â
   I've encounter a problem while compile the
program, mod_perl.
   I can successfully compile the mod_ssl and
Apache v1.3.9 without any problem.
   But when I try to compile the mod_perl
v1.21 into Apache Source in order to include this program, the makefile seems
not really like the GCC v2.95.2. It got the following error message
:-
Â
Configure mod_perl with ../apache_1.3.9/src ? [y] Shall I
build httpd in ../apache_1.3.9/src for you? [y] Appending mod_perl to
src/Configuration Using config file:
/source/javaserver/mod_perl-1.21/src/Configuration Creating
Makefile  + configured for Linux platform  + setting C compiler
to gcc  + setting C pre-processor to gcc -E  + checking for
system header files  + adding selected modules  + checking
sizeof various data types  + doing sanity check on compiler and
options ** A test compilation with your Makefile configuration ** failed.
This is most likely because your C compiler ** is not ANSI. Apache requires
an ANSI C Compiler, such ** as gcc. The above error message from your
compiler ** will also provide a clue.
   It's great the if you can help me to solve
this problem, since I've asked Apache while they said this problem should
related to GCC and not them...
Â
   Thanks again for your patient and awaiting
for your reply.
Â
Best Regards,
Â
Rolland Wong
System Adminstrator
Linkmark Technology Ltd.
next reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-03 7:19 Rolland Wong [this message]
2000-04-01 0:00 ` Rolland Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200001031518.KAA15506@mescaline.gnu.org \
--to=rolland@linkmark-tech.com \
--cc=gnu@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).