ltmain.sh not found
andrnils at gmail.com
Thu Apr 25 13:25:45 UTC 2019
it does have a good man page, as well as a chapter in the official
I assume you build your ports because you have non-standard options,
otherwise I'd recommend going with the prebuilt packages, the handling of
prebuilt packages has become much more solid now.
On Thu, Apr 25, 2019 at 3:14 PM Willem Offermans <Willem at offermans.rompen.nl>
> Dear FreeBSD friends,
> No, I have not yet considered using poudriere.
> I’m using portmaster for years now and I was too lazy to look for a
> better/another tool.
> When I have time, I will dig into poudriere. I assume there is
> documentation/tutorial around that will get me going.
> The man pages will also be helpful.
> Thank you for your suggestion.
> Wiel Offermans
> Willem at Offermans.Rompen.nl
> On 25 Apr 2019, at 14:58, Andreas Nilsson <andrnils at gmail.com> wrote:
> On Thu, Apr 25, 2019 at 2:28 AM Kevin Oberman <rkoberman at gmail.com> wrote:
>> On Wed, Apr 24, 2019 at 9:05 AM Christoph Moench-Tegeder <
>> cmt at burggraben.net>
>> > ## Willem Offermans (Willem at Offermans.Rompen.nl):
>> > > Unfortunately it is probably not gawk in my case, which causes
>> > > However, your response indicates that the problem will be solved
>> after I
>> > > have updated/reinstalled the guilty one.
>> > There's sysutils/bsdadminscripts, which provides pkg_libchk: that's a
>> > tool for checking if any port misses a shared library. It has been
>> > rather helpful back when I was using portupgrade...
>> > Regards,
>> > Christoph
>> I believe bsdadminscripts has been withdrawn. You should use "pkg check
>> to check.
>> Kevin Oberman, Part time kid herder and retired Network Engineer
>> E-mail: rkoberman at gmail.com
>> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
> Have you considered using poudriere to build your packages? It usually
> avoids these types of failures.
> Best regards
More information about the freebsd-stable