Am 25.03.2012 00:15, schrieb davidMbrooke:
> On Sat, 2012-03-24 at 20:37 +0100, KP Kirchdoerfer wrote:
>> 
>> Another issue is shorewall.
>> Latest version 4.5 "improved" install section for BUILD and HOST system.
>> I'm not shure if I got it right. So can you pls do me a favour and chekc
>> if works on a Fedora system? I tried with my latest commit to go without
>> the the underlying build system. If it doesn't work for you, I have to
>> rethink my approach.
>> 
>> kp
> 
> Hi kp,
> 
> I'm seeing errors creating Packages for shorewall (and shorewall6) :-(
> 
> Error from buildpacket.pl is:
>   Generating package shorwall
>   cp: cannot stat 
> `/home/leaf/bering-uclibc-next/staging/i486-unknown-linux-uclibc/etc/init.d/shorewall-init':
>  No such file or directory
> 
> Output from the "install" step running buildtool.pl is:
>   cp init.sh shorewall-4.5.1.1/init.sh
>   mkdir -p 
> /home/leaf/bering-uclibc-next/build/i486-unknown-linux-uclibc/shorewall
>   (cd shorewall-4.5.1.1; env 
> PREFIX=/home/leaf/bering-uclibc-next/build/i486-unknown-linux-uclibc/shorewall
>  ./install.sh)
>   Installing Redhat/Fedora-specific configuration...
>   Not setting file owner/group permissions, not running as root.
>   Installing Shorewall Version 4.5.1.1

My fault - forgot to commit a common.cfg which points to the correct file.

> I wonder if is possible / sensible to force a setting for $HOST when
> calling install.sh ? I would have thought we should select something
> which matches the Target rather than the Build host...

In the case of shorewall the "HOST" environment variable "describes the
system where the installed package will run."

Can you sow the error for shorewall6?

kp

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to