From: Daniel Jacobowitz <drow@false.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: compile-error: stdin is not a constant
Date: Wed, 3 Nov 1999 10:36:18 -0500 [thread overview]
Message-ID: <19991103103617.A26462@drow.res.cmu.edu> (raw)
In-Reply-To: <99110313351500.00438@localhost.localdomain>; from Wolfgang Haeuptli on Wed, Nov 03, 1999 at 01:25:44PM +0100
On Wed, Nov 03, 1999 at 01:25:44PM +0100, Wolfgang Haeuptli wrote:
>
> Hello people
>
> sorry for the (probably) basic question...
>
> Since I installed R5, some programs (that used to compile OK on R4)
> complain about :
>
> initializer element for 'foo' is not constant
>
> while compiling constructs like:
>
> FILE *foo = stdin; (or FILE *foo = {(FILE *) stdin}; )
Because it isn't a constant any more.
>
> when I replaced this line with: FILE *foo = STDIN_FILENO;
> ( defined in unistd.h), compilation works, but the resulting program
> segfaults...
Which should generate one hell of a warning, since STDIN_FILENO is a
small number, not a struct FILE *.
You need to initialize the variable early in main() or something along
those lines, or you can declare a constructor using __attribute__,
although I do not remember the syntax (search list archives).
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| dan@debian.org | | dmj+@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-11-03 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-03 12:25 compile-error: stdin is not a constant Wolfgang Haeuptli
1999-11-03 15:36 ` Daniel Jacobowitz [this message]
1999-11-03 17:53 ` Martin Costabel
1999-11-03 16:59 ` Daniel Jacobowitz
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=19991103103617.A26462@drow.res.cmu.edu \
--to=drow@false.org \
--cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).