Thread View: comp.unix.admin
9 messages
9 total messages
Started by Wade Williams
Fri, 04 May 2001 16:29
install rule not working
Author: Wade Williams
Date: Fri, 04 May 2001 16:29
Date: Fri, 04 May 2001 16:29
54 lines
2839 bytes
2839 bytes
I'm trying to build libpcap on Darwin. Everything goes fine, except
the install rule:
[localhost:libpcap/contrib/libpcap] root# make install
make: `install' is up to date.
Of course nothing is installed.
Here's the rule (the makefile was generated by configure):
# Top level hierarchy
prefix = /usr/local
exec_prefix = ${prefix}
# Pathname of directory to install the include files
includedir = ${prefix}/include
# Pathname of directory to install the library
libdir = ${exec_prefix}/lib
# Pathname of directory to install the man page
mandir = ${prefix}/man
install:
[ -d $(DESTDIR)$(libdir) ] || \
(mkdir -p $(DESTDIR)$(libdir); chmod 755
$(DESTDIR)$(libdir))
$(INSTALL_DATA) libpcap.a $(DESTDIR)$(libdir)/libpcap.a
$(RANLIB) $(DESTDIR)$(libdir)/libpcap.a
[ -d $(DESTDIR)$(includedir) ] || \
(mkdir -p $(DESTDIR)$(includedir); chmod 755
$(DESTDIR)$(includedir)
)
$(INSTALL_DATA) $(srcdir)/pcap.h $(DESTDIR)$(includedir)/pcap.h
$(INSTALL_DATA) $(srcdir)/pcap-namedb.h \
$(DESTDIR)$(includedir)/pcap-namedb.h
[ -d $(DESTDIR)$(includedir)/net ] || \
(mkdir -p $(DESTDIR)$(includedir)/net; chmod 755
$(DESTDIR)$(include
dir)/net)
$(INSTALL_DATA) $(srcdir)/bpf/net/bpf.h \
$(DESTDIR)$(includedir)/net/bpf.h
[ -d $(DESTDIR)$(mandir)/man3 ] || \
(mkdir -p $(DESTDIR)$(mandir)/man3; chmod 755
$(DESTDIR)$(mandir
)/man3)
$(INSTALL_DATA) $(srcdir)/pcap.3 \
$(DESTDIR)$(mandir)/man3/pcap.3
Any thoughts on why this might not be working?
Thanks,
Wade
Re: install rule not working
Author: Eli Zaretskii
Date: Fri, 04 May 2001 16:54
Date: Fri, 04 May 2001 16:54
12 lines
1384 bytes
1384 bytes
Wade Williams wrote: > > I'm trying to build libpcap on Darwin. Everything goes fine, except > the install rule: > > [localhost:libpcap/contrib/libpcap] root# make install > make: `install' is up to date. > > Of course nothing is installed. Is there by chance a file called `install' in that directory? If so, rename it and try again.
Re: install rule not working
Author: Wade Williams
Date: Fri, 04 May 2001 17:33
Date: Fri, 04 May 2001 17:33
14 lines
1584 bytes
1584 bytes
In article <3AF2DEBE.265CFB06@is.elta.co.il>, Eli Zaretskii <eliz@is.elta.co.il> wrote: > Is there by chance a file called `install' in that directory? If so, rename > it and try again. Yep, that was it. Unfortunately, it's a filesystem issue too. This OS X installation is installed on HFS+, which is case insenstive, so the INSTALL file was what was causing the conflict. Renaming it to INSTALL.txt solved the problem. Wade
Re: install rule not working
Author: Eli Zaretskii
Date: Sat, 05 May 2001 05:01
Date: Sat, 05 May 2001 05:01
19 lines
1648 bytes
1648 bytes
Wade Williams wrote: > > In article <3AF2DEBE.265CFB06@is.elta.co.il>, Eli Zaretskii > <eliz@is.elta.co.il> wrote: > > > Is there by chance a file called `install' in that directory? If so, rename > > it and try again. > > Yep, that was it. > > Unfortunately, it's a filesystem issue too. This OS X installation is > installed on HFS+, which is case insenstive, so the INSTALL file was > what was causing the conflict. Yes, a known problem with case-insensitive filesystems (DOS, Windows, etc.). > Renaming it to INSTALL.txt solved the problem. That is indeed a solution.
Re: install rule not working
Author: Paul D. Smith
Date: Sat, 05 May 2001 19:19
Date: Sat, 05 May 2001 19:19
34 lines
2421 bytes
2421 bytes
%% Eli Zaretskii <eliz@is.elta.co.il> writes:
ez> Wade Williams wrote:
>> Unfortunately, it's a filesystem issue too. This OS X installation is
>> installed on HFS+, which is case insenstive, so the INSTALL file was
>> what was causing the conflict.
ez> Yes, a known problem with case-insensitive filesystems (DOS,
ez> Windows, etc.).
You can add a .PHONY target, like this:
.PHONY: install
Now, if you use GNU make, that rule will be run whether or not a file
"install" exists. All autoconf-generated makefiles do this
automatically.
If you can't use GNU make, you can use a FORCE rule, like this:
install: FORCE
....
FORCE: ;
Of course, this fails to work if you have a file named "FORCE" (or
"force", I guess, on case-insensitive filesystems).
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith@gnu.org> Find some GNU make tips at:
http://www.gnu.org http://www.paulandlesley.org/gmake/
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
Re: install rule not working
Author: Eli Zaretskii
Date: Sun, 06 May 2001 14:33
Date: Sun, 06 May 2001 14:33
13 lines
1529 bytes
1529 bytes
"Paul D. Smith" wrote: > > If you can't use GNU make, you can use a FORCE rule, like this: > > install: FORCE > .... > > FORCE: ; > > Of course, this fails to work if you have a file named "FORCE" (or > "force", I guess, on case-insensitive filesystems). Both FORCE and force will interfere with this.
Re: install rule not working
Author: Nate Eldredge
Date: Sun, 06 May 2001 19:14
Date: Sun, 06 May 2001 19:14
22 lines
1787 bytes
1787 bytes
Eli Zaretskii <eliz@is.elta.co.il> writes: > "Paul D. Smith" wrote: > > > > If you can't use GNU make, you can use a FORCE rule, like this: > > > > install: FORCE > > .... > > > > FORCE: ; > > > > Of course, this fails to work if you have a file named "FORCE" (or > > "force", I guess, on case-insensitive filesystems). > > Both FORCE and force will interfere with this. You could use .PHONY to avoid that problem. -- Nate Eldredge neldredge@hmc.edu
Re: install rule not working
Author: Paul D. Smith
Date: Mon, 07 May 2001 05:06
Date: Mon, 07 May 2001 05:06
23 lines
2344 bytes
2344 bytes
%% Eli Zaretskii <eliz@is.elta.co.il> writes: >> Of course, this fails to work if you have a file named "FORCE" (or >> "force", I guess, on case-insensitive filesystems). ez> Both FORCE and force will interfere with this. Yes... I said that :). "force" is a much less common name for a file than "install", though. You could always name it something truly strange, it doesn't have to be FORCE; make it WDFRCNHKJSD or something. Or, if your filesystem has invalid filenames you could use one of those: about the only characters that aren't legel in make are ":", " ", and "=", so name your target FOO.BAR.BAZ and maybe it won't be recognized on DOS partitions. Or whatever. -- ------------------------------------------------------------------------------- Paul D. Smith <psmith@gnu.org> Find some GNU make tips at: http://www.gnu.org http://www.paulandlesley.org/gmake/ "Please remain calm...I may be mad, but I am a professional." --Mad Scientist
Re: install rule not working
Author: Paul D. Smith
Date: Mon, 07 May 2001 05:07
Date: Mon, 07 May 2001 05:07
29 lines
2366 bytes
2366 bytes
%% Nate Eldredge <neldredge@hmc.edu> writes: ne> Eli Zaretskii <eliz@is.elta.co.il> writes: >> "Paul D. Smith" wrote: >> > >> > If you can't use GNU make, you can use a FORCE rule, like this: >> > >> > install: FORCE >> > .... >> > >> > FORCE: ; >> > >> > Of course, this fails to work if you have a file named "FORCE" (or >> > "force", I guess, on case-insensitive filesystems). >> >> Both FORCE and force will interfere with this. ne> You could use .PHONY to avoid that problem. Yes, I mentioned that earlier in the thread. We were talking about what to do if you can't guarantee everyone will be using GNU make. -- ------------------------------------------------------------------------------- Paul D. Smith <psmith@gnu.org> Find some GNU make tips at: http://www.gnu.org http://www.paulandlesley.org/gmake/ "Please remain calm...I may be mad, but I am a professional." --Mad Scientist
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads