Re: [Pan-users] Build fail during configure FreeBSD 9.3

[Dave]

On Sunday 24 April 2016 00:55:01 Rhialto wrote:
> On Sat 23 Apr 2016 at 22:50:41 +0100, Dave wrote:
> > Ni, I didn't.  Do you know what value to set it/them to?
> > Do I need to set these in advance of running portinstall or make install 
> > clean
> > or do I set them as part of the command line, eg make -Dknob=foo install 
> > clean
> > 
> > It's possible you are assuming more knowledge than I actually have :-)
> 
> Possibly :)
> 
> > I suspect you are suggesting I do a manual compile/install outside of the
> > FreeBSD ports/pkg system which is something I've never done before.
> 
> That was indeed the direction I was thinking. You could give it a try,
> especially if you already have installed all the things it needs via
> ports/pkg.  It just might find them automatically. Apart from zlib then.
> (extract the tar file, run configure, then run make or gmake).
> 
> Otherwise, you have to "fight" with the extra level of indirection that
> the ports system creates. Personally I'm used to pkgsrc on NetBSD. That
> started out as a fork of FreeBSD's ports, but they have diverged quite a
> bit. So I can give some hints on what to try, but that's about it, I
> fear.
> 
> First, what value to use for those variables. You'd have to locate the
> zlib header file zlib.h. For me it is in /usr/include/zlib.h. Then I'd
> use
> 
>     ZLIB_CFLAGS=-I/usr/include
> 
> which would typically already be a default (so I guess for you it is
> either installed elsewhere, or the configure script just wants to see
> some value here so that it won't try to run pkg-config)
> 
> Similarly we need libz.so and (assuming it's in /usr/lib/libz.so)
> 
>     ZLIB_LIBS="-L/usr/lib -lz"
> 
> (yes the name of the library and the header file seem inconsistent...)
> 
> Now how to get those variables actually passed to the configure script.
> Here we need some improvisation. Check if other ports Makefiles have
> lines looking somewhat like the ones above; searching for -I and -L
> might be enough. It could be as simple as (for pkgsrc)
> 
>     CONFIGURE_ENV+=          MAKE_FLAGS=-j${MAKE_JOBS:Q}
> 
> which looks like it would pass some value for MAKE_FLAGS on to the
> configure stage. Once you identify how that works for ports (and there
> might even be documentation in the FreeBSD Handbook about it; I didn't
> check), simply adjust it it pass your ZLIB_CFLAGS=... and ZLIB_LIBS=...
> .  Put that in the Makefile of the port. Then run the usual "make
> install" for it.
> 
> > I seem to vaguely remember looking for info in the past when installing 
> > stuff
> > on FreeBSD and coming across lots of Linux based help taking about running
> > ./configure before make but that's something the ports system normal does in
> > FreeBSD so isn't something I'm familiar with. 
> 
> Yes, the usual "ritual" is running configure; make; make install,
> possibly with extra options and settings here and there for adjustments.
> Sometimes the software is straight from its master repository and it
> doesn't have a configure script generated. Then there is some step
> before it to create it (usually autogen.sh or autoreconf).
> 
Thanks for the comprehensive reply Olaf, I shall keep this one in my archive
for future reference, but as you may have seen by now from my other reply,
there was a rather simple and obvious workaround.  I really shouldn't start
these operations so late at night!

A lot of what you say above does actually look familiar.  I have probably read
up on and may even have done much of the above many years ago, back when I 
first started using FreeBSD (IIRC it was 4.3R, so about a decade or so ago)
when the ports system was often a bit behind the times and a lot less user 
friendly.  I don't think I ever went as far as having to manually locate header
files and set env variable to point to them though.  Fortunately, the ports and
binary pkg systems work so well it's rare to have to resort to manual fixes for
stuff these days.