linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Haeuptli <whaeuptli@bluewin.ch>
To: linuxppc-dev@lists.linuxppc.org
Subject: compile-error: stdin is not a constant
Date: Wed, 3 Nov 1999 13:25:44 +0100	[thread overview]
Message-ID: <99110313351500.00438@localhost.localdomain> (raw)


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};  )

when I replaced this line with: FILE *foo = STDIN_FILENO; 
( defined in unistd.h), compilation works, but the resulting program
segfaults...

Any hints to make this work would be very much appreciated.

Wolfgang Haeuptli
  

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~1999-11-03 12:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-03 12:25 Wolfgang Haeuptli [this message]
1999-11-03 15:36 ` compile-error: stdin is not a constant Daniel Jacobowitz
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=99110313351500.00438@localhost.localdomain \
    --to=whaeuptli@bluewin.ch \
    --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).