Re: Building zsh/db/gdbm on MacOS Sequoia
Mikael Magnusson <[email protected]> Wed, 24 Jun 2026 23:29:49 +0200
| Newsgroups | gmane.comp.shells.zsh.devel |
|---|---|
| Message-ID | <CAHYJk3RTeg_Jbzwd6FAA+z8Tsu6yfVJVaqgcLnH00VMiTwKonQ@mail.gmail.com> |
On Wed, Jun 24, 2026 at 8:44 PM Bart Schaefer <[email protected]> wrote: > > On Wed, Jun 24, 2026 at 11:01 AM Bart Schaefer > <[email protected]> wrote: > > > > (Sorry about the rapid followups) > > One more ... > > The only obvious (?) way I've found to track this down would be something like > > port contents gdbm | \ > sed -n '/\/lib\//{s,lib/.*,lib,;s/^[ ]*/-L/;p;q;}' > > This works for any port-installed package, e.g., replace gdbm with > pcre2 or whatever. > > Is there a better way? The full configure.ac entry would need to test > for the availability of the "port" command, etc. If you have dependencies outside $prefix then I believe you are expected to supply this path manually, eg via % ./configure --help Some influential environment variables: LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a nonstandard directory <lib dir> CPPFLAGS (Objective) C/C++ preprocessor flags, e.g. -I<include dir> if you have headers in a nonstandard directory <include dir> -- Mikael Magnusson