Re: Build error with GCC4.8 on Fedora19

2013-07-26 Thread Helio Frota
Hi,

Just feedback , build was ok with fedora 19. Thanks Omair Majid for the
flag tips.

$ sudo yum groupinstall Development Tools
$ sudo yum install gcc-c++
$ sudo yum install libXrender-devel
$ sudo yum install freetype-devel
$ sudo yum install libXt-devel
$ ./configure
$  make DEBUG_BINARIES=true SCTP_WERROR= all

Thanks,
Helio



2013/7/25 Helio Frota heliofr...@gmail.com

 Hi

 sudo yum install libXt-devel solve the dependency problem.

 but i get other...

 cc1: all warnings being treated as errors
 gmake[2]: ***
 [/home/hf/adopt_openjdk/openjdk8/build/linux-x86-normal-server-release/jdk/objs/libsctp/SctpChannelImpl.o]
 Error 1

 gmake[2]: *** Waiting for unfinished jobs
 cc1: all warnings being treated as errors
 gmake[2]: ***
 [/home/hf/adopt_openjdk/openjdk8/build/linux-x86-normal-server-release/jdk/objs/libsctp/SctpNet.o]
 Error 1
 gmake[1]: *** [libs-only] Error 2

 make: *** [jdk-only] Error 2

 is right disable warnings treated as errors ?

 Regards,
 Helio





 2013/7/25 Helio Frota heliofr...@gmail.com

 Hi Omair and Alan,


 I get this error:

 In file included from
 /home/hf/adopt_openjdk/openjdk8/build/linux-x86-normal-server-release/jdk/gensrc_x11wrappers/sizer.32.c:11:0:
 /home/hf/adopt_openjdk/openjdk8/jdk/src/solaris/native/sun/awt/awt_p.h:44:27:
 fatal error: X11/Intrinsic.h: No such file or directory
  #include X11/Intrinsic.h
^
 compilation terminated.
 gmake[2]: ***
 [/home/hf/adopt_openjdk/openjdk8/build/linux-x86-normal-server-release/jdk/gensrc_x11wrappers/sizer.32.exe]
 Error 1
 gmake[2]: *** Waiting for unfinished jobs
 gmake[1]: *** [gensrc-only] Error 2

 make: *** [jdk-only] Error 2

 Omair thanks for the tip make DEBUG_BINARIES=true all works.

 Regards,
 Helio



 2013/7/24 Helio Frota heliofr...@gmail.com

 Hi Omair,


 The only problem is that modern gcc versions don't produce stabs either.
 Try:
 $ make DEBUG_BINARIES=true all

 Thanks for the tip !

 I will try again tomorrow on job (fedora19) machine.

 Regards,
 Helio



 2013/7/24 Omair Majid oma...@redhat.com

 On 07/24/2013 04:11 PM, Helio Frota wrote:
  Hi,
 
  I got the same problem with GCC 4.8.1 and Manjaro distribution (
 distro
  son of archlinux )
 
  Generating precompiled header precompiled.hpp.gch
  cc1plus: error: the stabs debug format cannot be used with
  pre-compiled headers [-Werror=deprecated]
  cc1plus: all warnings being treated as errors
  gmake[6]: *** [precompiled.hpp.gch] Error 1
  gmake[5]: *** [the_vm] Error 2
  gmake[4]: *** [product] Error 2
  gmake[3]: *** [generic_build2] Error 2
  gmake[2]: *** [product] Error 2
  gmake[1]: ***
 
 [/home/hf/adopt_openjdk/openjdk8/build/linux-x86-normal-server-release/hotspot/_hotspot.timestamp]
  Error 2
  make: *** [hotspot-only] Error 2

 from hotspot/make/linux/makefiles/gcc.make:

 # DEBUG_BINARIES uses full -g debug information for all configs
 ifeq ($(DEBUG_BINARIES), true)
   CFLAGS += -g
 else
   # Use the stabs format for debugging information (this is the default
   # on gcc-2.91). It's good enough, has all the information about line
   # numbers and local variables, and libjvm.so is only about 16M.
   # Change this back to -g if you want the most expressive format.
   # (warning: that could easily inflate libjvm.so to 150M!)

 The only problem is that modern gcc versions don't produce stabs either.

 Try:

 $ make DEBUG_BINARIES=true all

 Cheers,
 Omair

 --
 PGP Key: 66484681 (http://pgp.mit.edu/)
 Fingerprint = F072 555B 0A17 3957 4E95  0056 F286 F14F 6648 4681




 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





-- 
Helio Frota
JUG Leader - CEJUG
http://www.cejug.org/ http://www.linuxgames.com.br/
http://www.linkedin.com/in/heliofrota


Re: Build error with GCC4.8 on Fedora19

2013-07-25 Thread Helio Frota
Hi Omair and Alan,


I get this error:

In file included from
/home/hf/adopt_openjdk/openjdk8/build/linux-x86-normal-server-release/jdk/gensrc_x11wrappers/sizer.32.c:11:0:
/home/hf/adopt_openjdk/openjdk8/jdk/src/solaris/native/sun/awt/awt_p.h:44:27:
fatal error: X11/Intrinsic.h: No such file or directory
 #include X11/Intrinsic.h
   ^
compilation terminated.
gmake[2]: ***
[/home/hf/adopt_openjdk/openjdk8/build/linux-x86-normal-server-release/jdk/gensrc_x11wrappers/sizer.32.exe]
Error 1
gmake[2]: *** Waiting for unfinished jobs
gmake[1]: *** [gensrc-only] Error 2
make: *** [jdk-only] Error 2

Omair thanks for the tip make DEBUG_BINARIES=true all works.

Regards,
Helio



2013/7/24 Helio Frota heliofr...@gmail.com

 Hi Omair,


 The only problem is that modern gcc versions don't produce stabs either.
 Try:
 $ make DEBUG_BINARIES=true all

 Thanks for the tip !

 I will try again tomorrow on job (fedora19) machine.

 Regards,
 Helio



 2013/7/24 Omair Majid oma...@redhat.com

 On 07/24/2013 04:11 PM, Helio Frota wrote:
  Hi,
 
  I got the same problem with GCC 4.8.1 and Manjaro distribution ( distro
  son of archlinux )
 
  Generating precompiled header precompiled.hpp.gch
  cc1plus: error: the stabs debug format cannot be used with
  pre-compiled headers [-Werror=deprecated]
  cc1plus: all warnings being treated as errors
  gmake[6]: *** [precompiled.hpp.gch] Error 1
  gmake[5]: *** [the_vm] Error 2
  gmake[4]: *** [product] Error 2
  gmake[3]: *** [generic_build2] Error 2
  gmake[2]: *** [product] Error 2
  gmake[1]: ***
 
 [/home/hf/adopt_openjdk/openjdk8/build/linux-x86-normal-server-release/hotspot/_hotspot.timestamp]
  Error 2
  make: *** [hotspot-only] Error 2

 from hotspot/make/linux/makefiles/gcc.make:

 # DEBUG_BINARIES uses full -g debug information for all configs
 ifeq ($(DEBUG_BINARIES), true)
   CFLAGS += -g
 else
   # Use the stabs format for debugging information (this is the default
   # on gcc-2.91). It's good enough, has all the information about line
   # numbers and local variables, and libjvm.so is only about 16M.
   # Change this back to -g if you want the most expressive format.
   # (warning: that could easily inflate libjvm.so to 150M!)

 The only problem is that modern gcc versions don't produce stabs either.

 Try:

 $ make DEBUG_BINARIES=true all

 Cheers,
 Omair

 --
 PGP Key: 66484681 (http://pgp.mit.edu/)
 Fingerprint = F072 555B 0A17 3957 4E95  0056 F286 F14F 6648 4681




 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





-- 
Helio Frota
JUG Leader - CEJUG
http://www.cejug.org/ http://www.linuxgames.com.br/
http://www.linkedin.com/in/heliofrota


Re: Build error with GCC4.8 on Fedora19

2013-07-25 Thread Helio Frota
Hi

sudo yum install libXt-devel solve the dependency problem.

but i get other...

cc1: all warnings being treated as errors
gmake[2]: ***
[/home/hf/adopt_openjdk/openjdk8/build/linux-x86-normal-server-release/jdk/objs/libsctp/SctpChannelImpl.o]
Error 1
gmake[2]: *** Waiting for unfinished jobs
cc1: all warnings being treated as errors
gmake[2]: ***
[/home/hf/adopt_openjdk/openjdk8/build/linux-x86-normal-server-release/jdk/objs/libsctp/SctpNet.o]
Error 1
gmake[1]: *** [libs-only] Error 2
make: *** [jdk-only] Error 2

is right disable warnings treated as errors ?

Regards,
Helio





2013/7/25 Helio Frota heliofr...@gmail.com

 Hi Omair and Alan,


 I get this error:

 In file included from
 /home/hf/adopt_openjdk/openjdk8/build/linux-x86-normal-server-release/jdk/gensrc_x11wrappers/sizer.32.c:11:0:
 /home/hf/adopt_openjdk/openjdk8/jdk/src/solaris/native/sun/awt/awt_p.h:44:27:
 fatal error: X11/Intrinsic.h: No such file or directory
  #include X11/Intrinsic.h
^
 compilation terminated.
 gmake[2]: ***
 [/home/hf/adopt_openjdk/openjdk8/build/linux-x86-normal-server-release/jdk/gensrc_x11wrappers/sizer.32.exe]
 Error 1
 gmake[2]: *** Waiting for unfinished jobs
 gmake[1]: *** [gensrc-only] Error 2

 make: *** [jdk-only] Error 2

 Omair thanks for the tip make DEBUG_BINARIES=true all works.

 Regards,
 Helio



 2013/7/24 Helio Frota heliofr...@gmail.com

 Hi Omair,


 The only problem is that modern gcc versions don't produce stabs either.
 Try:
 $ make DEBUG_BINARIES=true all

 Thanks for the tip !

 I will try again tomorrow on job (fedora19) machine.

 Regards,
 Helio



 2013/7/24 Omair Majid oma...@redhat.com

 On 07/24/2013 04:11 PM, Helio Frota wrote:
  Hi,
 
  I got the same problem with GCC 4.8.1 and Manjaro distribution ( distro
  son of archlinux )
 
  Generating precompiled header precompiled.hpp.gch
  cc1plus: error: the stabs debug format cannot be used with
  pre-compiled headers [-Werror=deprecated]
  cc1plus: all warnings being treated as errors
  gmake[6]: *** [precompiled.hpp.gch] Error 1
  gmake[5]: *** [the_vm] Error 2
  gmake[4]: *** [product] Error 2
  gmake[3]: *** [generic_build2] Error 2
  gmake[2]: *** [product] Error 2
  gmake[1]: ***
 
 [/home/hf/adopt_openjdk/openjdk8/build/linux-x86-normal-server-release/hotspot/_hotspot.timestamp]
  Error 2
  make: *** [hotspot-only] Error 2

 from hotspot/make/linux/makefiles/gcc.make:

 # DEBUG_BINARIES uses full -g debug information for all configs
 ifeq ($(DEBUG_BINARIES), true)
   CFLAGS += -g
 else
   # Use the stabs format for debugging information (this is the default
   # on gcc-2.91). It's good enough, has all the information about line
   # numbers and local variables, and libjvm.so is only about 16M.
   # Change this back to -g if you want the most expressive format.
   # (warning: that could easily inflate libjvm.so to 150M!)

 The only problem is that modern gcc versions don't produce stabs either.

 Try:

 $ make DEBUG_BINARIES=true all

 Cheers,
 Omair

 --
 PGP Key: 66484681 (http://pgp.mit.edu/)
 Fingerprint = F072 555B 0A17 3957 4E95  0056 F286 F14F 6648 4681




 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





-- 
Helio Frota
JUG Leader - CEJUG
http://www.cejug.org/ http://www.linuxgames.com.br/
http://www.linkedin.com/in/heliofrota


Re: Build error with GCC4.8 on Fedora19

2013-07-24 Thread Alan Bateman

On 10/07/2013 12:01, Omair Majid wrote:

On 07/09/2013 03:40 AM, Erik Joelsson wrote:

I would like to see a comment explaining why the option was needed. Is
this a bug in gcc or has the checking just become better?

-Werror is not a great default. It means all warnings are errors. The
set of warnings that a compiler emits changes all the time. Users and
distributions can enable additional warnings by default. Newer compiler
versions may omit additional warnings. So on any compiler other than the
typical compiler used, extra warnings are possible. With -Werror, this
will probably fail. Lots of people discourage it [1].

We have been setting SCTP_WERROR= to disable this -Werror on Fedora
builds [2].

I'm curious if there was a conclusion on this one. I assume SCTP_WERROR 
was originally intended for building libsctp (not libnio) so it would be 
strange to add to SCTP_WERROR to disable -Werror for issues coming from 
the file system code. One other thing that isn't clear is why there 
aren't other warnings as there are many other JNI functions in this 
source file that don't use the jclass this parameter.


-Alan


Re: Build error with GCC4.8 on Fedora19

2013-07-24 Thread Helio Frota
Hi,

I'm curious if there was a conclusion on this one. I assume SCTP_WERROR was
originally intended for building libsctp (not libnio) so it would be
strange to add to SCTP_WERROR to disable -Werror for issues coming from the
file system code. One other thing that isn't clear is why there aren't
other warnings as there are many other JNI functions in this source file
that don't use the jclass this parameter.

I have a plain raw new fedora 19 x86 env here.

Going to do the build right now... and post on this thread the feedback.

Regards,
Helio



2013/7/24 Alan Bateman alan.bate...@oracle.com

 On 10/07/2013 12:01, Omair Majid wrote:

 On 07/09/2013 03:40 AM, Erik Joelsson wrote:

 I would like to see a comment explaining why the option was needed. Is
 this a bug in gcc or has the checking just become better?

 -Werror is not a great default. It means all warnings are errors. The
 set of warnings that a compiler emits changes all the time. Users and
 distributions can enable additional warnings by default. Newer compiler
 versions may omit additional warnings. So on any compiler other than the
 typical compiler used, extra warnings are possible. With -Werror, this
 will probably fail. Lots of people discourage it [1].

 We have been setting SCTP_WERROR= to disable this -Werror on Fedora
 builds [2].

  I'm curious if there was a conclusion on this one. I assume SCTP_WERROR
 was originally intended for building libsctp (not libnio) so it would be
 strange to add to SCTP_WERROR to disable -Werror for issues coming from the
 file system code. One other thing that isn't clear is why there aren't
 other warnings as there are many other JNI functions in this source file
 that don't use the jclass this parameter.

 -Alan




-- 
Helio Frota
JUG Leader - CEJUG
http://www.cejug.org/ http://www.linuxgames.com.br/
http://www.linkedin.com/in/heliofrota


Re: Build error with GCC4.8 on Fedora19

2013-07-24 Thread Helio Frota
Ok first feedback

configure: error: Could not find a C++ compiler. You might be able to fix
this by running 'sudo yum groupinstall Development Tools'.

I did this but the error continue.

Going to investigate a workaround.

Regards,
Helio



2013/7/24 Helio Frota heliofr...@gmail.com

 Hi,

 I'm curious if there was a conclusion on this one. I assume SCTP_WERROR
 was originally intended for building libsctp (not libnio) so it would be
 strange to add to SCTP_WERROR to disable -Werror for issues coming from the
 file system code. One other thing that isn't clear is why there aren't
 other warnings as there are many other JNI functions in this source file
 that don't use the jclass this parameter.

 I have a plain raw new fedora 19 x86 env here.

 Going to do the build right now... and post on this thread the feedback.

 Regards,
 Helio



 2013/7/24 Alan Bateman alan.bate...@oracle.com

 On 10/07/2013 12:01, Omair Majid wrote:

 On 07/09/2013 03:40 AM, Erik Joelsson wrote:

 I would like to see a comment explaining why the option was needed. Is
 this a bug in gcc or has the checking just become better?

 -Werror is not a great default. It means all warnings are errors. The
 set of warnings that a compiler emits changes all the time. Users and
 distributions can enable additional warnings by default. Newer compiler
 versions may omit additional warnings. So on any compiler other than the
 typical compiler used, extra warnings are possible. With -Werror, this
 will probably fail. Lots of people discourage it [1].

 We have been setting SCTP_WERROR= to disable this -Werror on Fedora
 builds [2].

  I'm curious if there was a conclusion on this one. I assume SCTP_WERROR
 was originally intended for building libsctp (not libnio) so it would be
 strange to add to SCTP_WERROR to disable -Werror for issues coming from the
 file system code. One other thing that isn't clear is why there aren't
 other warnings as there are many other JNI functions in this source file
 that don't use the jclass this parameter.

 -Alan




 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





-- 
Helio Frota
JUG Leader - CEJUG
http://www.cejug.org/ http://www.linuxgames.com.br/
http://www.linkedin.com/in/heliofrota


Re: Build error with GCC4.8 on Fedora19

2013-07-24 Thread Helio Frota
Hi,

Please need to add the message on the autoconf config scripts:

You might be able to fix this by running 'sudo yum install gcc-c++'.

because   'sudo yum groupinstall Development Tools'  not installed the
gcc-c++ compiler.

Regards,
Helio





2013/7/24 Helio Frota heliofr...@gmail.com

 Ok first feedback

 configure: error: Could not find a C++ compiler. You might be able to fix
 this by running 'sudo yum groupinstall Development Tools'.

 I did this but the error continue.

 Going to investigate a workaround.

 Regards,
 Helio



 2013/7/24 Helio Frota heliofr...@gmail.com

 Hi,

 I'm curious if there was a conclusion on this one. I assume SCTP_WERROR
 was originally intended for building libsctp (not libnio) so it would be
 strange to add to SCTP_WERROR to disable -Werror for issues coming from the
 file system code. One other thing that isn't clear is why there aren't
 other warnings as there are many other JNI functions in this source file
 that don't use the jclass this parameter.

 I have a plain raw new fedora 19 x86 env here.

 Going to do the build right now... and post on this thread the feedback.

 Regards,
 Helio



 2013/7/24 Alan Bateman alan.bate...@oracle.com

 On 10/07/2013 12:01, Omair Majid wrote:

 On 07/09/2013 03:40 AM, Erik Joelsson wrote:

 I would like to see a comment explaining why the option was needed. Is
 this a bug in gcc or has the checking just become better?

 -Werror is not a great default. It means all warnings are errors. The
 set of warnings that a compiler emits changes all the time. Users and
 distributions can enable additional warnings by default. Newer compiler
 versions may omit additional warnings. So on any compiler other than the
 typical compiler used, extra warnings are possible. With -Werror, this
 will probably fail. Lots of people discourage it [1].

 We have been setting SCTP_WERROR= to disable this -Werror on Fedora
 builds [2].

  I'm curious if there was a conclusion on this one. I assume
 SCTP_WERROR was originally intended for building libsctp (not libnio) so it
 would be strange to add to SCTP_WERROR to disable -Werror for issues coming
 from the file system code. One other thing that isn't clear is why there
 aren't other warnings as there are many other JNI functions in this source
 file that don't use the jclass this parameter.

 -Alan




 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





-- 
Helio Frota
JUG Leader - CEJUG
http://www.cejug.org/ http://www.linuxgames.com.br/
http://www.linkedin.com/in/heliofrota


Re: Build error with GCC4.8 on Fedora19

2013-07-24 Thread Helio Frota
Hi,

Another problem:

configure: error: Could not find all X11 headers (shape.h Xrender.h
XTest.h). You might be able to fix this by running 'sudo yum install
libXtst-devel'.
configure exiting with result code 1

I did this, but the error persists.

Going to investigate...

Regards,
Helio



2013/7/24 Helio Frota heliofr...@gmail.com

 Hi,

 Please need to add the message on the autoconf config scripts:

 You might be able to fix this by running 'sudo yum install gcc-c++'.

 because   'sudo yum groupinstall Development Tools'  not installed the
 gcc-c++ compiler.

 Regards,
 Helio





 2013/7/24 Helio Frota heliofr...@gmail.com

 Ok first feedback

 configure: error: Could not find a C++ compiler. You might be able to fix
 this by running 'sudo yum groupinstall Development Tools'.

 I did this but the error continue.

 Going to investigate a workaround.

 Regards,
 Helio



 2013/7/24 Helio Frota heliofr...@gmail.com

 Hi,

 I'm curious if there was a conclusion on this one. I assume SCTP_WERROR
 was originally intended for building libsctp (not libnio) so it would be
 strange to add to SCTP_WERROR to disable -Werror for issues coming from the
 file system code. One other thing that isn't clear is why there aren't
 other warnings as there are many other JNI functions in this source file
 that don't use the jclass this parameter.

 I have a plain raw new fedora 19 x86 env here.

 Going to do the build right now... and post on this thread the feedback.

 Regards,
 Helio



 2013/7/24 Alan Bateman alan.bate...@oracle.com

 On 10/07/2013 12:01, Omair Majid wrote:

 On 07/09/2013 03:40 AM, Erik Joelsson wrote:

 I would like to see a comment explaining why the option was needed. Is
 this a bug in gcc or has the checking just become better?

 -Werror is not a great default. It means all warnings are errors. The
 set of warnings that a compiler emits changes all the time. Users and
 distributions can enable additional warnings by default. Newer compiler
 versions may omit additional warnings. So on any compiler other than
 the
 typical compiler used, extra warnings are possible. With -Werror, this
 will probably fail. Lots of people discourage it [1].

 We have been setting SCTP_WERROR= to disable this -Werror on Fedora
 builds [2].

  I'm curious if there was a conclusion on this one. I assume
 SCTP_WERROR was originally intended for building libsctp (not libnio) so it
 would be strange to add to SCTP_WERROR to disable -Werror for issues coming
 from the file system code. One other thing that isn't clear is why there
 aren't other warnings as there are many other JNI functions in this source
 file that don't use the jclass this parameter.

 -Alan




 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





-- 
Helio Frota
JUG Leader - CEJUG
http://www.cejug.org/ http://www.linuxgames.com.br/
http://www.linkedin.com/in/heliofrota


Re: Build error with GCC4.8 on Fedora19

2013-07-24 Thread Helio Frota
Hi,

Please add the message:

You might be able to fix this by running 'sudo yum install
libXrender-devel'.

sudo yum install libXrender-devel

Because shape.h Xrender.h XTest.h are not installed with sudo yum install
libXtst-devel

Regards,
Helio




2013/7/24 Helio Frota heliofr...@gmail.com

 Hi,

 Another problem:

 configure: error: Could not find all X11 headers (shape.h Xrender.h
 XTest.h). You might be able to fix this by running 'sudo yum install
 libXtst-devel'.
 configure exiting with result code 1

 I did this, but the error persists.

 Going to investigate...

 Regards,
 Helio



 2013/7/24 Helio Frota heliofr...@gmail.com

 Hi,

 Please need to add the message on the autoconf config scripts:

 You might be able to fix this by running 'sudo yum install gcc-c++'.

 because   'sudo yum groupinstall Development Tools'  not installed
 the gcc-c++ compiler.

 Regards,
 Helio





 2013/7/24 Helio Frota heliofr...@gmail.com

 Ok first feedback

 configure: error: Could not find a C++ compiler. You might be able to
 fix this by running 'sudo yum groupinstall Development Tools'.

 I did this but the error continue.

 Going to investigate a workaround.

 Regards,
 Helio



 2013/7/24 Helio Frota heliofr...@gmail.com

 Hi,

 I'm curious if there was a conclusion on this one. I assume SCTP_WERROR
 was originally intended for building libsctp (not libnio) so it would be
 strange to add to SCTP_WERROR to disable -Werror for issues coming from the
 file system code. One other thing that isn't clear is why there aren't
 other warnings as there are many other JNI functions in this source file
 that don't use the jclass this parameter.

 I have a plain raw new fedora 19 x86 env here.

 Going to do the build right now... and post on this thread the feedback.

 Regards,
 Helio



 2013/7/24 Alan Bateman alan.bate...@oracle.com

 On 10/07/2013 12:01, Omair Majid wrote:

 On 07/09/2013 03:40 AM, Erik Joelsson wrote:

 I would like to see a comment explaining why the option was needed.
 Is
 this a bug in gcc or has the checking just become better?

 -Werror is not a great default. It means all warnings are errors.
 The
 set of warnings that a compiler emits changes all the time. Users and
 distributions can enable additional warnings by default. Newer
 compiler
 versions may omit additional warnings. So on any compiler other than
 the
 typical compiler used, extra warnings are possible. With -Werror, this
 will probably fail. Lots of people discourage it [1].

 We have been setting SCTP_WERROR= to disable this -Werror on Fedora
 builds [2].

  I'm curious if there was a conclusion on this one. I assume
 SCTP_WERROR was originally intended for building libsctp (not libnio) so 
 it
 would be strange to add to SCTP_WERROR to disable -Werror for issues 
 coming
 from the file system code. One other thing that isn't clear is why there
 aren't other warnings as there are many other JNI functions in this source
 file that don't use the jclass this parameter.

 -Alan




 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





-- 
Helio Frota
JUG Leader - CEJUG
http://www.cejug.org/ http://www.linuxgames.com.br/
http://www.linkedin.com/in/heliofrota


Re: Build error with GCC4.8 on Fedora19

2013-07-24 Thread Omair Majid
On 07/24/2013 03:44 PM, Helio Frota wrote:
 Hi,
 
 Another problem:
 
 configure: error: Could not find all X11 headers (shape.h Xrender.h
 XTest.h). You might be able to fix this by running 'sudo yum install
 libXtst-devel'.
 configure exiting with result code 1
 
 I did this, but the error persists.
 
 Going to investigate...
 

The package manager suggestions are very unlikely to be exactly right
for all versions of all distributions. You can follow the error message
to get better results and install the files it is complaining about.

For example, using yum, you can ask to install the package that provides
this file (eg XTest.h) by name:

# yum install '*/XTest.h'

You should do the same for all other header file dependencies configure
complains about.

If you are on Fedora 19, you can also get all the dependencies faster by
getting all the dependencies that java-1.8.0-openjdk (that's what the
OpenJDK 8 package is called in Fedora) declares:

# yum-builddep java-1.8.0-openjdk

This may not be as up-to-date as what configure expects, though. It
should be faster.

Cheers,
Omair

-- 
PGP Key: 66484681 (http://pgp.mit.edu/)
Fingerprint = F072 555B 0A17 3957 4E95  0056 F286 F14F 6648 4681


Re: Build error with GCC4.8 on Fedora19

2013-07-24 Thread Helio Frota
Hi,

Configure ok



A new configuration has been successfully created in
/home/hf/adopt_openjdk/openjdk8/build/linux-x86-normal-server-release
using default settings.

Configuration summary:
* Debug level:release
* JDK variant:normal
* JVM variants:   server
* OpenJDK target: OS: linux, CPU architecture: x86, address length: 32

Tools summary:
* Boot JDK:   java version 1.7.0_25 Java(TM) SE Runtime Environment
(build 1.7.0_25-b15) Java HotSpot(TM) Server VM (build 23.25-b01, mixed
mode)  (at /home/hf/java/jdk)
* C Compiler: gcc (GCC) 4.8.1 20130603 (Red Hat-1) version 4.8.1-1) (at
/usr/bin/gcc)
* C++ Compiler:   g++ (GCC) 4.8.1 20130603 (Red Hat-1) version 4.8.1-1) (at
/usr/bin/g++)

Build performance summary:
* Cores to use:   3
* Memory limit:   3449 MB
* ccache status:  not installed (consider installing)

Build performance tip: ccache gives a tremendous speedup for C++
recompilations.
You do not have ccache installed. Try installing it.
You might be able to fix this by running 'sudo yum install ccache'.

Going to build with make all

Regards,
Helio




2013/7/24 Helio Frota heliofr...@gmail.com

 Hi Omair,

 Thanks for the tips !

 About freetype:

 Just change to  sudo yum install freetype-devel
 This solve the problem..

 Going to validate the alsa now...

 Regards,
 Helio


 2013/7/24 Omair Majid oma...@redhat.com

 On 07/24/2013 03:44 PM, Helio Frota wrote:
  Hi,
 
  Another problem:
 
  configure: error: Could not find all X11 headers (shape.h Xrender.h
  XTest.h). You might be able to fix this by running 'sudo yum install
  libXtst-devel'.
  configure exiting with result code 1
 
  I did this, but the error persists.
 
  Going to investigate...
 

 The package manager suggestions are very unlikely to be exactly right
 for all versions of all distributions. You can follow the error message
 to get better results and install the files it is complaining about.

 For example, using yum, you can ask to install the package that provides
 this file (eg XTest.h) by name:

 # yum install '*/XTest.h'

 You should do the same for all other header file dependencies configure
 complains about.

 If you are on Fedora 19, you can also get all the dependencies faster by
 getting all the dependencies that java-1.8.0-openjdk (that's what the
 OpenJDK 8 package is called in Fedora) declares:

 # yum-builddep java-1.8.0-openjdk

 This may not be as up-to-date as what configure expects, though. It
 should be faster.

 Cheers,
 Omair

 --
 PGP Key: 66484681 (http://pgp.mit.edu/)
 Fingerprint = F072 555B 0A17 3957 4E95  0056 F286 F14F 6648 4681




 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





-- 
Helio Frota
JUG Leader - CEJUG
http://www.cejug.org/ http://www.linuxgames.com.br/
http://www.linkedin.com/in/heliofrota


Re: Build error with GCC4.8 on Fedora19

2013-07-24 Thread Helio Frota
Sorry, its me again.

I get the configure error:
configure: error: Could not find freetype2! You might be able to fix this
by running 'sudo yum install freetype2-devel'.
configure exiting with result code 1

But after run the command:
sudo yum install freetype2-devel

Fedora 19 appears not to have the package
Loaded plugins: langpacks, refresh-packagekit
No package freetype2-devel available.
Error: Nothing to do

Going to investigate this...

Regards,
Helio






2013/7/24 Helio Frota heliofr...@gmail.com

 Hi,

 Please add the message:

 You might be able to fix this by running 'sudo yum install
 libXrender-devel'.

 sudo yum install libXrender-devel

 Because shape.h Xrender.h XTest.h are not installed with sudo yum install
 libXtst-devel

 Regards,
 Helio




 2013/7/24 Helio Frota heliofr...@gmail.com

 Hi,

 Another problem:

 configure: error: Could not find all X11 headers (shape.h Xrender.h
 XTest.h). You might be able to fix this by running 'sudo yum install
 libXtst-devel'.
 configure exiting with result code 1

 I did this, but the error persists.

 Going to investigate...

 Regards,
 Helio



 2013/7/24 Helio Frota heliofr...@gmail.com

 Hi,

 Please need to add the message on the autoconf config scripts:

 You might be able to fix this by running 'sudo yum install gcc-c++'.

 because   'sudo yum groupinstall Development Tools'  not installed
 the gcc-c++ compiler.

 Regards,
 Helio





 2013/7/24 Helio Frota heliofr...@gmail.com

 Ok first feedback

 configure: error: Could not find a C++ compiler. You might be able to
 fix this by running 'sudo yum groupinstall Development Tools'.

 I did this but the error continue.

 Going to investigate a workaround.

 Regards,
 Helio



 2013/7/24 Helio Frota heliofr...@gmail.com

 Hi,

 I'm curious if there was a conclusion on this one. I assume
 SCTP_WERROR was originally intended for building libsctp (not libnio) so 
 it
 would be strange to add to SCTP_WERROR to disable -Werror for issues 
 coming
 from the file system code. One other thing that isn't clear is why there
 aren't other warnings as there are many other JNI functions in this source
 file that don't use the jclass this parameter.

 I have a plain raw new fedora 19 x86 env here.

 Going to do the build right now... and post on this thread the
 feedback.

 Regards,
 Helio



 2013/7/24 Alan Bateman alan.bate...@oracle.com

 On 10/07/2013 12:01, Omair Majid wrote:

 On 07/09/2013 03:40 AM, Erik Joelsson wrote:

 I would like to see a comment explaining why the option was needed.
 Is
 this a bug in gcc or has the checking just become better?

 -Werror is not a great default. It means all warnings are errors.
 The
 set of warnings that a compiler emits changes all the time. Users and
 distributions can enable additional warnings by default. Newer
 compiler
 versions may omit additional warnings. So on any compiler other than
 the
 typical compiler used, extra warnings are possible. With -Werror,
 this
 will probably fail. Lots of people discourage it [1].

 We have been setting SCTP_WERROR= to disable this -Werror on Fedora
 builds [2].

  I'm curious if there was a conclusion on this one. I assume
 SCTP_WERROR was originally intended for building libsctp (not libnio) so 
 it
 would be strange to add to SCTP_WERROR to disable -Werror for issues 
 coming
 from the file system code. One other thing that isn't clear is why there
 aren't other warnings as there are many other JNI functions in this 
 source
 file that don't use the jclass this parameter.

 -Alan




 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





-- 
Helio Frota
JUG Leader - CEJUG
http://www.cejug.org/ http://www.linuxgames.com.br/
http://www.linkedin.com/in/heliofrota


Re: Build error with GCC4.8 on Fedora19

2013-07-24 Thread Helio Frota
Hi,

I got the same problem with GCC 4.8.1 and Manjaro distribution ( distro son
of archlinux )

Generating precompiled header precompiled.hpp.gch
cc1plus: error: the stabs debug format cannot be used with pre-compiled
headers [-Werror=deprecated]
cc1plus: all warnings being treated as errors
gmake[6]: *** [precompiled.hpp.gch] Error 1
gmake[5]: *** [the_vm] Error 2
gmake[4]: *** [product] Error 2
gmake[3]: *** [generic_build2] Error 2
gmake[2]: *** [product] Error 2
gmake[1]: ***
[/home/hf/adopt_openjdk/openjdk8/build/linux-x86-normal-server-release/hotspot/_hotspot.timestamp]
Error 2
make: *** [hotspot-only] Error 2

And i did this one to solve :
my web site:
http://www.heliofrota.com/blog/2013/06/25/building-openjdk8-plus-gcc-4-dot-8-1-plus-manjaro-gnu-linux-x86/

Regards,
Helio



2013/7/24 Helio Frota heliofr...@gmail.com

 Hi,

 Configure ok


 
 A new configuration has been successfully created in
 /home/hf/adopt_openjdk/openjdk8/build/linux-x86-normal-server-release
 using default settings.

 Configuration summary:
 * Debug level:release
 * JDK variant:normal
 * JVM variants:   server
 * OpenJDK target: OS: linux, CPU architecture: x86, address length: 32

 Tools summary:
 * Boot JDK:   java version 1.7.0_25 Java(TM) SE Runtime Environment
 (build 1.7.0_25-b15) Java HotSpot(TM) Server VM (build 23.25-b01, mixed
 mode)  (at /home/hf/java/jdk)
 * C Compiler: gcc (GCC) 4.8.1 20130603 (Red Hat-1) version 4.8.1-1)
 (at /usr/bin/gcc)
 * C++ Compiler:   g++ (GCC) 4.8.1 20130603 (Red Hat-1) version 4.8.1-1)
 (at /usr/bin/g++)

 Build performance summary:
 * Cores to use:   3
 * Memory limit:   3449 MB
 * ccache status:  not installed (consider installing)

 Build performance tip: ccache gives a tremendous speedup for C++
 recompilations.
 You do not have ccache installed. Try installing it.
 You might be able to fix this by running 'sudo yum install ccache'.

 Going to build with make all

 Regards,
 Helio




 2013/7/24 Helio Frota heliofr...@gmail.com

 Hi Omair,

 Thanks for the tips !

 About freetype:

 Just change to  sudo yum install freetype-devel
 This solve the problem..

 Going to validate the alsa now...

 Regards,
 Helio


 2013/7/24 Omair Majid oma...@redhat.com

 On 07/24/2013 03:44 PM, Helio Frota wrote:
  Hi,
 
  Another problem:
 
  configure: error: Could not find all X11 headers (shape.h Xrender.h
  XTest.h). You might be able to fix this by running 'sudo yum install
  libXtst-devel'.
  configure exiting with result code 1
 
  I did this, but the error persists.
 
  Going to investigate...
 

 The package manager suggestions are very unlikely to be exactly right
 for all versions of all distributions. You can follow the error message
 to get better results and install the files it is complaining about.

 For example, using yum, you can ask to install the package that provides
 this file (eg XTest.h) by name:

 # yum install '*/XTest.h'

 You should do the same for all other header file dependencies configure
 complains about.

 If you are on Fedora 19, you can also get all the dependencies faster by
 getting all the dependencies that java-1.8.0-openjdk (that's what the
 OpenJDK 8 package is called in Fedora) declares:

 # yum-builddep java-1.8.0-openjdk

 This may not be as up-to-date as what configure expects, though. It
 should be faster.

 Cheers,
 Omair

 --
 PGP Key: 66484681 (http://pgp.mit.edu/)
 Fingerprint = F072 555B 0A17 3957 4E95  0056 F286 F14F 6648 4681




 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





 --
 Helio Frota
 JUG Leader - CEJUG
 http://www.cejug.org/ http://www.linuxgames.com.br/
 http://www.linkedin.com/in/heliofrota





-- 
Helio Frota
JUG Leader - CEJUG
http://www.cejug.org/ http://www.linuxgames.com.br/
http://www.linkedin.com/in/heliofrota


Re: Build error with GCC4.8 on Fedora19

2013-07-24 Thread Omair Majid
On 07/24/2013 04:11 PM, Helio Frota wrote:
 Hi,
 
 I got the same problem with GCC 4.8.1 and Manjaro distribution ( distro
 son of archlinux )
 
 Generating precompiled header precompiled.hpp.gch
 cc1plus: error: the stabs debug format cannot be used with
 pre-compiled headers [-Werror=deprecated]
 cc1plus: all warnings being treated as errors
 gmake[6]: *** [precompiled.hpp.gch] Error 1
 gmake[5]: *** [the_vm] Error 2
 gmake[4]: *** [product] Error 2
 gmake[3]: *** [generic_build2] Error 2
 gmake[2]: *** [product] Error 2
 gmake[1]: ***
 [/home/hf/adopt_openjdk/openjdk8/build/linux-x86-normal-server-release/hotspot/_hotspot.timestamp]
 Error 2
 make: *** [hotspot-only] Error 2

from hotspot/make/linux/makefiles/gcc.make:

# DEBUG_BINARIES uses full -g debug information for all configs
ifeq ($(DEBUG_BINARIES), true)
  CFLAGS += -g
else
  # Use the stabs format for debugging information (this is the default
  # on gcc-2.91). It's good enough, has all the information about line
  # numbers and local variables, and libjvm.so is only about 16M.
  # Change this back to -g if you want the most expressive format.
  # (warning: that could easily inflate libjvm.so to 150M!)

The only problem is that modern gcc versions don't produce stabs either.

Try:

$ make DEBUG_BINARIES=true all

Cheers,
Omair

-- 
PGP Key: 66484681 (http://pgp.mit.edu/)
Fingerprint = F072 555B 0A17 3957 4E95  0056 F286 F14F 6648 4681


Re: Build error with GCC4.8 on Fedora19

2013-07-24 Thread Helio Frota
Hi Omair,

Thanks for the tips !

About freetype:

Just change to  sudo yum install freetype-devel
This solve the problem..

Going to validate the alsa now...

Regards,
Helio


2013/7/24 Omair Majid oma...@redhat.com

 On 07/24/2013 03:44 PM, Helio Frota wrote:
  Hi,
 
  Another problem:
 
  configure: error: Could not find all X11 headers (shape.h Xrender.h
  XTest.h). You might be able to fix this by running 'sudo yum install
  libXtst-devel'.
  configure exiting with result code 1
 
  I did this, but the error persists.
 
  Going to investigate...
 

 The package manager suggestions are very unlikely to be exactly right
 for all versions of all distributions. You can follow the error message
 to get better results and install the files it is complaining about.

 For example, using yum, you can ask to install the package that provides
 this file (eg XTest.h) by name:

 # yum install '*/XTest.h'

 You should do the same for all other header file dependencies configure
 complains about.

 If you are on Fedora 19, you can also get all the dependencies faster by
 getting all the dependencies that java-1.8.0-openjdk (that's what the
 OpenJDK 8 package is called in Fedora) declares:

 # yum-builddep java-1.8.0-openjdk

 This may not be as up-to-date as what configure expects, though. It
 should be faster.

 Cheers,
 Omair

 --
 PGP Key: 66484681 (http://pgp.mit.edu/)
 Fingerprint = F072 555B 0A17 3957 4E95  0056 F286 F14F 6648 4681




-- 
Helio Frota
JUG Leader - CEJUG
http://www.cejug.org/ http://www.linuxgames.com.br/
http://www.linkedin.com/in/heliofrota


Re: Build error with GCC4.8 on Fedora19

2013-07-24 Thread Helio Frota
Hi Omair,

The only problem is that modern gcc versions don't produce stabs either.
Try:
$ make DEBUG_BINARIES=true all

Thanks for the tip !

I will try again tomorrow on job (fedora19) machine.

Regards,
Helio



2013/7/24 Omair Majid oma...@redhat.com

 On 07/24/2013 04:11 PM, Helio Frota wrote:
  Hi,
 
  I got the same problem with GCC 4.8.1 and Manjaro distribution ( distro
  son of archlinux )
 
  Generating precompiled header precompiled.hpp.gch
  cc1plus: error: the stabs debug format cannot be used with
  pre-compiled headers [-Werror=deprecated]
  cc1plus: all warnings being treated as errors
  gmake[6]: *** [precompiled.hpp.gch] Error 1
  gmake[5]: *** [the_vm] Error 2
  gmake[4]: *** [product] Error 2
  gmake[3]: *** [generic_build2] Error 2
  gmake[2]: *** [product] Error 2
  gmake[1]: ***
 
 [/home/hf/adopt_openjdk/openjdk8/build/linux-x86-normal-server-release/hotspot/_hotspot.timestamp]
  Error 2
  make: *** [hotspot-only] Error 2

 from hotspot/make/linux/makefiles/gcc.make:

 # DEBUG_BINARIES uses full -g debug information for all configs
 ifeq ($(DEBUG_BINARIES), true)
   CFLAGS += -g
 else
   # Use the stabs format for debugging information (this is the default
   # on gcc-2.91). It's good enough, has all the information about line
   # numbers and local variables, and libjvm.so is only about 16M.
   # Change this back to -g if you want the most expressive format.
   # (warning: that could easily inflate libjvm.so to 150M!)

 The only problem is that modern gcc versions don't produce stabs either.

 Try:

 $ make DEBUG_BINARIES=true all

 Cheers,
 Omair

 --
 PGP Key: 66484681 (http://pgp.mit.edu/)
 Fingerprint = F072 555B 0A17 3957 4E95  0056 F286 F14F 6648 4681




-- 
Helio Frota
JUG Leader - CEJUG
http://www.cejug.org/ http://www.linuxgames.com.br/
http://www.linkedin.com/in/heliofrota


Re: Build error with GCC4.8 on Fedora19

2013-07-10 Thread Omair Majid
On 07/09/2013 03:40 AM, Erik Joelsson wrote:
 I would like to see a comment explaining why the option was needed. Is
 this a bug in gcc or has the checking just become better?

-Werror is not a great default. It means all warnings are errors. The
set of warnings that a compiler emits changes all the time. Users and
distributions can enable additional warnings by default. Newer compiler
versions may omit additional warnings. So on any compiler other than the
typical compiler used, extra warnings are possible. With -Werror, this
will probably fail. Lots of people discourage it [1].

We have been setting SCTP_WERROR= to disable this -Werror on Fedora
builds [2].

Cheers,
Omair

[1] https://blog.flameeyes.eu/2009/02/future-proof-your-code-dont-use-werror
[2]
http://pkgs.fedoraproject.org/cgit/java-1.8.0-openjdk.git/tree/java-1.8.0-openjdk.spec#n425
-- 
PGP Key: 66484681 (http://pgp.mit.edu/)
Fingerprint = F072 555B 0A17 3957 4E95  0056 F286 F14F 6648 4681


Re: Build error with GCC4.8 on Fedora19

2013-07-09 Thread Erik Joelsson
I would like to see a comment explaining why the option was needed. Is
this a bug in gcc or has the checking just become better?

/Erik

On 2013-07-09 07:46, Dan Xu wrote:
 Adding build-dev mailing list.


 On 07/08/2013 09:54 PM, Yasu wrote:
 Sorry, I forgot to attach a patch:

 --

 diff -r 52454985425d makefiles/CompileNativeLibraries.gmk
 --- a/makefiles/CompileNativeLibraries.gmk Mon Jul 08 19:24:22 2013 -0700
 +++ b/makefiles/CompileNativeLibraries.gmk Tue Jul 09 13:41:12 2013 +0900
 @@ -1987,7 +1987,7 @@

 ifneq ($(OPENJDK_TARGET_OS),macosx)

 - SCTP_WERROR := -Werror
 + SCTP_WERROR := -Werror -Wno-error=unused-parameter
 ifeq ($(OPENJDK_TARGET_CPU_ARCH), ppc)
 SCTP_WERROR :=
 endif


Re: Build error with GCC4.8 on Fedora19

2013-07-09 Thread Helio Frota
Hi great all,

This is my first mail here, i'm Jug Leader of CEJUG and OpenJDK Adoptor.

I did the build of OpenJDK with GCC 4.8.1

Please look:
http://www.heliofrota.com/blog/2013/06/25/building-openjdk8-plus-gcc-4-dot-8-1-plus-manjaro-gnu-linux-x86/

And here all discussion on Adopt OpenJDK mailing list:
https://groups.google.com/d/msg/adopt-openjdk/-6CQLEclN-Q/NkrCc96WeM8J

I will try with fedora 19 soon.

Thanks.


2013/7/9 Erik Joelsson erik.joels...@oracle.com

 I would like to see a comment explaining why the option was needed. Is
 this a bug in gcc or has the checking just become better?

 /Erik

 On 2013-07-09 07:46, Dan Xu wrote:
  Adding build-dev mailing list.
 
 
  On 07/08/2013 09:54 PM, Yasu wrote:
  Sorry, I forgot to attach a patch:
 
  --
 
  diff -r 52454985425d makefiles/CompileNativeLibraries.gmk
  --- a/makefiles/CompileNativeLibraries.gmk Mon Jul 08 19:24:22 2013
 -0700
  +++ b/makefiles/CompileNativeLibraries.gmk Tue Jul 09 13:41:12 2013
 +0900
  @@ -1987,7 +1987,7 @@
 
  ifneq ($(OPENJDK_TARGET_OS),macosx)
 
  - SCTP_WERROR := -Werror
  + SCTP_WERROR := -Werror -Wno-error=unused-parameter
  ifeq ($(OPENJDK_TARGET_CPU_ARCH), ppc)
  SCTP_WERROR :=
  endif




-- 
Helio Frota
JUG Leader - CEJUG
http://www.cejug.org/ http://www.linuxgames.com.br/
http://www.linkedin.com/in/heliofrota


RE: Build error with GCC4.8 on Fedora19

2013-07-09 Thread Yasu
Hi Erik,

I posted email as following:
http://mail.openjdk.java.net/pipermail/core-libs-dev/2013-July/018790.html
---
Hi,

I tried to build JDK8 with GCC4.8 on Fedora19.
However, build process has been failed as following:

--
/usr/src/OpenJDK/tl/jdk/src/solaris/native/sun/nio/fs/UnixNativeDispatcher.c: 
In function ‘Java_sun_nio_fs_UnixNativeDispatcher_getgrnam0’:
/usr/src/OpenJDK/tl/jdk/src/solaris/native/sun/nio/fs/UnixNativeDispatcher.c:1071:68:
 warning: unused parameter ‘this’ [-Wunused-parameter]
 Java_sun_nio_fs_UnixNativeDispatcher_getgrnam0(JNIEnv* env, jclass this,
^
gmake[1]: *** [libs-only] Error 2
make: *** [jdk-only] Error 2
--

I guess this issue is caused by -Werror.
So I've made a patch and it seems to work fine.


Could you push this patch?


Thanks,

Yasumasa Suenaga
---

I think that this is GCC spec.
This option is described in manpage of gcc as following:

---
   -Wunused
   All the above -Wunused options combined.

   In order to get a warning about an unused function parameter, you
   must either specify -Wextra -Wunused (note that -Wall implies
   -Wunused), or separately specify -Wunused-parameter.
---


Thanks,

Yasumasa



RE: Build error with GCC4.8 on Fedora19

2013-07-09 Thread Yasu
Hi Helio,

I've read your article.
Can you try to build class library?
I encountered this issue on building SCTP module.


Thanks,

Yasumasa


Re: Build error with GCC4.8 on Fedora19

2013-07-09 Thread Andrew Haley
On 07/09/2013 12:11 PM, Yasu wrote:
 Hi Erik,
 
 I posted email as following:
 http://mail.openjdk.java.net/pipermail/core-libs-dev/2013-July/018790.html
 ---
 Hi,
 
 I tried to build JDK8 with GCC4.8 on Fedora19.
 However, build process has been failed as following:
 
 --
 /usr/src/OpenJDK/tl/jdk/src/solaris/native/sun/nio/fs/UnixNativeDispatcher.c: 
 In function ‘Java_sun_nio_fs_UnixNativeDispatcher_getgrnam0’:
 /usr/src/OpenJDK/tl/jdk/src/solaris/native/sun/nio/fs/UnixNativeDispatcher.c:1071:68:
  warning: unused parameter ‘this’ [-Wunused-parameter]
  Java_sun_nio_fs_UnixNativeDispatcher_getgrnam0(JNIEnv* env, jclass this,
 ^
 gmake[1]: *** [libs-only] Error 2
 make: *** [jdk-only] Error 2
 --
 
 I guess this issue is caused by -Werror.

Better to fix the code:

--- a/src/solaris/native/sun/nio/fs/UnixNativeDispatcher.c  Tue Jul 02 
15:08:32 2013 +0100
+++ b/src/solaris/native/sun/nio/fs/UnixNativeDispatcher.c  Tue Jul 09 
12:39:35 2013 +0100
@@ -1039,7 +1039,7 @@
 }

 JNIEXPORT jint JNICALL
-Java_sun_nio_fs_UnixNativeDispatcher_getgrnam0(JNIEnv* env, jclass this,
+Java_sun_nio_fs_UnixNativeDispatcher_getgrnam0(JNIEnv* env, jclass,
 jlong nameAddress)
 {
 jint gid = -1;

Andrew.



Re: Build error with GCC4.8 on Fedora19

2013-07-09 Thread Helio Frota
Hi Yasu,

Can you try to build class library?

Yes i will try.

Thanks,





2013/7/9 Yasu y...@ysfactory.dip.jp

 Hi Helio,

 I've read your article.
 Can you try to build class library?
 I encountered this issue on building SCTP module.


 Thanks,

 Yasumasa




-- 
Helio Frota
JUG Leader - CEJUG
http://www.cejug.org/ http://www.linuxgames.com.br/
http://www.linkedin.com/in/heliofrota


Re: Build error with GCC4.8 on Fedora19

2013-07-08 Thread Dan Xu
Adding build-dev mailing list.


On 07/08/2013 09:54 PM, Yasu wrote:
 Sorry, I forgot to attach a patch:

 --

 diff -r 52454985425d makefiles/CompileNativeLibraries.gmk
 --- a/makefiles/CompileNativeLibraries.gmk Mon Jul 08 19:24:22 2013 -0700
 +++ b/makefiles/CompileNativeLibraries.gmk Tue Jul 09 13:41:12 2013 +0900
 @@ -1987,7 +1987,7 @@

 ifneq ($(OPENJDK_TARGET_OS),macosx)

 - SCTP_WERROR := -Werror
 + SCTP_WERROR := -Werror -Wno-error=unused-parameter
 ifeq ($(OPENJDK_TARGET_CPU_ARCH), ppc)
 SCTP_WERROR :=
 endif