From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Mon 11 Jul 2005 - 23:50:44 BST
On Tue, Jul 12, 2005 at 08:04:49AM +0930, Mike O'Connor wrote:
> Hi Herbert
>
> Little hard to do with woody as I would need to recompile a large number
> of other packages.
>
> The reason why I need to have a woody version of the tools is that is
> just to hard to upgrade all the systems I have out there, particularly
> as they a mostly in data center in places a long way a way.
hmm, and I always thought that gentoo uses source only
packages not debian :)
> The other option would be if someone could tell me how I could hide the
> ip addresses of other client OS's using the old tools, this would delay
> my requirments to upgrades.
it requires a newer kernel not newer tools ...
HTH,
Herbert
PS: thread hijacking is not nice :)
> Cheer
> Mike
>
>
>
> Herbert Poetzl wrote:
>
> >On Mon, Jul 11, 2005 at 03:47:43PM +0930, Mike O'Connor wrote:
> >
> >
> >>Hi All
> >>
> >>I have been unable to compile any of the beta util-vserver tools for
> >>Debian woody even after back porting from unstable a number of packages
> >>
> >>I back ported the following packages
> >>nasm_0.98.38-1.2_i386.deb
> >>dietlibc_0.29-2_i386.deb
> >>dietlibc-dev_0.29-2_i386.deb
> >>libbeecrypt6-dev_4.1.2-1_i386.deb
> >>libbeecrypt6_4.1.2-1_i386.deb
> >>
> >>The url
> >>http://www.pineview.net/~mike/util-vserver/debian-build-problems-0.30.207.txt,
> >>show a full build log.
> >>
> >>These seemed of intrest to me:
> >>checking whether gcc and cc understand -c and -o together... yes
> >>checking whether g++ is a C++ compiler... no
> >>configure: WARNING: *** some programs will not be built because a C++
> >>compiler is lacking
> >>checking whether gcc is a C99 compiler... no
> >>configure: WARNING: *** some programs will not be built because system
> >>is lacking a C99 compiler
> >>checking whether to enable dietlibc... yes (autodetected, 0.29)
> >>checking whether dietlibc supports C99... skipped (compiler does not
> >>support C99)
> >>configure:
> >>
> >>
> >
> >what about trying a recent compiler?
> >
> >i.e. something which understands C99 standard?
> >(e.g. 3.3.5 is a very good choice)
> >
> >HTH,
> >Herbert
> >
> >
> >
> >>util-vserver 0.30.207
> >>
> >>Features:
> >> CC: gcc, 2.95.4
> >> CXX: g++, 2.95.4
> >> CPPFLAGS: ''
> >> CFLAGS: '-g -O2 -Wall -pedantic -W'
> >> CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W'
> >> build/host: i686-pc-linux-gnu/i686-pc-linux-gnu
> >> Use dietlibc: yes
> >> Build C++ programs: no (affected: vbuild, vcheck)
> >> Build C99 programs: no (affected: vunify, vcopy, vhashify, vdlimit)
> >> Available APIs: compat,v11,v13,fscompat,net,oldproc,olduts
> >> ext2fs Source: e2fsprogs
> >> syscall(2) invocation: alternative
> >> vserver(2) syscall#: 273/default
> >>
> >>Paths:
> >> prefix: /usr/local
> >> sysconf-Directory: ${prefix}/etc
> >> cfg-Directory: ${prefix}/etc/vservers
> >> initrd-Directory: $(sysconfdir)/init.d
> >> pkgstate-Directory: ${prefix}/var/run/vservers
> >> Kernelheaders: /lib/modules/2.6.11.6-smp-vs.1.9.5/build/include
> >> vserver-Rootdir: /vservers
> >>
> >>The build errors seemed to be mostly about parsing errors.
> >>
> >>Any ideas would be great.
> >>
> >>
> >>Thanks
> >>Mike
> >>_______________________________________________
> >>Vserver mailing list
> >>Vserver_at_list.linux-vserver.org
> >>http://list.linux-vserver.org/mailman/listinfo/vserver
> >>
> >>
>
> _______________________________________________
> Vserver mailing list
> Vserver_at_list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver