Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Jan 2018 05:00:22 -0800
From:      David Wolfskill <david@catwhisker.org>
To:        Jason Harmening <jason.harmening@gmail.com>
Cc:        "O. Hartmann" <ohartmann@walstatt.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   Re: svn commit: r328489 - head/sys/conf
Message-ID:  <20180129130022.GT1125@albert.catwhisker.org>
In-Reply-To: <98501f75-1a1b-9221-c52d-24415230a886@gmail.com>
References:  <201801272013.w0RKDaMU098200@repo.freebsd.org> <20180127214755.3c59661e@thor.intern.walstatt.dynvpn.de> <98501f75-1a1b-9221-c52d-24415230a886@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--bAwSoJxbKYwy34Oe
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 29, 2018 at 02:10:04AM -0800, Jason Harmening wrote:
> >=20
> > This happens now if PORTS_MODULE=3Dx11/nvidia-driver is defined in /etc=
/src.conf:
> >=20
> > [...]
> > --- kernel-install ---
> > mkdir -p /boot/kernel
> > install -p -m 555 -o root -g wheel kernel /boot/kernel/
> > --- ports-install ---
> > Variable OBJTOP is recursive.
> >=20
> > make[8]: stopped
> ...
>=20
> David sent me logs of the failing case; thanks David!

Happy to help! :-)

> The failure happens when buildkernel and installkernel are run=20
> separately instead of all-up, e.g. 'make kernel'.  The installkernel=20
> step is leaving MK_AUTO_OBJ=3Dno in the env passed to the port build.  It=
=20
> looks like at least one of the install stages of nvidia-driver needs to=
=20
> generate temporary output, which leads to confusion when the port isn't=
=20
> built as though it's an in-tree component.
>=20
> Can you guys try out the attached patch?

I tried it both on my build machine (which does not use kernel modules
=66rom ports, and thus did not exhibit the problem -- but I thought that
verifying that the patch did not break that case worth checking) and on
my laptop (which did exhibit the problem).

It worked in both cases with no issues for me.

Thanks! :-)

Peace,
david
--=20
David H. Wolfskill				david@catwhisker.org
"unfortunately, no trust!=E2=80=9D -- well, of course!  You reap what you s=
ow.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.

--bAwSoJxbKYwy34Oe
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlpvGuZfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND
QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ
7heZ7QgAsyi5myq2vhU7CZ6c1BrTeyOUMXXvtiiS/CIWoTxwrGVLHDFDCVxn0O9s
CfTPxETnyV4kdM6r0mZeGMMMvQTcEPb2iJx1n1lsYshaJ6FrEeobGKdyCAvOVS6r
TRUuRsFM6SNoY5BdOOwolmQzVbWCi1TrFRWEwsA1inkY8ndhqM4u9iZDZqmeQoql
jNPYx4dEvR1lNXOnJ8CzS7QlNe4JE5rvSvJGmHW4KTotRBcYTwLj10UwQhVLAnxe
R9Ez6qfCGlJEHlRywA2bF5MAVi8GhncH4r+o6J4h8gf3SqdZvxOHMAZV8YZkPNzM
ewSiZi5qHBRUy+CJpQYf1zzJ8deGPg==
=9LA2
-----END PGP SIGNATURE-----

--bAwSoJxbKYwy34Oe--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180129130022.GT1125>