[Bug bootstrap/49555] libjava fails to configure if --enable-symvers=gnu or --enable-symvers=sun

2016-11-05 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49555

Andrew Pinski  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #11 from Andrew Pinski  ---
libgcj/libjava has been removed so closing as won't fix

[Bug bootstrap/49555] libjava fails to configure if --enable-symvers=gnu or --enable-symvers=sun

2012-07-02 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49555

Richard Guenther rguenth at gcc dot gnu.org changed:

   What|Removed |Added

   Target Milestone|4.7.1   |---


[Bug bootstrap/49555] libjava fails to configure if --enable-symvers=gnu or --enable-symvers=sun

2012-03-22 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49555

Richard Guenther rguenth at gcc dot gnu.org changed:

   What|Removed |Added

   Target Milestone|4.7.0   |4.7.1

--- Comment #10 from Richard Guenther rguenth at gcc dot gnu.org 2012-03-22 
08:27:20 UTC ---
GCC 4.7.0 is being released, adjusting target milestone.


[Bug bootstrap/49555] libjava fails to configure if --enable-symvers=gnu or --enable-symvers=sun

2011-07-01 Thread ro at CeBiTec dot Uni-Bielefeld.DE
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49555

--- Comment #9 from ro at CeBiTec dot Uni-Bielefeld.DE ro at CeBiTec dot 
Uni-Bielefeld.DE 2011-07-01 14:07:55 UTC ---
 --- Comment #7 from Bryan Hundven bryanhundven at gmail dot com 2011-06-29 
 19:30:03 UTC ---
[...]
 So, Yann found that sh4 did not need this option anymore, and he has since
 removed the --enable-symvers option from the build:

 http://crosstool-ng.org/hg/crosstool-ng/rev/b24ead1a5947

 So now we just let gcc figure it out.

Excellent, thanks for pursuing this.

 As for the inconsistent check in libjava and the previous change to remove
 enable-symvers from ct-ng in mind, this can probably be resolved as invalid
 unless you'd like to just add gnu|sun to the
 libjava_cv_anon_version_script=yes;; case. (attaching patch to give an
 example).

I'll certainly have a look: perhaps this will prompt me to unify the
symbol versioning configure support across all gcc target libraries :-)

 wrt all of the extra configuration options, it would be very appreciated if in
 another thread we could discuss some of them. I'm sure a lot of the options we
 have for building binutils and gcc are ported forward from the older crosstool
 scripts and aren't needed anymore. My theory on that has been: if it ain't
 broke, don't fix it
 ...until now.

We can certainly do this, either in private mail or on some mailing list
(unless I don't have to subscribe to yet another one :-).

Thanks.
Rainer


[Bug bootstrap/49555] libjava fails to configure if --enable-symvers=gnu or --enable-symvers=sun

2011-06-29 Thread ro at CeBiTec dot Uni-Bielefeld.DE
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49555

--- Comment #5 from ro at CeBiTec dot Uni-Bielefeld.DE ro at CeBiTec dot 
Uni-Bielefeld.DE 2011-06-29 08:58:43 UTC ---
 * why do you insist on specifying the symvers flavor manually?

 I didn't insist on specifying it manually. crosstool-ng did.
 While you might say that is a problem with crosstool-ng, but the older
 crosstool and other cross tool scripts use this as well.

 If every other component besides libjava specifically check for
 yes|no|gnu*|sun, why doesn't libjava?

Simply because the gnu* vs. sun distinction is immaterial for the
version maps used by libjava: anonymous version maps work the same for
both flavors, only the on vs. off distinction is important (if at all).

 Or...

 If I shouldn't use --enable-symvers=gnu, shouldn't all other components fail 
 to
 support it?

No, because their behavior differs depending no the flavor used.

You could probably argue that libjava should accept them for
consistencies sake, though.

My usual stance on this (especially when I see configure lines with
dozens of options): why in hell do people do this?  The defaults should
work fine for them, and if they don't, I'd like to know about this.  In
many cases, I'd expect the gcc maintainers to know how to determine
sensible defaults.  Of course there are exceptions, but unless proven
otherwise this doesn't seem to be an instance.

Rainer


[Bug bootstrap/49555] libjava fails to configure if --enable-symvers=gnu or --enable-symvers=sun

2011-06-29 Thread ro at CeBiTec dot Uni-Bielefeld.DE
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49555

--- Comment #6 from ro at CeBiTec dot Uni-Bielefeld.DE ro at CeBiTec dot 
Uni-Bielefeld.DE 2011-06-29 09:03:46 UTC ---
 Sure. Re-reading comment #3, maybe I sounded a bit brass.

No problem, I can stand some heat :-)

  * why do you insist on specifying the symvers flavor manually?

 I had a discussion with Yann E. Morin, and it sounds like this option was
 ported forward from the legacy options in Dan Kegel's crosstool.

 The questions I am asking should be:

 * Should this ever (for any platform) be set manually? Or should this always 
 be
 an 'automatic' setting?

Except for the (experimental) gnu vs. gnu-versioned-namespace
distinction in libstdc++-v3, I don't believe so.  We had a case where
--disable-symvers/--enable-symvers=no was necessary as a workaround, but
otherwise I'd prefer users to leave this alone.  Unfortunately, the
configure checks in different target libraries are currently
inconsistent.  I hope to get back to this at some point, though.

 * Isn't it inconsistent that every component checks for 'gnu*' and 'sun',
 except for libjava?

In a way, it is, except that it matters for those components, but not
for libjava.  But the check should be for gnu and sun alone,
gnu-versioned-namespace is probably wrong here.

 Yann is currently retesting the sh4 build without --enable-symvers=gnu set to
 see if it still needs it. If it does not, then he will remove it completely,
 otherwise it should be target specific in crosstool-ng and not for all 
 targets.

Excellent, thanks for checking this.

Rainer


[Bug bootstrap/49555] libjava fails to configure if --enable-symvers=gnu or --enable-symvers=sun

2011-06-29 Thread bryanhundven at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49555

--- Comment #7 from Bryan Hundven bryanhundven at gmail dot com 2011-06-29 
19:30:03 UTC ---
(In reply to comment #6)
  I had a discussion with Yann E. Morin, and it sounds like this option was
  ported forward from the legacy options in Dan Kegel's crosstool.
 
  The questions I am asking should be:
 
  * Should this ever (for any platform) be set manually? Or should this 
  always be
  an 'automatic' setting?
 
 Except for the (experimental) gnu vs. gnu-versioned-namespace
 distinction in libstdc++-v3, I don't believe so.  We had a case where
 --disable-symvers/--enable-symvers=no was necessary as a workaround, but
 otherwise I'd prefer users to leave this alone.  Unfortunately, the
 configure checks in different target libraries are currently
 inconsistent.  I hope to get back to this at some point, though.

Ok. Thanks for the explanation!

  * Isn't it inconsistent that every component checks for 'gnu*' and 'sun',
  except for libjava?
 
 In a way, it is, except that it matters for those components, but not
 for libjava.  But the check should be for gnu and sun alone,
 gnu-versioned-namespace is probably wrong here.
 
  Yann is currently retesting the sh4 build without --enable-symvers=gnu set 
  to
  see if it still needs it. If it does not, then he will remove it completely,
  otherwise it should be target specific in crosstool-ng and not for all 
  targets.
 
 Excellent, thanks for checking this.
 
 Rainer

So, Yann found that sh4 did not need this option anymore, and he has since
removed the --enable-symvers option from the build:

http://crosstool-ng.org/hg/crosstool-ng/rev/b24ead1a5947

So now we just let gcc figure it out.

As for the inconsistent check in libjava and the previous change to remove
enable-symvers from ct-ng in mind, this can probably be resolved as invalid
unless you'd like to just add gnu|sun to the
libjava_cv_anon_version_script=yes;; case. (attaching patch to give an
example).

wrt all of the extra configuration options, it would be very appreciated if in
another thread we could discuss some of them. I'm sure a lot of the options we
have for building binutils and gcc are ported forward from the older crosstool
scripts and aren't needed anymore. My theory on that has been: if it ain't
broke, don't fix it
...until now.


[Bug bootstrap/49555] libjava fails to configure if --enable-symvers=gnu or --enable-symvers=sun

2011-06-29 Thread bryanhundven at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49555

--- Comment #8 from Bryan Hundven bryanhundven at gmail dot com 2011-06-29 
19:30:42 UTC ---
Created attachment 24639
  -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=24639
libjava-version_script-consistency.diff


[Bug bootstrap/49555] libjava fails to configure if --enable-symvers=gnu or --enable-symvers=sun

2011-06-28 Thread ro at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49555

Rainer Orth ro at gcc dot gnu.org changed:

   What|Removed |Added

 CC|ro at CeBiTec dot   |ro at gcc dot gnu.org
   |Uni-Bielefeld.DE, ro at |
   |techfak dot |
   |uni-bielefeld.de|
   Target Milestone|--- |4.7.0

--- Comment #2 from Rainer Orth ro at gcc dot gnu.org 2011-06-28 10:20:50 UTC 
---
Please provide a bit mor information:

* what platform are you on?

* what are your configure options?

* why do you insist on specifying the symvers flavor manually?


[Bug bootstrap/49555] libjava fails to configure if --enable-symvers=gnu or --enable-symvers=sun

2011-06-28 Thread bryanhundven at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49555

Bryan Hundven bryanhundven at gmail dot com changed:

   What|Removed |Added

 Target||x86_64-unknown-linux-gnu
   Host||i686-unknown-linux-gnu
  Build||i686-unknown-linux-gnu

--- Comment #3 from Bryan Hundven bryanhundven at gmail dot com 2011-06-28 
18:18:33 UTC ---
(In reply to comment #2)
 Please provide a bit mor information:
 
 * what platform are you on?

It happens on every platform I configure, but if you want something specific:
--build=i686-unknown-linux-gnu --host=i686-unknown-linux-gnu
--target=x86_64-unknown-linux-gnu

I also have the same problems on:
--build=i686-unknown-linux-gnu --host=i686-unknown-linux-gnu
--target=mips64-unknown-linux-gnu

and:
--build=x86_64-unknown-linux-gnu --host=x86_64-unknown-linux-gnu
--target=powerpc-unknown-linux-gnuspe

This is a build from crosstool-ng. --enable-symvers=gnu is set staticly in:
http://crosstool-ng.org/hg/crosstool-ng/file/tip/scripts/build/cc/gcc.sh

 * what are your configure options?

--enable-languages=c,c++,fortran,objc,obj-c++ --disable-multilib
--with-tune=core2 --with-pkgversion=crosstool-NG hg_unknown@20110627.135200
--disable-sjlj-exceptions --enable-__cxa_atexit --enable-libmudflap
--enable-libgomp --enable-libssp
--with-gmp=/home/bryan/builds/x86_64-unknown-linux-gnu/.build/x86_64-unknown-linux-gnu/build/static
--with-mpfr=/home/bryan/builds/x86_64-unknown-linux-gnu/.build/x86_64-unknown-linux-gnu/build/static
--with-mpc=/home/bryan/builds/x86_64-unknown-linux-gnu/.build/x86_64-unknown-linux-gnu/build/static
--with-ppl=/home/bryan/builds/x86_64-unknown-linux-gnu/.build/x86_64-unknown-linux-gnu/build/static
--with-cloog=/home/bryan/builds/x86_64-unknown-linux-gnu/.build/x86_64-unknown-linux-gnu/build/static
--with-libelf=/home/bryan/builds/x86_64-unknown-linux-gnu/.build/x86_64-unknown-linux-gnu/build/static
--with-host-libstdcxx=-static-libgcc -Wl,-Bstatic,-lstdc++ -lm
-L/home/bryan/builds/x86_64-unknown-linux-gnu/.build/x86_64-unknown-linux-gnu/build/static/lib
-lpwl --enable-threads=posix --enable-target-optspace --disable-libstdcxx-pch
--with-long-double-128 --enable-gold

 * why do you insist on specifying the symvers flavor manually?

I didn't insist on specifying it manually. crosstool-ng did.
While you might say that is a problem with crosstool-ng, but the older
crosstool and other cross tool scripts use this as well.

If every other component besides libjava specifically check for
yes|no|gnu*|sun, why doesn't libjava?

Or...

If I shouldn't use --enable-symvers=gnu, shouldn't all other components fail to
support it?


[Bug bootstrap/49555] libjava fails to configure if --enable-symvers=gnu or --enable-symvers=sun

2011-06-28 Thread bryanhundven at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49555

Bryan Hundven bryanhundven at gmail dot com changed:

   What|Removed |Added

 CC||yann.morin.1998 at free dot
   ||fr

--- Comment #4 from Bryan Hundven bryanhundven at gmail dot com 2011-06-28 
21:01:43 UTC ---
(In reply to comment #3)
 (In reply to comment #2)
  Please provide a bit mor information:

Sure. Re-reading comment #3, maybe I sounded a bit brass.
Let me try again.

Yann requested to be CC'd.

  * what platform are you on?
 
 It happens on every platform I configure, but if you want something specific:
 --build=i686-unknown-linux-gnu --host=i686-unknown-linux-gnu
 --target=x86_64-unknown-linux-gnu
 
 I also have the same problems on:
 --build=i686-unknown-linux-gnu --host=i686-unknown-linux-gnu
 --target=mips64-unknown-linux-gnu
 
 and:
 --build=x86_64-unknown-linux-gnu --host=x86_64-unknown-linux-gnu
 --target=powerpc-unknown-linux-gnuspe

same response.

 This is a build from crosstool-ng. --enable-symvers=gnu is set staticly in:
 http://crosstool-ng.org/hg/crosstool-ng/file/tip/scripts/build/cc/gcc.sh
 
  * what are your configure options?
 
 --enable-languages=c,c++,fortran,objc,obj-c++ --disable-multilib
 --with-tune=core2 --with-pkgversion=crosstool-NG hg_unknown@20110627.135200
 --disable-sjlj-exceptions --enable-__cxa_atexit --enable-libmudflap
 --enable-libgomp --enable-libssp
 --with-gmp=/home/bryan/builds/x86_64-unknown-linux-gnu/.build/x86_64-unknown-linux-gnu/build/static
 --with-mpfr=/home/bryan/builds/x86_64-unknown-linux-gnu/.build/x86_64-unknown-linux-gnu/build/static
 --with-mpc=/home/bryan/builds/x86_64-unknown-linux-gnu/.build/x86_64-unknown-linux-gnu/build/static
 --with-ppl=/home/bryan/builds/x86_64-unknown-linux-gnu/.build/x86_64-unknown-linux-gnu/build/static
 --with-cloog=/home/bryan/builds/x86_64-unknown-linux-gnu/.build/x86_64-unknown-linux-gnu/build/static
 --with-libelf=/home/bryan/builds/x86_64-unknown-linux-gnu/.build/x86_64-unknown-linux-gnu/build/static
 --with-host-libstdcxx=-static-libgcc -Wl,-Bstatic,-lstdc++ -lm
 -L/home/bryan/builds/x86_64-unknown-linux-gnu/.build/x86_64-unknown-linux-gnu/build/static/lib
 -lpwl --enable-threads=posix --enable-target-optspace --disable-libstdcxx-pch
 --with-long-double-128 --enable-gold

Same response.

  * why do you insist on specifying the symvers flavor manually?

I had a discussion with Yann E. Morin, and it sounds like this option was
ported forward from the legacy options in Dan Kegel's crosstool.

The questions I am asking should be:

* Should this ever (for any platform) be set manually? Or should this always be
an 'automatic' setting?

* Isn't it inconsistent that every component checks for 'gnu*' and 'sun',
except for libjava?

Yann is currently retesting the sh4 build without --enable-symvers=gnu set to
see if it still needs it. If it does not, then he will remove it completely,
otherwise it should be target specific in crosstool-ng and not for all targets.

 I didn't insist on specifying it manually. crosstool-ng did.
 While you might say that is a problem with crosstool-ng, but the older
 crosstool and other cross tool scripts use this as well.
 
 If every other component besides libjava specifically check for
 yes|no|gnu*|sun, why doesn't libjava?
 
 Or...
 
 If I shouldn't use --enable-symvers=gnu, shouldn't all other components fail 
 to
 support it?


[Bug bootstrap/49555] libjava fails to configure if --enable-symvers=gnu or --enable-symvers=sun

2011-06-27 Thread bryanhundven at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49555

--- Comment #1 from Bryan Hundven bryanhundven at gmail dot com 2011-06-28 
00:09:28 UTC ---
Meant to say libjava/configure in the previous comment.