ipcop-devel Mailing List for IPCop Firewall

Thank, Achim. That worked.


> Hi Perry,
>
> do a './make.sh clean' before build.
>
>
> Achim
>
>
>
>> Hi guys,
>>
>> I've just updated my IPCop service to the latest SVN revision (7114).
>> I'm building on CentOS release 6.4 using kernel 2.6.32-358.18.1.el6.x86_64.
>>
>> Here's my command line session:
>>
>> -----------
>>
>> $ linux32
>> $ ./make.sh build
>>
>> ... Snipped command-line outputs ...
>>
>> *** Building packages options            version     time (sec)    status
>> fix-up [   svn-6854 ] [         0 ] [ DONE ]
>> installer [   svn-6039 ] [         0 ] [ DONE ]
>> initramfs [   svn-7075 ] [        23 ] [ DONE ]
>> Skip floppy images
>> Skip avm drivers
>> update [ PASS=2.1.0 ]  [   svn-6584 ] [         0 ] [ FAIL ]
>>
>> ERROR: Building update [ FAIL ]
>> Check log_i486/_latest_interrupt.log for errors if applicable
>>
>>
>> $ tail -f -n 500 log_i486/_latest_interrupt.log
>> + cd /usr/src/lfs
>> + make -f update LFS_BASEDIR=/usr/src install
>> # Clean out some old stuff first
>> rm -rf /installer/images/ipcop-2.1.0-update.i486.tgz /tmp/*
>> # Build update for architecture: i486 version: 2.1.0
>> # Collect the files that have changed since last IPCop version
>> tar -c --files-from=/usr/src/updates/2.1.0/ROOTFILES.i486-2.1.0 \
>>           -f /tmp/patch.tar --exclude='#*'
>> tar: Removing leading `/' from member names
>> tar: /etc/sysctlpostinit.conf: Cannot stat: No such file or directory
>> tar: Removing leading `/' from hard link targets
>> tar: Exiting with failure status due to previous errors
>> make: *** [install] Error 2
>>
>> -----------
>>
>> The file "/etc/sysctlpostinit.conf" cannot be found by the build process.
>>
>> Am I missing something? Please help. Thanks.
>>
>>
>> - Perry
>>
>>
>> ------------------------------------------------------------------------------
>> October Webinars: Code for Performance
>> Free Intel webinars can help you accelerate application performance.
>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
>> the latest Intel processors and coprocessors. See abstracts and register >
>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
>> _______________________________________________
>> IPCop-devel mailing list
>> IPC...@li...
>> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
> _______________________________________________
> IPCop-devel mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel

Hi Perry,

do a './make.sh clean' before build.


Achim



> Hi guys,
> 
> I've just updated my IPCop service to the latest SVN revision (7114). 
> I'm building on CentOS release 6.4 using kernel 2.6.32-358.18.1.el6.x86_64.
> 
> Here's my command line session:
> 
> -----------
> 
> $ linux32
> $ ./make.sh build
> 
> ... Snipped command-line outputs ...
> 
> *** Building packages options            version     time (sec)    status
> fix-up [   svn-6854 ] [         0 ] [ DONE ]
> installer [   svn-6039 ] [         0 ] [ DONE ]
> initramfs [   svn-7075 ] [        23 ] [ DONE ]
> Skip floppy images
> Skip avm drivers
> update [ PASS=2.1.0 ]  [   svn-6584 ] [         0 ] [ FAIL ]
> 
> ERROR: Building update [ FAIL ]
> Check log_i486/_latest_interrupt.log for errors if applicable
> 
> 
> $ tail -f -n 500 log_i486/_latest_interrupt.log
> + cd /usr/src/lfs
> + make -f update LFS_BASEDIR=/usr/src install
> # Clean out some old stuff first
> rm -rf /installer/images/ipcop-2.1.0-update.i486.tgz /tmp/*
> # Build update for architecture: i486 version: 2.1.0
> # Collect the files that have changed since last IPCop version
> tar -c --files-from=/usr/src/updates/2.1.0/ROOTFILES.i486-2.1.0 \
>          -f /tmp/patch.tar --exclude='#*'
> tar: Removing leading `/' from member names
> tar: /etc/sysctlpostinit.conf: Cannot stat: No such file or directory
> tar: Removing leading `/' from hard link targets
> tar: Exiting with failure status due to previous errors
> make: *** [install] Error 2
> 
> -----------
> 
> The file "/etc/sysctlpostinit.conf" cannot be found by the build process.
> 
> Am I missing something? Please help. Thanks.
> 
> 
> - Perry
> 
> 
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
> _______________________________________________
> IPCop-devel mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel

Hi guys,

I've just updated my IPCop service to the latest SVN revision (7114). 
I'm building on CentOS release 6.4 using kernel 2.6.32-358.18.1.el6.x86_64.

Here's my command line session:

-----------

$ linux32
$ ./make.sh build

... Snipped command-line outputs ...

*** Building packages options            version     time (sec)    status
fix-up [   svn-6854 ] [         0 ] [ DONE ]
installer [   svn-6039 ] [         0 ] [ DONE ]
initramfs [   svn-7075 ] [        23 ] [ DONE ]
Skip floppy images
Skip avm drivers
update [ PASS=2.1.0 ]  [   svn-6584 ] [         0 ] [ FAIL ]

ERROR: Building update [ FAIL ]
Check log_i486/_latest_interrupt.log for errors if applicable


$ tail -f -n 500 log_i486/_latest_interrupt.log
+ cd /usr/src/lfs
+ make -f update LFS_BASEDIR=/usr/src install
# Clean out some old stuff first
rm -rf /installer/images/ipcop-2.1.0-update.i486.tgz /tmp/*
# Build update for architecture: i486 version: 2.1.0
# Collect the files that have changed since last IPCop version
tar -c --files-from=/usr/src/updates/2.1.0/ROOTFILES.i486-2.1.0 \
         -f /tmp/patch.tar --exclude='#*'
tar: Removing leading `/' from member names
tar: /etc/sysctlpostinit.conf: Cannot stat: No such file or directory
tar: Removing leading `/' from hard link targets
tar: Exiting with failure status due to previous errors
make: *** [install] Error 2

-----------

The file "/etc/sysctlpostinit.conf" cannot be found by the build process.

Am I missing something? Please help. Thanks.


- Perry

> Correction, it should be 2.0.3 which is revision 6339. The svn bumped up 
> to 2.1.x immediately after. Everything else up to 2.0.6 were updates 
> only and minor, not major system changes.
> 

Thanks.  I'll get that started, and hopefully will have an environment
by morning!

David

On 10/13/2013 12:23 PM, Administrator wrote:
> O
> n Sun, 2013-10-13 at 11:37 -0700, David W Studeman wrote:
>> On 10/13/2013 11:14 AM, Administrator wrote:
>> > I've tried building the latest ipcop from svn on a clean slackware VM,
>> > and it won't build.  ulogd stops as it doesn't have libnetfilter_log.
>> > Here's the end of the log from the build:
>>
>> The latest which is pre2.1.1 in svn or 2.0.6 which is a story in itself?
>>
>> >
>> > Please can you advise me what I need to edit so this happens.
>> >
>> > Thanks
>> > David
>> >
>>
>> There isn't much compelling reason to build 2.0.6 as it was a one off
>> exercise to satisfy the timezone data changes when 2.1.x was not ready
>> for distribution. You'd be better off building 2.0.4 and then using
>> updates as the svn was in it's natural progression state as of 2.0.4. By
>> the time 2.0.5 and 2.0.6 updates came out, the svn trunk was well into
>> version 2.1.x with a much newer kernel. It took a temporary svn exercise
>> off to the side to make 2.0.5 and 2.0.6 at the time.
>>
>> Someone did try to fix 2.0.6 in svn after the fact but I've been focused
>> on 2.1.0/2.1.1 to make sure that my adaptation for Cobalts is ready when
>> IPCop is and I can't think of a reason to build anything between 2.0.4
>> and 2.1.0.
>>
>> What exactly are you trying to accomplish by building 2.0.6?
>
> Thanks David
>
> how do I download the source for 2.0.4?  What's the right version.
>
> I have 2.0.6 running on my firewall, and want to add the TOR addon,
> which I have to build myself - so I've got to get a clean build
> environment built ...
>
> I thought it'd be relatively easy.  I guess if I'd done this before
> 2.0.5 & 6 came out, it would have been ...
> Your advice would be appreciated ...
>
> Thanks
> David

Correction, it should be 2.0.3 which is revision 6339. The svn bumped up 
to 2.1.x immediately after. Everything else up to 2.0.6 were updates 
only and minor, not major system changes.

-- 
Dave Studeman
http://www.raqcop.com

O
n Sun, 2013-10-13 at 11:37 -0700, David W Studeman wrote:

> On 10/13/2013 11:14 AM, Administrator wrote:
> > I've tried building the latest ipcop from svn on a clean slackware VM,
> > and it won't build.  ulogd stops as it doesn't have libnetfilter_log.
> > Here's the end of the log from the build:
> 
> The latest which is pre2.1.1 in svn or 2.0.6 which is a story in itself?
> 
> >
> > Please can you advise me what I need to edit so this happens.
> >
> > Thanks
> > David
> >
> 
> There isn't much compelling reason to build 2.0.6 as it was a one off 
> exercise to satisfy the timezone data changes when 2.1.x was not ready 
> for distribution. You'd be better off building 2.0.4 and then using 
> updates as the svn was in it's natural progression state as of 2.0.4. By 
> the time 2.0.5 and 2.0.6 updates came out, the svn trunk was well into 
> version 2.1.x with a much newer kernel. It took a temporary svn exercise 
> off to the side to make 2.0.5 and 2.0.6 at the time.
> 
> Someone did try to fix 2.0.6 in svn after the fact but I've been focused 
> on 2.1.0/2.1.1 to make sure that my adaptation for Cobalts is ready when 
> IPCop is and I can't think of a reason to build anything between 2.0.4 
> and 2.1.0.
> 
> What exactly are you trying to accomplish by building 2.0.6?


Thanks David

how do I download the source for 2.0.4?  What's the right version.

I have 2.0.6 running on my firewall, and want to add the TOR addon,
which I have to build myself - so I've got to get a clean build
environment built ...

I thought it'd be relatively easy.  I guess if I'd done this before
2.0.5 & 6 came out, it would have been ...
Your advice would be appreciated ...

Thanks
David

On 10/13/2013 11:14 AM, Administrator wrote:
> I've tried building the latest ipcop from svn on a clean slackware VM,
> and it won't build.  ulogd stops as it doesn't have libnetfilter_log.
> Here's the end of the log from the build:

The latest which is pre2.1.1 in svn or 2.0.6 which is a story in itself?

>
> Please can you advise me what I need to edit so this happens.
>
> Thanks
> David
>

There isn't much compelling reason to build 2.0.6 as it was a one off 
exercise to satisfy the timezone data changes when 2.1.x was not ready 
for distribution. You'd be better off building 2.0.4 and then using 
updates as the svn was in it's natural progression state as of 2.0.4. By 
the time 2.0.5 and 2.0.6 updates came out, the svn trunk was well into 
version 2.1.x with a much newer kernel. It took a temporary svn exercise 
off to the side to make 2.0.5 and 2.0.6 at the time.

Someone did try to fix 2.0.6 in svn after the fact but I've been focused 
on 2.1.0/2.1.1 to make sure that my adaptation for Cobalts is ready when 
IPCop is and I can't think of a reason to build anything between 2.0.4 
and 2.1.0.

What exactly are you trying to accomplish by building 2.0.6?
-- 
Dave Studeman
http://www.raqcop.com

I've tried building the latest ipcop from svn on a clean slackware VM,
and it won't build.  ulogd stops as it doesn't have libnetfilter_log.
Here's the end of the log from the build:


checking pkg-config is at least version 0.9.0... yes
checking for LIBNFNETLINK... yes
checking for LIBMNL... yes
checking for LIBNETFILTER_LOG... no
configure: error: Package requirements (libnetfilter_log >= 1.0.0) were
not met:

No package 'libnetfilter_log' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables
LIBNETFILTER_LOG_CFLAGS
and LIBNETFILTER_LOG_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
make: *** [/usr/src/files_i486/03_ipcop/ulogd-2.0.2] Error 1


It looks to me that libnetfilter_log needs to be built before ulogd (it
isn't).

Please can you advise me what I need to edit so this happens.

Thanks
David

I'd like to thank learnet for the translation of the Admin Manual into
Spanish. It can be found on the IPCop website amongst the the links to
documentation.
http://ipcop.org/2.0.0/es/admin/html/

Eric