Re: PACKAGE_NAME, PACKAGE_VERSION etc

--[Bruce Korb]--[EMAIL PROTECTED] Bob Friesenhahn wrote: On Wed, 18 Feb 2004, Daniel Reed wrote: On 2004-02-18T00:31-, Balint Joo wrote: ) /* Name of package */ ) #define PACKAGE qdp ... ) The trouble is that when we configure two packages, ... If at all possible,

Re: support for --localedir

--[Bruno Haible]--[EMAIL PROTECTED] * lib/autoconf/general.m4: Add new configure option --localedir. * doc/autoconf.texi (Installation Directory Variables): Document localedir. The question is: why not create an autoconf macro to define arbitrary installation directories?

Re: [autoconf] Autoconf on new platforms

--[Paul Eggert]--[EMAIL PROTECTED] Dan Kalowsky [EMAIL PROTECTED] writes: - there is no native shell environment yet, so everything needs to use cross build tools. Besides setting the CC flag, is there some way to automate this? Setting CC etc. is the usual way. Am I missing

Re: proposal to fork the build-tools projects

--[Tom Lord]--[EMAIL PROTECTED] It could be that we should tell people to use Bash to build GNU packages if their native shells have trouble handling the job. That would be a smaller change and perhaps worth doing. How is `bash' built? You need to be able

Re: [autoconf] AmigaOS fork()

--[Akim Demaille]--[EMAIL PROTECTED] Paul, this patch was sent later, and you did not comment it. Does silence means it is refused? Come on, whoever has some authority on this subject, say something, you aren't Dave Zaroski, are you? 2001-06-19 Rüdiger Kuhlmann [EMAIL PROTECTED

Re: [autoconf] doc dirs?

Hi! --[Russ Allbery]--[EMAIL PROTECTED] Rüdiger Kuhlmann [EMAIL PROTECTED] writes: I'd like to re-kindle the discussion about options for where to put a programs documentation by suggesting the following patch: Wouldn't some sort of general facility for adding a new *dir switch

Re: [autoconf] AmigaOS fork()

--[Eric Siegerman]--[EMAIL PROTECTED] On Mon, Jun 18, 2001 at 03:29:17PM +0200, Rüdiger Kuhlmann wrote: [fork + vfork + ac_fork + ac_vfork] I guess you know _I_ agree, but the others don't seem so. Suits me just fine. Okay, people, what do you think about

doc dirs?

Hi! I'd like to re-kindle the discussion about options for where to put a programs documentation by suggesting the following patch: 2001-06-19 Rüdiger Kuhlmann [EMAIL PROTECTED] * acgeneral.m4: (_AC_INIT_PARSE_ARGS) Add switches for install dirs of documentation in html, ps

Re: [autoconf] AmigaOS fork()

2001-06-15 Rüdiger Kuhlmann [EMAIL PROTECTED] * acfunctions.m4: (AC_FUNC_VFORK) renamed to _AC_FUNC_VFORK. Remove AC_DEFINEs and don't guess cross-compilation values. (_AC_FUNC_FORK) New, check whether fork() isn't just a stub. (AC_FUNC_FORK) New, use

Re: [autoconf] AmigaOS fork()

Hi! Since the discussion stopped, can we agree on the following patch? Feel free to add more documentation on fork() vs vfork() later. 2001-06-15 Rüdiger Kuhlmann [EMAIL PROTECTED] * acfunctions.m4: (AC_FUNC_VFORK) renamed to _AC_FUNC_VFORK. Remove AC_DEFINEs and don't

Re: [autoconf] AmigaOS fork()

--[Paul Eggert]--[EMAIL PROTECTED] I don't think the uses are portable. Wait, why not? The latest POSIX draft says this: [...] Okay. And if they aren't, would it be okay to change the HAVE_WORKING_VFORK to !HAVE_WORKING_FORK? No. For AC_FUNC_WAIT3 and AC_SYS_RESTARTABLE_SYSCALLS

Re: [autoconf] AmigaOS fork()

to define vfork yourself, either when !HAVE_WORKING_VFORK, or if you prefer to use fork, when HAVE_WORKING_FORK. I would replace this code with #if !HAVE_WORKING_VFORK # define vfork fork #endif Okay. 2001-06-01 Rüdiger Kuhlmann [EMAIL PROTECTED] * acfunctions.m4

Re: [autoconf] AmigaOS fork()

--[Paul Eggert]--[EMAIL PROTECTED] ... Kuhlmann's patch ... *giggle* feel free to use my first name. I don't think the uses are portable. Wait, why not? And if they aren't, would it be okay to change the HAVE_WORKING_VFORK to !HAVE_WORKING_FORK? The forkvfork() idea would be safest.

Re: [autoconf] AmigaOS fork()

--[Rüdiger Kuhlmann]--[EMAIL PROTECTED] 2001-06-01 Rüdiger Kuhlmann [EMAIL PROTECTED] * acfunctions.m4: (AC_FUNC_VFORK) renamed to _AC_FUNC_VFORK. Remove AC_DEFINEs and don't guess cross-compilation values. (_AC_FUNC_FORK) New, check whether fork() isn't just a stub

Re: [autoconf] AmigaOS fork()

Ehm, what do you want me to change to have this patch accepted? Yours, Rüdiger. -- A No uttered from deepest conviction is better and greater than a Yes merely uttered to please, or what is worse, to avoid trouble. -- Mahatma Ghandi

Re: [autoconf] AmigaOS fork()

in the sense of prefer fork, but replace by vfork. Comments about that? 2001-05-31 Rüdiger Kuhlmann [EMAIL PROTECTED] * acfunctions.m4: (AC_FUNC_FORK) New, check whether fork() isn't just a stub and define HAVE_WORKING_FUNC if it works. (AC_FUNC_GETPGRP, AC_FUNC_WAIT3) Use

Re: [autoconf] AmigaOS fork()

--[Tim Van Holder]--[EMAIL PROTECTED] On 31 May 2001 15:15:49 +0200, Rüdiger Kuhlmann wrote: Akim was talking about the 'case $host', I think. The problem is that since we are testing whether a function works, we need to _run_ that function. When cross-compiling, this is not possible, so

Re: [autoconf] AmigaOS fork()

does AC_FUNC_FNMATCH define HAVE_FNMATCH instead of HAVE_WORKING_FNMATCH? Next try: 2001-05-31 Rüdiger Kuhlmann [EMAIL PROTECTED] * acfunctions.m4: (AC_FUNC_FORK) New, check whether fork() isn't just a stub and define HAVE_WORKING_FORK if it works. Also, take over

Re: [autoconf] AmigaOS fork()

--[Russ Allbery]--[EMAIL PROTECTED] Peter Eisentraut [EMAIL PROTECTED] writes: [Yes, I do read the mailing lists I'm writing to. I even set a Mail-Followup-To:] The key question here is, if a program requires fork(), would it normally work with Amiga's vfork()? My guess is no, so this

Re: [autoconf] AmigaOS fork()

--[Tim Van Holder]--[EMAIL PROTECTED] For the cross-compiling case, I think Okay, what about this: It doesn't #define fork anymore, but HAVE_FORK if it works. Then the program has to check this itself. 2001-05-24 Rüdiger Kuhlmann [EMAIL PROTECTED] * acfunctions.m4: (AC_FUNC_FORK

AmigaOS fork()

(), @@ -1442,6 +1443,39 @@ AU_ALIAS([AC_UTIME_NULL], [AC_FUNC_UTIME_NULL]) +# AC_FUNC_FORK +# - +AC_DEFUN([AC_FUNC_FORK], +[AC_CACHE_CHECK(for working fork, ac_cv_func_fork_works, +[AC_TRY_RUN([/* By Rüdiger Kuhlmann. */ +#include stdio.h +#include sys/types.h +#include sys/stat.h

Re: [autoconf-patches] _AC_OUTPUT_SUBDIRS: check for configure.gnu as well

Hi! --[Akim Demaille]--[EMAIL PROTECTED] "diger" == diger Kuhlmann R writes: Well... I don't have to tell you what I think about "Gnus"... Still, why don't you want both Configure and configure in the same dir? Are you using a case insensitive FS? AmigaOS filesystems are traditionally

Re: [autoconf-patches] _AC_OUTPUT_SUBDIRS: check for configure.gnu as well [Resend]

igure.gnu. Or do you prefer a different name? This is wrong: you should update the --help recursion too. The Q. is, whether --help does make sense in this situation. But I guess you're right. Okay, next try: Index: ChangeLog from Rüdiger Kuhlmann [EMAIL PROTECTED] * acgeneral.m4(_AC_OU

_AC_OUTPUT_SUBDIRS: check for configure.gnu as well [Resend]

of a part of [EMAIL PROTECTED]. Index: ChangeLog from Rüdiger Kuhlmann [EMAIL PROTECTED] * acgeneral.m4(_AC_OUTPUT_SUBDIRS): check for configure.in as well Index: acgeneral.m4 === RCS file: /cvs/autoconf/acgeneral.m4,v

AC_ARG_ENABLE, AC_ARG_WITH: Prevent commands from being glued together

cho" or "fielse" to be a "fi" command. While the "dnl" may be bad practice, this breaks v 2.13 scripts. Here's a patch to fix it - just add a semicolon, so no line is wasted, yet no commands are glued together. This is basically a resend of [EMAIL PROTECTE

Re: [autoconf] HTML format documentation

Hi! --[Greg A. Woods]--[EMAIL PROTECTED] [ On , September 6, 2000 at 21:57:04 (-0700), Russ Allbery wrote: ] very different in what they do. Indeed it should be possible to adjust ${DESTDIR} during "make install" (and it would only have effect during "make install"). $(prefix) specifies

Re: [autoconf] HTML format documentation

--[David Morgan]--[EMAIL PROTECTED] --- Peter Eisentraut [EMAIL PROTECTED] wrote: I fully support making "docdir" a separate directory that defaults to `${prefix}/doc' -- after all, this has been reality for years. But I'd like to see this taken further: make "info" a subdirectory of

Crosscompiling (was: Guess what...)

Hi! Another problem I have is the following: When configuring a source tree of unrelated projects, I sometimes want to give configuration options for a specific project Sometimes it helps to look how other people do it. What about this patch: --snip-- diff -u -r autoconf/acgeneral.m4

Glueing fi to following commands - fix

Hi! Using autoconf 2.49a, I often found fi's glued to following commands. Obviously, a newline is missing. The cause is an ARG_WITH or ARG_ENABLE command with a dnl at its end - autoconf 2.13 seems to have generated a bogus newline, so that "everyone" removed it with a dnl. So either remove the

Re: [autoconf] Guess what...

Hi! --[Akim Demaille]--[EMAIL PROTECTED] ... we finally have a snapshot! No, I really mean it! We have one! ps/ Jim, could you please upload 2.49a in ftp://alpha.gnu.org/gnu/autoconf/autoconf-2.49a.tar.gz Looks like it's still not there... :( Anyway, I have some questions

AC_PROG_RANLIB

Hi, can we please change AC_PROG_RANLIB to use CHECK_TOOL? --snip-- diff acspecific.m4.orig acspecific.m4 109a110,111 # AC_PROG_RANLIB # -- 111c113 [AC_CHECK_PROG(RANLIB, ranlib, ranlib, :)]) --- [AC_CHECK_TOOL (RANLIB, ranlib, :)]) --snip-- Yours, Rüdiger.