Re: gcc issue [SOLVED]

2009-02-05 Thread Steve
Mamoru Tasaka wrote: > Steve wrote, at 02/05/2009 11:26 PM +9:00: > > OK, now I am really confused. ... > > In that way you are not using the srpm you downloaded anymore. > You are just unpacking the tarball (with no patched) and are > compiling vanilla source by yourself. Ah... umm...

Re: gcc issue

2009-02-05 Thread Bryn M. Reeves
Steve wrote: I went to rpmfind (http://rpmfind.net/linux/RPM/fedora/updates/9/x86_64/dhclient-4.0.0-22.fc9.x86_64.html) to get the dhcp src rpm and downloaded it. It comes from ftp://download.fedora.redhat.com/pub/fedora/linux/updates/9/SRPMS.newkey/dhcp-4.0.0-22.fc9.src.rpm When I ran rpm -q

Re: gcc issue

2009-02-05 Thread Mamoru Tasaka
Steve wrote, at 02/05/2009 11:26 PM +9:00: OK, now I am really confused. I went to rpmfind (http://rpmfind.net/linux/RPM/fedora/updates/9/x86_64/dhclient-4.0.0-22.fc9.x86_64.html) to get the dhcp src rpm and downloaded it. It comes from ftp://download.fedora.redhat.com/pub/fedora/linux/updat

Re: gcc issue

2009-02-05 Thread Steve
Steve wrote: > > Mamoru Tasaka wrote: > > Steve wrote, at 02/05/2009 03:55 AM +9:00: > > > Kevin Kofler wrote: > > >> Steve wrote: > > >>> I had tried putting #define __USE_GNU in the code but that didn't make > > >>> any > > >>> difference. > > >> You need to #define _GNU_S

Re: gcc issue

2009-02-04 Thread Steve
Mamoru Tasaka wrote: > Steve wrote, at 02/05/2009 03:55 AM +9:00: > > Kevin Kofler wrote: > >> Steve wrote: > >>> I had tried putting #define __USE_GNU in the code but that didn't make any > >>> difference. > >> You need to #define _GNU_SOURCE, not __USE_GNU. glibc #undefs all the >

Re: gcc issue

2009-02-04 Thread Mamoru Tasaka
Steve wrote, at 02/05/2009 03:55 AM +9:00: Kevin Kofler wrote: Steve wrote: I had tried putting #define __USE_GNU in the code but that didn't make any difference. You need to #define _GNU_SOURCE, not __USE_GNU. glibc #undefs all the __USE_* macros, then #defines them based on the _*_SOUR

Re: gcc issue

2009-02-04 Thread Steve
Kevin Kofler wrote: > Steve wrote: > > I had tried putting #define __USE_GNU in the code but that didn't make any > > difference. > > You need to #define _GNU_SOURCE, not __USE_GNU. glibc #undefs all the > __USE_* macros, then #defines them based on the _*_SOURCE macros you used. > ...an

Re: gcc issue

2009-02-04 Thread Kevin Kofler
Steve wrote: > I had tried putting #define __USE_GNU in the code but that didn't make any > difference. You need to #define _GNU_SOURCE, not __USE_GNU. glibc #undefs all the __USE_* macros, then #defines them based on the _*_SOURCE macros you used. Kevin Kofler -- fedora-list mailing li

Re: gcc issue

2009-02-04 Thread Steve
Jakub Jelinek wrote: > On Wed, Feb 04, 2009 at 10:35:09AM -0500, Steve wrote: > > On my fully-up-to-date F9 system, this file, junk.c: > > > > #include > > > > struct my_struct { > > struct in6_addripi6_addr; > > unsigned intipi6_ifindex; > > }; > > > > int main ( i

Re: gcc issue

2009-02-04 Thread Jakub Jelinek
On Wed, Feb 04, 2009 at 10:35:09AM -0500, Steve wrote: > On my fully-up-to-date F9 system, this file, junk.c: > > #include > > struct my_struct { > struct in6_addripi6_addr; > unsigned intipi6_ifindex; > }; > > int main ( int argc, char **argv ) > { > int

gcc issue

2009-02-04 Thread Steve
On my fully-up-to-date F9 system, this file, junk.c: #include struct my_struct { struct in6_addripi6_addr; unsigned intipi6_ifindex; }; int main ( int argc, char **argv ) { int x,y; struct in6_pktinfo junk; struct my