Date: Wed, 13 Sep 2017 09:09:42 -0600 From: Sean Bruno <sbruno@freebsd.org> To: John Baldwin <jhb@freebsd.org> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r323518 - head/sys/conf Message-ID: <af97fd40-d3ff-6917-e9db-51f1e401ff80@freebsd.org> In-Reply-To: <9497208.8lqLTVLir6@ralph.baldwin.cx> References: <201709130356.v8D3u4ve095428@repo.freebsd.org> <9497208.8lqLTVLir6@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Ds1fvJegLutcNiTU8WEWQ7OXvhJSpqf5b Content-Type: multipart/mixed; boundary="T63TJMWNOokQmlvXAtSxucm6Cn5TduO8M"; protected-headers="v1" From: Sean Bruno <sbruno@freebsd.org> To: John Baldwin <jhb@freebsd.org> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Message-ID: <af97fd40-d3ff-6917-e9db-51f1e401ff80@freebsd.org> Subject: Re: svn commit: r323518 - head/sys/conf References: <201709130356.v8D3u4ve095428@repo.freebsd.org> <9497208.8lqLTVLir6@ralph.baldwin.cx> In-Reply-To: <9497208.8lqLTVLir6@ralph.baldwin.cx> --T63TJMWNOokQmlvXAtSxucm6Cn5TduO8M Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 09/13/17 08:35, John Baldwin wrote: > On Wednesday, September 13, 2017 03:56:04 AM Sean Bruno wrote: >> Author: sbruno >> Date: Wed Sep 13 03:56:03 2017 >> New Revision: 323518 >> URL: https://svnweb.freebsd.org/changeset/base/323518 >> >> Log: >> Jenkins i386 LINT build uses NOTES to generate its LINT kernel confi= g. >> =20 >> ixl(4) isn't in here either, so I'll remove lio(4) too. >=20 > ixl missing is a bug, please put it in sys/amd64/conf/NOTES (or better = yet, > just fix the build on !amd64) >=20 In the case of lio(4), Cavium is explicitly not compiling for 32 bit architectures. I'm inquiring to find out if they want to build on the other 64bit architectures we have. In the case of ixl(4), Intel has said that this is not supported on 32bit architectures. I'm unsure what the best course of action is. sean --T63TJMWNOokQmlvXAtSxucm6Cn5TduO8M-- --Ds1fvJegLutcNiTU8WEWQ7OXvhJSpqf5b Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE6MTp+IA1BOHj9Lo0veT1/om1/LYFAlm5SjZfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEU4 QzRFOUY4ODAzNTA0RTFFM0Y0QkEzNEJERTRGNUZFODlCNUZDQjYACgkQveT1/om1 /LaOmwf8CS0iCKyRR2XEWZiyz4dS0//cWcHMlvAMEr1UNyuHTwniJmSV102znVi3 jCqkSgfYCXztoqGjQ83ZpxJhz8G+io69ZhBMwO82H4qJFoWi2pHun3dwlHo5jSkO omxbR6kxUOB5JKWs79S8PVfsA+Y6Qc3JXBUIBrfoEvOjecQdZpTAzDsBoFNLERtc 4cSqm+pIuz260ThJjXh2w6tInX1TqCxqg1/i5mXWmhTRDoXVeiDHK10zn8Hptz4J td1Mrn9Mc1L0viag+Hs8a/I2GkkvN2tM1DTezG0QOWqI9cU4wndL+llggsFdbmt/ ETNZk1B9N4sGiB/7qidTamWwXtYKcA== =P5/g -----END PGP SIGNATURE----- --Ds1fvJegLutcNiTU8WEWQ7OXvhJSpqf5b--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?af97fd40-d3ff-6917-e9db-51f1e401ff80>