, as should any makefile rule
which is about to run "configure" but detects that the script is newer
than the cache file.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
Only configure does.
Hmm good point. I guess that means it's ever more important that
the right kinds of "version" information be included in the config.cache
file and that configure scripts be always careful to check for the
appropriate compatability of such cache information before trusting it.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
ased RE parser I've ever seen have always
supported the '?' meta-char, the REs handled by 'ed' and 'sed' have
often been limited subsets. On V7 '?' works in grep but not ed or sed.
However what's the context for this question?
--
w works
with the OpenBSD M4). I can readily accept that there are inferior
implementations of M4 but I cannot accept that something unique called
"GNUM4", and that goes double if what makes it unique is undocumented
magic.
--
Greg A. W
3.3 so perhaps even the
odd-ball cases will work faster with it.
(what's interesting in my timings is the excessive system time that nawk
always seems to take! ;-)
Now I do have to ask what the purpose of that awk script could possibly
be, and why it has to do things the way it seems to want to do them?
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
'm guessing that nawk and gawk may do this test automatically as an
optimisation internally
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
- just the blanks and blank lines
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
programmers dealing with security sensitive tools of
course, but even software development tools can cause harm too!
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
utoconf. As a
result I think it's not sensible to even try to have autoconf (or
automake) handle filenames with embedded ':' characters, or even
extension separators other than '.'.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
* written even a line of
code that uses "curses", whereas that library is a major central part of
the BSD "philosophy"! ;-)
So, in the end I'd have to say that being BSD is simply the state of
being 100% free of all original Unix code!
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
irst close brace ends the variable substitution.
! test -z "$INSTALL_PROGRAM" && INSTALL_PROGRAM='${INSTALL} -c'
AC_SUBST(INSTALL_PROGRAM)dnl
! test -z "$INSTALL_SCRIPT" && INSTALL_SCRIPT='${INSTALL} -c'
AC_SUBST(INSTALL_SCRIPT)dnl
! test -z "$INSTALL_DATA" && INSTALL_DATA='${INSTALL} -c -m 644'
AC_SUBST(INSTALL_DATA)dnl
])# AC_PROG_INSTALL
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
[ On Tuesday, June 6, 2000 at 18:09:13 (+0200), Peter Eisentraut wrote: ]
> Subject: Re: proposed change to setting of INSTALL (and friends)
>
> Greg A. Woods writes:
>
> > It turns out that some versions of *BSD "install" (aka xinstall.c in the
> > 4.4bsd
ent portable?
>
> no
Where is it not?
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
by ATT
USG sometime around SysVr2 or so (it's not in SysIII). V7's sh, and
thus all those based directly on it (including close mimics like perhaps
even minix), don't allow the option. (As I would have known if I'd
looked at my V7 source! ;-)
--
g!
BTW, the only reason lots of recent code can't compile in K&R mode is
because its authors are either lazy, or ignorant (of C's heritage), or
both! ;-)
C != C++
--
Greg A. Woods
+1 416 218-0098 VE3TCP &
amp;R source base would involve tons of extra work for the
> maintainers rewriting all that code.
That's a good point! The code I'm concerned about won't suffer that
problem for some time yet though
--
Greg A. Woods
ever by default on NetBSD or FreeBSD.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
[ On , August 24, 2000 at 23:33:32 (-0400), Paul D. Smith wrote: ]
> Subject: Re: HTML format documentation
>
> %% [EMAIL PROTECTED] (Greg A. Woods) writes:
>
> >> Moving man to .../share (${datadir}) on some systems was painful
> >> enough, and there was a ver
to actually build a system without a separate /usr
hierarchy, where I'd want "--prefix=/", it still doesn't really make
sense to me that one would include $(prefix) as a part of $(sysconfdir).
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
nstallation of multiple versions)
then you need only install the new version without de-installing the old
one and then do a three-way diff on any config file in order to update
the live config file with new stuff. This can even be automated by the
"enable" procedure (in its guise as a
onfigure with --sysconfdir=/etc as well?
Yes of course you can -- it's just that the default is wrong given the
naming conventions. Consider $(sharedstatedir) and $(localstatedir).
--
Greg A. Woods
+1 416 218-0098 VE3TCP &l
quot;
I would have to say that this seems like the most error prone possible
way of doing such sharing!
In any case if "sysconfdir" means what it says, i.e. "system
configuration directory", then it must default to /etc (i.e. without
$(prefix) prepended) on any unix or unix-like
[ On , August 27, 2000 at 01:26:36 (-0300), Alexandre Oliva wrote: ]
> Subject: Re: HTML format documentation
>
> On Aug 26, 2000, [EMAIL PROTECTED] (Greg A. Woods) wrote:
>
> > In any case if "sysconfdir" means what it says, i.e. "system
> > configuration
er the assumption that the native configuration
files being referred to had been supplanted by other add-on packages.
However this case is undoubtably better handled by explicit
--with-file=path settings since one cannot guarantee that all such files
have been relocated to the same place.
--
(and start/stop scripts, etc.)
Whatever the variable is called it should only be used to refer to the
location where live configuration files will be found when the package
program(s) is(are) run.
--
Greg A. Woods
+1 416 218-0098 VE3T
for the Coding Standards to offer these as good
ways to solve the resulting dilema faced by those who want to just
install a package hand have it work by default.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
uld someone like to do that?
Are all of the relevant developers subscribed to the list, or
would it be necessary to post to a more public forum? How would one
best measure the responses?
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[E
no /usr.
Indeed in that case there are no "exceptions", but in that case there's
no need for autoconf either! ;-)
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
directory (at least not unless prefix==/).
I.e. the name is still wrong then.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
e able to cope with
mixing add-on packages with system stuff -- eg. I may avoid /local if
I've got a fine-grained packaging system that can clearly identify all
native and foreign files, and especially if I normally provide wrappers
ala "ports"/"pkgsrc" for autoc
to match)
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
ion of config files and their base names
such that $(confdir) [or whatever] can be used to identify their
location at runtime, but $(DESTDIR)/$(examples) might be where they are
installed.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
autoconf in the first place!
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
e end what this boils down to is that it is currently hard to
prevent this practice, but it should definitely be discourage in
documentation and usage guides.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
t run-time. It
would be one thing to simply ignore the difference and always assume
that files are always installed directly into their run-time locations,
but $(exec_prefix) adds to the confusion because it takes the baby step
of going part way to making a distinction but it does so only for a
single class of files.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
ing the intent of variables that specify
installation locations and run-time locations is far more productive
than their current overloaded state.
> There was some discussion of this on the list a while back.
hmmm
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
first explaining the
entire *BSD build system
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
nk it statically
-- i.e. the build has to know from the beginning that you're intending
to use the result at run-time from single-user mode.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Plani
anent headaches for everyone.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
___
say unfortunately sometimes taken from
the environment) have the nature of being variables in the sense that
they may contain many command-line settings and they're usually used in
command invocations via variable expansion features (be they of the
shell, or Make, or whatever).
--
nd on
some broken mailing list manager corrupting subject headers.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets o
ink
4.2BSD had it, but it's in 4.3BSD for sure. AT&T PD'd the code for one
of their versions in 1985.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secre
r3.2, or even my SunOS-4 systems, for the last few years to see if
my programs still build and work on them. Such portability is truly
just an academic excercise in this day and age, especially when any VAX
capable of running fast enough to even be usable any more is capable of
running a modern OS. Perhaps
ll into that category.
This would be good.
> example, I see software that uses ANSI C function prototypes but tests for
> varargs.h vs. stdarg.h and chooses the right variadic argument syntax
> accordingly. Are there really ANSI C compilers that don't have stdarg.h?
> gcc appears to supply its own.
Not likely any modern ones, but there were some early adopters who
didn't shoot for full compliance (I'm not sure any were on Unix
though).
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
.bell-labs.com/cm/cs/who/bwk/awk.tar.gz
There's a note in the FIXES file from the nawk source distribution
stating that a function call memory leak was fixed on April 21, 2000. I
don't know if that'll fix the bug referred to in this thread, or not.
--
y hard to do. Perhaps if
Autoconf offered some way to build intermediate configurations that
still allowed some further configuration to be done at a later time then
things would be a bit simpler to manage.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
that only subscribers may post freely to
them. If the list managers should wish to sort through unsolicited
postings by non-subscribers and forward on only the non-spam then they'd
obviosly be welcome to do the job!
--
Greg A. Woods
+
mate poster will then help
fight against spam. Truly legitimate posters will always be able to
find a way to successfully post from a secure mail server.
The only valid argument in this discussion is over which blocking lists
can be trusted and which should be avoided.
--
web-based forums suck compared to mailing lists. I
> wish more SourceForge groups would use mailing lists instead of forums;
> the forums are annoying in the extreme.
Hmmm indeed.
--
Greg A. Woods
+1 416 218-0098 VE3TCP
to take
responsibility for the message (and thus avoid having to trust a forged
sender address) and yet at the same time return a hopefully useful
message to the sender indicating the reason for the refusal and perhaps
providing pointers to how the block can be cleared.
--
use I'm not a subscriber than
to even see all the spam in the archives!)
--
Greg A. Woods
+1 416 218-0098; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; VE3TCP; Secrets of the Weird <[EMAIL PROTECTED]>
51 matches
Mail list logo
