From: Johan Rydberg <johan.rydberg@netinsight.se>
To: sid@sources.redhat.com
Subject: build error
Date: Wed, 03 Jan 2001 03:50:00 -0000 [thread overview]
Message-ID: <3A531293.45FFFB6@netinsight.se> (raw)
Hi!
I get the following error:
/bin/sh ../../libtool --mode=link c++ -g -O2 -o libbusif.la -rpath -module -no-undefined busif.lo -lm -lstdc++
libtool: link: only absolute run-paths are allowed
make[3]: *** [libbusif.la] Error 1
make[3]: Leaving directory `/.automount/nfs1/export2/home/johryd/prj/sid/src/sid/component/mapper/testsuite'
It seems that VPATH is unset:
libbusif_la_LDFLAGS = -rpath $(VPATH) -module -no-undefined
I run the following version of GNU make:
GNU Make version 3.78.1, by Richard Stallman and Roland McGrath.
It is configured to compile in the source directory! I also get an error
when trying to build the testsuite for the lcd component. Here's a small
patch that fixes that;
RCS file: /cvs/src/src/sid/component/lcd/testsuite/Makefile.am,v
retrieving revision 1.1
diff -u -r1.1 Makefile.am
--- Makefile.am 2000/12/07 19:30:53 1.1
+++ Makefile.am 2001/01/03 11:47:38
@@ -7,12 +7,12 @@
INCLUDES = -I. -I../../../include -I$(srcdir)/../../../include -I$(srcdir)/..
all-local:
- cp $(srcdir)/hd-one-line.conf .
- cp $(srcdir)/hd-two-line.conf .
- cp $(srcdir)/hd-5X10.conf .
- cp $(srcdir)/hd-europe.conf .
- cp $(srcdir)/t6963c-tcl.conf .
- cp $(srcdir)/t6963c-japan.conf .
+ test -e ./hd-one-line.conf || cp $(srcdir)/hd-one-line.conf .
+ test -e ./hd-two-line.conf || cp $(srcdir)/hd-two-line.conf .
+ test -e ./hd-5X10.conf || cp $(srcdir)/hd-5X10.conf .
+ test -e ./hd-europe.conf || cp $(srcdir)/hd-europe.conf .
+ test -e ./t6963c-tcl.conf || cp $(srcdir)/t6963c-tcl.conf .
+ test -e ./t6963c-japan.conf || cp $(srcdir)/t6963c-japan.conf .
libt6963c_test_la_SOURCES = t6963c-tester.cxx
libt6963c_test_la_LDFLAGS = -rpath $(VPATH) -module -no-undefined
next reply other threads:[~2001-01-03 3:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 3:50 Johan Rydberg [this message]
2001-01-03 4:36 ` Frank Ch. Eigler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A531293.45FFFB6@netinsight.se \
--to=johan.rydberg@netinsight.se \
--cc=sid@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).