This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/48135] build fails on Solaris2.8 due to Glob.pm not found within /usr/perl5
- From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 17 Mar 2011 16:17:50 +0000
- Subject: [Bug bootstrap/48135] build fails on Solaris2.8 due to Glob.pm not found within /usr/perl5
- Auto-submitted: auto-generated
- References: <bug-48135-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48135
--- Comment #15 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-03-17 16:17:47 UTC ---
>> Btw., what's your reason to still be running Solaris 8? I'm the Solaris
>> GCC maintainer and seriously consider to deprecate it for GCC 4.7.
> Here we still have many Solaris8's working, with support from Sun/Oracle up to
> March 2012
> (http://www.oracle.com/us/support/library/lifetime-support-hardware-os-337182.pdf).
I know, but regular support has ended in March 2009 alreay, this one is
only by special arrangement. E.g., Solaris 8 patches are only available
anymore with a special contract.
> You will not be blamed if GCC support is discontinued (ie
> removed) after that. Deprecation is ok for GCC 4.7.
I'll probably do so soon so people get a heads-up.
>> > I would have to also find a working binary perl, no big deal but if we can
>> > avoid that using a few sed commands, that's perfect.
>> Certainly not: either I can make make_sunver.pl work with the core perl
>> glob, or the --disable-symver option will be made to work properly.
> It would be bad use of your time if you do this only for me. On the other hand,
Not really: this is a stupid bug in a documented feature and supposed to
work. A fix shouldn't be hard, but probably after 4.6.0 is released.
> i successfully built 4.6.0-RC on Solaris 10, but only after having performed
> sed -e 's|complex\.h|nonexistent&|g' inside the file mpc/configure installed
> in the source tree (from mpc-0.9.tar.gz).
That's part your fault and part ours: while install.texi states `MPC
Library version 0.8.1 (or later)', later versions are rarely tested and
often break, so it's best to stay with those exact versions. We need to
improve the install docs in this regard.
> Perhaps only a short sentence in "Host/target specific installation notes"
> is enough.
I'm reluctant to document every corner case in install.texi: nobody will
read this and important stuff gets missed. This PR will probably have
to do.
Rainer