Martin Man wrote:
> Erast Benson wrote:
>   
>> On Tue, 2007-07-17 at 15:07 +0200, Martin Man wrote:
>>     
>>> Nico Sabbi wrote:
>>>       
>>>> what I'd really like to have in some more documentation, especially
>>>> guides on how to package ON stuff (not all of it is available in Nexenta,
>>>> including pieces that are CDDL such as the xsvc driver, BTW why?)
>>>> so that we poor users can contribute more
>>>>         
>>> yes, the scripts to compile & package nevada should be available 
>>> publicly in the long run, I personally would like them to become part of 
>>> the repository itself, much in the same way as kernel-package does for 
>>> linux kernel. Just FYI: I have already tried to compile Nevada under 
>>> Nexenta to see what are the external dependencies and gotchas in order 
>>> to have Nexenta self-contained.
>>>
>>> Hopefully Erast will give us more clue regarding the ON build scripts.
>>>       
>> I'd say, it would make sense to make ON compilable on Nexenta first,
>> workout issues and come up with diff first. And after that I will try to
>> find some time to put everything together as a buildable sunw source
>> package. Currently those scripts are very much SXCR specific and needs
>> to be fixed to work properly in native env too.
>>     
>
> My initial testing reveals that the patch to build ON on Nexenta must
> address usage of sed/awk/echo, these are fine and just one-liners in
> multiple locations. What is however not that easy are build-depends for
> certain ON parts. I have identified the evil to be net-snmp, glib, dbus,
> all of them have headers conveying info how they were compiled, so using
> nexenta versions of these packages is not easy yet, I'm trying to use
> SXCE versions now. The same applies for GNU as. I hope to put the
> summary to my blog as soon as I have a full build. At the moment around
> 30 components are still failing to build due to various issues.
>
> Which means, that it might make sense to publish the ON->dpkg scripts as
> soon as possible and simply using SXCE zone to build ON for now...
>
> what do you think?
> Martin
>   

I know it's not open source but what about using SUNWspro compilers 
instead of GNU? They are decent IMHO.

-Tim
_______________________________________________
gnusol-devel mailing list
[email protected]
http://lists.sonic.net/mailman/listinfo/gnusol-devel

Reply via email to