Building hardware agnostic systems

I'm having trouble building a machine which I can reliably clone onto another machine and have everything run correctly.

My make.conf has no CPUTYPE, CFLAGS, or COPTFLAGS. Does the default -O cause gcc to build hardware specific? Do I need NO_CPU_CFLAGS and NO_CPU_COPTFLAGS as well?

Typically, my kernel boots OK (I usually use GENERIC anyway); but some of the ports don't work. Notably clamd sometimes segfaults when I move it to another machine.

Thanks.
_______________________________________________
freebsd-isp@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isp
To unsubscribe, send any mail to "freebsd-isp-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: periodic, short freezes
    ... CPUTYPE, CFLAGS, COPTFLAGS? ... I remember seeing some strange effects ...
    (freebsd-questions)
  • Re: clock reverts to epoch on boot?
    ... possibilities to exploit aliasing optimizations. ... CFLAGS and -O2 for COPTFLAGS although I have read a lot of things ... the gcc optimizer was known to have bugs ...
    (freebsd-stable)
  • java / azureus core dumps if cputype is set in make.conf
    ... This time i added the CPUTYPE, ... CFLAGS and NOPROFILE variables to my /etc/make.conf so it would look ... I installed Azureus. ...
    (freebsd-questions)
  • Re: r219385 build error.
    ... i think core2 was always wrong to set in make.conf, because the base gcc simply ... value to set CPUTYPE / MACHINE_CPU, ... use CPUTYPE to set the cpu and CFLAGS for -O*, -pipe, etc. ... also please keep in mind that the optimisations that can be achieved by ...
    (freebsd-current)
  • Re: I need help with HALD...
    ... Do not set CFLAGS and COPTFLAGS unless you know what you're ... and even used to be the default values on FreeBSD ...
    (comp.unix.bsd.freebsd.misc)