Undefined reference to 'S_ISLINK'

[Guest]

Hi all,
I have to implement ls using system calls. The S_ISREG, S_ISDIR,
S_ISCHR etc. seem to be working fine. But S_ISLINK Is giving this
error:

/tmp/ccWJ1Lbs.o: In function `longls':
ls.c.text+0x354): undefined reference to `S_ISLINK'
collect2: ld returned 1 exit status

In man pages it is written that this macro is 'Not in POSIX.1-1996'.
So does that mean my system isn't POSIX.1-1996? If so, how can I know
whether the file is a link? Can anyone help me out?

 

[Kenny McCormack]

Hi all,
I have to implement ls using system calls. The S_ISREG, S_ISDIR,
S_ISCHR etc. seem to be working fine. But S_ISLINK Is giving this
error:

/tmp/ccWJ1Lbs.o: In function `longls':
ls.c.text+0x354): undefined reference to `S_ISLINK'
collect2: ld returned 1 exit status

In man pages it is written that this macro is 'Not in POSIX.1-1996'.
So does that mean my system isn't POSIX.1-1996? If so, how can I know
whether the file is a link? Can anyone help me out?

Please do. Allow me to be the first in the feeding frenzy:

Off topic. Not portable. Cant discuss it here. Blah, blah, blah.

Useful clc-related links:

 

[Mark Bluemel]

Hi all,
I have to implement ls using system calls. The S_ISREG, S_ISDIR,
S_ISCHR etc. seem to be working fine. But S_ISLINK Is giving this
error:

/tmp/ccWJ1Lbs.o: In function `longls':
ls.c.text+0x354): undefined reference to `S_ISLINK'
collect2: ld returned 1 exit status

Of course this is not about C but about un*x facilities,
so it would be better addressed somewhere like
comp.unix.programmer, really. However ...

<OT>
On my linux system this is S_ISLNK, with only one 'I'... I suspect
that's your problem...
</OT>

 

[Jens Thoms Toerring]

I have to implement ls using system calls. The S_ISREG, S_ISDIR,
S_ISCHR etc. seem to be working fine. But S_ISLINK Is giving this
error:

/tmp/ccWJ1Lbs.o: In function `longls':
ls.c.text+0x354): undefined reference to `S_ISLINK'
collect2: ld returned 1 exit status

In man pages it is written that this macro is 'Not in POSIX.1-1996'.
So does that mean my system isn't POSIX.1-1996? If so, how can I know
whether the file is a link? Can anyone help me out?

You better ask these kinds of questions in a UNIX newsgroup, e.g.
comp.unix.programmer, since these macros aren't part of the C but
of the POSIX standard, which isn't the same;-)

<OT>
Perhaps you should read the man page again and check if 'S_ISLINK'
is really spelled that way and not perhaps 'S_ISLNK' instead...
</OT>
Regards, Jens

 

[Richard]

Of course this is not about C but about un*x facilities,
so it would be better addressed somewhere like
comp.unix.programmer, really. However ...

<OT>
On my linux system this is S_ISLNK, with only one 'I'... I suspect
that's your problem...
</OT>

Please guys, stop with the <OT> tags. It is just *so* pathetic and
"jobsworth".

 

[Mark Bluemel]

<OT>
Perhaps you should read the man page again and check if 'S_ISLINK'
is really spelled that way and not perhaps 'S_ISLNK' instead...
</OT>

According to Brian Kernighan and Rob Pike: Ken Thompson was once asked
what he would do differently if he were redesigning the UNIX System.
His reply: "I'd spell creat with an e." (as related in a footnote in
"The UNIX Programming Environment" by K&P)

 

[Martin Ambuhl]

Please guys, stop with the <OT> tags. It is just *so* pathetic and

^^
an interesting missing comma

"jobsworth".

Please, Richard, stop your inane attempts to destroy the topicality of
< It is incredibly childish and suggests that you
need to find something, anything, positive to do with your life.

 

[Kenny McCormack]

^^
an interesting missing comma

Please, Richard, stop your inane attempts to destroy the topicality of
< It is incredibly childish and suggests that you
need to find something, anything, positive to do with your life.

Oh, the complete irony...