On Dec 7, 2013, at 12:19 AM, Kai Ruottu wrote:
> 7.12.2013 2:38, Don Krause kirjoitti:
>> On Dec 5, 2013, at 1:11 PM, Ian Lance Taylor wrote:
>>
>>> On Thu, Dec 5, 2013 at 10:20 AM, Don Krause <dkrause@xxxxxxxxxxx> wrote:
>>>> I've been trying to build gcc-4.8.2 on Solaris 10 on Sparc.
>>>>
>>>> The bootstrap process gives me an "internal compiler error"
>>>>
>>>> ./configure --prefix=/home/tools/solaris2013
>>>>
>>>> make.
>>>>
>>>> That churns for a couple hours. (yes, old and crappy equipment. No options here..)
>>>>
>>>> Then:
>>>>
>>>> ../../../libgcc/libgcc2.c: In function '__muldi3':
>>>> ../../../libgcc/libgcc2.c:549:17: internal compiler error: Segmentation Fault
>>>> const DWunion uu = {.ll = u};
>>>> ^
>>>>
>>>> Suggestions?
>>>
>>> Since GCC 4.8.2 is known to build on SPARC Solaris 10, the first thing
>>> I would consider is which compiler you are using to build GCC.
>>> Can you perhaps stage the build by building an earlier version of GCC and using that to
>>> build GCC 4.8.2?
>>>
>>>
>>>
>> Still have the same problem, and this is after switching machines, with a fresh
>> install of Sparc Solaris10, a new user, no environment stuff set.
>>
>> Building gcc-4.8.2 using gcc-3.4.6 from sunfreeware gets along far enough to create
>> what I believe is a stage one xgcc, then that binary crashes with an internal compiler error as above.
>>
>> The build starts with Make 3.81 gcc 3.4.6 and bunutils 2.17.
>>
>> I guess my only option now is to try to build an intermediate, maybe 4.2.* gcc and try it again.
>
> Maybe only using the '--disable-build-with-cxx' could succeed... Using an intermediate GCC 4.x could however
> be the only working way. But whether gcc-4.2 is enough I'm not sure :(
>
> Using the g++-4.1.2 (like in CentOS5) has caused some build crashes when using the current '--enable-build-with-cxx'
> default in the GCC build. So I myself have used g++-4.6 or g++-4.7 as the minimum with g++ as the build compiler.
>
Well, I was successful at building 4.7.3 on my old Ultra 10, which is likely more than good enough for what I needed.
But, because the host isn't doing anything else, I'm now trying to build 4.8.2 again with 4.7.3. We'll see.
Thanks everyone!
--
Don Krause
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
