Re: Trying to build 6177, perl failing

Eric Shubert <[email protected]> Tue, 09 Apr 2013 19:02:08 -0700
Newsgroups gmane.comp.security.ipcop.devel
Organization Eric Shubert & Associates
Message-ID <[email protected]>
On 04/05/2013 11:33 AM, Eric Shubert wrote:
> I'm attempting to build v6177 (should be 2.0.6 if I'm not mistaken) on a
> COS6 host. I've gotten over several hurdles, but I'm stuck on perl now.
> I ran ./make.sh gettoolchain, so perl wasn't built in that phase.
>
> The make.sh is choking at "chroot_make perl", with the following error:
>
> + cd /usr/src/lfs
> + make -f perl LFS_BASEDIR=/usr/src install
> ====================================== Installing perl-5.10.1 ...
> Install started; saving file list to /usr/src/lsalr ...
> cd /usr/src/perl-5.10.1 && tar zxf /usr/src/cache/
> tar (child): /usr/src/cache/: Cannot read: Is a directory
> tar (child): At beginning of tape, quitting now
> tar (child): Error is not recoverable: exiting now
>
> gzip: stdin: unexpected end of file
> tar: Child returned status 2
> tar: Error is not recoverable: exiting now
> make: *** [/usr/src/files_i486/02_base/perl-5.10.1] Error 2
>
> Any help would be greatly appreciated.
> I'll continue to learn what that script's doing in the meantime.
> Thanks.
>

Thanks to Gilles and David for the pointers.

I've since adjusted my tact. I've changed to debian to do the build, and 
have fetched the entire ipcop svn tree, and am using the 
tag/release-2.0.3 branch for building.

I've adjusted locations and a couple versions and successfully obtained 
the other sources. Using the current trunk was helpful with this, 
especially the kernel related packages. I've thus been able to build 
current 2.1.1 and older 2.0.3 isos. So far so good.

My purpose of doing this is to include the kernel paravirtualized 
drivers virtio-net and virtio-blk for use with IPCops running as a KVM. 
I realize that some folks here are leery about running IPCop as a VM, 
but I'm not so inclined. While the merits of such a setup can be 
debated, I think that having the option is none the less a benefit.

I changed the config/kernel/kernel-config.i486 file using menuconfig to 
include virtualization modules, and built an iso. An associate of mine 
who's working with me on this installed the iso using the e1000 network 
drivers, then changed the nic types from the e1000 to virtio. IPCop 
handles it fine with the modified kernel which includes the virtio 
modules. Network performance went from 80MB/s using e1000 to 269MB/s 
using virtio. That's a sizable improvement.

We're in need of a little guidance regarding how to get setup to detect 
the virtio device type. I haven't been able to hack that bit yet, and 
would appreciate a little help getting that going.

While the virtio-blk disk driver won't provide nearly the overall 
performance gain as virtio-net, I'd also like the installer to recognize 
and use the virtio-blk device for the hdd. Any pointers for that would 
be appreciated as well.

Once I get all this working, I'd be happy to provide a patch file for 
all of the changes required for this, or do whatever might be needed to 
help get these drivers into the stock IPCop distro.

Thanks for all your work with IPCop. I hope I can make a little 
contribution in this area too.

-- 
-Eric 'shubes'


------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter