Were you both using identical hardware? CPUs? Compiler flags? This may seem like an obvious line of questioning, but I've found that it always isn't.

Anyway, assuming that pacbuid is using a chroot for all the builds, it should work independently of the currently running kernel and for that matter, the currently running system. That said, what if a makefile tries to use the current kernel version (uname -r) for something? Does pacbuild have facilities for dealing with this sort of problem?

On 7/13/06, Varun Acharya <ganja.guru.x64@gmail.com> wrote:
I'm not too sure of this Andy. Remember a while back, when I was running a
custom kernel, we tested out some packages for size and ours always
differed by a couple of bytes? Both packages worked but we couldn't figure
out why the file sizes were slightly different.

ganja_guru



>
> building packages running a custom kernel shouldn't make the package
> different. should be ok.
>
> andyrtr
>
> _______________________________________________
> arch-ports mailing list
> arch-ports@archlinux.org
> http://www.archlinux.org/mailman/listinfo/arch-ports



_______________________________________________
arch-ports mailing list
arch-ports@archlinux.org
http://www.archlinux.org/mailman/listinfo/arch-ports