make.conf for a poudriere jail and CPUTYPE

Clay Daniels Jr. clay.daniels.jr at
Sat Sep 28 18:58:15 UTC 2019

RE: " as btver1 and sandybridge are the same arch (amd64) just different
cpus "

I'm confused here:
" *Sandy Bridge* is the codename for the microarchitecture used in the
"second generation" of the Intel Core processors (Core i7, i5, i3) "

" AMD Bobcat CPU (btver1)"
" ‘btver1’ CPUs based on AMD Family 14h cores with x86-64 instruction set
" btver1 is a SSSE3/SSE4a only CPU - it doesn't have AVX and doesn't
support XSAVE."

On Sat, Sep 28, 2019 at 8:36 AM tech-lists <tech-lists at> wrote:

> Hi,
> On Sat, Sep 28, 2019 at 03:06:29PM +0200, Polytropon wrote:
> >On Sat, 28 Sep 2019 13:16:24 +0100, tech-lists wrote:
> >> thought I'd experiment. Seems setting CPUTYPE?=btver1 causes some ports
> to
> >> fail at the configure or build stage. python36 and lzo2 for example.
> Unsure
> >> why that should be (or where to ask???)
> >
> >Some ports are restricted in a way that they can only be built
> >for specific architectures. Not everything is "cross-platform
> >compatible". :-) For example, some ports will only work on i386
> >and amd64 because they contain assembly code that is only supported
> >on those two architectures, and _not_ on, let's say, arm or ppc.
> >
> >Reference:
> >
> >For I'd say the best
> >list to ask specific questions probably is the freebsd-ports
> >mailing list.
> OK I'll do that. I was wondering if it needed to go in -toolchain as btver1
> and sandybridge are the same arch (amd64) just different cpus. What do you
> think?
> thanks,
> --
> J.

More information about the freebsd-questions mailing list