Hi Bob, Russ,
* Russ Allbery wrote on Sun, Apr 30, 2006 at 05:34:53AM CEST:
Bob Rossi [EMAIL PROTECTED] writes:
noinst_bin_PROGRAMS = gdbmi_driver
noinst_bindir = $(top_builddir)/progs
Try using $(abs_top_builddir) instead. I've always had bad luck with
relative paths and anything
On Sat, Apr 29, 2006 at 08:34:53PM -0700, Russ Allbery wrote:
Bob Rossi [EMAIL PROTECTED] writes:
I have
noinst_bin_PROGRAMS = gdbmi_driver
noinst_bindir = $(top_builddir)/progs
Try using $(abs_top_builddir) instead. I've always had bad luck with
relative paths and anything that
On 2006-04-30, Bob Rossi [EMAIL PROTECTED] wrote:
Unfortunatly, that doesn't work either.
test -z /progs || mkdir -p -- /progs
mkdir: cannot create directory `/progs': Permission denied
abs_top_builddir isn't set in the Makefile (with automake 1.8.5, and I
can't see a ChangeLog entry in 1.9.6
On Sun, Apr 30, 2006 at 12:05:57PM +, Olly Betts wrote:
On 2006-04-30, Bob Rossi [EMAIL PROTECTED] wrote:
Unfortunatly, that doesn't work either.
test -z /progs || mkdir -p -- /progs
mkdir: cannot create directory `/progs': Permission denied
abs_top_builddir isn't set in the
On Sun, Apr 30, 2006 at 08:18:34AM -0400, Bob Rossi wrote:
Is there any difference between using abs_top_builddir vs top_builddir?
The former has an absolute path, while the latter may not (in fact for
builddir I think it never will; for srcdir, the non-abs_ versions may
also in fact be
Bob Rossi [EMAIL PROTECTED] writes:
noinst_bin_PROGRAMS = gdbmi_driver
noinst_bindir = $(abs_top_builddir)/progs
Unfortunatly, that doesn't work either.
test -z /progs || mkdir -p -- /progs
mkdir: cannot create directory `/progs': Permission denied
Well, that makes it look like
Bob Rossi [EMAIL PROTECTED] writes:
I have
noinst_bin_PROGRAMS = gdbmi_driver
noinst_bindir = $(top_builddir)/progs
Try using $(abs_top_builddir) instead. I've always had bad luck with
relative paths and anything that involves libtool.
--
Russ Allbery ([EMAIL PROTECTED])
