From: Igor Gueths <igueths@comcast.net>
To: speakup@braille.uwo.ca
Subject: apache compile problem fixed
Date: Mon, 19 Jan 2004 00:41:35 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0401190040490.5809-100000@igueths> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all. Its amazing what copying one header file from
/usr/local/gcc-lib/i686-pc-linux-gnu/3.3/include to /usr/local/include can
do. Turns out my compile problems are now fixed...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Made with pgp4pine 1.75-6
iD8DBQFAC24RGT7f58lCbH0RAnOSAJwJGC5LYCv8CfAsH8DvXMxxGXC9lACgqE00
F54yJp/Ry8cg+unwchzyDFY=
=KBeF
-----END PGP SIGNATURE-----
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.44.0401190040490.5809-100000@igueths \
--to=igueths@comcast.net \
--cc=speakup@braille.uwo.ca \
/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).