Re: a gcc3.1 bug ?
On Sun, Jul 28, 2002 at 02:40:15PM +0800, Huang wen hui wrote: hi, I used gcc3.1 from ports to compile jdk1.3.1-p7 hotspot, I got problem in compiing /usr/src/lib/libc_r/uthread/pthread_private.h : While I - unfortunately - do not know the solution to your problem, I would like to report that I compiled the jdk with the new patchset just yesterday on my week-old -CURRENT and it worked ok. However, I always clean out /usr/include before installworld, so there may be no stale header files there. -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: a gcc3.1 bug ?
On Sun, Jul 28, 2002 at 02:40:15PM +0800, Huang wen hui wrote: /usr/src/lib/libc_r/uthread/pthread_private.h:947: parse error before `__null' /usr/src/lib/libc_r/uthread/pthread_private.h:957: parse error before `__null' /usr/src/lib/libc_r/uthread/pthread_private.h:965: parse error before `__null' gmake[2]: *** [os_linux_i486.o] Error 1 gmake[2]: Leaving directory `/usr/ports/java/jdk13/work/hotspot1.3.1/build/linux/linux_i486_core/jvmg' gmake[1]: *** [the_vm] Error 2 gmake[1]: Leaving directory `/usr/ports/java/jdk13/work/hotspot1.3.1/build/linux/linux_i486_core/jvmg' gmake: *** [jvmgcore] Error 2 but if I change pthread_attr pthread_attr_default to other name, the compiler will pass. Does gcc31 have bug ? Nope, #undef that symbol. And try again. I can't remember exactly what the line is but repeat for all three places. bill To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: a gcc3.1 bug ?
On Sun, Jul 28, 2002 at 02:40:15PM +0800, Huang wen hui wrote: /usr/ports/java/jdk13/work/hotspot1.3.1/src/os_cpu/linux_i486/vm/os_linux_i486.cpp:41: /usr/src/lib/libc_r/uthread/pthread_private.h:947: parse error before `__null' /usr/src/lib/libc_r/uthread/pthread_private.h:957: parse error before `__null' /usr/src/lib/libc_r/uthread/pthread_private.h:965: parse error before `__null' ... but if I change pthread_attr pthread_attr_default to other name, the compiler will pass. Does gcc31 have bug ? Revisited Do it like this: #undef pthread_attr_default #undef pthread_mutexattr_default #undef pthread_condattr_default #include uthread/pthread_private.h before the header files is included. I'm a bit surprised that my changes to those source files (HotSpot) weren't included in the latest release. Building it otherwise is just going to be pure hell. bill To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: a gcc3.1 bug ?
On Sun, Jul 28, 2002 at 03:11:01AM -0700, Bill Huey wrote: On Sun, Jul 28, 2002 at 02:40:15PM +0800, Huang wen hui wrote: /usr/ports/java/jdk13/work/hotspot1.3.1/src/os_cpu/linux_i486/vm/os_linux_i486.cpp:41: /usr/src/lib/libc_r/uthread/pthread_private.h:947: parse error before `__null' /usr/src/lib/libc_r/uthread/pthread_private.h:957: parse error before `__null' /usr/src/lib/libc_r/uthread/pthread_private.h:965: parse error before `__null' ... but if I change pthread_attr pthread_attr_default to other name, the compiler will pass. Does gcc31 have bug ? Revisited Do it like this: #undef pthread_attr_default #undef pthread_mutexattr_default #undef pthread_condattr_default #include uthread/pthread_private.h before the header files is included. I'm a bit surprised that my changes to those source files (HotSpot) weren't included in the latest release. Building it otherwise is just going to be pure hell. The patchset matches what is in the repository. Are you sure you've committed these changes? -- Greg Lewis Email : [EMAIL PROTECTED] Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: a gcc3.1 bug ?
On Mon, Jul 29, 2002 at 01:43:21AM +0930, Greg Lewis wrote: The patchset matches what is in the repository. Are you sure you've committed these changes? I missed that changed some how, it's now commited. ;) bill To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
