Skip to contentSkip to conversation

compile-error: stdin is not a constant

DISCUSSION Wolfgang Haeuptli 3 participants 4 messages Nov 3, 1999

lore
Share & tools
lore
#0 lore 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/

#1 lore raw
Quoted 5 lines · Wolfgang Haeuptli

Hello people

sorry for the (probably) basic question...

Quoted 8 lines

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.

Quoted 4 lines

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   |
|         [email protected]         |  |       [email protected]      |
\--------------------------------/  \--------------------------------/

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

#3 lore raw
In reply to Martin Costabel
Quoted 3 lines · Martin Costabel

Maybe this will work (1):

FILE *foo = (FILE *) STDIN_FILENO;

No no no no no! STDIN_FILENO is a -number-, not a -pointer-!

Quoted 6 lines

In a similar situation, I learned from Tom Rini that the correct way would be (2)

static file *file ;
static void file_construct (void) __attribute__((constructor)); static void file_construct (void) { file = stdin; }

Yes, that's it. gcc specific, but works. (1) is DEFINITELY wrong.

Dan

/--------------------------------\ /--------------------------------\

|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         [email protected]         |  |       [email protected]      |
\--------------------------------/  \--------------------------------/

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

#2 lore raw
In reply to Daniel Jacobowitz
Quoted 10 lines · Daniel Jacobowitz
Quoted 8 lines · Wolfgang Haeuptli

Hello people

sorry for the (probably) basic question...

Since I installed R5, some programs (that used to compile OK on R4) complain about :

Quoted 10 lines
Quoted 5 lines

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.

Quoted 2 lines

when I replaced this line with: FILE *foo = STDIN_FILENO;

Maybe this will work (1):

FILE *foo = (FILE *) STDIN_FILENO;

Quoted 9 lines
Quoted 2 lines

( 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).

In a similar situation, I learned from Tom Rini that the correct way would be (2)

static file *file ;
static void file_construct (void) __attribute__((constructor)); static void file_construct (void) { file = stdin; }

This might be in the list archives somewhere. I had a similar problem with stdout when compiling Scilab. I used Tom's version (2), and it worked, but I saw that the Scilab people in a later version used the shorter version (1), and this seems to work, too.

More precisely, they just added the "|| defined(__GNUC__)" in the following code:

#if defined(__CYGWIN32__) || defined(__MINGW32__) || defined(__GNUC__) static FILE *file= (FILE *) 0;
#define FPRINTF(x) ( file != (FILE*) 0) ? fprintf x : 0 #else
static FILE *file= stdout ;
#define FPRINTF(x) fprintf x
#endif

--
Martin

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