From: Momchil Velikov <velco@fadata.bg>
To: "tcheer@gmx.de" <tcheer@gmx.de>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Problem with gcc-3.2
Date: Wed, 30 Oct 2002 04:03:00 -0000 [thread overview]
Message-ID: <20021030140143.6aca86e7.velco@fadata.bg> (raw)
In-Reply-To: <3DBFCED5.4070400@gmx.de>
On Wed, 30 Oct 2002 13:21:41 +0100
"tcheer@gmx.de" <tcheer@gmx.de> wrote:
> Hi group,
>
> I have a programm I was able to compile with gcc-2.96, Right now I
> have gcc-3.2 on my machine and I experience some problems during
> compilation.
>
> "type specifier omitted for parameter `va_list'"
> How can I solve this?
#include <stdarg.h>
> I would like to reinstall gcc-2.96 in case my code could not be solved
> with this gcc version, but at http://gcc.gnu.org I was not able to
> find exactly this version. I would appreciate a link where I can
> download it from.
gcc-2.96 is not a FSF release, I guess you'd need to find the RedHat's
rpm.
~velco
prev parent reply other threads:[~2002-10-30 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 3:24 tcheer
2002-10-30 4:03 ` Momchil Velikov [this message]
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=20021030140143.6aca86e7.velco@fadata.bg \
--to=velco@fadata.bg \
--cc=gcc-help@gcc.gnu.org \
--cc=tcheer@gmx.de \
/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).