Michael Cargile wrote:
> Sorry I have not gotten back to this till now. I was placed on another 
> project for a couple of days. Anyways...
> 
> Currently I am compiling the basic x86 system from the developement 
> enviroment and we will use that till I can build an x86_64 optimized build.
> 
> One thing that I did notice the first time I build the x86 version is 
> that the zaptel is hard coded to use the 2.6.13.3 kernel not to the 
> version specified in the .config for buildroot (I did not get to zaptel 
> in the build before so I did not notice this). Is there a reason for 
> this? I orginally was going to use the 2.6.16.1 kernel (probably use the 
> 2.6.16.3 build now if I can).

        I hacked that for now.  For some reason, the (strip) code in the 
Makefile didn't like parsing the config option.  It is like that in a 
few other places.  I spent about 20 minutes on it and had to move on!

        Why not 2.6.16.5? :)

> Once I have the x86 system setup and working. I will run the build in 
> script and post the results somewhere as well as my config. I do not 
> know how much good svn diff will do as I have just been pulling down the 
> latest every morning and moving my configs over. Same with make dirclean.
> 
> Also how hard is it to get the development enviroment to use the head 
> version of asterisk instead of the stable... I realize that some of the 
> patches might need to be updated but besides that. The reason I ask is 
> we found some bugs in asterisk and are patching the head to fix them.

        I want to start making snapshots of head.  No one else is doing it. 
That way, when you select "asterisk" you will be able to select "Use 
daily snapshot?" just like with uclibc and busybox.  Good for testing.

> Thanks
> Michael Cargile
> 

--
Kristian Kielhofner
_______________________________________________
Astlinux-users mailing list
[email protected]
http://lists.kriscompanies.com/mailman/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to [EMAIL 
PROTECTED]

Reply via email to