[luci] problems with LuCi Asterisk Webpages, Asterisk-XIP and running with Asterisk 1.4

[Paul dubliner]

Hi JoW -

Unfortunately I am still having problems with getting asterisk-xip package
to build. There seems to be a problem where the package is not appearing in
'menuconfig' even after selecting the option to view broken packages - there
are warning messages being generated after 'menuconfig' is closed. I have
copied the full output at the end of this email; the line referring to
asterisk-xip is here:

tmp/.config-package.in:4621:warning: 'select' used by config symbol
'PACKAGE_luci-app-asterisk' refer to undefined symbol
'PACKAGE_asterisk14-xip-core'

I had a look in tmp/.config-package.in, where the packages are listed, and
it strikes me that the asterisk-xip just doesn't seem to be getting defined.

I am wondering at this stage should I:

a] explicitly define an asterisk-xip package in a Makefile outside the
../contrib/packages/asterisk-xip folder,

b] waht name it should be, if this should be 'asterisk14-xip' or
'asterisk14-xip-core',

c] if maybe there is a bug whereby the Kamikaze menuconfig is not picking up
'broken' packages (kamikaze trunk svn r14731) - this could be an OpenWRT
issue and not related to the asterisk-xip package at all,

d] and if there is a way to make asterisk-xip 'unbroken'.

Any additional debug steps suggestions would be great, in the mean time I am
going to plug away at trying to build it by modification to the Makefiles.

Thanks again

Paul








tmp/.config-package.in:985:warning: 'select' used by config symbol
'PACKAGE_xrelayd' refer to undefined symbol 'PACKAGE_libxyssl'
tmp/.config-package.in:4621:warning: 'select' used by config symbol
'PACKAGE_luci-app-asterisk' refer to undefined symbol
'PACKAGE_asterisk14-xip-core'
tmp/.config-package.in:4786:warning: 'select' used by config symbol
'PACKAGE_luci-app-statistics' refer to undefined symbol
'PACKAGE_collectd-mod-interfaces'
tmp/.config-package.in:5540:warning: 'select' used by config symbol
'PACKAGE_collectd-mod-sensors' refer to undefined symbol
'PACKAGE_libsensors'
tmp/.config-package.in:6030:warning: 'select' used by config symbol
'PACKAGE_luaxyssl' refer to undefined symbol 'PACKAGE_libxyssl'
#
# using defaults found in .config
#


*** End of OpenWrt configuration.
*** Execute 'make' to build the OpenWrt or try 'make help'.





On Mon, Mar 30, 2009 at 9:52 PM, Jo-Philipp Wich <xm at subsignal.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Good evening Paul.
>
> > Q1: did I miss something when dropping the asterisk-xip folder in? should
> > there have been a step where a package index file or something is updated
> to
> > 'see' the new asterisk-xip?
>
> Run make menuconfig, enable and navigate to
>  "Advanced configuration options (for developers)  --->"
> and enable
>  "Show broken platforms / packages"
>
> You should now see asterisk-xip in "Network  --->" .
>
> > Q2: In the Makefile the PKG_SOURCE name and location is declared but I
> > didn't see reference to a build location  or location for where the
> source
> > for the asterisk14-core etc  - am I misreading the Makefile? what is the
> > significance of @!TARGET_avr32?
>
> The "@!TARGET_avr32" token just specifies that Asterisk does not work on
> the AVR32 platform. It's CPU is MMU-less and therfore not really
> suitable for things like Asterisk.
>
> If BUILD_DIR is unset, it defaults to
> "build_dir/<target-platform>/<packagename>-<packageversion>".
>
> Also the asterisk-xip package needs a bunch of dependencies from
> mainline OpenWrt which are not properly defined atm. In order to
> sucessfully build asterisk you have to ./scripts/feeds install at least
> the following packages (their names might differ, use ./scripts/feeds
> list to search them):
>
>  - iksemel
>  - speex
>  - postgresql
>  - gsm
>  - zaptel-1.4.x
>  - openh323
>  - sqlite2
>  - alsa-lib
>  - uclibc++
>  - libdlna (?)
>  - libtasn1 (?)
>
> > Q3: Can I build asterisk-xip only as a package using a manually
> downloaded
> > asterisk 1.4.22.tar.gz? Where should I put this? would it be best to
> > manually extract it first?
>
> Just put the tarball in dl/ within the top level folder of your buildroot.
>
> > Q4 Is there a recommended sequence of steps in taking the asterisk-xip
> down
> > from the trunk and porting into my LuCi codebase you can suggest?
>
> No. You did it mostly right, I believe the culprit might be that it's
> marked broken which can be circumvented with the options mentioned above.
>
>
> ~ JoW
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAknRMRYACgkQdputYINPTPNYrgCfX4sjIWL++iTwnV8nU62EpuHL
> dv8An23+T6/lEXAkTbLMxdc47myTu0mJ
> =/tCV
> -----END PGP SIGNATURE-----
> _______________________________________________
> luci mailing list
> luci at lists.subsignal.org
> https://lists.subsignal.org/mailman/listinfo/luci
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.subsignal.org/pipermail/luci/attachments/20090331/52afd53e/attachment.htm