Sponsored Content
Top Forums UNIX for Advanced & Expert Users Enable 'make uninstall' hook? Post 302950863 by sea on Wednesday 29th of July 2015 01:23:14 PM
Old 07-29-2015
Enable 'make uninstall' hook?

Heyas

I'm currently trying to make 'make uninstall' work properly, as it doesnt remove empty directories.

To do so, i've applied:
Code:
uninstall-hook:
    if test -d $docdir; then rmdir $docdir; fi

As stated (example) in automake - 'make uninstall': Howto remove empty directories - Stack Overflow

Befor i had applied the above 2 lines, the installation went all fine.
After these changes were applied, i did run:
Code:
$ autoconf ; automake --add-missing 
$ ./configure && make && make check && su -c "make install"

Which then fails with:
Code:
Makefile:815: *** missing separator.  Stop.

And the changes seem applied in the project root dir its Makefile.in
Code:
$ tail -n6 Makefile.in | head -n2
uninstall-hook:
    if test -d $docdir; then rmdir $docdir; fi

Any ideas?
What am i missing?
What more info do you need?

Thank you in advance
 

8 More Discussions You Might Find Interesting

1. Linux

would like to hook up linux system to another computer!

I have desktop with both windows and fedora core 2 installed on it which I have also hooked up to my psion 5mx palm device that is stored in the windows drive... and i just access the files by mounting them onto my linux drive.. now I have a laptop too .. with the same directories as the linux... (7 Replies)
Discussion started by: moxxx68
7 Replies

2. Solaris

File System Hook

Background: DEDS is used to exchange files between Our Client and outside world. It is running on Sun v480 server OS 5.8. The files can come into or go out from various directories configured for various interfaces and come from both Our Client side as well as outside world. Requirement: ... (0 Replies)
Discussion started by: kdhana
0 Replies

3. Solaris

Perl - How to uninstall? Will pkgrm uninstall all versions?

Hello, I'm working on a Solaris 9/Sparc machine and it has the Solaris 10 version of Perl (5.8.8) installed on it, which always requires all kinds of library files that Solaris 9 doesn't come with. I think the best way to do is to uninstall this wrong version and install the correct Solaris 9... (1 Reply)
Discussion started by: alanlh
1 Replies

4. Linux

how to enable #ifdef macro in the command line of make?

Linux, C++, make, macro In source code, we used some #ifdef macros. How can I enable #ifdef macro in the command line of "make" (NOTE: I do NOT want to change source code or makefile to define that macro from time to time). e.g. test.cpp: ... #ifdef TEST1 // code segment for test1 ...... (3 Replies)
Discussion started by: princelinux
3 Replies

5. UNIX for Dummies Questions & Answers

The Gary Hook tutorial

Hi All, There has been talk about UNIX self-paced online tutorials written by Gary Hook, and that they are very good, specifically AIX. I am looking for the latest version of AIX, administration, tuning, networking, etc. (Like version 5 or 5L.) Basics to mid-range. I have searched all... (0 Replies)
Discussion started by: jeffpas
0 Replies

6. UNIX for Dummies Questions & Answers

The Gary Hook tutorial

Hi All, One more time (!). I have started a contract job and am looking for any online tutorials for AIX, 5 or 5L, just an overview to brush up on system administration, security, networking, etc. with the newer and Linux linked versions. Several people on the web have indicated in other... (1 Reply)
Discussion started by: jeffpas
1 Replies

7. Programming

How to hook file changes?

hello, Im trying to create some kind of a file change hook on unix machines (should be generic if possible). Do any of you know how can i write some code that will trigger whenever a file is being modified and then will approve the modifications, or throw an exception if the new content of... (2 Replies)
Discussion started by: ErezB
2 Replies

8. Shell Programming and Scripting

Get Home Directory for Users in Login Hook Script

I'm writing a script to use as a LoginHook for my Mac users. As part of this script, I need to write to a location in their home directory, but I can't seem to access the path - at this point in the login process, $HOME is empty and ~ gives the path to root's home. Unfortunately, I can't just do... (1 Reply)
Discussion started by: blondepianist
1 Replies
AUTOMAKE(1)						      General Commands Manual						       AUTOMAKE(1)

NAME
automake - automatically create Makefile.in's from Makefile.am's SYNOPSIS
automake [ -a | --add-missing ] [ --amdir=DIR ] [ --build-dir=DIR ] [ -c | --copy ] [ --cygnus ] [ -f | --force-missing ] [ --foreign ] [ --gnits ] [ --gnu ] [ --help ] [ -i | --ignore-deps ] [ --include-deps ] [ --no-force ] [ -o DIR ] [ --output-dir=DIR ] [ --srcdir-name=DIR ] [ -v | --verbose ] [ --version ] [ --Werror | --Wno-error ] DESCRIPTION
To create all the Makefile.ins for a package, run the automake program in the top level directory, with no arguments. automake will auto- matically find each appropriate Makefile.am (by scanning configure.in) and generate the corresponding Makefile.in. Note that automake has a rather simplistic view of what constitutes a package; it assumes that a package has only one configure.in, at the top. If your package has multiple configure.ins, then you must run automake in each directory holding a configure.in. You can optionally give automake an argument; .am is appended to the argument and the result is used as the name of the input file. This feature is generally only used to automatically rebuild an out-of-date Makefile.in. Note that automake must always be run from the topmost directory of a project, even if being used to regenerate the Makefile.in in some subdirectory. This is necessary because automake must scan configure.in, and because automake uses the knowledge that a Makefile.in is in a subdirectory to change its behavior in some cases. automake accepts the following options: -a --add-missing Automake requires certain common files to exist in certain situations; for instance config.guess is required if configure.in runs AC_CANONICAL_HOST. Automake is distributed with several of these files; this option will cause the missing ones to be automatically added to the package, whenever possible. In general if Automake tells you a file is missing, try using this option. By default Automake tries to make a symbolic link pointing to its own copy of the missing file; this can be changed with --copy. --libdir=DIR Look for Automake data files in directory DIR instead of in the installation directory. This is typically used for debugging. -c --copy When used with --add-missing, causes installed files to be copied. The default is to make a symbolic link. --cygnus Causes the generated Makefile.ins to follow Cygnus rules, instead of GNU or Gnits rules. -f --force-missing When used with --add-missing, causes standard files to be rebuilt even if they already exist in the source tree. This involves removing the file from the source tree before creating the new symlink (or, with --copy, copying the new file). --foreign Set the global strictness to foreign. --gnits Set the global strictness to gnits. --gnu Set the global strictness to gnu. This is the default strictness. --help Print a summary of the command line options and exit. -i --ignore-deps This disables the dependency tracking feature. --include-deps This enables the dependency tracking feature. This feature is enabled by default. This option is provided for historical reasons only and probably should not be used. --no-force Ordinarily automake creates all Makefile.ins mentioned in configure.in. This option causes it to only update those Makefile.ins which are out of date with respect to one of their dependents. -o DIR --output-dir=DIR Put the generated Makefile.in in the directory DIR. Ordinarily each Makefile.in is created in the directory of the corresponding Makefile.am. This option is used when making distributions. -v --verbose Cause Automake to print information about which files are being read or created. --version Print the version number of Automake and exit. --Werror --Wno-error --Werror will cause all warnings issued by automake to become errors. Errors affect the exit status of automake, while warnings do not. --Wno-error, the default, causes warning to be treated as warnings only. SEE ALSO
aclocal(1), and the Texinfo documentation for automake AUTHORS
Automake was written primarily by David Mackenzie and Tom Tromey. This manpage written by Ben Pfaff <pfaffben@pilot.msu.edu> for the Debian GNU/Linux automake package. 28 Jan 2002 AUTOMAKE(1)
All times are GMT -4. The time now is 07:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy