From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: T Kiernan <tkiernan@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: GCC4.1.1
Date: Fri, 26 Oct 2007 21:23:00 -0000 [thread overview]
Message-ID: <20071026150510.GA31750@ins.uni-bonn.de> (raw)
In-Reply-To: <705ae6ad0710260155x2af15b93r49110bd36e0c6916@mail.gmail.com>
Hello T,
* T Kiernan wrote on Fri, Oct 26, 2007 at 10:55:11AM CEST:
> Hi Ralf,
>
> I am running GCC4.1.1 on RedHat4.5 on powerpc .
I'm not quite sure how come I get honored by being asked this question,
but 'fraid I can't help you much, sorry. You could try to
#undef _XOPEN_SOURCE
to avoid getting the crypt from unistd.h. I'm sure the openssl people
can help you better on this one, their mailing list would be more
suitable than gcc-help, too.
Cheers,
Ralf
parent reply other threads:[~2007-10-26 15:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <705ae6ad0710260155x2af15b93r49110bd36e0c6916@mail.gmail.com>]
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=20071026150510.GA31750@ins.uni-bonn.de \
--to=ralf.wildenhues@gmx.de \
--cc=gcc-help@gcc.gnu.org \
--cc=tkiernan@gmail.com \
/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).