Date: Sat, 14 Jun 2014 00:24:39 +0200 From: Rolf Nielsen <rmg1970swe@gmail.com> To: Yuri <yuri@rawbw.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Build of FreeBSD-10 fails on 9 with unknown target CPU Message-ID: <539B7A27.9010106@gmail.com> In-Reply-To: <539B6570.5080209@rawbw.com> References: <539AC3A7.4040309@rawbw.com> <539B2041.7000202@gmail.com> <alpine.BSF.2.00.1406131118180.46469@wonkity.com> <539B4064.1010108@rawbw.com> <539B4B04.904@gmail.com> <539B6570.5080209@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-06-13 22:56, Yuri wrote: > On 06/13/2014 12:03, Rolf Nielsen wrote: >> As I stated in my previous reply, to Warren Block's question, I >> don't remember where I found it. However, on my 10.0-STABLE >> r265900 I found these lines in /usr/share/examples/etc/make.conf > > Ok, 10 source has corei7 in share/examples/etc/make.conf, so should > be no problem. > > My problem is probably because buildworld uses old /usr/share/mk/ > make files (from FreeBSD 9 in my case). I usually do > buildworld,installworld,buildkernel,installkernel,mergemaster > stages to update the system. However, these steps use the old > /usr/share/mk/ files, and this causes this error "unknown target > CPU 'amd64'" in buildworld. > > Is there any recommended way to solve this dependency on the old > makefiles during build of the newer version on the older system? > > Yuri _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions To > unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" Yes, I do understand. However, your problem still puzzles me, as the setting worked for me in 9-STABLE; the build system just replaced corei7 with something that gcc was able to use, and so it should on your system as well. You never answered my questions though: Do you set some variables on the commandline as well, that might confuse the compiler? And by llvm build, do you mean when building llvm or do you mean that you use llvm/clang to perform the build? Rolf -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBAgAGBQJTm3omAAoJEB1OKfQ0M8TgmlgP/jsXaXSZFj4WCJ/H6Xgoo1RY dTjn9lXWlF957MiEiTGvJYNLpQAlBAOd0mb72iJNNoxB9AIncr9+saWHci8xVcRF M/MBtIOo9EnvNw/YLwGrxDEz96MMB3+K206uugqGXPUtbRJ+f37sGUvNpcYWZuQQ ZKR775D7Xi2HCj4ocKkZe12SbUO1eRbVJh7L3qOHQORQkUzdwlz7LmTU3Yamaa0q hEB2mYmkVZ0b8jekIgBV7C1qoEiEYl2gR5B9RKlVRKgFGTSTL0Bntfk/O/j5/o+X R1qMbSZ7BDI81wf3KETciHND2WGxrkBW4o7SWDkKhDhPFg/ee4/ZyqJfl+YmWprp uBpIf7QBAdeAdxADJ5fuJPZNfjj7yYm+LuMn3Od+ccefYRtEkcWGTOX7wqm77y7n omR8Mb7rxiZSQ4iqZgjUaYwpCiqV52y6RL9DoRkUvb3mKSGCltYsxZHHjEjC6yGg Xv2l7ktj1mDRj54HlFcDLCLZocTVsUKOIbpl0nvKEbjOcMK36smle+XgyFUOYFex cPK1u9SLNYJEATHuYOY7MwJxSorHpZOoNxZ39yY46mjkhkXnInALqJrfkEHmKzyR WY2AFuK2ukWjcMKQGFCWgSktGq7D7pGIs7V+hFRCnBqogh2Yg5d2T/x0YB1pl5HP of7aUvqMpy3vkZdOPtrX =NXaA -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?539B7A27.9010106>