[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
libc0.3-dev: weirdness with sockaddr_un
From: |
Robert Millan |
Subject: |
libc0.3-dev: weirdness with sockaddr_un |
Date: |
Thu, 3 Apr 2003 03:42:11 +0200 |
User-agent: |
Mutt/1.5.3i |
Package: libc0.3-dev
Severity: normal
hi!
the following code seems to be compliant with the Glibc documentation
referred to sockaddr_un, as it provides a char* as the second component
of the struct:
#include <sys/socket.h>
#include <sys/un.h>
main ()
{
sockaddr_un test = { AF_LOCAL, "" };
}
however, when built with g++ (and not with gcc) on GNU/Hurd, it reports
mismatch errors:
test.c: In function `int main()':
test.c:6: invalid conversion from `const char*' to `unsigned char'
which is strange that it expects a char when both the documentation
and <sys/un.h> agree that it should be a char*.
the code in question compiles fine on GNU/Linux.
--
Robert Millan
make: *** No rule to make target `war'. Stop.
Another world is possible - Just say no to genocide
- libc0.3-dev: weirdness with sockaddr_un,
Robert Millan <=
- Re: Bug#187391: libc0.3-dev: weirdness with sockaddr_un, GOTO Masanori, 2003/04/03
- Message not available
- Re: Bug#187391: libc0.3-dev: weirdness with sockaddr_un, GOTO Masanori, 2003/04/03
- Re: Bug#187391: libc0.3-dev: weirdness with sockaddr_un, Stephan Trebels, 2003/04/03
- Re: Bug#187391: libc0.3-dev: weirdness with sockaddr_un, Robert Millan, 2003/04/03
- Re: Bug#187391: libc0.3-dev: weirdness with sockaddr_un, Jeff Bailey, 2003/04/03
- Re: Bug#187391: libc0.3-dev: weirdness with sockaddr_un, Robert Millan, 2003/04/03
- Re: Bug#187391: libc0.3-dev: weirdness with sockaddr_un, Niels Möller, 2003/04/03
Re: libc0.3-dev: weirdness with sockaddr_un, Niels Möller, 2003/04/03