This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]