Hi!
> > I tried this for PAM:
> >
> > PAM_CONFIGURE_WITH+= pam
> > PAM_USE= PAM=yes
[...]
> You don't need += there -- just plain =
That '+' does not make a difference, I tried both versions.
> That should have resulted in configure being called with the argument
> --with-pam or --without-pam according to the option setting.
Olli Hauer wrote in private mail:
> some buggy configure scripts are setting an option to on if they
> get an --without-foo as argument but setting the build option to
> off by default.
> try with only an explizit opt_foo_on=--with-foo and without foo_off
> and look if this is working.
> i dont remember the ports but was running in this issue last year.
So it seems there are cases where this happens.
> >> - The port cannot be staged as a non-root user. This is due to the
> >> way the contrib Makefiles are written -- although elsewhere it
> >> uses standard autoconf stuff, which pretty much just works for
> >> staging purposes.
> >
> > I'm unsure what you mean with "the contrib Makefiles" ?
> >
> > You refer to the
> >
> > cd ${WRKSRC}/sql/${f} && ${GMAKE} \
> > STAGEDIR=${STAGEDIR} \
> > PREFIX=${PREFIX} \
> > ${INSTALL_TARGET}
> >
> > construct in target post-install ?
>
> Yes -- that's what I mean. If you try running 'make stage' as a
> non-root user, you'll see where it tries to run 'install -o root ...'
> (which doesn't work).
I'll dig further, but not this evening 8-}
--
p...@freebsd.org +49 171 3101372 6 years to go
!
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
