autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: transform problem with ac-2.52/am-1.5?


From: Akim Demaille
Subject: Re: transform problem with ac-2.52/am-1.5?
Date: 03 Jan 2002 12:28:55 +0100
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp)

>>>>> "Harlan" == Harlan Stenn <address@hidden> writes:

Harlan> Discussing a problem I"m seeing with the amanda-2 CVS code...
Harlan> Tom Tromey says:

Harlan> The Makefiles generated by autoconf-2.52/automake-1.5 have a
Harlan> "transform" definition that ends with a semicolon followed by
Harlan> a space, and the stock sed on FreeBSD-4 hates this (at least
Harlan> somewhere in the install target rule).

>> Automake gets the definition of transform from autoconf.  From
>> header-vars.am:

>> transform = @program_transform_name@

>> So I'm guessing this is a problem with autoconf.

Harlan> Ideas/solution?

I dunno: I don't see the whole problem.  The doc of Autoconf seems
clear:

|Transformation Rules
|--------------------
|
|   Here is how to use the variable `program_transform_name' in a
|`Makefile.in':
|
|     PROGRAMS = cp ls rm
|     transform = @program_transform_name@
|     install:
|             for p in $(PROGRAMS); do \
|               $(INSTALL_PROGRAM) $$p $(DESTDIR)$(bindir)/`echo $$p | \
|                                                   sed '$(transform)'`; \
|             done
|     
|     uninstall:
|             for p in $(PROGRAMS); do \
|               rm -f $(DESTDIR)$(bindir)/`echo $$p | sed '$(transform)'`; \
|             done
|
|   It is guaranteed that `program_transform_name' is never empty, and
|that there are no useless separators.  Therefore you may safely embed
|`program_transform_name' within a sed program using `;':
|
|     transform = @program_transform_name@
|     transform_exe = s/$(EXEEXT)$$//;$(transform);s/$$/$(EXEEXT)/
|
|   Whether to do the transformations on documentation files (Texinfo or
|`man') is a tricky question; there seems to be no perfect answer, due
|to the several reasons for name transforming.  Documentation is not
|usually particular to a specific architecture, and Texinfo files do not
|conflict with system documentation.  But they might conflict with
|earlier versions of the same files, and `man' pages sometimes do
|conflict with system documentation.  As a compromise, it is probably
|best to do name transformations on `man' pages but not on Texinfo
|manuals.

I something is not like in the doc, we have a bug.

How did you get this semi?

~/src/bison-1.29 % ./configure --program-transform-name=s/foo/bar/ >/dev/null
~/src/bison-1.29 % fgrep transf Makefile                         nostromo 12:27
transform = s/foo/bar/
~/src/bison-1.29 % fgrep transf Makefile | cat -A                nostromo 12:28
transform = s/foo/bar/$



reply via email to

[Prev in Thread] Current Thread [Next in Thread]