From: Bart Veer <bartv@redhat.com>
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Re: Building eCos
Date: Fri, 03 Mar 2000 06:49:00 -0000 [thread overview]
Message-ID: <200003031449.OAA11291@sheesh.cygnus.co.uk> (raw)
In-Reply-To: <200003011701.JAA18830@cygnus.com>
>>>>> "Robert" == Robert Swindells <swindellsr@genrad.co.uk> writes:
Robert> Is anyone building eCos under UNIX ?
Robert> If so, is there any documentation that describes how to do
Robert> this.
Robert> If I try to use pkgconf.tcl to configure a build tree I
Robert> just get:
Robert> % gmake
Robert> makefile:9: pkgconf/pkgconf.mak: No such file or directory
Robert> gmake: *** No rule to make target `pkgconf/pkgconf.mak'. Stop.
Robert and I have now managed to track down the problem. The eCos
build system was assuming the GNU version of the install utility. On
some versions of Unix including FreeBSD there is a different version
of install, which by default deletes the original rather than just
copying it. During the first run the make system will install various
files from the build tree to the install tree, leaving the build tree
unusable for subsequent runs.
The following patch to pkgconf/makevars should sort out the problem,
and should still work with the GNU version of install (it accepts and
ignores the -c flag).
Bart Veer // eCos net maintainer
Index: makevars
===================================================================
RCS file: /cvs/ecc/ecc/pkgconf/makevars,v
retrieving revision 1.15
diff -u -5 -u -r1.15 makevars
--- makevars 2000/02/02 19:13:29 1.15
+++ makevars 2000/03/03 14:47:47
@@ -97,11 +97,11 @@
ifeq ($(OBJCOPY),)
OBJCOPY := $(PKGCONF_OBJCOPY)
#OBJCOPY :=
endif
ifeq ($(CP),)
-CP := install -m 0644
+CP := install -c -m 0644
#CP :=
endif
ifeq ($(RM),)
RM := rm -f
#RM :=
next prev parent reply other threads:[~2000-03-03 6:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200003011701.JAA18830@cygnus.com>
2000-03-01 9:27 ` [ECOS] " Bart Veer
2000-03-03 6:49 ` Bart Veer [this message]
2014-04-02 19:52 kalibar6
2014-04-03 18:02 ` [ECOS] " John Dallaway
2014-04-03 22:11 ` kalibar6
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=200003031449.OAA11291@sheesh.cygnus.co.uk \
--to=bartv@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.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).