Re: Different behavior in the chroot and build services
- To: debian-bsd@lists.debian.org
- Subject: Re: Different behavior in the chroot and build services
- From: Sylvestre Ledru <sylvestre@debian.org>
- Date: Wed, 08 Jun 2011 16:25:29 +0200
- Message-id: <1307543129.10829.37.camel@losinj.inria.fr>
- In-reply-to: <alpine.LRH.2.02.1105311521010.32046@sci.felk.cvut.cz>
- References: <1306825316.4606.62.camel@korcula.inria.fr> <alpine.LRH.2.02.1105310945070.31727@sci.felk.cvut.cz> <1306844795.4606.99.camel@korcula.inria.fr> <20110531124652.GC18909@mraw.org> <1306846129.4606.101.camel@korcula.inria.fr> <20110531130131.GD18909@mraw.org> <alpine.LRH.2.02.1105311521010.32046@sci.felk.cvut.cz>
Hello,
Le mardi 31 mai 2011 à 15:33 +0200, Petr Salinger a écrit :
> Anyway, the difference between buildd and porter machine is also CPU.
> On one my machine (and seems also on both GNU/kFreeBSD builld)
> "make getarch_2nd" fails.
>
> The "param.h" handles OPTERON, but not INTEL_UNKNOWN
> as generated by "getarch 1":
Thanks for spotting that. I think it is the issue.
Could you share the output of /proc/cpuinfo ?
I would like to report a bug upstream on this (looks like it does not
fall-back on the generic define if it cannot detect the CPU).
Since I have no way to reproduce myself the issue, would you mind to
test some stuff for me ?
1) Just apply displayCpuInfo.diff (forceGeneric.diff should not be
applied here)
and type "make getarch"
2) Apply forceGeneric.diff
it should fix the report issue.
If you don't have time for that, no worries.
many thanks,
Sylvestre
Reply to: