Date: Thu, 27 Jul 2017 10:13:27 +0200 From: Willem Jan Withagen <wjw@digiware.nl> To: Adam Weinberger <adamw@adamw.org> Cc: mokhi <mokhi64@gmail.com>, ports@freebsd.org Subject: Re: Trying to get poudriere to start Message-ID: <a072862c-f46b-1171-2a7e-44a677c6370f@digiware.nl> In-Reply-To: <5E0BF59F-005D-4C92-997F-7EE405DC6850@adamw.org> References: <d96d08ae-02c4-2018-e306-e378e9914661@digiware.nl> <59791C56.4010600@quip.cz> <34782206-c4cf-c050-544b-7b5467b40a93@digiware.nl> <CAByVWPW7m6_hfCy-UMWC9OWHCRe_sLupAtcamz-Z_ewigoVwag@mail.gmail.com> <cd81d2a2-f53f-24b1-40fe-e4a163afd81f@digiware.nl> <5E0BF59F-005D-4C92-997F-7EE405DC6850@adamw.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Op 27-7-2017 om 02:20 schreef Adam Weinberger: >> On 26 Jul, 2017, at 17:23, Willem Jan Withagen <wjw@digiware.nl> wrote: >> >> Op 27-7-2017 om 01:15 schreef mokhi: >>> Hmm, >>> I don't know if it's same thing happened to me once. >>> But I **guess** you should kldload both of linux32 and linux64 and >>> also linprocfs modules >>> >> I did it the other way around. >> Hacked poudriere/..../common.sh >> And commented the kldoad for linux out... >> So I can atleast check this one port. > Setting NOLINUX=yes in poudriere.conf accomplishes the same thing. > I saw variable that in the code, but could not really find anything about it in the manpage. But your suggestion is of course a very logical. Still leaves the question what kldload is complaining about, and why. But I'll look into that once I've completed upgrading the port. --WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a072862c-f46b-1171-2a7e-44a677c6370f>