[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
re: port-alpha/55545: /usr/src/build.sh script only known alpha/alpha, but my machnine is EV56
The following reply was made to PR port-alpha/55545; it has been noted by GNATS.
From: matthew green <mrg%eterna.com.au@localhost>
To: Jason Thorpe <thorpej%me.com@localhost>
Cc: port-alpha-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
netbsd-bugs%netbsd.org@localhost, michael%telkp.bme.hu@localhost, gnats-bugs%netbsd.org@localhost
Subject: re: port-alpha/55545: /usr/src/build.sh script only known alpha/alpha, but my machnine is EV56
Date: Sun, 09 Aug 2020 19:30:03 +1000
Jason Thorpe writes:
> > On Aug 8, 2020, at 4:15 PM, David Holland <dholland-bugs%netbsd.org@localhost>
> >> How can i compile src for ev56 cpu?
> > Is it not an alpha? Does the -m alpha -a alpha build not work?
> I think what's being suggested is that it would be nice to say "I want
> code optimized for this specific Alpha". In general, we do not provide
> that w/ build.sh, but it could be done with mk.conf variables to set
> COPTS accordingly.
i think CPUFLAGS is the thing we want for _end users_ to compile
with their specific cpus flags.
netbsd build only sets CPUFLAGS when it's building a cpu specific
thing for code expecting that (eg, "-marm" for a bunch of the
arm boot programs.)
you should be able to set CPUFLAGS in mk.conf _or_ build.sh -V.
Main Index |
Thread Index |