This might be related, or it might not be, but I just tried to compile
rev. 1956 and it failed 30 minutes in with
"./Setup drivers
--builddir=/media/disk/Downloads/astlinux-0.6/build_i586/wanpipe-3.3.10/ast_build_dir
--with-linux=/media/disk/Downloads/astlinux-0.6/build_i586/linux-2.6.20.21-astlinux
--zaptel-path=/media/disk/Downloads/astlinux-0.6/build_i586/zaptel-1.4.10.1/kernel
--usr-cc=/media/disk/Downloads/astlinux-0.6/build_i586/staging_dir/bin/i586-linux-uclibc-gcc
--protocol=DEF-TDM --no-zaptel-compile --noautostart --arch=i386
--silent
./Setup: 1357: Syntax error: "(" unexpected
make[1]: *** [all_bin_kmod] Error 2
make[1]: Leaving directory
`/media/disk/Downloads/astlinux-0.6/build_i586/wanpipe-3.3.10'
make: *** [/media/disk/Downloads/astlinux-0.6/build_i586/wanpipe-3.3.10/.built]
Error 2"
On Fri, 12, 2008 at 5:46 PM, Philip Prindeville
<[EMAIL PROTECTED]> wrote:
> David Kerr wrote:
>>
>> What is the right way to build after I do a "svn update" ? A few days
>> ago I pulled the 0.6 branch and it build cleanly (except for the
>> asterisk-gui problem that I reported the other day). Today I did an
>> svn update and it pulled down a few updated files (including a fix to
>> asterisk-gui, nice thank you). But I run into two problems...
>>
>> First, while building asterisk-gui it halts stating that manager.conf
>> has already been patched and askes me whether to assume -R. it
>> defaults to no. Which turned out to be wrong, so I tried again and
>> said yes. But I don't know what -R does?
>>
>> Second, sometime later, I get the following and I don't know what to do.
>>
>> # Use fakeroot so genext2fs believes the previous fakery
>> INITRD_GENEXT2_REALSIZE=`LANG=C du -l -s -c -k
>> /home/david/astlinux0.6/astlinux-0.6/build_i586/initrd | grep total |
>> sed -e "s/total//"`; \
>> INITRD_GENEXT2_ADDTOROOTSIZE=`if [ $INITRD_GENEXT2_REALSIZE
>> -ge 20000 ] ; then echo 16384; else echo 2400; fi`; \
>> INITRD_GENEXT2_SIZE=`expr $INITRD_GENEXT2_REALSIZE +
>> $INITRD_GENEXT2_ADDTOROOTSIZE`; \
>> INITRD_GENEXT2_ADDTOINODESIZE=`find
>> /home/david/astlinux0.6/astlinux-0.6/build_i586/initrd | wc -l`; \
>> INITRD_GENEXT2_INODES=`expr $INITRD_GENEXT2_ADDTOINODESIZE +
>> 400`; \
>> set -x; \
>>
>> /home/david/astlinux0.6/astlinux-0.6/build_i586/staging_dir/usr/bin/fakeroot
>> \
>> -i
>> /home/david/astlinux0.6/astlinux-0.6/build_i586/staging_dir/fakeroot.env \
>> -s
>> /home/david/astlinux0.6/astlinux-0.6/build_i586/staging_dir/fakeroot.env
>> -- \
>>
>> /home/david/astlinux0.6/astlinux-0.6/build_i586/genext2fs-1.4/genext2fs \
>> -b $INITRD_GENEXT2_SIZE \
>> -i $INITRD_GENEXT2_INODES \
>> -d
>> /home/david/astlinux0.6/astlinux-0.6/build_i586/initrd \
>> -U initrd.img
>> +
>> /home/david/astlinux0.6/astlinux-0.6/build_i586/staging_dir/usr/bin/fakeroot
>> -i
>> /home/david/astlinux0.6/astlinux-0.6/build_i586/staging_dir/fakeroot.env
>> -s
>> /home/david/astlinux0.6/astlinux-0.6/build_i586/staging_dir/fakeroot.env
>> --
>> /home/david/astlinux0.6/astlinux-0.6/build_i586/genext2fs-1.4/genext2fs
>> -b 5148 -i 712 -d
>> /home/david/astlinux0.6/astlinux-0.6/build_i586/initrd -U initrd.img
>> /home/david/astlinux0.6/astlinux-0.6/build_i586/genext2fs-1.4/genext2fs:
>> /home/david/astlinux0.6/astlinux-0.6/build_i586/genext2fs-1.4/genext2fs:busybox:
>> Invalid argument
>> make: *** [initrd.img] Error 1
>>
>> I know I could erase everything, pull the 0.6 branch again, and build
>> the lot all over again and it would probably build cleanly. But that
>> would take several hours and shouldn't be necessary for simply
>> updating a couple of files.
>>
>> What should I do to get a successful (incremental, not a recompile
>> everything) build after an svn update?
>>
>> Thanks
>> David
>
>
> That's a known issue and I'd like to fix it but haven't had time.
>
> After an "svn update", you can do either:
>
> make clean
>
> but that's pretty brutal. The contents of "toolchain" rarely change, so
> I wouldn't bother zapping that unless you see a posting suggesting
> otherwise.
>
> You can also do:
>
> rm -rf build_i586/
>
> which just zaps the package builds, not the tools.
>
> Lastly, for the exact issue you are seeing above, I'd just do:
>
> rm -rf asterisk-clean asterisk-dirclean asterisk-gui-clean
> asterisk-gui-dirclean webinterface-clean webinterface-dirclean
>
> ... this is because manager.conf gets installed by asterisk, but then
> updated twice by asterisk-gui and webinterface which "layer on" patches
> to it. This step resets everything back to zero.
>
> Let me know if you're still having issues.
>
> -Philip
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Astlinux-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to [EMAIL
> PROTECTED]
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to [EMAIL
PROTECTED]
