Re: [Astlinux-users] Rhino compile problem (0.4 branch)

[Darrick H. <dha...@dj...>]

Sebastian Auriol wrote:
>>> The only package I have used "make clean" on is the linux package
>>> (done from the folder in build_i586). AFAIK this is the only
>>> solution in order to get the kernel to re-compile after changing the
>>> kernel build options. Please correct me if there is another, better,
>>> way. 
>>>
>>>       
>> Several packages require the kernel (linux package) to be
>> built first.
>> If you remove the kernel, you also need to remove wanpipe, zaptel,
>> madwifi ... The only SAFE way to do this is remove the entire
>> build_i586 tree.  I apologize for that, but it's the only safe way. 
>> If 
>> you have a
>> reasonably fast processor it shouldn't take more than 30 minutes to
>> build the entire thing anyway.
>>     
>
> If I remove the kernel I also lose the configuration changes I have made to
> it, or should I create a patch with the configuration changes and put it in
> the linux package directory? I see you have something in the mk file to
> patch the kernal with all .patch files...
>   
In 0.4, the kernel configuration file is in 
target/device/XXX/linux-XXX-ABC.config  You could put your own file in 
that location.  I would not suggest doing any extra patching as you are 
suggesting.

> Wanpipe is the first thing to fail after removing the build_i586 tree. This
> is before doing any make cleans or any other errors. I'm giving you this
> information to help AstLinux - not because I need it to work personally.
>   
I understand this, but I also suspect that you have modified some other 
things.
>> I also don't wish to be rude, but you are working on a development
>> system.  The final compiled "Astlinux" product works.  It is
>> also mostly
>> stable which for a 0.4x version of a program is pretty
>> reasonable.  If
>> we were post 1.0, I can understand your complaint.  If you've been
>> involved in other projects SVN is a dynamic creature.
>> Sometimes changes
>> are submitted which temporarily break things.  When we create
>> the 0.4.5
>> tag, we hope to have some of these issues resolved.
>>
>> Perhaps some of this is my fault.  I had referred to 0.4 branch as
>> stable.  Compared to trunk it is stable, but it is still a development
>> environment.
>>     
>
> OK, I understand. But don't take my messages as complaints - they are not:
> merely feedback and questions (and, sometimes, thanks). But you did
> specifically suggest to me to try the latest version of 0.4 after my hotplug
> firmware problem so I have been trying to compile the latest version of
> 0.4... (And I also would quite like to get these updates anyway.)
>   
I'll have to look back through my notes on the hotplug stuff.  
Diethotplug is what is included with Astlinux.  I'm not sure how that 
handles the firmware.  Perhaps there is a flag you can pass to insmod 
that will load the firmware (try modinfo yourmodule).

Some of these issues may need to be addressed after 0.4.5 is released.  
There have been significant changes and improvements which need to get 
out.  There are security risks with older versions of Asterisk. 

I do appreciate the feedback.  It would be nice to get feed back of the 
released images.  We're aware that the build system is somewhat less 
than perfect.  That's something that we're correcting a little at a 
time.  However, if you are making changes or altering the build system, 
we're not going to be able to troubleshoot exactly what the problem is 
since we don't know what you changed.

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com