Sane CFLAGS.

Nathan Whitehorn nwhitehorn at freebsd.org
Mon Dec 8 11:50:21 PST 2008


Justin Hibbits wrote:
> On Mon, Dec 08, 2008 at 11:35:33AM -0600, Nathan Whitehorn wrote:
>   
>> Horst Günther Burkhardt III wrote:
>>     
>>> On Mon, 2008-12-08 at 10:13 -0500, Justin Hibbits wrote:
>>>   
>>>       
>>>> Your problem is Altivec - there is no altivec support in the kernel yet, so
>>>> you'll get SIGILL whenever it hits an altivec instruction.
>>>>
>>>> - Justin
>>>>     
>>>>         
>>> Wow, thanks. Dealt with. 
>>>
>>> So... considering I've built most things with those broken CFLAGS, how
>>> do I go about rebuilding everything I have installed ? :\
>>>
>>> (Also, how far along the line is Altivec support expected to be?) :\
>>>
>>> Thanks kindly,
>>> --Horst.
>>>   
>>>       
>> Assuming these are only ports, I would suggest rebuilding ruby by hand, 
>> then doing a portupgrade -fa, which will force rebuild all ports. If you 
>> rebuilt critical system components (gcc for instance) with these CFLAGS, 
>> you might have no option but to reinstall world from CD.
>>
>> Altivec support shouldn't be too very complicated to add to the kernel 
>> (a matter of saving/restoring vector registers and parsing VRSAVE), and 
>> is on my todo list when I have free time again and G5 support is imported.
>> -Nathan
>> _______________________________________________
>> freebsd-ppc at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc
>> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe at freebsd.org"
>>     
>
> Nathan,
>
> 	I started working on Altivec support in the kernel, but haven't been
> 	successful.  I mostly started with a port from NetBSD, but if you want the
> 	patches I made, I'll be happy to send them your way.
>   
The "after I do x, y, z" above implies something like March, so please 
continue.
-Nathan


More information about the freebsd-ppc mailing list