On Fri, 2006-05-19 at 10:05 -0400, Lists wrote:
> On Sun, 14 May 2006, Johnny Hughes wrote:
> > On Sat, 2006-05-13 at 08:56 -0500, Erick Perez wrote:
> >> Scott, The system will handle .... up all they way to 200 agents
> >> talking simultaneously. It must also record the phone conversations
> >>
> >> we will definitely recompile asterisk in that box. we will not run the
> >> bianries. However when you say compatibilities, you mean development
> >> tools? the compiler? sendmail? apache?
>
> > If you are going to compile items on an x86_64 box using the CentOS
> > x86_64 arch, there are gotchas introduced by multiple libraries.
> > What you want to make sure you have is a pure x86_64 build environment
> > to build all x86_64 files.
> >
> > You may need these 2 files that are i[3,4,5,6]86 (and only these x86
> > files ... any others can produce badly built binaries).
> > glibc.i686
> > glibc-devel.i386
> >
> > What this means is, you can't run i386 items (like Open Office) on your
> > x86_64 machine that you want to use for building packages.
>
> Does using mock get around this restriction?
>
> -David
I don't use mock ... BUT, if it does it in a chroot, yes. If not, no.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.centos.org/pipermail/centos/attachments/20060519/4180860c/attachment.bin
