public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: sherry <sherry@zeroknowledge.com>
To: Agung Yogaswara <azung@xerxes.intern.trabas.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc-2.95.2
Date: Thu, 22 Feb 2001 10:46:00 -0000	[thread overview]
Message-ID: <3A955E62.F1901903@zeroknowledge.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0102221324280.1809-100000@xerxes.intern.trabas.com>

I have seen something like .... in my case, I was missing the _D_GNU_SOURCE .
For more info check /usr/include/features.h, to get the right flavor..
hope it helps

Agung Yogaswara wrote:

> I have gcc-2.95.2 installed with glibc-2.2 updated for Red Hat 7.0 plus
> the patch. But I got this error when compiling a program:
>
> In file included from
> /usr/lib/gcc-lib/i586-pc-linux-gnu/2.95.2/../../../../include/g++-3/iostream.h:31,
>                  from
> /usr/lib/gcc-lib/i586-pc-linux-gnu/2.95.2/../../../../include/g++-3/iostream:6,
>                  from ../include/JTC/Types.h:58,
>                  from Cond.cpp:11:
> /usr/lib/gcc-lib/i586-pc-linux-gnu/2.95.2/../../../../include/g++-3/streambuf.h: In
> method `struct streampos streambuf::pubseekoff(long long int,
> ios::seek_dir, int = 3)':
> /usr/lib/gcc-lib/i586-pc-linux-gnu/2.95.2/../../../../include/g++-3/streambuf.h:362: conversion
> from `__off64_t' to non-scalar type `streampos' requested
> /usr/lib/gcc-lib/i586-pc-linux-gnu/2.95.2/../../../../include/g++-3/streambuf.h: In
> method `struct streampos streambuf::pubseekpos(_G_fpos64_t, int = 3)':
> /usr/lib/gcc-lib/i586-pc-linux-gnu/2.95.2/../../../../include/g++-3/streambuf.h:364: `struct
> streampos' used where a `long long int' was expected
>
> In file included from Cond.cpp:28:
> /usr/include/sys/time.h: At top level:
> /usr/include/sys/time.h:69: two or more data types in declaration of
> `__tz'
>
> Any ideas?
>
> Thanks

  parent reply	other threads:[~2001-02-22 10:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-21 22:29 gcc-2.95.2 Agung Yogaswara
2001-02-21 23:12 ` gcc-2.95.2 Alexandre Oliva
2001-02-22 17:50   ` gcc-2.95.2 Agung Yogaswara
2001-02-22 18:08     ` gcc-2.95.2 Agung Yogaswara
2001-02-21 23:18 ` gcc-2.95.2 Jerry Miller
2001-02-22 17:50   ` gcc-2.95.2 Agung Yogaswara
2001-02-22 18:00     ` gcc-2.95.2 Jerry Miller
2001-02-22 18:08     ` gcc-2.95.2 Agung Yogaswara
2001-02-22 10:46 ` sherry [this message]
2001-02-22 10:50 ` gcc-2.95.2 sherry
  -- strict thread matches above, loose matches on Subject: below --
2001-10-29 20:09 gcc-2.95.2 sachin lamsoge
2001-03-16  8:13 gcc-2.95.2 David Korn
2001-03-16  7:29 gcc-2.95.2 Jumblat, Ghassan
1999-11-06 13:08 gcc-2.95.2 Inferno
1999-11-06 14:50 ` gcc-2.95.2 Tim Prince
1999-11-06 17:09   ` gcc-2.95.2 Inferno
1999-11-07 22:52     ` gcc-2.95.2 Mumit Khan
1999-11-08  5:55       ` gcc-2.95.2 Inferno
1999-11-30 23:28         ` gcc-2.95.2 Inferno
1999-11-08  5:58       ` gcc-2.95.2 Inferno
1999-11-08 19:09         ` gcc-2.95.2 Tim Prince
1999-11-30 23:28           ` gcc-2.95.2 Tim Prince
1999-11-30 23:28         ` gcc-2.95.2 Inferno
1999-11-30 23:28       ` gcc-2.95.2 Mumit Khan
1999-11-30 23:28     ` gcc-2.95.2 Inferno
1999-11-30 23:28   ` gcc-2.95.2 Tim Prince
1999-11-30 23:28 ` gcc-2.95.2 Inferno

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=3A955E62.F1901903@zeroknowledge.com \
    --to=sherry@zeroknowledge.com \
    --cc=azung@xerxes.intern.trabas.com \
    --cc=gcc-help@gcc.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).