This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
RE: cross toolchain vs. info files
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: "'Dave Korn'" <dave dot korn at artimi dot com>, "'Nick Clifton'" <nickc at redhat dot com>
- Cc: <binutils at sourceware dot org>
- Date: Tue, 10 Jan 2006 16:45:43 -0000
- Subject: RE: cross toolchain vs. info files
Dave Korn wrote:
> Would overriding install-info-am in Makefile.am be the proper approach?
Well, it looks roughly right to me now I've worked around my autotools
problems, but I couldn't judge whether this should be done by overriding
install-auto-am in the (several) local Makefile.am sources, or whether it
would best be done with a patch to the automake texinfos.am; if so, I presume
I'd have to make it conditional in some fashion so that it retains unchanged
backward-compatible behaviour in the default case.
> I was trying this patch,
and it has at least one cut'n'paste error:
> --- Makefile.am 20 May 2004 16:24:27 -0000 1.1
> +++ Makefile.am 10 Jan 2006 10:39:34 -0000
> + if test -f $$d/$$ifile; then \
> + inst=`echo $$ifile | sed '$(transform)'`.$$ext; \
> + echo " $(INSTALL_DATA)$$d/$$ifile
$(DESTDIR)$(man1dir)/$$inst";
> \ + $(INSTALL_DATA) $$file $(DESTDIR)$(man1dir)/$$inst; \
> + else : ; fi; \
LOL :) Not quite sure how I managed to get that there, but I'm fairly sure I
don't want to install my info files into the manpage dir! Will try the
obvious fix now.
cheers,
DaveK
--
Can't think of a witty .sigline today....