TODO list for each hardware target can be found as sticky topic in the corresponding forum
Re: Is porting Asterisk + modules a lot of work? It appears that running the command manually works OK, so it could be some setting in the build process (missing shopt -s globstar?):
Code:
|
|
|
Administrator has disabled public posting |
Re: Is porting Asterisk + modules a lot of work?Strange, maybe it is building for you now. It didn't look like it before. My own shell is zsh but make uses the system shell, which is sh in my case as it most likely is in yours so I don't think that matters. Maybe the bash version makes a difference? I have 4.2. Try replacing the ** with just * because the directories currently only go one level deep anyway. Let me know if that works. It does for me. |
|
|
Administrator has disabled public posting |
Re: Is porting Asterisk + modules a lot of work? Thanks for the tip, but still no go :-/
Code:
If anyone can think of a work-around... |
|
|
Administrator has disabled public posting |
Re: Is porting Asterisk + modules a lot of work? http://pastebin.com/5HM61sS6
|
|
|
Administrator has disabled public posting |
Re: Is porting Asterisk + modules a lot of work? That output looks okay. I'm on Gentoo, which means no particular release. I take it if you do...
Code:ls /usr/src/switchfin/build_ip01/root/usr/lib/yate/{,*/}*.yate Then you get the same error? The shortcut expands to this, which you can also try.
Code:ls /usr/src/switchfin/build_ip01/root/usr/lib/yate/*.yate /usr/src/switchfin/build_ip01/root/usr/lib/yate/*/*.yate |
|
|
Administrator has disabled public posting |
Re: Is porting Asterisk + modules a lot of work? Nope, it works fine:
|
|
|
Administrator has disabled public posting |
Re: Is porting Asterisk + modules a lot of work? Still no go:
Code:
|
|
|
Administrator has disabled public posting |
Re: Is porting Asterisk + modules a lot of work? No, the HD is only 42% full. The compiling just stopped at the "/usr/src/switchfin/build_ip01/root/usr/lib/yate/*/*.yate" line with no error message.
|
|
|
Administrator has disabled public posting |
Re: Is porting Asterisk + modules a lot of work?That line is the last step. If there was no error then it worked. I don't fully understand the "no free space" error but I didn't mean your disk is out of space. It certainly has nothing to do with Yate, except perhaps that including it has caused you to go over some limit. Try enabling the "Cull unused ELF shared libraries" build option in menuconfig if you haven't already. This saves a lot of space. |
|
|
Administrator has disabled public posting |
Re: Is porting Asterisk + modules a lot of work? I already had that a long time ago. The cause is apparently that the uImage is too big, and we must remove some files from the root filesystem.
|
|
|
Administrator has disabled public posting |
Re: Is porting Asterisk + modules a lot of work?Like I said, the "Cull unused ELF shared libraries" option makes a big difference so try that first. I don't think it's a hardware limit but there might be some artificial limit in the code and you also have to ensure the NAND is partitioned appropriately. The first box I received only supported images up to 8MB and I had to repartition it to go beyond that. This is another area I plan on making big changes to but not today, I'm afraid. |
|
|
Administrator has disabled public posting |
Re: Is porting Asterisk + modules a lot of work? Problem solved: Indeed, I had to remove some apps so "make image" could work.
|
|
|
Administrator has disabled public posting |
Re: Is porting Asterisk + modules a lot of work? Who said anything about CentOS? But I've figured it out anyway. I had forgotten that Ubuntu's /bin/sh actually points to Dash rather than Bash. I better be careful not to use Bashisms in makefiles in future. Now fixed in trunk. Thanks for your persistence in tracking this down.
|
|
|
Administrator has disabled public posting |
Re: Is porting Asterisk + modules a lot of work? Sorry, I meant "Gentoo", not CentOS.
|
|
|
Administrator has disabled public posting |
Re: Is porting Asterisk + modules a lot of work?You can boot with an image in RAM but it will still use /persistent from the NAND. That's not so bad though and may even be what you want. Just fire up U-Boot and transfer the image over TFTP. It will usually boot automatically. |
|
|
Administrator has disabled public posting |
Re: Is porting Asterisk + modules a lot of work? Thanks for the tip. Do you know what Switchfin puts in /persistent, how much space it takes? It's not so much space taken in the NAND that bother me, rather that it uses RAM to hold the root filesystem while BAPS uses the NAND for that. The Atcom only has 64MB of RAM, which doesn't leave much after Asterisk + root fs are loaded.
|
|
|
Administrator has disabled public posting |
Re: Is porting Asterisk + modules a lot of work? The /persistent partition is 236MB but the default setup barely uses 1MB of that. I've talked about the waste of RAM in the other thread, which I know you've seen.
|
|
|
Administrator has disabled public posting |
Re: Is porting Asterisk + modules a lot of work? Hi Guys,
|
|
|
Administrator has disabled public posting |
Re: Is porting Asterisk + modules a lot of work? Hello,
cheers'n'beers Henning |
|
|
Administrator has disabled public posting |
- Index
- » Developers
- » General discussions
- » Is porting Asterisk + modules a lot...
Most Active Users
Board Info
- Board Stats: Total Users: 2587 Total Topics: 299 Total Polls: 1 Total Posts: 1727 Dormant
- User Info: Newest User : user2553 Members Online: 0 Guests Online: 260
- Online There are no members online
- Topic
- New
- Locked
- Sticky
- Active
- New/Active
- New/Locked
- New Sticky
- Locked/Active
- Active/Sticky
- Sticky/Locked
- Sticky/Active/Locked