Fred wrote:
> At 20:51 22/01/2008 -0800, Philip Prindeville wrote:
>   
>> For #4, I run fsck on the /dev/loop mounted image when I burn it.  That 
>> way, the filesystem is marked as having been fsck'd and clean the next 
>> time it's mounted.
>>     
>
> Good to know. I'll give it a shot with the next flashing.
>
>   
>>> BTW, the trunk fails compiling vim, so have to use Nano.
>>>       
>> How is it failing?  I submitted some patches recently that should resolve 
>> a few problems...
>>     
>
> $ make
> [...]
> make[1]: Entering directory `/home/compile/astlinux-trunk/build_i586/vim71'
> Starting make in the src directory.
> If there are problems, cd to the src directory and run make there
> cd src && make first
> make[2]: Entering directory 
> `/home/compile/astlinux-trunk/build_i586/vim71/src'
> mkdir objects
> CC="/home/compile/astlinux-trunk/build_i586/staging_dir/bin/i586-linux-uclibc-gcc
>  
> -Iproto -DHAVE_CONFIG_H           " 
> srcdir=/home/compile/astlinux-trunk/build_i586/vim71/src/auto sh 
> /home/compile/astlinux-trunk/build_i586/vim71/src/auto/osdef.sh
> sh: /home/compile/astlinux-trunk/build_i586/vim71/src/auto/osdef.sh: No 
> such file or directory
> make[2]: *** [auto/osdef.h] Error 127
> make[2]: Leaving directory `/home/compile/astlinux-trunk/build_i586/vim71/src'
> make[1]: *** [first] Error 2
> make[1]: Leaving directory `/home/compile/astlinux-trunk/build_i586/vim71'
> make: *** [/home/compile/astlinux-trunk/build_i586/vim71/src/vim] Error 2
>
> HTH,
> Fred.
>   

And what version of the branch are you at?

-Philip


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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]

Reply via email to