Re: BSD make and dependencies

2000-12-26 Thread Assar Westerlund

Tom Tromey <[EMAIL PROTECTED]> writes:
> Derek> Apparently BSD wants something like the following:
> Derek> .include "file"
> Derek> or
> Derek> .include 
> 
> Yuck.  Does make have -I options too?

Yes.  From make(1):

 -I directory
 Specify a directory in which to search for makefiles and included
 makefiles.  The system makefile directory (or directories, see
 the -m option) is automatically included as part of this list.

/assar




Re: BSD make and dependencies

2000-12-26 Thread Derek R. Price

Tom Tromey wrote:Derek> Apparently BSD wants something like the following:

> Derek> .include "file"
> Derek> or
> Derek> .include 
>
> Yuck.  Does make have -I options too?

Don't know.  I didn't actually have a BSD box until last week and I haven't
touched it over the last few days.  I'll ask the guy who reported this to me
in the first place too.  I'll let you know what I discover.

Derek

--
Derek Price  CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
The Christmas Pageant does not stink.
The Christmas Pageant does not stink.
The Christmas Pageant does not stink...

  - Bart Simpson on chalkboard, _The Simpsons_







Re: distributing files generated by configure

2000-12-26 Thread Derek R. Price

"Derek R. Price" wrote:

> Raja R Harinath wrote:
>
> > BTW, why do you need to 'configure' or 'sed' substitute a version
> > number into a .c file -- you already have config.h which defines the
> > symbol 'VERSION' to the version number string.
>
> That's a good point.  They're there because I just converted this source to use
> Automake and I hadn't considered that yet.  version.c is the name of the file where
> the information was kept before Automake.

Although a quick glance at what it would take to switch over reveals that I would have
to hook into the application's init functions or rewrite some code to change over
since the VERSION is being sed'd dirtectly into a global string.  I don't want to
worry about that yet.

Derek

--
Derek Price  CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
I am not a 32 year old woman.
I am not a 32 year old woman.
I am not a 32 year old woman...

  - Bart Simpson on chalkboard, _The Simpsons_







Re: distributing files generated by configure

2000-12-26 Thread Derek R. Price

Raja R Harinath wrote:

> BTW, why do you need to 'configure' or 'sed' substitute a version
> number into a .c file -- you already have config.h which defines the
> symbol 'VERSION' to the version number string.

That's a good point.  They're there because I just converted this source to use
Automake and I hadn't considered that yet.  version.c is the name of the file where
the information was kept before Automake.

Derek

--
Derek Price  CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
I will not torment the emotionally frail.
I will not torment the emotionally frail.
I will not torment the emotionally frail...

  - Bart Simpson on chalkboard, _The Simpsons_







Re: [Fwd: --add-missing]

2000-12-26 Thread Derek R. Price

Tom Tromey wrote:

> I wouldn't be averse to adding a `pdf' target so that `make pdf' works
> as expected.  Someone else would have to write it though since I don't
> know how.

It should be the exact target used for DVI except for the addition of a
'--pdf' switch to the texi2dvi command line.  I'm using the following,
stripped directly from my Automake generated Makefile.in's DVI targets,
but I didn't research enough to know if any of the constituent elements
(TEXINPUTS, MAKEINFO, makeinfo includes) vary with Makefile.am
parameters:

SUFFIXES = .aux .txt .pdf
# texinfo based targets automake neglects to include
.texinfo.pdf:
TEXINPUTS=$(srcdir):$$TEXINPUTS \
  MAKEINFO='$(MAKEINFO) -I $(srcdir)' $(TEXI2DVI) --pdf $<
.txi.pdf:
TEXINPUTS=$(srcdir):$$TEXINPUTS \
  MAKEINFO='$(MAKEINFO) -I $(srcdir)' $(TEXI2DVI) --pdf $<
.texi.pdf:
TEXINPUTS=$(srcdir):$$TEXINPUTS \
  MAKEINFO='$(MAKEINFO) -I $(srcdir)' $(TEXI2DVI) --pdf $<

By the way, there may not be much demand for it any longer, but we have
legacy targets to generate ASCII versions of our manuals as well.  I'm
told they ocassionally came in handy for mailing:

.texinfo.txt:
TEXINPUTS=$(srcdir):$$TEXINPUTS \
  MAKEINFO='$(MAKEINFO) -I $(srcdir)' $(MAKEINFO) $< --no-headers
-o $@
.txi.txt:
TEXINPUTS=$(srcdir):$$TEXINPUTS \
  MAKEINFO='$(MAKEINFO) -I $(srcdir)' $(MAKEINFO) $< --no-headers
-o $@
.texi.txt:
TEXINPUTS=$(srcdir):$$TEXINPUTS \
  MAKEINFO='$(MAKEINFO) -I $(srcdir)' $(MAKEINFO) $< --no-headers
-o $@

Derek

--
Derek Price  CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
This is the fourth?
- Thomas Jefferson's last words
(he died on the 4th of July)







Snowhite and the Seven Dwarfs - The REAL story!

2000-12-26 Thread Hahaha

Today, Snowhite was turning 18. The 7 Dwarfs always where very educated and
polite with Snowhite. When they go out work at mornign, they promissed a 
*huge* surprise. Snowhite was anxious. Suddlently, the door open, and the Seven
Dwarfs enter...


 sexy virgin.scr