Date: Wed, 8 Apr 2020 14:51:14 -0700 From: John Baldwin <jhb@FreeBSD.org> To: gljennjohn@gmail.com, current@freebsd.org Subject: Re: buildkernel failure because ctfconvert not installed Message-ID: <814e8e7d-68e6-bead-481b-21c5552583c4@FreeBSD.org> In-Reply-To: <20200408083204.4a2d6dbc@ernst.home> References: <20200408083204.4a2d6dbc@ernst.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/7/20 11:32 PM, Gary Jennejohn wrote:
> Has anyone else seen this error?
>
> I tried to build a kernel yesterday, but the build failed while compiling
> modules because ctfconvert was not found.
>
> I've had WITH_CTF=no in my src.conf for years, so neither ctfconvert nor
> ctfmerge were installed.
>
> OK, I'll just go to the source dirctories and build and install.
>
> Nope. I got this error:
> make: exec(ctfconvert) failed (No such file or directory)
> and the build failed.
>
> WTF? ctfconvert requires ctfconvert to build? That makes no sense and is
> a real chicken-and-egg problem if I've ever seen one.
>
> I ended up creating /usr/bin/ctf{convert,merge} shell scripts which simply
> did exit 0. That allowed me to finally compile and install the utilities.
>
> Now I'm forced to have WITH_CTF=yes in my src.conf. No big deal.
>
> Still, it seems like the change to the make infrastructure which assumed
> that cft{convert,merge} are always installed was rather premature.
The change is that GENERIC has 'makeoptions WITH_CTF=yes'. If you build a
kernel without that, you shouldn't need to have ctfconvert installed. This
does mean you need to use a custom kernel instead of GENERIC.
--
John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?814e8e7d-68e6-bead-481b-21c5552583c4>