astlinux-users — AstLinux Users Mailing List

Re: [Astlinux-users] Hotplug firmware problem

[Kristian K. <kri...@gm...>]

On 3/13/07, Bryce Chidester <br...@rh...> wrote:
>
>  Just my $.02 - The Digium modules use the kernel hotplug firmware loading
> to retrieve and download their firmware, just like the Rhino modules do. I
> can't say for certain about Digium's modules but to re-install the firmware
> for Rhino cards (specifically, rcbfx), you simply pass force_fw=1; they
> automatically upgrade if the firmware file is a newer version than what's
> installed.
>  There are several meanings to the word firmware in this discussion and I
> feel it's necessary to determine exactly what everyone is referring to. Are
> you talking about loading the firmware in order to run the card, as I know
> some wireless cards require? Or just upgrading the card, in which case it
> can be done on another machine and then moved over?
>  Regards,
> Bryce Chidester
> Rhino Equipment Corp.
> br...@rh...
> Tel: +1 (480) 940-1826 x6351
> Fax: +1 (480) 961-1826
> FWD: 633686 x6351
> IP: asterisk.rhinoequipment.com x6351
>

Bryce,

  The Digium modules DO NOT require hotplug.  When compiling zaptel
you can pass NO_HOTPLUG (something like that) and it will compile the
current firmware into the module.

  What everyone is talking about here is firmware required for the
card, like for Intel wireless cards.

  I looked into this a while back but I never got very far...

  Hotlpug is just a bunch of scripts.  It shouldn't be that hard to
build into AstLinux.  The only reason why it isn't in right now is
because I don't trust it %100.  I think it tries to be smarter than it
really is and I have seen it cause problems on many systems.

  Running hotplug on my laptop I don't mind.  But on a headless,
mission critical PBX (for instance), it makes me nervous...


-- 
Kristian Kielhofner

Re: [Astlinux-users] Hotplug firmware problem

[Sebastian A. <sp...@sy...>]

You pass force_fw=1 as a parameter to insmod?
 
The firmware is required to run the card - I believe it is not stored on the
device and needs to be loaded each time.
 
Many thanks,
 
Sebastian


  _____  

From: ast...@li...
[mailto:ast...@li...] On Behalf Of Bryce
Chidester
Sent: 13 March 2007 21:06
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] Hotplug firmware problem


Just my $.02 - The Digium modules use the kernel hotplug firmware loading to
retrieve and download their firmware, just like the Rhino modules do. I
can't say for certain about Digium's modules but to re-install the firmware
for Rhino cards (specifically, rcbfx), you simply pass force_fw=1; they
automatically upgrade if the firmware file is a newer version than what's
installed.
There are several meanings to the word firmware in this discussion and I
feel it's necessary to determine exactly what everyone is referring to. Are
you talking about loading the firmware in order to run the card, as I know
some wireless cards require? Or just upgrading the card, in which case it
can be done on another machine and then moved over?

Regards,

Bryce Chidester

Rhino Equipment Corp.

br...@rh...

Tel: +1 (480) 940-1826 x6351

Fax: +1 (480) 961-1826

FWD: 633686 x6351

IP: asterisk.rhinoequipment.com x6351



THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE  PROPRIETARY
MATERIAL and is thus for use only by the intended  recipient. If you
received this in error, please contact the sender  and delete the email and
its attachments from all computers.

Re: [Astlinux-users] Hotplug firmware problem

[Sebastian A. <sp...@sy...>]

Darrick Hartman wrote:
>> Darrick Hartman wrote:
>> 
>>> 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).
>>> 
>> 
>> There don't seem to be any flags I can pass to insmod for this
>> module (or at least nothing obvious from looking at the modinfo
>> output). Do you know where Diethotplug is looking for the firmware?
>> 
>> 
>> 
> Looking at this further, I'm not sure why we're even including
> diethotplug.  It's not configured to do anything.  It also
> looks pretty
> dated and possibly replaced by something newer.  Sorry I can't be of
> more help.  I'm almost thinking that there should be a utility that
> comes with the driver to load the firmware.  The only hardware
> experience I have with firmware are the Hauppauge PVR X50 cards which
> work with a firmware loader. 
> 
> Darrick

If diethotplug is not configured to do anything, does that mean it won't do
anything? Is it possible to configure it with some conf files?

There is a loader for the firmware for use on Linux 2.4 kernels, but it is
not supposed to be needed on Linux 2.6 kernels. I tried to build a package I
created from the source of this firmware loader (and other utils) for
AstLinux anyway, before I realised that it wasn't required (and might not
even work with 2.6), and had problems as there seemed to be a dependency on
libusb-devel, which is not included in AstLinux, (not to mention a badly
written make file).

Many thanks,

Sebastian

Re: [Astlinux-users] Hotplug firmware problem

[Bryce C. <br...@rh...>]

Just my $.02 - The Digium modules use the kernel hotplug firmware 
loading to retrieve and download their firmware, just like the Rhino 
modules do. I can't say for certain about Digium's modules but to 
re-install the firmware for Rhino cards (specifically, rcbfx), you 
simply pass force_fw=1; they automatically upgrade if the firmware file 
is a newer version than what's installed.
There are several meanings to the word firmware in this discussion and I 
feel it's necessary to determine exactly what everyone is referring to. 
Are you talking about loading the firmware in order to run the card, as 
I know some wireless cards require? Or just upgrading the card, in which 
case it can be done on another machine and then moved over?

Regards,
Bryce Chidester
Rhino Equipment Corp.
br...@rh...
Tel: +1 (480) 940-1826 x6351
Fax: +1 (480) 961-1826
FWD: 633686 x6351
IP: asterisk.rhinoequipment.com x6351

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE  PROPRIETARY MATERIAL and is thus for use only by the intended  recipient. If you received this in error, please contact the sender  and delete the email and its attachments from all computers.



Darrick Hartman wrote:
> Sebastian Auriol wrote:
>   
>>> Sebastian Auriol <> wrote:
>>>     
>>>       
>>>> Hi,
>>>>
>>>> Does anyone know if AstLinux will load firmware for hotplug
>>>> usb devices and
>>>> where it is looking for the firmware if it can / does?
>>>>
>>>> I initially copied the firmware into /usr/lib/hotplug/firmware and
>>>> modprobe'd the device driver (kernel module) but I got this
>>>> in the messages
>>>> log:
>>>> firmware unavailable (system misconfigured?)
>>>>
>>>> So I tried copying the firmware to /lib/firmware just in case
>>>> it was looking
>>>> there, but that didn't help.  Any ideas?
>>>>
>>>> Many thanks,
>>>>
>>>> Sebastian
>>>>
>>>> P.S.  I am using AstLinux 0.4 branch from end of Jan.
>>>>       
>>>>         
>> Darrick Hartman wrote:
>>   
>>     
>>> 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).
>>>     
>>>       
>> There don't seem to be any flags I can pass to insmod for this module (or at
>> least nothing obvious from looking at the modinfo output). Do you know where
>> Diethotplug is looking for the firmware?
>>
>>
>>   
>>     
> Looking at this further, I'm not sure why we're even including 
> diethotplug.  It's not configured to do anything.  It also looks pretty 
> dated and possibly replaced by something newer.  Sorry I can't be of 
> more help.  I'm almost thinking that there should be a utility that 
> comes with the driver to load the firmware.  The only hardware 
> experience I have with firmware are the Hauppauge PVR X50 cards which 
> work with a firmware loader.
>
> Darrick
>
>   

Re: [Astlinux-users] Hotplug firmware problem

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

Sebastian Auriol wrote:
>> Sebastian Auriol <> wrote:
>>     
>>> Hi,
>>>
>>> Does anyone know if AstLinux will load firmware for hotplug
>>> usb devices and
>>> where it is looking for the firmware if it can / does?
>>>
>>> I initially copied the firmware into /usr/lib/hotplug/firmware and
>>> modprobe'd the device driver (kernel module) but I got this
>>> in the messages
>>> log:
>>> firmware unavailable (system misconfigured?)
>>>
>>> So I tried copying the firmware to /lib/firmware just in case
>>> it was looking
>>> there, but that didn't help.  Any ideas?
>>>
>>> Many thanks,
>>>
>>> Sebastian
>>>
>>> P.S.  I am using AstLinux 0.4 branch from end of Jan.
>>>       
>
> Darrick Hartman wrote:
>   
>> 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).
>>     
>
> There don't seem to be any flags I can pass to insmod for this module (or at
> least nothing obvious from looking at the modinfo output). Do you know where
> Diethotplug is looking for the firmware?
>
>
>   
Looking at this further, I'm not sure why we're even including 
diethotplug.  It's not configured to do anything.  It also looks pretty 
dated and possibly replaced by something newer.  Sorry I can't be of 
more help.  I'm almost thinking that there should be a utility that 
comes with the driver to load the firmware.  The only hardware 
experience I have with firmware are the Hauppauge PVR X50 cards which 
work with a firmware loader.

Darrick

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

Re: [Astlinux-users] Hotplug firmware problem

[Sebastian A. <sp...@sy...>]

>Sebastian Auriol <> wrote:
>> Hi,
>> 
>> Does anyone know if AstLinux will load firmware for hotplug
>> usb devices and
>> where it is looking for the firmware if it can / does?
>> 
>> I initially copied the firmware into /usr/lib/hotplug/firmware and
>> modprobe'd the device driver (kernel module) but I got this
>> in the messages
>> log:
>> firmware unavailable (system misconfigured?)
>> 
>> So I tried copying the firmware to /lib/firmware just in case
>> it was looking
>> there, but that didn't help.  Any ideas?
>> 
>> Many thanks,
>> 
>> Sebastian
>> 
>> P.S.  I am using AstLinux 0.4 branch from end of Jan.

Darrick Hartman wrote:
>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).

There don't seem to be any flags I can pass to insmod for this module (or at
least nothing obvious from looking at the modinfo output). Do you know where
Diethotplug is looking for the firmware?

Many thanks,

Sebastian

[Astlinux-users] 0.4 revision 757 build statistics

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

I just completed a clean build of SVN revision 757 from the 0.4 branch.  
Here is a list of the steps I took (from my history)

 1016   svn co 
https://astlinux.svn.sourceforge.net/svnroot/astlinux/branches/0.4 0.4
 1017  cd 0.4/
 1018  ls
 1019  cp astlinux.config .config
 1020  make oldconfig
 1021  make menuconfig
 1022  make
 1023  ls -lah build_i586/root/boot/grub/e2fs_stage1_5
 1024  svn update
 1025  history

Note in the menuconfig, I did not change anything.  I just verified that 
the settings were correct.

the ls -lah command was to check the timestamp on that file.  That's the 
last file in the build process.

-rwxr-xr-x  1 dhartman dhartman 7.9K Mar 13 12:34 
build_i586/root/boot/grub/e2fs_stage1_5

Compare that to the kernel .config file to that file.  (the kernel 
.config was the last file touched prior to issuing make)

-rw-rw-r--    1 dhartman dhartman 9.6K Mar 13 11:15 .config

You can see that the total build time on this system was 1 h 19 
minutes.  This included downloading all of the source files.  I'd 
estimate removing at least 20 minutes from that total for download 
time.  This also includes building the tool chain.  My build system is a 
virtual machine with 256MB of ram.  It is hosted on a Athlon 64 x2 
3800+.  I have three virtual machines running on this system as well as 
processes running on the host OS.  (this is my main workstation).

Everything compiled without issue.  I urge others to try those exact 
same steps to verify that their system is fully functional prior to 
making any setting changes anywhere in the build system.  If you are 
getting build errors, look very closely at the error messages.  Are they 
telling you're missing a tool on your build system?

Darrick

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

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

[Sebastian A. <sp...@sy...>]

Darrick Hartman wrote:
> Sebastian Auriol wrote:
>> 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.

Ah, thanks. I didn't know about the target/device/XXX/linux-XXX-ABC.config
file. I will certainly try using this next time.

Kind regards,

Sebastian

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

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

[Sebastian A. <sp...@sy...>]

Darrick Hartman wrote:
> Sebastian Auriol wrote:
>> Darrick Hartman wrote:
>> 
>>> Sebastian,
>>> 
>>> 1).  even though it should work, currently "make
>>> <package>-clean" then
>>> trying to remake that same package will probably result in errors. 
>>> Some of the packages have interdependancies.  The guaranteed way
>>> which will work is to remove the build_i586 directory.  We are
>>> trying to address this in trunk, but it will not be fixed in the
>>> 0.4 branch. 
>  There are
>>> just too many issues to try to fix them all with our limited
>>> resources. 
>>> 
>> 
>> 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...

Unfortunately it takes several hours to build on my system if I remove the
whole build_i586 tree. Even on another system I use that is a Dual Xeon 3
GHz server it takes a few hours IIRC.

>>> 2).  Kristian and I both built 0.4 from scratch (less the
>>> toolchain) in the last day or so and neither of us had problems.  I
>>> suspect that your problems are related to #1.
>>> 
>> 
>> I am not the only one to have wanpipe not compile on them from last
>> night's svn - Manuel also had this. The iaxmodem problem was after
>> another make after touching some files to make the wanpipe package
>> believe it had been built, so I suppose it could be due to that.
>> 
> I suspect that both you and Manuel are doing the same thing.  I doubt
> the 0.4 branch will ever reach a point where "make
> <package-foo>-clean
> will work as well as we'd like it to.  This is why I've
> stated several
> times that you should remove the build_i586 directory if you are
> changing things in your target packages.

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.

>>> 3).  rhino is known not to work.  That's why I have it flagged as
>>> testing/experimental.  They have not released the driver
>>> publicly yet.
>> I don't wish to rude, but why update the rhino package in the stable
>> branch if it was working before and the new version is known not to
>> work?  Can I simply revert to using the old version of the rhino
>> package?  Are there known issues with the older version?  If so,
>> what are they? 
>> 
> The old rhino package was outdated and didn't work with the
> updates to
> zaptel.  It was based on zaptel 1.2.7.  Rhino Equipment supplies the
> download.  Their old download would not work with newer versions of
> zaptel without changing the patch.  We decided that it would
> be better
> for Rhino to provide a proper package that works along the
> same lines as
> the wanpipe package.  What we have partially works, but is also
> partially broken.  Rhino Equipment knows this and is working
> to resolve
> it.  We are making every effort to have this included in
> 0.4.5, but if
> they are unable to get a working package to us, it may not be
> included. We are very grateful to all of the hardware companies that
> are working
> with us to have their drivers included (and therefore their hardware
> supported). 

Thanks for the explanation - this makes sense now.

> 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 complain.  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.
> 
> Darrick

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.)

Thanks for all your hard work.

Kind regards,

Sebastian

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

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

Sebastian Auriol wrote:
> Darrick Hartman wrote:
>   
>> Sebastian,
>>
>> I'm not going to reply to each of the individual compile
>> errors you are
>> receiving.  I will try to address most of them here.
>>
>> 1).  even though it should work, currently "make
>> <package>-clean" then
>> trying to remake that same package will probably result in
>> errors.  Some
>> of the packages have interdependancies.  The guaranteed way
>> which will
>> work is to remove the build_i586 directory.  We are trying to address
>> this in trunk, but it will not be fixed in the 0.4 branch.  There are
>> just too many issues to try to fix them all with our limited
>> resources. 
>>     
>
> 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.
>> 2).  Kristian and I both built 0.4 from scratch (less the
>> toolchain) in
>> the last day or so and neither of us had problems.  I suspect
>> that your
>> problems are related to #1.
>>     
>
> I am not the only one to have wanpipe not compile on them from last night's
> svn - Manuel also had this. The iaxmodem problem was after another make
> after touching some files to make the wanpipe package believe it had been
> built, so I suppose it could be due to that.
>   
I suspect that both you and Manuel are doing the same thing.  I doubt 
the 0.4 branch will ever reach a point where "make <package-foo>-clean 
will work as well as we'd like it to.  This is why I've stated several 
times that you should remove the build_i586 directory if you are 
changing things in your target packages.
>> 3).  rhino is known not to work.  That's why I have it flagged as
>> testing/experimental.  They have not released the driver
>> publicly yet.
> I don't wish to rude, but why update the rhino package in the stable branch
> if it was working before and the new version is known not to work?  Can I
> simply revert to using the old version of the rhino package?  Are there
> known issues with the older version?  If so, what are they?
>   
The old rhino package was outdated and didn't work with the updates to 
zaptel.  It was based on zaptel 1.2.7.  Rhino Equipment supplies the 
download.  Their old download would not work with newer versions of 
zaptel without changing the patch.  We decided that it would be better 
for Rhino to provide a proper package that works along the same lines as 
the wanpipe package.  What we have partially works, but is also 
partially broken.  Rhino Equipment knows this and is working to resolve 
it.  We are making every effort to have this included in 0.4.5, but if 
they are unable to get a working package to us, it may not be included.  
We are very grateful to all of the hardware companies that are working 
with us to have their drivers included (and therefore their hardware 
supported).

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 complain.  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.

Darrick

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

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

[Sebastian A. <sp...@sy...>]

Darrick Hartman wrote:
> Sebastian,
> 
> I'm not going to reply to each of the individual compile
> errors you are
> receiving.  I will try to address most of them here.
> 
> 1).  even though it should work, currently "make
> <package>-clean" then
> trying to remake that same package will probably result in
> errors.  Some
> of the packages have interdependancies.  The guaranteed way
> which will
> work is to remove the build_i586 directory.  We are trying to address
> this in trunk, but it will not be fixed in the 0.4 branch.  There are
> just too many issues to try to fix them all with our limited
> resources. 

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.

> 2).  Kristian and I both built 0.4 from scratch (less the
> toolchain) in
> the last day or so and neither of us had problems.  I suspect
> that your
> problems are related to #1.

I am not the only one to have wanpipe not compile on them from last night's
svn - Manuel also had this. The iaxmodem problem was after another make
after touching some files to make the wanpipe package believe it had been
built, so I suppose it could be due to that.

> 3).  rhino is known not to work.  That's why I have it flagged as
> testing/experimental.  They have not released the driver
> publicly yet.
> (that's why Kristian has a copy on one of his server for testing
> purposes).  It does appear that whatever Kristian has on his site is
> corrupt though.  In any case, rhino is known not to work.
> We're waiting
> for some fixes from Rhino Equipment.
> 
> Darrick

I don't wish to rude, but why update the rhino package in the stable branch
if it was working before and the new version is known not to work?  Can I
simply revert to using the old version of the rhino package?  Are there
known issues with the older version?  If so, what are they?

Many thanks,

Sebastian

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

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

Sebastian,

I'm not going to reply to each of the individual compile errors you are 
receiving.  I will try to address most of them here.

1).  even though it should work, currently "make <package>-clean" then 
trying to remake that same package will probably result in errors.  Some 
of the packages have interdependancies.  The guaranteed way which will 
work is to remove the build_i586 directory.  We are trying to address 
this in trunk, but it will not be fixed in the 0.4 branch.  There are 
just too many issues to try to fix them all with our limited resources.

2).  Kristian and I both built 0.4 from scratch (less the toolchain) in 
the last day or so and neither of us had problems.  I suspect that your 
problems are related to #1.

3).  rhino is known not to work.  That's why I have it flagged as 
testing/experimental.  They have not released the driver publicly yet.   
(that's why Kristian has a copy on one of his server for testing 
purposes).  It does appear that whatever Kristian has on his site is 
corrupt though.  In any case, rhino is known not to work.  We're waiting 
for some fixes from Rhino Equipment.

Darrick

Sebastian Auriol wrote:
> AstLinux 0.4 branch from yesterday evening fails to compile in the rhino
> package (and there is also a problem with the ftp script):
>
> touch -c
> /home/seb/astlinux-0.4/build_i586/staging_dir/include/readline/readline.h
> toolchain/getter_script.sh -P /home/seb/astlinux-0.4/dl
> ftp://ftp.rhinoequipment.com/Drivers//rhino-0.0.2b1.tbz2
> --12:53:04--  ftp://ftp.rhinoequipment.com/Drivers//rhino-0.0.2b1.tbz2
>            => `/home/seb/astlinux-0.4/dl/rhino-0.0.2b1.tbz2'
> Resolving ftp.rhinoequipment.com... 66.93.157.130
> Connecting to ftp.rhinoequipment.com|66.93.157.130|:21... connected.
> Logging in as anonymous ... Logged in!
> ==> SYST ... done.    ==> PWD ... done.
> ==> TYPE I ... done.  ==> CWD /Drivers/ ... 
> No such directory `Drivers/'.
>
> Retrying from astlinux alternate site...
> --12:53:14--  http://files.astlinux.org/rhino-0.0.2b1.tbz2
>            => `/home/seb/astlinux-0.4/dl/rhino-0.0.2b1.tbz2'
> Resolving files.astlinux.org... 208.109.78.142
> Connecting to files.astlinux.org|208.109.78.142|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: unspecified [text/html]
>
>     [ <=>                                          ] 227           --.--K/s
>
>
> 12:53:16 (114.68 KB/s) - `/home/seb/astlinux-0.4/dl/rhino-0.0.2b1.tbz2'
> saved [227]
>
> bzcat /home/seb/astlinux-0.4/dl/rhino-0.0.2b1.tbz2 | tar -C
> /home/seb/astlinux-0.4/build_i586   -xf -
> bzcat: /home/seb/astlinux-0.4/dl/rhino-0.0.2b1.tbz2 is not a bzip2 file.
> touch /home/seb/astlinux-0.4/build_i586/rhino-0.0.2b1/.unpacked
> touch: cannot touch
> `/home/seb/astlinux-0.4/build_i586/rhino-0.0.2b1/.unpacked': No such file or
> directory
> make: *** [/home/seb/astlinux-0.4/build_i586/rhino-0.0.2b1/.unpacked] Error
> 1
> [seb@IVRA1 astlinux-0.4]$ 
>
>
> BTW, this was with 2 concurrent jobs set to run; i386; i586; VIA. 
>
> Kind regards,
>
> Sebastian 
>
>
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>   


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

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

[Sebastian A. <sp...@sy...>]

AstLinux 0.4 branch from yesterday evening fails to compile in the rhino
package (and there is also a problem with the ftp script):

touch -c
/home/seb/astlinux-0.4/build_i586/staging_dir/include/readline/readline.h
toolchain/getter_script.sh -P /home/seb/astlinux-0.4/dl
ftp://ftp.rhinoequipment.com/Drivers//rhino-0.0.2b1.tbz2
--12:53:04--  ftp://ftp.rhinoequipment.com/Drivers//rhino-0.0.2b1.tbz2
           => `/home/seb/astlinux-0.4/dl/rhino-0.0.2b1.tbz2'
Resolving ftp.rhinoequipment.com... 66.93.157.130
Connecting to ftp.rhinoequipment.com|66.93.157.130|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done.    ==> PWD ... done.
==> TYPE I ... done.  ==> CWD /Drivers/ ... 
No such directory `Drivers/'.

Retrying from astlinux alternate site...
--12:53:14--  http://files.astlinux.org/rhino-0.0.2b1.tbz2
           => `/home/seb/astlinux-0.4/dl/rhino-0.0.2b1.tbz2'
Resolving files.astlinux.org... 208.109.78.142
Connecting to files.astlinux.org|208.109.78.142|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]

    [ <=>                                          ] 227           --.--K/s


12:53:16 (114.68 KB/s) - `/home/seb/astlinux-0.4/dl/rhino-0.0.2b1.tbz2'
saved [227]

bzcat /home/seb/astlinux-0.4/dl/rhino-0.0.2b1.tbz2 | tar -C
/home/seb/astlinux-0.4/build_i586   -xf -
bzcat: /home/seb/astlinux-0.4/dl/rhino-0.0.2b1.tbz2 is not a bzip2 file.
touch /home/seb/astlinux-0.4/build_i586/rhino-0.0.2b1/.unpacked
touch: cannot touch
`/home/seb/astlinux-0.4/build_i586/rhino-0.0.2b1/.unpacked': No such file or
directory
make: *** [/home/seb/astlinux-0.4/build_i586/rhino-0.0.2b1/.unpacked] Error
1
[seb@IVRA1 astlinux-0.4]$ 


BTW, this was with 2 concurrent jobs set to run; i386; i586; VIA. 

Kind regards,

Sebastian 

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

[Manuel <lis...@gm...>]

Sorry I have read you email very quickly (in my job). I can`t help you. 

Bye!

--
Manuel

-----Mensaje original-----
De: ast...@li...
[mailto:ast...@li...] En nombre de Sebastian
Auriol
Enviado el: martes, 13 de marzo de 2007 13:27
Para: 'AstLinux Users Mailing List'
Asunto: Re: [Astlinux-users] Linux kernel compile problem (0.4 branch)

Manuel wrote:
> Sebastian,
> 
> Yesterday at night I compiled 0.4 and the only problem was wanpipe. I
> disabled the package and all compile without problems. Before
> start the
> process I removed the builroot and toolchain_xxx directory.

Good to know, but as I said "...fails to compile in the linux package after
changing some of kernel options". The kernel compiled fine before I changed
those options, but when I copied my .config for the linux package over from
my January build system it failed as I said.

I copied over wanrouter.h and wanpipe.h from my old build system and now it
has compiled the part that was failing earlier.

(I also disabled the wanpipe, efax and iaxmodem packages since they were
failing as previously posted.)

Kind regards,

Sebastian


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to
pa...@kr....

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

[Sebastian A. <sp...@sy...>]

Manuel wrote:
> Sebastian,
> 
> Yesterday at night I compiled 0.4 and the only problem was wanpipe. I
> disabled the package and all compile without problems. Before
> start the
> process I removed the builroot and toolchain_xxx directory.

Good to know, but as I said "...fails to compile in the linux package after
changing some of kernel options". The kernel compiled fine before I changed
those options, but when I copied my .config for the linux package over from
my January build system it failed as I said.

I copied over wanrouter.h and wanpipe.h from my old build system and now it
has compiled the part that was failing earlier.

(I also disabled the wanpipe, efax and iaxmodem packages since they were
failing as previously posted.)

Kind regards,

Sebastian

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

[Manuel <lis...@gm...>]

Sebastian,

Yesterday at night I compiled 0.4 and the only problem was wanpipe. I
disabled the package and all compile without problems. Before start the
process I removed the builroot and toolchain_xxx directory. 

Regards, 

--
Manuel

-----Mensaje original-----
De: ast...@li...
[mailto:ast...@li...] En nombre de Sebastian
Auriol
Enviado el: martes, 13 de marzo de 2007 12:47
Para: 'AstLinux Users Mailing List'
Asunto: [Astlinux-users] Linux kernel compile problem (0.4 branch)

AstLinux 0.4 branch from yesterday evening fails to compile in the linux
package after changing some of kernel options:

  LD      arch/i386/pci/built-in.o
  CC      arch/i386/power/cpu.o
  LD      arch/i386/power/built-in.o
  CC      net/socket.o
net/socket.c:71:29: linux/wanrouter.h: No such file or directory
make[2]: *** [net/socket.o] Error 1
make[1]: *** [net] Error 2
make[1]: Leaving directory
`/home/seb/astlinux-0.4/build_i586/linux-2.6.16.12'
make: ***
[/home/seb/astlinux-0.4/build_i586/linux-2.6.16.12/arch/i386/boot/bzImage]
Error 2
[seb@IVRA1 astlinux-0.4]$ 

I note that wanrouter.h is indeed missing from linux-2.6.16.12/include/linux
(as is wanpipe.h) whereas in AstLinux 0.4 svn from Jan it was present. It
was presumably moved with the wanpipe changes?

BTW, this was with 2 concurrent jobs set to run; i386; i586; VIA.

Kind regards,

Sebastian 



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to
pa...@kr....

[Astlinux-users] Linux kernel compile problem (0.4 branch)

[Sebastian A. <sp...@sy...>]

AstLinux 0.4 branch from yesterday evening fails to compile in the linux
package after changing some of kernel options:

  LD      arch/i386/pci/built-in.o
  CC      arch/i386/power/cpu.o
  LD      arch/i386/power/built-in.o
  CC      net/socket.o
net/socket.c:71:29: linux/wanrouter.h: No such file or directory
make[2]: *** [net/socket.o] Error 1
make[1]: *** [net] Error 2
make[1]: Leaving directory
`/home/seb/astlinux-0.4/build_i586/linux-2.6.16.12'
make: ***
[/home/seb/astlinux-0.4/build_i586/linux-2.6.16.12/arch/i386/boot/bzImage]
Error 2
[seb@IVRA1 astlinux-0.4]$ 

I note that wanrouter.h is indeed missing from linux-2.6.16.12/include/linux
(as is wanpipe.h) whereas in AstLinux 0.4 svn from Jan it was present. It
was presumably moved with the wanpipe changes?

BTW, this was with 2 concurrent jobs set to run; i386; i586; VIA.

Kind regards,

Sebastian 

[Astlinux-users] iaxmodem compile problem (0.4 branch)

[Sebastian A. <sp...@sy...>]

AstLinux 0.4 branch from yesterday evening fails to compile in the iaxmodem
package
(which is enabled by default due to efax being enabled by default):

/home/seb/astlinux-0.4/build_i586/staging_dir/bin/i586-linux-uclibc-ar cru
.libs/libiax.a  iax2-parser.o iax.o md5.o jitterbuf.o
/home/seb/astlinux-0.4/build_i586/staging_dir/bin/i586-linux-uclibc-ranlib
.libs/libiax.a
creating libiax.la
(cd .libs && rm -f libiax.la && ln -s ../libiax.la libiax.la)
make[2]: Leaving directory
`/home/seb/astlinux-0.4/build_i586/iaxmodem-0.1.14/lib/libiax2/src'
make[2]: Entering directory
`/home/seb/astlinux-0.4/build_i586/iaxmodem-0.1.14/lib/libiax2'
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory
`/home/seb/astlinux-0.4/build_i586/iaxmodem-0.1.14/lib/libiax2'
make[1]: Leaving directory
`/home/seb/astlinux-0.4/build_i586/iaxmodem-0.1.14/lib/libiax2'
touch /home/seb/astlinux-0.4/build_i586/iaxmodem-0.1.14/.libiax2_built
(cd /home/seb/astlinux-0.4/build_i586/iaxmodem-0.1.14; \
 
/home/seb/astlinux-0.4/build_i586/staging_dir/bin/i586-linux-uclibc-gcc
-Wall -g -O2 -DMODEMVER=\"ODEMVER\" -DDSPVER=\"SPVER\" \
        -DIAXVER=\"AXVER\" -DSTATICLIBS -D_GNU_SOURCE -std=c99 \
        -I/home/seb/astlinux-0.4/build_i586/staging_dir/usr/include
-L/home/seb/astlinux-0.4/build_i586/root/usr/lib \
        -Ilib/libiax2/src -Ilib/spandsp/src -c -o iaxmodem.o iaxmodem.c && \
 
/home/seb/astlinux-0.4/build_i586/staging_dir/bin/i586-linux-uclibc-gcc
-I/home/seb/astlinux-0.4/build_i586/staging_dir/usr/include
-L/home/seb/astlinux-0.4/build_i586/root/usr/lib \
        -lm -lutil -ltiff -o iaxmodem iaxmodem.o
lib/spandsp/src/.libs/libspandsp.a \
        lib/libiax2/src/.libs/libiax.a \
);
iaxmodem.o: In function `lrintf':
/home/seb/astlinux-0.4/build_i586/iaxmodem-0.1.14/iaxmodem.c:139: undefined
reference to `lrint'
collect2: ld returned 1 exit status
make: *** [/home/seb/astlinux-0.4/build_i586/iaxmodem-0.1.14/.built] Error 1
[seb@IVRA1 astlinux-0.4]$

BTW, this was with 2 concurrent jobs set to run; i386; i586; VIA. 

Kind regards,

Sebastian 

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

[Sebastian A. <sp...@sy...>]

Darrick Hartman wrote:
>> Sebastian,
>> 
>> I know what the problem is, but I don't have time to fix it this
>> afternoon.  For the short term, either include libpq or delete the
>> asterisk-makefile-apps.patch.  I need to edit the patch to only add
>> apps_sql_postgres if selected.
>> 
>> 
> This should be fixed.  Do an svn update, delete build_i586 and you
> should be good to go. 
> 
> Darrick

Thanks! I'll try building it now overnight.

Sebastian

[Astlinux-users] trunk bash compile minor error

[<ast...@el...>]

Got a bit of a surprise shock when I decided to go a little bleeding edge
with a trunk compile. Seems bash has a minor issue, though I hadn't seen
it before when I either was able to complete a compile, or at least get
much farther along.

This is trunk 757 with gcc 4.2 snapshot 20070307 , compile with ObjC,
shared libraries, and libtool. This is on an older svn checkout where I
had wiped out toolchain, toolchain_buildi586, and build_i586 and did a svn
update to rebuild those parts cleanly while retaining the dl directory.


make[2]: Leaving directory
`/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/bash-3.0/po'
make[1]: Leaving directory
`/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/bash-3.0'
rm -f
/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/root/bin/bash*
mv
/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/root/usr/bin/bash*
/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/root/bin/
(cd /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/root/bin;
/bin/ln -fs bash sh)
rm -rf
/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/root/share/locale
/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/root/usr/info \
        /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/root/usr/man
/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/root/usr/share/doc
/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/staging_dir/bin/i586-linux-uclibc-strip
--remove-section=.comment --remove-section=.note
/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/root/usr/bin/bash
/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/staging_dir/bin/i586-linux-uclibc-strip:
'/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/root/usr/bin/bash':
No such file
make: ***
[/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/root/bin/bash]
Error 1

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

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

Darrick Hartman wrote:
> Sebastian,
>
> I know what the problem is, but I don't have time to fix it this 
> afternoon.  For the short term, either include libpq or delete the 
> asterisk-makefile-apps.patch.  I need to edit the patch to only add 
> apps_sql_postgres if selected.
>   
>
This should be fixed.  Do an svn update, delete build_i586 and you 
should be good to go.

Darrick

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

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

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

Sebastian,

I know what the problem is, but I don't have time to fix it this 
afternoon.  For the short term, either include libpq or delete the 
asterisk-makefile-apps.patch.  I need to edit the patch to only add 
apps_sql_postgres if selected.

Darrick

Sebastian Auriol wrote:
> And I don't even have Asterisk PostgrSQL support enabled!
>
> /home/seb/astlinux-0.4/build_i586/staging_dir/bin/i586-linux-uclibc-gcc
> -pipe  -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations
> -Iinclude -I../include -D_REENTRANT -D_GNU_SOURCE  -Os -pipe -march=i586
> -DZAPTEL_OPTIMIZATIONS         -fomit-frame-pointer  -fPIC   -c -o
> app_stack.o app_stack.c
> /home/seb/astlinux-0.4/build_i586/staging_dir/bin/i586-linux-uclibc-gcc
> -shared -Xlinker -x -o app_stack.so  app_stack.o
> /home/seb/astlinux-0.4/build_i586/staging_dir/bin/i586-linux-uclibc-gcc
> -pipe
> -I/home/seb/astlinux-0.4/build_i586/asterisk-1.2.16/apps/../../staging_dir/u
> sr/local/pgsql/include  -pipe  -Wall -Wstrict-prototypes
> -Wmissing-prototypes -Wmissing-declarations  -Iinclude -I../include
> -D_REENTRANT -D_GNU_SOURCE  -Os -pipe -march=i586 -DZAPTEL_OPTIMIZATIONS
> -fomit-frame-pointer  -fPIC -c -o app_sql_postgres.o app_sql_postgres.c
> app_sql_postgres.c:46:22: libpq-fe.h: No such file or directory
> app_sql_postgres.c: In function `aPGSQL_connect':
> app_sql_postgres.c:231: error: `PGconn' undeclared (first use in this
> function)
> app_sql_postgres.c:231: error: (Each undeclared identifier is reported only
> once
> app_sql_postgres.c:231: error: for each function it appears in.)
> app_sql_postgres.c:231: error: `karoto' undeclared (first use in this
> function)
> app_sql_postgres.c:245: warning: implicit declaration of function
> `PQconnectdb'
> app_sql_postgres.c:246: warning: implicit declaration of function `PQstatus'
> app_sql_postgres.c:246: error: `CONNECTION_BAD' undeclared (first use in
> this function)
> app_sql_postgres.c:248: warning: implicit declaration of function
> `PQerrorMessage'
> app_sql_postgres.c:248: warning: format argument is not a pointer (arg 7)
> app_sql_postgres.c: In function `aPGSQL_query':
> app_sql_postgres.c:270: error: `PGconn' undeclared (first use in this
> function)
> app_sql_postgres.c:270: error: `karoto' undeclared (first use in this
> function)
> app_sql_postgres.c:271: error: `PGresult' undeclared (first use in this
> function)
> app_sql_postgres.c:271: error: `PGSQLres' undeclared (first use in this
> function)
> app_sql_postgres.c:294: warning: implicit declaration of function `PQexec'
> app_sql_postgres.c:296: warning: format argument is not a pointer (arg 7)
> app_sql_postgres.c:300: warning: implicit declaration of function
> `PQresultStatus'
> app_sql_postgres.c:300: error: `PGRES_BAD_RESPONSE' undeclared (first use in
> this function)
> app_sql_postgres.c:301: error: `PGRES_NONFATAL_ERROR' undeclared (first use
> in this function)
> app_sql_postgres.c:302: error: `PGRES_FATAL_ERROR' undeclared (first use in
> this function)
> app_sql_postgres.c:303: warning: implicit declaration of function
> `PQcmdStatus'
> app_sql_postgres.c:303: warning: format argument is not a pointer (arg 7)
> app_sql_postgres.c:307: warning: implicit declaration of function
> `PQnfields'
> app_sql_postgres.c: In function `aPGSQL_fetch':
> app_sql_postgres.c:328: error: `PGresult' undeclared (first use in this
> function)
> app_sql_postgres.c:328: error: `PGSQLres' undeclared (first use in this
> function)
> app_sql_postgres.c:380: warning: implicit declaration of function
> `PQntuples'
> app_sql_postgres.c:389: warning: implicit declaration of function
> `PQgetvalue'
> app_sql_postgres.c:389: warning: assignment makes pointer from integer
> without a cast
> app_sql_postgres.c: In function `aPGSQL_reset':
> app_sql_postgres.c:419: error: `PGconn' undeclared (first use in this
> function)
> app_sql_postgres.c:419: error: `karoto' undeclared (first use in this
> function)
> app_sql_postgres.c:434: warning: implicit declaration of function `PQreset'
> app_sql_postgres.c: In function `aPGSQL_clear':
> app_sql_postgres.c:445: error: `PGresult' undeclared (first use in this
> function)
> app_sql_postgres.c:445: error: `karoto' undeclared (first use in this
> function)
> app_sql_postgres.c:460: warning: implicit declaration of function `PQclear'
> app_sql_postgres.c: In function `aPGSQL_disconnect':
> app_sql_postgres.c:475: error: `PGconn' undeclared (first use in this
> function)
> app_sql_postgres.c:475: error: `karoto' undeclared (first use in this
> function)
> app_sql_postgres.c:490: warning: implicit declaration of function `PQfinish'
> make[2]: *** [app_sql_postgres.o] Error 1
> make[2]: Leaving directory
> `/home/seb/astlinux-0.4/build_i586/asterisk-1.2.16/apps'
> make[1]: *** [subdirs] Error 1
> make[1]: Leaving directory
> `/home/seb/astlinux-0.4/build_i586/asterisk-1.2.16'
> make: *** [/home/seb/astlinux-0.4/build_i586/asterisk-1.2.16/asterisk] Error
> 2
> [seb@IVRA1 astlinux-0.4]$ 
>
> Kind regards,
>
> Sebastian 
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>   


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

[Astlinux-users] app_sql_postgres compile problem (0.4 branch)

[Sebastian A. <sp...@sy...>]

And I don't even have Asterisk PostgrSQL support enabled!

/home/seb/astlinux-0.4/build_i586/staging_dir/bin/i586-linux-uclibc-gcc
-pipe  -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations
-Iinclude -I../include -D_REENTRANT -D_GNU_SOURCE  -Os -pipe -march=i586
-DZAPTEL_OPTIMIZATIONS         -fomit-frame-pointer  -fPIC   -c -o
app_stack.o app_stack.c
/home/seb/astlinux-0.4/build_i586/staging_dir/bin/i586-linux-uclibc-gcc
-shared -Xlinker -x -o app_stack.so  app_stack.o
/home/seb/astlinux-0.4/build_i586/staging_dir/bin/i586-linux-uclibc-gcc
-pipe
-I/home/seb/astlinux-0.4/build_i586/asterisk-1.2.16/apps/../../staging_dir/u
sr/local/pgsql/include  -pipe  -Wall -Wstrict-prototypes
-Wmissing-prototypes -Wmissing-declarations  -Iinclude -I../include
-D_REENTRANT -D_GNU_SOURCE  -Os -pipe -march=i586 -DZAPTEL_OPTIMIZATIONS
-fomit-frame-pointer  -fPIC -c -o app_sql_postgres.o app_sql_postgres.c
app_sql_postgres.c:46:22: libpq-fe.h: No such file or directory
app_sql_postgres.c: In function `aPGSQL_connect':
app_sql_postgres.c:231: error: `PGconn' undeclared (first use in this
function)
app_sql_postgres.c:231: error: (Each undeclared identifier is reported only
once
app_sql_postgres.c:231: error: for each function it appears in.)
app_sql_postgres.c:231: error: `karoto' undeclared (first use in this
function)
app_sql_postgres.c:245: warning: implicit declaration of function
`PQconnectdb'
app_sql_postgres.c:246: warning: implicit declaration of function `PQstatus'
app_sql_postgres.c:246: error: `CONNECTION_BAD' undeclared (first use in
this function)
app_sql_postgres.c:248: warning: implicit declaration of function
`PQerrorMessage'
app_sql_postgres.c:248: warning: format argument is not a pointer (arg 7)
app_sql_postgres.c: In function `aPGSQL_query':
app_sql_postgres.c:270: error: `PGconn' undeclared (first use in this
function)
app_sql_postgres.c:270: error: `karoto' undeclared (first use in this
function)
app_sql_postgres.c:271: error: `PGresult' undeclared (first use in this
function)
app_sql_postgres.c:271: error: `PGSQLres' undeclared (first use in this
function)
app_sql_postgres.c:294: warning: implicit declaration of function `PQexec'
app_sql_postgres.c:296: warning: format argument is not a pointer (arg 7)
app_sql_postgres.c:300: warning: implicit declaration of function
`PQresultStatus'
app_sql_postgres.c:300: error: `PGRES_BAD_RESPONSE' undeclared (first use in
this function)
app_sql_postgres.c:301: error: `PGRES_NONFATAL_ERROR' undeclared (first use
in this function)
app_sql_postgres.c:302: error: `PGRES_FATAL_ERROR' undeclared (first use in
this function)
app_sql_postgres.c:303: warning: implicit declaration of function
`PQcmdStatus'
app_sql_postgres.c:303: warning: format argument is not a pointer (arg 7)
app_sql_postgres.c:307: warning: implicit declaration of function
`PQnfields'
app_sql_postgres.c: In function `aPGSQL_fetch':
app_sql_postgres.c:328: error: `PGresult' undeclared (first use in this
function)
app_sql_postgres.c:328: error: `PGSQLres' undeclared (first use in this
function)
app_sql_postgres.c:380: warning: implicit declaration of function
`PQntuples'
app_sql_postgres.c:389: warning: implicit declaration of function
`PQgetvalue'
app_sql_postgres.c:389: warning: assignment makes pointer from integer
without a cast
app_sql_postgres.c: In function `aPGSQL_reset':
app_sql_postgres.c:419: error: `PGconn' undeclared (first use in this
function)
app_sql_postgres.c:419: error: `karoto' undeclared (first use in this
function)
app_sql_postgres.c:434: warning: implicit declaration of function `PQreset'
app_sql_postgres.c: In function `aPGSQL_clear':
app_sql_postgres.c:445: error: `PGresult' undeclared (first use in this
function)
app_sql_postgres.c:445: error: `karoto' undeclared (first use in this
function)
app_sql_postgres.c:460: warning: implicit declaration of function `PQclear'
app_sql_postgres.c: In function `aPGSQL_disconnect':
app_sql_postgres.c:475: error: `PGconn' undeclared (first use in this
function)
app_sql_postgres.c:475: error: `karoto' undeclared (first use in this
function)
app_sql_postgres.c:490: warning: implicit declaration of function `PQfinish'
make[2]: *** [app_sql_postgres.o] Error 1
make[2]: Leaving directory
`/home/seb/astlinux-0.4/build_i586/asterisk-1.2.16/apps'
make[1]: *** [subdirs] Error 1
make[1]: Leaving directory
`/home/seb/astlinux-0.4/build_i586/asterisk-1.2.16'
make: *** [/home/seb/astlinux-0.4/build_i586/asterisk-1.2.16/asterisk] Error
2
[seb@IVRA1 astlinux-0.4]$ 

Kind regards,

Sebastian 

[Astlinux-users] LINUX_VERSION

[Wojciech T. <wo...@Vo...>]

Hi,
I can not read the $LINUX_VERSION in my package.mk version.
What is a proper way to obtain the kernel version at the beginning of  
package.mk? I need that as my download string contains the kernel  
version (file-2.16.20.tar.gz)

Thanks,
Wojtek