From netlist@netlist.net Wed Jan 01 09:48:18 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TkAM-0007Gf-00
	for autoconf@gnu.org; Wed, 01 Jan 2003 09:48:18 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18TkAI-0007Fj-00
	for autoconf@gnu.org; Wed, 01 Jan 2003 09:48:17 -0500
Received: from ppp11-213.isnet.net.tr ([212.98.11.213] helo=localhost.com)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18TkAG-0007E3-00
	for autoconf@gnu.org; Wed, 01 Jan 2003 09:48:13 -0500
From: autoconf@gnu.org
To: autoconf@gnu.org
Date: Wed, 1 Jan 2003 16:46:33 +0200
X-Mailer: MailXSender 1.02
MIME-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: base64
Message-Id: <E18TkAG-0007E3-00@monty-python.gnu.org>
Subject: Download Eminem-Shaggy'S Mp3s  01.01.2003 16:46:33
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: deop@netlist.net
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 01 Jan 2003 14:48:18 -0000

PGh0bWw+DQo8Ym9keT4NCjxwIGFsaWduPSJjZW50ZXIiPjxhIGhyZWY9Imh0dHA6Ly9uZXRsaXN0
Lm5ldCI+PGltZw0Kc3JjPSJodHRwOi8vd3d3Lm5ldGxpc3QubmV0L2lpX2ltZy9sb2dvYmFubmVy
LmdpZiIgYm9yZGVyPSIwIj48L2E+PC9wPg0KPHAgYWxpZ249ImNlbnRlciI+PGZvbnQgZmFjZT0i
QXJpYWwiIHNpemU9IjIiIGNvbG9yPSIjRkYwMDAwIj48c3Ryb25nPiEgSGVsbG8gV2VibWFzdGVy
cyAhPC9zdHJvbmc+PC9mb250PjwvcD4NCjxwIGFsaWduPSJjZW50ZXIiPjxzdHJvbmc+PGZvbnQg
ZmFjZT0iQXJpYWwiIHNpemU9IjIiPjxhIGhyZWY9Imh0dHA6Ly93d3cuTmV0bGlzdC5uZXQiPnd3
dy5OZXRsaXN0Lm5ldDwvYT4NCmhhcyBPcGVuZWQgITwvZm9udD48L3N0cm9uZz48L3A+DQo8cCBh
bGlnbj0iY2VudGVyIj48c3Ryb25nPjxmb250IGZhY2U9IkFyaWFsIiBzaXplPSIyIj48Zm9udCBj
b2xvcj0iI0ZGMDAwMCI+U28gSm9pbiBPdXINCnRvcGxpc3QgYW5kIGluY3JlYXNlIHlvdXIgdHJh
ZmZpYyBmb3IgZnJlZS4gWW91IHdvbnQgbmVlZCB0byBvcGVuIHBvcC11cCAhPGJyPg0KPC9mb250
PkJlY2F1c2Ugd2UgaGF2ZSBhIGRpbmFtaWMgY291bnRlciBsb29rcyBsaWtlOjxicj4NCjxhIGhy
ZWY9Imh0dHA6Ly9uZXRsaXN0Lm5ldCI+PGltZyBzcmM9Imh0dHA6Ly93d3cubmV0bGlzdC5uZXQv
aW1hZ2UvdXllLmdpZiIgYm9yZGVyPSIwIj48L2E+PC9mb250Pjwvc3Ryb25nPjwvcD4NCjxwIGFs
aWduPSJjZW50ZXIiPjxmb250IGZhY2U9IkFyaWFsIiBzaXplPSIyIj48c3Ryb25nPkNsaWNrIFRo
YXQgbG9nbyBhbmQgY29tZSB0byBvdXINCnNpdGUuIFRoYW4gQWRkIFlvdXIgc2l0ZSB0byB0aGUg
Y29ycmVjdCBDYXRlZ29yeS4uPGJyPg0KV2UgQWNjZXAgQWxsIEtpbmRzIG9mIFNpdGVzICEuIGFk
ZCB5b3VyIHNpdGUgYW5kIHB1dCB0aGUgaHRtbCBjb2RlIHdoYXQgeW91IGdpdmVuLi4hIFRoYXRz
DQppdCAhPC9zdHJvbmc+PC9mb250PjwvcD4NCjxwIGFsaWduPSJjZW50ZXIiPjxzdHJvbmc+PGZv
bnQgZmFjZT0iQXJpYWwiIHNpemU9IjIiPkdvb2QgTHVjay48L2ZvbnQ+PC9zdHJvbmc+PC9wPg0K
PHAgYWxpZ249ImNlbnRlciI+PHN0cm9uZz48Zm9udCBmYWNlPSJBcmlhbCIgc2l6ZT0iMiI+VGhh
bmtzPC9mb250Pjwvc3Ryb25nPjwvcD4NCjxwIGFsaWduPSJjZW50ZXIiPjxmb250IGZhY2U9IkFy
aWFsIiBzaXplPSIyIj48c3Ryb25nPiEhISBERUFSIFNVUkZFUlMgISEhPC9zdHJvbmc+PC9mb250
PjwvcD4NCjxwIGFsaWduPSJjZW50ZXIiPjxzdHJvbmc+PGZvbnQgZmFjZT0iQXJpYWwiIHNpemU9
IjIiPllvdSBjYW4gYWxzbyByZWFjaCB0aGUgYmVzdCBzaXRlcyBieQ0KPGEgaHJlZj0iaHR0cDov
L3d3dy5uZXRsaXN0Lm5ldCI+d3d3Lm5ldGxpc3QubmV0PC9hPiA8YnI+DQo8L2ZvbnQ+PGZvbnQg
Y29sb3I9IiNGRjAwMDAiIGZhY2U9IkFyaWFsIiBzaXplPSIyIj5BbmQgeW91IGNhbiBkb3dubG9h
ZCB0aGUgbW9zdCBwb3B1bGVyDQpNcDNzIGZvciBmcmVlIGxpa2UgU2hhZ2d5LSBFbWluZW0tIE1h
cnlsPC9mb250Pjxmb250IGNvbG9yPSIjRkYwMDAwIj48Zm9udCBzaXplPSIyIj48Zm9udA0KZmFj
ZT0iQXJpYWwiPmk8L2ZvbnQ+PC9mb250Pjxmb250IGZhY2U9IkFyaWFsIiBzaXplPSIyIj5uIE1h
bnNvbjwvZm9udD48L2ZvbnQ+PC9zdHJvbmc+PC9wPg0KPHNjcmlwdD4gDQpuZXRsaXN0PXdpbmRv
dy5vcGVuKCJodHRwOi8vd3d3Lm5ldGxpc3QubmV0IiwibmV0bGlzdCIpOyBzZWxmLmZvY3VzKCk7
IA0KPC9zY3JpcHQ+DQo8L2JvZHk+DQo8L2h0bWw+



From guidod-2002-@gmx.de Thu Jan 02 00:47:48 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18TyCq-00054O-00
	for autoconf@gnu.org; Thu, 02 Jan 2003 00:47:48 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18TyCk-0004tt-00
	for autoconf@gnu.org; Thu, 02 Jan 2003 00:47:47 -0500
Received: from imap.gmx.net ([213.165.65.60] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18TyCj-0004nH-00
	for autoconf@gnu.org; Thu, 02 Jan 2003 00:47:41 -0500
Received: (qmail 10744 invoked by uid 0); 2 Jan 2003 05:47:37 -0000
Received: from pd9e82405.dip.t-dialin.net (HELO gmx.de) (217.232.36.5)
  by mail.gmx.net (mp011-rz3) with SMTP; 2 Jan 2003 05:47:37 -0000
Message-ID: <3E13D2D4.4070303@gmx.de>
Date: Thu, 02 Jan 2003 06:49:08 +0100
From: Guido Draheim <guidod-2002-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: autoconf@gnu.org
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: OT: doc install into omf/scrollkeeper
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 02 Jan 2003 05:47:49 -0000

This is offtopic from autotool technology, I did just observe that
not many people have come to notice the benefits of omf/scrollkeeper
for providing documentation to the local user of software.

* what is omf/scrollkeeper

interesting bits can be found starting on http://scrollkeeper.sf.net
"It manages documentation metadata (as specified by the Open Source
Metadata Framework(OMF)) [link to osrt/omf given] and provides a
simple API to allow help browsers to find, sort, and search the
document catalog." .. [in browsers.html] "KDE's help browser has had
ScrollKeeper support since the 2.x days." .. "Yelp will replace
Nautilus as the GNOME help browser [in GNOME 2.x]".

* installing documentation files

The documentation files can be created and intalled traditionally, well
here we do more deal with html (or xml) files than troff man pages.
Actually, quite some projects have a doc/ subdirectory that carries
project information along and they are installed somewhere in the
system, in many cases into ${datadir}/doc/${PACKAGE} or perhaps just
into ${datadir}/${PACKAGE}/html

* the index/search problem

there is no traditional directory for html/xml documentation, and
a user has problems to (a) find the place and (b) search into it.
The gnu .info files system has just that - one will install the
files and make a call to `install-info` to register it in a
central overview page, kinda `table of content`. An info-browser
like `info` or `pinfo` can be used to read into it or even search
for parts of interest.

* the omf/scrollkeeper approach

The omf has created a DTD for an xml format that can be used to
register html documentation in the system - omf enabled browsers
can read this TOC-like index file and present it to the user. The
user can read it or search into it with the help provided by these
browsers - both kde/gnome help browsers span across omf and troff
pages.

The tool of interest here is `scrollkeeper-update` - after having
all the html files installed in a directory of your choice, the
last step shall then be the installation of *.omf file(s) into
${datadir}/omf/${PACKAGE} followed by a call to scrollkeeper-update.
No special arguments are needed when datadir/omf is present in
the $OMF_DIR list or your scrollkeeper.conf

* omf file creation

The only trick is in creating a valid omf file. First of all, you
need an omf key - because internally the omf registry does *not*
work with the filepath of your *.omf file but only this numeric
key. When multiple omf files with the same key are present only
the newest is taken - that's great for renaming the omf file or
installing multiple parallel versions of the same documents. A
unique omf key can be created by `scrollkeeper-gen-seriesid`, and
it should be run only once and the value be memorized in the
doc/ makfile.in/makefile.am

DOCSERIES = 1a894a10-1e10-11d7-83ae-a34c0931e5e5

The entries to be put into the xml-type omf file are sometimes
not easy to grasp from the omf documentation, it took me some
trial and error - my goal was to pick up most of the information
from a rpm spec file. That actually a good idea - the "category"
of the doc should match the value you've chosen for the rpm spec
files "Group" entry since opensource categorization has already
a common scheme across packaging systems (.rpm/.deb/slack etc),
and the scrollkeeper tools/browsers have correct translations of
these catagories at hand (better browsing experience!).

Anyway, here is some real world example for you to pick up and
modify according to the needs of your project:

# -------------------------------------------------------------------
DOCSERIES= 775fb73e-1874-11d7-93e9-e18cd7ea3c2e
FROMSPEC= zziplib.spec | head -1 | sed -e 's,<,\&lt;,g' -e 's,>,\&gt;,g'
DATESPEC= `date +%Y-%m-%d`

$(PACKAGE)-doc.omf : zziplib.spec Makefile
         echo '<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>' >$@
         echo '<omf><resource><creator> Guido Draheim </creator>' >>$@
         grep Packager $(FROMSPEC) | sed -e 's,Packager *: *, <maintainer>,' \
                                     -e '/<maintainer>/s,$$,</maintainer>,' >>$@
         grep Summary  $(FROMSPEC) | sed -e 's,Summary *: *, <title>,' \
                        -e '/<title>/s,$$,</title>,' >>$@
         echo ' <date>'$(DATESPEC)'</date>' >>$@
         echo ' <version identifier="$(VERSION)" date="'$(DATESPEC)'"/>' >>$@
         grep Group  $(FROMSPEC) | sed -e 's,Group *: *, <subject category=",' \
                         -e 's,/,|,g' -e '/<subject/s,$$," />,' >>$@
         echo ' <format mime="text/html"/>' >>$@
         echo ' <identifier url="file:$(pkgdocdir)/index.html"/>' >>$@
         echo ' <language code="C"/>' >>$@
         echo ' <relation seriesid="$(DOCSERIES)"/>' >>$@
         echo ' <rights type="GNU LGPL" holder="Guido Draheim"' >>$@
         echo '         license="$(pkgdocdir)/COPYING.LIB"/>' >>$@
         echo '</resource></omf>' >>$@

Note that documentation was installed to $(pkgdocdir) and has a starting
point of index.html and carries also a copy of COPYING.LIB. The specfile
"Group" has "Development/Libraries" which `yelp` shows as "Entwicklung"->
"Bibliotheken" in German. The doc files themselves are english and placed
here as "<language code="C"/> as the general fallback documentation when
no translation is available.

* omf install part

 From old times, I had an `install-doc` target at hand, and in some automake
project there was not even that and just some pkgdoc_DATA files around to
be installed automatically. The html/xml files get installed and we are
ready to register them into the systems help browsers via scrollkeeper.

omfdir=${datadir}/omf
pkgomfdir=${omfdir}/${PACKAGE}

install-omf : $(PACKAGE)-doc.omf $(PACKAGE)-man.omf
         $(mkinstalldirs) $(DESTDIR)$(pkgomfdir)
         $(INSTALL_DATA) $(PACKAGE)-doc.omf $(DESTDIR)$(pkgomfdir)/
         $(INSTALL_DATA) $(PACKAGE)-man.omf $(DESTDIR)$(pkgomfdir)/
         - test ".$(DESTDIR)" != "." || scrollkeeper-update -v

The last call is conditionalized with a $DESTDIR check simply for
packaging traditions - you do not want to recreate a scrollkeeper
index repository in the tmp-installpath used by destdir-packaging.
Instead, a scrollkeeper-update call should be part of the rpm/deb
package's post-install/post-uninstall specification. In a .spec
file I am currently writing this:

%files doc
%dir  %{_docdir}/%{name}
       %{_docdir}/%{name}/*
%dir  %{_datadir}/omf/%{name}
       %{_datadir}/omf/%{name}/*
%post doc
test ! -f /usr/bin/scrollkeeper-update || /usr/bin/scrollkeeper-update
%postun doc
test ! -f /usr/bin/scrollkeeper-update || /usr/bin/scrollkeeper-update

* that's it.

it's perhaps a bit a long description but at the same time it should
make it most easy for you to go with it step by step and take benefit
of modern help facilities for the developer/enduser html documentation.
It can be as easy as the html files that you install on your project's
homepage anyway - and just install/register them via scrollkeeper so
that people can read/search them locally, possibly including translations.
And this help system can well make you drop any `todo` for an .info file
as well, in case you do not have one around up to now.... and it may well
be that the whole info system becomes largely obsolete when more developer's
pick up the facilities provided by omf/scrollkeeper.

-- have fun, guido       http://zziplib.sf.net    http://ac-archive.sf.net




From noisyb@gmx.net Thu Jan 02 06:30:49 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U3Xo-0002Ua-00
	for autoconf@gnu.org; Thu, 02 Jan 2003 06:29:48 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U3Xd-0002CG-00
	for autoconf@gnu.org; Thu, 02 Jan 2003 06:29:40 -0500
Received: from pop.gmx.net ([213.165.65.60] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18U3XK-0001vc-00
	for autoconf@gnu.org; Thu, 02 Jan 2003 06:29:18 -0500
Received: (qmail 21747 invoked by uid 0); 2 Jan 2003 11:29:16 -0000
Received: from p3ee21983.dip.t-dialin.net (HELO gmx.net) (62.226.25.131)
  by mail.gmx.net (mp004-rz3) with SMTP; 2 Jan 2003 11:29:16 -0000
Message-ID: <3E14215F.6020607@gmx.net>
Date: Thu, 02 Jan 2003 12:24:15 +0100
From: Dirk <noisyb@gmx.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.3b) Gecko/20021222
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: autoconf@gnu.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: autoconf && ipv6
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 02 Jan 2003 11:30:49 -0000

how would i find out if ipv6 is available (enabled)?



From guidod-2003-@gmx.de Thu Jan 02 12:21:02 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18U91E-0006zR-00
	for autoconf@gnu.org; Thu, 02 Jan 2003 12:20:32 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18U90c-0006fC-00
	for autoconf@gnu.org; Thu, 02 Jan 2003 12:20:00 -0500
Received: from pop.gmx.de ([213.165.65.60] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18U8xc-0005J1-00
	for autoconf@gnu.org; Thu, 02 Jan 2003 12:16:48 -0500
Received: (qmail 5557 invoked by uid 0); 2 Jan 2003 17:16:46 -0000
Received: from pd9e81c3b.dip.t-dialin.net (HELO gmx.de) (217.232.28.59)
  by mail.gmx.net (mp007-rz3) with SMTP; 2 Jan 2003 17:16:46 -0000
Message-ID: <3E147457.6090009@gmx.de>
Date: Thu, 02 Jan 2003 18:18:15 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dirk <noisyb@gmx.net>
References: <3E14215F.6020607@gmx.net>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: autoconf && ipv6
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 02 Jan 2003 17:21:05 -0000

Dirk wrote:
> how would i find out if ipv6 is available (enabled)?
> 

"enabled" is a runtime problem.

autoconf handles compile/link issues.

That will include to check for a header file
to declare ipv6 symbols and a lib to export
the actual implementations. In general, the
developer docs of your ipv6-enabled OS should
tell you which is where. -- guido




From netlist@netlist.net Thu Jan 02 13:55:23 2003
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18UATA-0006E8-00
	for autoconf@gnu.org; Thu, 02 Jan 2003 13:53:28 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18UASi-00063j-00
	for autoconf@gnu.org; Thu, 02 Jan 2003 13:53:04 -0500
Received: from ppp11-210.isnet.net.tr ([212.98.11.210] helo=localhost.com)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18UAIu-0003Bn-00
	for autoconf@gnu.org; Thu, 02 Jan 2003 13:42:56 -0500
From: autoconf@gnu.org
To: autoconf@gnu.org
Date: Thu, 2 Jan 2003 20:41:14 +0200
X-Mailer: MailXSender 1.02
MIME-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: base64
Message-Id: <E18UAIu-0003Bn-00@monty-python.gnu.org>
Subject: NeTLiST.net ACILDI !!  02.01.2003 20:41:14
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: deop@netlist.net
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 02 Jan 2003 18:55:25 -0000

PGh0bWw+DQo8Ym9keT4NCjxwIGFsaWduPSJjZW50ZXIiPjxhIGhyZWY9Imh0dHA6Ly9uZXRsaXN0
Lm5ldCI+PGltZw0Kc3JjPSJodHRwOi8vd3d3Lm5ldGxpc3QubmV0L2lpX2ltZy9sb2dvYmFubmVy
LmdpZiIgYm9yZGVyPSIwIj48L2E+PC9wPg0KPHAgYWxpZ249ImNlbnRlciI+PGZvbnQgZmFjZT0i
QXJpYWwiIHNpemU9IjIiIGNvbG9yPSIjRkYwMDAwIj48c3Ryb25nPiEgTWVyaGFiYSBEZWdlcmxp
DQpXZWJtYXN0ZXJsYXIgITwvc3Ryb25nPjwvZm9udD48L3A+DQo8cCBhbGlnbj0iY2VudGVyIj48
Zm9udCBmYWNlPSJBcmlhbCIgc2l6ZT0iMiI+PHN0cm9uZz48YSBocmVmPSJodHRwOi8vd3d3Lk5l
dGxpc3QubmV0Ij53d3cuTmV0bGlzdC5uZXQ8L2E+DQpBQ0lMREkgITwvc3Ryb25nPjwvZm9udD48
L3A+DQo8cCBhbGlnbj0iY2VudGVyIj48c3Ryb25nPjxmb250IGZhY2U9IkFyaWFsIiBzaXplPSIy
IiBjb2xvcj0iI0ZGMDAwMCI+VG9wbGlzdGltaXplDQprYXlkb2x1biB2ZSBzaXRlbml6aSBZQUJB
TkNJIGxhcmEgdGFuaXRpbi4gVGFtYW1lbiBpbmdpbGl6Y2Ugb2xhbiBwb3J0YWxpbWl6IHV6ZXJp
bmRlbg0KcmVrbGFtaW5pemkgdWNyZXRzaXogeWFwaW4uICE8YnI+DQo8L2ZvbnQ+PGZvbnQgZmFj
ZT0iQXJpYWwiIHNpemU9IjIiPlNpc3RlbSBkaW5hbWljIHNheWFjbGEgaXN0ZXJzZW5peiBkZSBw
b3AtdXAgbGENCmNhbGlzaXlvci4gUG9wLXVwIGVrbGVyc2VuaXogbGlzdGVkZSAyIGthdCBkYWhh
IGhpemxpIHl1a3NlbGlyc2luaXouIHNlY2ltIHNpemluLiBMb2dvDQphc3NhZ2lkYWtpIGdpYmkg
Z29ydW5lY2VrIHNheWZhbml6ZGEuLjxicj4NCjxhIGhyZWY9Imh0dHA6Ly9uZXRsaXN0Lm5ldCI+
PGltZyBzcmM9Imh0dHA6Ly93d3cubmV0bGlzdC5uZXQvaW1hZ2UvdXllLmdpZiIgYm9yZGVyPSIw
Ij48L2E+PC9mb250Pjwvc3Ryb25nPjwvcD4NCjxwIGFsaWduPSJjZW50ZXIiPjxmb250IGZhY2U9
IkFyaWFsIiBzaXplPSIyIj48c3Ryb25nPkxvZ295YSB0aWtsYXlpbiB2ZSBhbmEgc2F5ZmFkYWtp
DQombmJzcDsgQUREIFNpVEUgbGlua2luZSB0aWtsYXlpbiBzaXRlbml6aSBrYXlkZWRpbi4uPC9z
dHJvbmc+PC9mb250PjwvcD4NCjxwIGFsaWduPSJjZW50ZXIiPjxmb250IGZhY2U9IkFyaWFsIiBz
aXplPSIyIj48c3Ryb25nPlphbWFuaW5pemkgQm9zYSBoYXJjYW1heWluIHZlIGhlbWVuDQpidSB5
ZW5pIG5lc2lsIGxpc3RleWUgb2x1biAhLi48YnI+DQpIZXIgdHVybHUgc2l0ZSBrYWJ1bCBlZGls
bWVrdGVkaXIuIFR1cmtjZSB2ZXlhIEluZ2lsaXpjZSBvbG1hc2kgeWV0ZXJsaSB2ZSBpY2VyaWsg
c2FoaWJpDQpvbG1hc2kuPC9zdHJvbmc+PC9mb250PjwvcD4NCjxwIGFsaWduPSJjZW50ZXIiPjxm
b250IGZhY2U9IkFyaWFsIiBzaXplPSIyIj48c3Ryb25nPkJvbCBTYW5zbGFyLjwvc3Ryb25nPjwv
Zm9udD48L3A+DQo8cCBhbGlnbj0iY2VudGVyIj48Zm9udCBmYWNlPSJBcmlhbCIgc2l6ZT0iMiI+
PHN0cm9uZz5UZXNla2t1cmxlcjwvc3Ryb25nPjwvZm9udD48L3A+DQo8L2JvZHk+DQo8L2h0bWw+



From MAILER-DAEMON Fri Jan 03 18:37:18 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18UbJE-0006Bo-00
	for mharc-autoconf@gnu.org; Fri, 03 Jan 2003 18:33:00 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18UbIw-00060I-00
	for autoconf@gnu.org; Fri, 03 Jan 2003 18:32:42 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18UbIi-0005ry-00
	for autoconf@gnu.org; Fri, 03 Jan 2003 18:32:30 -0500
Received: from gnudist.gnu.org ([199.232.41.7])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18UbIK-0005cG-00
	for autoconf@gnu.org; Fri, 03 Jan 2003 18:32:04 -0500
Received: from [211.216.83.188] (helo=VipYou)
	by gnudist.gnu.org with smtp (Exim 4.10.13)
	id 18UbIJ-0004qI-00
	for autoconf@gnu.org; Fri, 03 Jan 2003 18:32:03 -0500
From: VipYou<master@vipyou.com>
To: autoconf@gnu.org
Date: Sat, 4 Jan 2003 08:32:01 +0900
Mime-Version: 1.0
Content-Type: text/html; charset="euc-kr"
Message-Id: <E18UbIJ-0004qI-00@gnudist.gnu.org>
Subject: 
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: dksghdud@lycos.co.kr
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 03 Jan 2003 23:32:57 -0000

<HTML>
<HEAD>
<TITLE></TITLE>
</HEAD>
<BODY>
<DIV align=center>&nbsp;&nbsp;<FONT color=#0080c0><FONT size=2> </FONT>O 본 메일은
정보통신망 이용촉진 및 정보보호 등에 관한 법률 제 50조에 의거한 [광고] 메일입니다<BR>O e-mail주소는 인터넷상에서 취득하였으며,
주소외 어떠한 개인 정보도 가지고 있지 않습니다</FONT><BR></DIV><FONT color=#0080c0>
<HR color=#8bb5e2>
</FONT><FONT color=#000000>
<HR color=#8bb5e2>
<P align=center><A href="http://vipyou.com"><img src="http://vipyou.com/popup_image/newmail_logo1.gif" border=0></a></P>
<P align=center><FONT color=#0080ff>성인용품점</FONT></P>
<P align=center><FONT color=#0080ff>이젠</FONT></P>
<P align=center><FONT color=#0080ff>바뀌어야 한다</FONT></P>
<P align=center><FONT color=#0080ff>한번 보고 결정하세요</FONT></P>
<P align=center><STRONG><FONT color=#0000a0></FONT></STRONG>&nbsp;</P>
<P align=center><STRONG><A href="http://vipyou.com"><FONT
color=#ff0000>VipYou</FONT></A></STRONG></P>
<P align=center><FONT color=#0080c0>보기만 했던 성인용품 </FONT></P>
<P align=center><FONT color=#0080c0>이제한번 써보세요</FONT></P>
<P align=center><FONT color=#0080c0>절대 비밀보장</FONT></P>
<P align=center><STRONG><A href="http://vipyou.com"><FONT
color=#ff0000>VipYou</FONT></A></STRONG></P>
<P align=center><FONT color=#0000ff>저희는 고객에게 만족을 팝니다.</FONT></P>
<P align=center><FONT color=#0000ff>단,미성년자는 돌아가주세요.</FONT></P>
<P align=center><FONT color=#0000ff>좋은하루 되세요</FONT></P>
<HR color=#8bb5e2>
<HR color=#8bb5e2>
<DIV align=center><FONT face=굴림 color=#0080c0 size=2>허락없이 메일을 보내서
죄송합니다.</FONT></DIV>
<DIV align=center><FONT color=#0080c0><FONT face=굴림 size=2>본 메일은 정보통신부 권고 사항에 의거
제목에 [광고]라 표시된 광고 메일입니다.</FONT><BR></FONT><FONT color=#000000 size=2><FONT
color=#0080c0>메일 수신을 원하시지 않으시면&nbsp; 다음을 클릭해 주세요</FONT> </FONT></DIV>
<DIV align=center><A style="PADDING-RIGHT: 3px; PADDING-LEFT: 3px; FONT-SIZE: 12px; PADDING-BOTTOM: 3px; COLOR: #ffff00; PADDING-TOP: 3px; FONT-FAMILY: 굴림; BACKGROUND-COLOR: #8bb5e2; TEXT-DECORATION: none" href="mailto:dksghdud@lycos.co.kr">수신거부</A><FONT color=#0080c0>
</FONT><FONT color=#8bb5e2 size=2><FONT color=#0080c0>버튼을 클릭하시면 수신거부처리가 이루어
집니다</FONT>.</FONT></DIV>
<DIV align=center>&nbsp;<FONT size=2><FONT color=#0080c0> If you don`t want this
type of information or e-mail, please click the `refuse`
button</FONT>.</FONT></DIV>
<HR color=#8bb5e2>
<HR color=#8bb5e2>
</BODY>
</HTML>



From MAILER-DAEMON Sun Jan 05 15:42:30 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VHZs-0002Xn-00
	for mharc-autoconf@gnu.org; Sun, 05 Jan 2003 15:41:00 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VHYv-0002FA-00
	for autoconf@gnu.org; Sun, 05 Jan 2003 15:40:01 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VHWu-0000xu-00
	for autoconf@gnu.org; Sun, 05 Jan 2003 15:37:57 -0500
Received: from relais.videotron.ca ([24.201.245.36]
	helo=VL-MS-MR004.sc1.videotron.ca)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18VHVy-0000om-00
	for autoconf@gnu.org; Sun, 05 Jan 2003 15:36:58 -0500
Received: from riemann.nyongwa.montreal.qc.ca ([24.202.211.97])
 by VL-MS-MR004.sc1.videotron.ca
 (iPlanet Messaging Server 5.2 HotFix 0.9 (built Jul 29 2002))
 with ESMTP id <0H8900I4FDBPNI@VL-MS-MR004.sc1.videotron.ca> for
 autoconf@gnu.org; Sun, 05 Jan 2003 15:38:13 -0500 (EST)
Received: from steve by riemann.nyongwa.montreal.qc.ca with local
	(Exim 3.36 #1 (Debian))	id 18VHVv-0004hW-00;
	Sun, 05 Jan 2003 15:36:55 -0500
Date: Sun, 05 Jan 2003 15:36:53 -0500
From: "Steve M. Robbins" <steven.robbins@videotron.ca>
In-reply-to: <3E0395BF.5090903@ixiacom.com>
To: Dan Kegel <dkegel@ixiacom.com>
Message-id: <20030105203653.GA6696@riemann.nyongwa.montreal.qc.ca>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
User-Agent: Mutt/1.4i
References: <3DF8CCB1.1020109@gmx.de> <3DF888E3.9060405@ph.ed.ac.uk>
 <Pine.LNX.4.50.0212121306250.4362-100000@squyres.com>
 <Pine.LNX.4.50.0212180736520.25659-100000@squyres.com>
 <Pine.LNX.4.50.0212200723500.12627-100000@squyres.com>
 <200212202159.gBKLx0215340@green.twinsun.com> <3E0395BF.5090903@ixiacom.com>
cc: autoconf@gnu.org
Subject: Re: AC_DEFINE questions
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 05 Jan 2003 20:40:58 -0000

On Fri, Dec 20, 2002 at 02:12:15PM -0800, Dan Kegel wrote:

> FWIW, while Debian supports multiple installations of autoconf,
> it doesn't yet support multiple installations of automake.

That is true of the stable debian release, but it has since been
changed in "unstable".  I have both 1.6 and 1.7 installed, for
example.

-S



From MAILER-DAEMON Sun Jan 05 20:18:46 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VLrq-0000t1-00
	for mharc-autoconf@gnu.org; Sun, 05 Jan 2003 20:15:50 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VLrn-0000p0-00
	for autoconf@gnu.org; Sun, 05 Jan 2003 20:15:47 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VLrY-0000ZH-00
	for autoconf@gnu.org; Sun, 05 Jan 2003 20:15:34 -0500
Received: from pop.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18VLrB-0008Ke-00
	for autoconf@gnu.org; Sun, 05 Jan 2003 20:15:09 -0500
Received: (qmail 19967 invoked by uid 0); 6 Jan 2003 01:15:06 -0000
Received: from pd9e80ed2.dip.t-dialin.net (HELO gmx.de) (217.232.14.210)
  by mail.gmx.net (mp012-rz3) with SMTP; 6 Jan 2003 01:15:06 -0000
Message-ID: <3E18D8FC.9040907@gmx.de>
Date: Mon, 06 Jan 2003 02:16:44 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: autoconf@gnu.org
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: ac-archive: obsolete detection and AX_ prefix
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 06 Jan 2003 01:15:48 -0000

with the ongoing expansion of ac-archive, it started to problematic
to keep the macros sorted out. There has been a discussion a while
back whether it might make sense to reserve a macro-prefix for
those registered in the ac-archive - the usage of AX_ sounds best.

This AX_ prefix is now detected by the `acinclude` distributed in
the tarball of the sfnet branch, and it will warn about any macro
call within a configure.ac that has an AX_ prefix but that could not
be found while creating acinclude.m4 - this has worked quite well
for a while and I want to start now asking maintainers of extra
ac-macros to pick up this AX_ prefix in the future.

A deeper reasoning comes from the fact that the ac-archive has
now a series of macros available that follow a certain scheme,
look for the great work of Luc Maisonobe for the C++-Support
section - it has now ac-macros for all relevant differences in
c++ compilers at hand. Perhaps some of these will diffuse later
into the autoconf base package and in which case these macros
might come to exist multiple times - both in an acinclude.m4 and
in the systems autoconf installation.

Even now, some people have started to rename their macros from
using the AC_-prefix to something different. That makes it
perhaps not easy for maintainers of large software sites to
keep up with updates of extra ac-macros - unlike the autoconf
base package, they are not extra tested and it is therefore quite
likely be see them changed for finding little bugs around, or
perhaps even replaced with another one that has a better call
synopsis and different defaults for empty arguments.

Where the gnuorg branch simply deletes the old files, I have come
to the conclusion to keep the old ac-macros around under their
old name for a while (a year or so) and instead put a marker
"obsoleted by ..." into the header of these .m4 files. That makes
it easy for large-site maintainers to find renamed/obsoleted
macros - they can simply `grep` them for "obsoleted". Additionaly,
the `acinclude` tool from the sfnet ac-archive will utter now
non-fatal warning messages for every of these as well.

hints? comments? objections? ;-)

-- cheers, guido                         http://ac-archive.sf.net




From MAILER-DAEMON Sun Jan 05 20:37:22 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VMBy-00089q-00
	for mharc-autoconf@gnu.org; Sun, 05 Jan 2003 20:36:38 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VMBq-0007q2-00
	for autoconf@gnu.org; Sun, 05 Jan 2003 20:36:30 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VMBk-0007gD-00
	for autoconf@gnu.org; Sun, 05 Jan 2003 20:36:27 -0500
Received: from pop.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18VMBQ-0006q0-00
	for autoconf@gnu.org; Sun, 05 Jan 2003 20:36:04 -0500
Received: (qmail 26244 invoked by uid 0); 6 Jan 2003 01:36:02 -0000
Received: from pd9e80ed2.dip.t-dialin.net (HELO gmx.de) (217.232.14.210)
  by mail.gmx.net (mp012-rz3) with SMTP; 6 Jan 2003 01:36:02 -0000
Message-ID: <3E18DDE5.7020900@gmx.de>
Date: Mon, 06 Jan 2003 02:37:41 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: autoconf@gnu.org
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: Ville Laurikari <vl@iki.fi>
Subject: ac-archive: ax_cflags_<option> macros...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 06 Jan 2003 01:36:37 -0000

I did lately needed again extensions of the old scheme to add
compiler-specific options. The macros being most in usage
where
   ac_prog_cc_warnings.m4 (renamed to) vl_prog_cc_warnings.m4
   ac_prog_cc_no_writeable_strings.m4  (needed widely around, and)
   ac_check_cc_opt.m4 (to add arbritrary long-options to gcc/others).

Looking at the implementation bits, we see quite different
approaches at detecting the correct option for the compiler
currently under test. An even different scheme can be seen
in the -ansi detection in the autoconf base macros for the
common AC_PROG_CC_STDC

 From these, I did start to invent a different detection scheme
that is hopefully generic enough to add step-by-step more
ac-macros that can add compiler-specific options intended for
the same compile-scheme that the programmers want to have.

It basically picks up the for-list scheme from AC_PROG_CC_STDC
and extends it - the list items contain "%" separator marks
that will mark breaks in the option strings. Each option to
be tested has a _selector test_ - in other words, all compilers
but one shall error-out on these selectors. The selector
options however will not be part of the resulting option
string for the feature that is wished for.

These selector-tests are usually derived from the different
schemes that enable ansi-constraints for the compilers, now
just have a look at the following example take up from
ax_cflags_warn_all.m4

  AC_LANG_SAVE
  AC_LANG_C
  ac_save_CFLAGS="$CFLAGS"
for ac_arg dnl
in "-pedantic  % -Wall"       dnl   GCC
    "-xstrconst % -v"          dnl Solaris C
    "-std1      % -verbose -w0 -warnprotos" dnl Digital Unix
    "-qlanglvl=ansi % -qsrcmsg -qinfo=all:noppt:noppc:noobs:nocnd" dnl AIX
    "-ansi -ansiE % -fullwarn" dnl IRIX
    "+ESlit     % +w1"         dnl HP-UX C
    "-Xc        % -pvctl[,]fullmsg" dnl NEC SX-5 (Super-UX 10)
    "-h conform % -h msglevel 2" dnl Cray C (Unicos)
    #
do CFLAGS="$ac_save_CFLAGS "`echo $ac_arg | sed -e 's,%%.*,,' -e 's,%,,'`
    AC_TRY_COMPILE([],[return 0;],
    [ac_cv_cflags_warn_all=`echo $ac_arg | sed -e 's,.*% *,,'`
    break])
done
  CFLAGS="$ac_save_CFLAGS"
  AC_LANG_RESTORE

The reason: some compilers will happily accept "-v" or "+w1" for
something not intended - they are valid but they do not do what
we want, to just enable additional warning-options.

With this scheme, I have reworked the existing macros that I do
use widely to pick up this detection, and furthermore I did change
them all to a common result-scheme - they add to CFLAGS or CXXFLAGS
when no output-variable has been given as an argument. Note that
each of the following files contains two macros, one for adding to
CFLAGS (AX_CFLAGS_...) and one for C++ flags (AX_CXXFLAGS_...)

http://ac-archive.sf.net/guidod/ax_cflags_warn_all.html
http://ac-archive.sf.net/guidod/ax_cflags_warn_all_ansi.html
http://ac-archive.sf.net/guidod/ax_cflags_strict_prototypes.html
http://ac-archive.sf.net/guidod/ax_cflags_no_writable_strings.html

hints? comments? objections? ;-)

-- cheers, guido                         http://ac-archive.sf.net




From MAILER-DAEMON Sun Jan 05 20:47:15 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VMJt-0004iy-00
	for mharc-autoconf@gnu.org; Sun, 05 Jan 2003 20:44:49 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VMJf-00049t-00
	for autoconf@gnu.org; Sun, 05 Jan 2003 20:44:36 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VMJ6-0003nr-00
	for autoconf@gnu.org; Sun, 05 Jan 2003 20:44:03 -0500
Received: from imap.gmx.net ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18VMJ1-0003dY-00
	for autoconf@gnu.org; Sun, 05 Jan 2003 20:43:55 -0500
Received: (qmail 26465 invoked by uid 0); 6 Jan 2003 01:43:53 -0000
Received: from pd9e80ed2.dip.t-dialin.net (HELO gmx.de) (217.232.14.210)
  by mail.gmx.net (mp013-rz3) with SMTP; 6 Jan 2003 01:43:53 -0000
Message-ID: <3E18DFBB.2050500@gmx.de>
Date: Mon, 06 Jan 2003 02:45:31 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: autoconf@gnu.org
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: ac-archive: ax_prefix_config_h.m4 - newest variant..
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 06 Jan 2003 01:44:47 -0000

The newest variant for making prefixed config.h defines is now up at
the sfnet ac-archive - I did just found a last bug, and after having
it used in a few projects of mine, I think it is now time to make
them available to the world ;-) ... all the other prefix_config_h
macros are now marked "obsolete".

The AX_PREFIX_CONFIG_H macro does now properly nest itself into the
usual autoconf scheme by adding the actual functionality to the
config.status script, and it does also get its input-header from
the var-name used by AM_CONFIG_HEADER. In most places, it should
be sufficient now to mention AX_PREFIX_CONFIG_H anywhere in your
configure.ac script :-)

http://ac-archive.sf.net/guidod/ax_prefix_config_h.html

Description (a copy from above's html link...)

this is a new variant from ac_prefix_config_    this one will use a
lowercase-prefix if  the config-define was starting with a lowercase-char,
e.g.
    #define const or #define restrict or #define off_t
    (and this one can live in another directory, e.g. testpkg/config.h
     therefore I decided to move the output-header to be the first arg)

takes the usual config.h generated header file; looks for each of the
generated "#define SOMEDEF" lines, and prefixes the defined name (ie.
makes it "#define PREFIX_SOMEDEF". The result is written to the output
config.header file. The PREFIX is converted to uppercase for the conversions.

default OUTPUT-HEADER = $PACKAGE-config.h
default PREFIX = $PACKAGE
default ORIG-HEADER, from AM_CONFIG_HEADER(config.h)

Your configure.ac script should contain both macros in this order, and
unlike the earlier variations of this prefix-macro it is okay to place
the AX_PREFIX_CONFIG_H call before the AC_OUTPUT invokation.

example:    AC_INIT(config.h.in)        # config.h.in as created by "autoheader"
    AM_INIT_AUTOMAKE(testpkg, 0.1.1)    # makes #undef VERSION and PACKAGE
    AM_CONFIG_HEADER(config.h)          # prep config.h from config.h.in
    AX_PREFIX_CONFIG_H(mylib/_config.h) # prep mylib/_config.h from it..
    AC_MEMORY_H                         # makes "#undef NEED_MEMORY_H"
    AC_C_CONST_H                        # makes "#undef const"
    AC_OUTPUT(Makefile)                 # creates the "config.h" now
                                        # and also mylib/_config.h

if the argument to AX_PREFIX_CONFIG_H would have been omitted then the
default outputfile would have been called simply "testpkg-config.h", but
even under the name "mylib/_config.h" it contains prefix-defines like
    #ifndef TESTPKG_VERSION
    #define TESTPKG_VERSION "0.1.1"
    #endif
    #ifndef TESTPKG_NEED_MEMORY_H
    #define TESTPKG_NEED_MEMORY_H 1
    #endif
    #ifndef _testpkg_const
    #define _testpkg_const _const
    #endif

    and this "mylib/_config.h" can be installed along with other
    header-files, which is most convenient when creating a shared
    library (that has some headers) where some functionality is
    dependent on the OS-features detected at compile-time. No
    need to invent some "mylib-confdefs.h.in" manually. :-)

Note that some AC_DEFINEs that end up in the config.h file are actually
self-referential - e.g. AC_C_INLINE, AC_C_CONST, and the AC_TYPE_OFF_T
say that they "will define inline|const|off_t if the system does not
do it by itself". You might want to clean up about these - consider
an extra mylib/conf.h that reads something like:

     #include <mylib/_config.h>
     #ifndef _testpkg_const
     #define _testpkg_const const
     #endif

and then start using _testpkg_const in the header files. That is also
a good thing to differentiate whether some library-user has starting
to take up with a different compiler, so perhaps it could read something
like this:

    #ifdef _MSC_VER
    #include <mylib/_msvc.h>
    #else
    #include <mylib/_config.h>
    #endif
    #ifndef _testpkg_const
    #define _testpkg_const const
    #endif





From MAILER-DAEMON Sun Jan 05 21:16:54 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VMor-00055W-00
	for mharc-autoconf@gnu.org; Sun, 05 Jan 2003 21:16:49 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VMon-0004yc-00
	for autoconf@gnu.org; Sun, 05 Jan 2003 21:16:45 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VMoc-0004ig-00
	for autoconf@gnu.org; Sun, 05 Jan 2003 21:16:37 -0500
Received: from pop.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18VMob-0004fJ-00
	for autoconf@gnu.org; Sun, 05 Jan 2003 21:16:33 -0500
Received: (qmail 18876 invoked by uid 0); 6 Jan 2003 02:16:31 -0000
Received: from pd9e83c47.dip.t-dialin.net (HELO gmx.de) (217.232.60.71)
  by mail.gmx.net (mp013-rz3) with SMTP; 6 Jan 2003 02:16:31 -0000
Message-ID: <3E18E761.9020200@gmx.de>
Date: Mon, 06 Jan 2003 03:18:09 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: autoconf@gnu.org
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: ac-archive: ac_sys_largefile and libraries...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 06 Jan 2003 02:16:47 -0000

In a discussion lately, I did observe something that may have
been interesting to many but got by unnoticed - the problems
of largefile support modern unix systems.

First, ALL unix98 system are REQUIRED to support largefile access
in their base installation:
        http://unix.org/version2/unix98fm.html
        http://unix.org/version2/whatsnew/lfs.html

However, the support scheme is quite different - linux has
adopted the scheme from solaris to stick to the old 32bit
off_t sizes, and only specific -Defines will make your
program to use the 64bit off_t largefile support of the
system.

On the other hand, freebsd and darwin have done better and
simply changed over to use 64bit off_t by default. Well, an
application writer can take advantage of a prepackaged
macro in autoconf AC_SYS_LARGEFILE that will ensure that
his/her program gets compiled with largefile support on
either unix98 flavours.

If you are currently up on a solaris or linux system (and
most likely you are), you can see the different results
by grepping into the symbol table of your binaries - the
unix98 standard mandates that all base utilities must be
compiled as largefile binaries:

$ objdump -T /bin/cp | grep seek
080490c4      DF *UND*  00000088  GLIBC_2.1   lseek64

$ objdump -T /usr/bin/gdb | grep seek
08161e00 g    DF .text  000001e9  Base        bfd_seek
08070944      DF *UND*  000000d1  GLIBC_2.0   fseek
08070b84      DF *UND*  0000003d  GLIBC_2.0   lseek

* The library problem ...

As you see, the AC_SYS_LARGEFILE call will make these
binaries to be linked with different symbols compiled
into the base libraries (glibc here). That is easily
achieved by specific forms in the header files of the
C library which boils down to

#ifdef _LARGEFILE_SOURCE
#define lseek lseek64
#endif

and the glibc maintainers have ensured that any call
to (32bit type) lseek will be converted into a call
to the actual lseek64, simply because the underlying
unix kernel uses 64bit fileoffsets natively, it's
just that some arguments have to be checked. In
effect, the library exports two lseek symbols:

$ objdump -T /lib/libc.so.6 | grep " lseek"
000bf9a0  w   DF .text  0000003d  GLIBC_2.0   lseek
000cba90  w   DF .text  00000088  GLIBC_2.1   lseek64

* Third party libraries....

While this sounds logical, how would you guide a
developer of a third-party library to support this
dual-mode off_t field. And how can autoconf support
it actually.

First of all, the AC_SYS_LARGEFILE macro is a bit
short-sighted - it does simply enable 64bit off_t
but it does so on either freebsd system where this
is native and on linux system where it is optional.
However, on linux system we want the 64bit variant
of library calls to be named slightly differently.

http://ac-archive.sf.net/guidod/ac_sys_largefile_sensitive.html
has been build on top of it to AC_DEFINE an extra
symbol called LARGEFILE_SENSITIVE which guides the
library maker to the knowledege that this system
is actually off_t/off64_t sensitive. In the header
file of his library, he may write now:

#if defined _LARGEFILE_SOURCE && defined LARGEFILE_SENSITIVE
#define my_seek my_seek64
#define my_open my_open64
#endif

An application linking to the library will now be
made to link with the *64 variants, and the library
itself will provide them if being compiled as a
largefile variant. If the application and library
are both in 32bit then they will also link correctly,
but when they mismatch... then the linkage will fail,
i.e.
    ld: my_open not found
and doing a grep on the system table of the library
will reveal a symbol my_open64.

* Combined exports...

this scheme can be extended however - when the library
sources detect a LARGEFILE_SENSITIVE system and that it
is being compiled as _LARGEFILE_SOURCE then it can
choose to export a catch-call symbol as well.

off_t my_lseek (int fd, off_t offs, int whence)
{ ..... }

#if defined _LARGEFILE_SOURCE && defined LARGEFILE_SENSITIVE
#undef my_lseek /* has been diverted to my_lseek64 */
long my_lseek (int fd, long offs, int whence)
{
     off_t off = my_lseek64 (fd, offs, whence);
     offs = off;
     if (offs != off) { errno=EOVERFLOW; return -1; }
     return offs;
}
#endif


* Conclusions....

Well, what do you want - the 32bit off_t in a largefile unix98
is definitly a bad choice from the beginning. It is always
questionable whether it is good choice to extend the lifetime
of this nuisiance. On the other hand, there is sometimes the
need to create and maintain a library that may be regarded as
a "base library" for many programs and which should therefore
support the ability to -Define an off_t type and size.

hints? comments? objections?

-- cheers, guido        example project: http://zziplib.sf.net




From MAILER-DAEMON Sun Jan 05 22:12:18 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VNfT-0003mN-00
	for mharc-autoconf@gnu.org; Sun, 05 Jan 2003 22:11:11 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VNfE-0003LO-00
	for autoconf@gnu.org; Sun, 05 Jan 2003 22:10:56 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VNei-0002pm-00
	for autoconf@gnu.org; Sun, 05 Jan 2003 22:10:26 -0500
Received: from pop.gmx.net ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18VNeL-0002Qp-00
	for autoconf@gnu.org; Sun, 05 Jan 2003 22:10:01 -0500
Received: (qmail 20001 invoked by uid 0); 6 Jan 2003 03:03:19 -0000
Received: from pd9e83c47.dip.t-dialin.net (HELO gmx.de) (217.232.60.71)
  by mail.gmx.net (mp021-rz3) with SMTP; 6 Jan 2003 03:03:19 -0000
Message-ID: <3E18F259.8050306@gmx.de>
Date: Mon, 06 Jan 2003 04:04:57 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: autoconf@gnu.org
References: <3E18E761.9020200@gmx.de>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: ac-archive: ac_sys_largefile and libraries...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 06 Jan 2003 03:11:10 -0000

http://cvs.samba.org/cgi-bin/cvsweb/samba/source/configure.in?rev=1.383

The AC_SYS_LARGEFILE macro looks a bit outdated in comparison.

Note also the agreement of the large.file.summit people to use
-D_LARGEFILE_SOURCE as the primary define to enable 64bit off_t.





From MAILER-DAEMON Tue Jan 07 20:57:26 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Vwue-0005uH-00
	for mharc-autoconf@gnu.org; Tue, 07 Jan 2003 11:49:12 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VZjd-0004YB-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 11:04:17 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VZhb-0003rK-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 11:02:14 -0500
Received: from gnudist.gnu.org ([199.232.41.7])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18VYMU-0001kf-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 09:36:18 -0500
Received: from mail.gmx.net ([213.165.64.20])
	by gnudist.gnu.org with smtp (Exim 4.10.13)
	id 18VYA4-0003qr-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 09:23:28 -0500
Received: (qmail 16482 invoked by uid 0); 6 Jan 2003 10:45:35 -0000
Received: from pd9e83c47.dip.t-dialin.net (HELO gmx.de) (217.232.60.71)
  by mail.gmx.net (mp013-rz3) with SMTP; 6 Jan 2003 10:45:35 -0000
Message-ID: <3E195EB2.3080302@gmx.de>
Date: Mon, 06 Jan 2003 11:47:14 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Ville Laurikari <vlaurika@hutcs.cs.hut.fi>
References: <3E18DDE5.7020900@gmx.de> <20030106094527.GA28548@hutcs.cs.hut.fi>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: ac-archive: ax_cflags_<option> macros...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 06 Jan 2003 16:16:31 -0000

Ville Laurikari schrieb:
> I'm not on the autoconf list so excuse me for possibly repeating stuff
> that has been on the list already.  Also, if you want me to reply, CC
> your list replies to me as well.

there was nothing so far, and even the initial post included your
address, so it is most likely all responders will as well ;-)

> It's good that your macro names are prefixed with ax_ instead of ac_
> or a personal prefix (like guido_).  People feel that ax_ or ac_ -macros
> are "more official" than macros prefixed with just some guy's
> initials, and are more likely to use them.  But the ac_ prefix is
> reserved for official autoconf macros, right?
> 
> Some of my original macros have the ac_ prefix, and I later renamed
> them to have the vl_ prefix so as not to pollute the official macro
> namespace with my silly inventions.  I was flamed for this of course
> (I wasn't aware of just how widely used some of the macros had become
> and I made life a little harder for some people).   
> 

I hope that the "obsolete"-marking in the ac-archive can help in that
a bit, so that maintainance is supported (there as another post on
the autoconf ML about this).

As for the prefixes
a) the AC_ prefix should be reserved for macros shipped by "autoconf"
b) the AM_ prefix should be reserved for macros shipped by "automake"
c) the AX_ prefix is fine for every macro shipped with the "ac-archive"
b) a different prefix is good for something not shipped by a)b)c)

That ensures that there will never be two macros with the same name
and different sources - and which could possibly shadow each other
for executions of autoconf or aclocal or acinclude tools - and which
would in turn make for hard-to-find bugs when their implementation
differs slightly.

It was utterly correct to rename your macro from AC_ to something
different, since it could have been really that autoconf might
ship a similar macro later on. Well, renaming without tools that
automate an update-process, hmm, it must be a PITA, but it was
necessary IMO anyway. It's probably not needed again ;-) and now
everyone submitting an AC_-macro to me would be hinted to rename
it please into an AX_-macro for inclusion into the ac-archive :-)=)

thanks, have fun, guido                    http://ac-archive.sf.net
p.s. sadly, I can not make that last a strict rules, since I am not
in the ruling over the gnuorg ac-archive - in fact Peter has thrown
me out about a year ago, he does not inform me about changes, I can
not update macros that I receive directly into the savannah cvs, the
mailing process is always weeks in delay with him making the gnuorg
ac-archive somewhat late in comparison, and new people might only
get to know the rules of the gnuorg ac-archive since Peter broke
his promise to put up a crosslink from the gnuorg ac-archive to the
sfnet branch, and the autoconf homepage only has a link to the
gnuorg branch and not the sfnet branch - well, life ain't easy ;-)






From MAILER-DAEMON Tue Jan 07 22:50:37 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18W6vF-000147-00
	for mharc-autoconf@gnu.org; Tue, 07 Jan 2003 22:30:29 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18W6Zb-0004zY-00
	for autoconf@gnu.org; Tue, 07 Jan 2003 22:08:07 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18W6Yv-0004pf-00
	for autoconf@gnu.org; Tue, 07 Jan 2003 22:07:57 -0500
Received: from pop.gmx.net ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18W4fF-0003GD-00
	for autoconf@gnu.org; Tue, 07 Jan 2003 20:05:49 -0500
Received: (qmail 5345 invoked by uid 0); 8 Jan 2003 01:05:46 -0000
Received: from pd9e83d29.dip.t-dialin.net (HELO gmx.de) (217.232.61.41)
  by mail.gmx.net (mp018-rz3) with SMTP; 8 Jan 2003 01:05:46 -0000
Message-ID: <3E1B79D0.5080003@gmx.de>
Date: Wed, 08 Jan 2003 02:07:28 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
CC: autoconf@gnu.org
References: <3E18E761.9020200@gmx.de>
	<200301060943.h069hS328448@green.twinsun.com> <3E195771.6030506@gmx.de>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: ac-archive: ac_sys_largefile and libraries...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 08 Jan 2003 03:30:26 -0000

resending....

Guido Draheim schrieb:
> Paul Eggert schrieb:
> 
>> I don't think we should worry about supporting mixed 32- and 64-bit
>> off_t.  All sane programs will use plain 64-bit off_t on modern
>> platforms.  Libraries should be built in 64-bit mode as well.  If you
>> really need a 32-bit off_t library for some strange reason, build it
>> separately; that's easy to do.
>>
>> People who want to spend time building libraries that support both 32-
>> and 64-bit off_t simultaneously are obviously free to do so, but I
>> wouldn't make Autoconf any more complicated than it already is to help
>> them maintain their chimeras.
>>
> 
> The problem is in call-mismatch: the library is compiled as 64bit off_t
> which makes a call like "lseek (int,off_t,int)" to be actually an
> "lseek (int,off64_t,int)". When an application is compiled without the
> largefile-macro, it will be including the header files however as 32bit
> off_t, ie. the callframe is build as "lseek (int,off32_t,int)". That's
> a callframe mismatch between the shared library and user application.
> 
> A library maker should therefore put in efforts to defend itself from
> these problems - detecting a LARGEFILE_SENSITIVE system is therefore
> desperatly needed. If it makes any sense to support dualmode chimeras,
> well, that's verrry questionable indeed, I just wanted to show that
> it is possible as soon as one detects a LARGEFILE_SENSITIVE system ;-)
> 
> thanks, and have fun, guido              http://ac-archive.sf.net
> 




From MAILER-DAEMON Tue Jan 07 23:17:41 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Vwuk-0005uc-00
	for mharc-autoconf@gnu.org; Tue, 07 Jan 2003 11:49:18 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VZsu-0007Ep-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 11:13:52 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VZFr-0008KT-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 10:33:34 -0500
Received: from gnudist.gnu.org ([199.232.41.7])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18VYZP-0002s6-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 09:49:39 -0500
Received: from hutcs.cs.hut.fi ([130.233.192.7])
	by gnudist.gnu.org with esmtp (Exim 4.10.13)
	id 18VTtv-0007qx-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 04:50:31 -0500
Received: from vlaurika by hutcs.cs.hut.fi with local (Exim 4.10)
	id 18VTp2-0005w6-00; Mon, 06 Jan 2003 11:45:28 +0200
Date: Mon, 6 Jan 2003 11:45:28 +0200
From: Ville Laurikari <vlaurika@hutcs.cs.hut.fi>
To: Guido Draheim <guidod-2003-@gmx.de>
Message-ID: <20030106094527.GA28548@hutcs.cs.hut.fi>
References: <3E18DDE5.7020900@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3E18DDE5.7020900@gmx.de>
User-Agent: Mutt/1.4i
Sender: Ville Laurikari <vlaurika@cs.hut.fi>
cc: autoconf@gnu.org
Subject: Re: ac-archive: ax_cflags_<option> macros...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 06 Jan 2003 16:18:40 -0000

I'm not on the autoconf list so excuse me for possibly repeating stuff
that has been on the list already.  Also, if you want me to reply, CC
your list replies to me as well.

On Mon, Jan 06, 2003 at 02:37:41AM +0100, Guido Draheim wrote:

> It basically picks up the for-list scheme from AC_PROG_CC_STDC
> and extends it - the list items contain "%" separator marks
> that will mark breaks in the option strings. Each option to
> be tested has a _selector test_ - in other words, all compilers
> but one shall error-out on these selectors. The selector
> options however will not be part of the resulting option
> string for the feature that is wished for.
> 
> These selector-tests are usually derived from the different
> schemes that enable ansi-constraints for the compilers, now
> just have a look at the following example take up from
> ax_cflags_warn_all.m4
> 
>  AC_LANG_SAVE
>  AC_LANG_C
>  ac_save_CFLAGS="$CFLAGS"
> for ac_arg dnl
> in "-pedantic  % -Wall"       dnl   GCC
>    "-xstrconst % -v"          dnl Solaris C
>    "-std1      % -verbose -w0 -warnprotos" dnl Digital Unix
>    "-qlanglvl=ansi % -qsrcmsg -qinfo=all:noppt:noppc:noobs:nocnd" dnl AIX
>    "-ansi -ansiE % -fullwarn" dnl IRIX
>    "+ESlit     % +w1"         dnl HP-UX C
>    "-Xc        % -pvctl[,]fullmsg" dnl NEC SX-5 (Super-UX 10)

The comma was quoted in my macro against m4 confusing it for a macro
argument separator.  So this line should likely read:
     "-Xc        % -pvctl,fullmsg" dnl NEC SX-5 (Super-UX 10)

>    "-h conform % -h msglevel 2" dnl Cray C (Unicos)
>    #
> do CFLAGS="$ac_save_CFLAGS "`echo $ac_arg | sed -e 's,%%.*,,' -e 's,%,,'`
>    AC_TRY_COMPILE([],[return 0;],
>    [ac_cv_cflags_warn_all=`echo $ac_arg | sed -e 's,.*% *,,'`
>    break])
> done
>  CFLAGS="$ac_save_CFLAGS"
>  AC_LANG_RESTORE
> 
> The reason: some compilers will happily accept "-v" or "+w1" for
> something not intended - they are valid but they do not do what
> we want, to just enable additional warning-options.

Have there been problems with the way vl_prog_cc_warnings works?  At
least I haven't heard about it... :)

I'm not 100% sure now but I remember seeing a compiler somewhere that
basically ignored any options it didn't recognize (gave a warning
message about them though) and went ahead with whatever options it
found.  So even with selector tests we cannot be sure that some
compiler somewhere doesn't do something weird when being tested for
options.  This is why I decided to go with grepping version strings
first to avoid trouble since there are less chances of getting "cc -v"
to do something drastic than "cc -some -option -for -some -compiler".


> With this scheme, I have reworked the existing macros that I do
> use widely to pick up this detection, and furthermore I did change
> them all to a common result-scheme - they add to CFLAGS or CXXFLAGS
> when no output-variable has been given as an argument. Note that
> each of the following files contains two macros, one for adding to
> CFLAGS (AX_CFLAGS_...) and one for C++ flags (AX_CXXFLAGS_...)

Seems good to me.  Maybe we could go one step further and just
generate some generic compiler identifier string which could then be
used for anything, be it compiler options or something else...
AX_PROG_CC_FLAVOR or something, sort of like config.guess but for
compilers.   This could then be used in other macros to do the dirty
work, and there would be only one place to update when compilers
change.

It's good that your macro names are prefixed with ax_ instead of ac_
or a personal prefix (like guido_).  People feel that ax_ or ac_ -macros
are "more official" than macros prefixed with just some guy's
initials, and are more likely to use them.  But the ac_ prefix is
reserved for official autoconf macros, right?

Some of my original macros have the ac_ prefix, and I later renamed
them to have the vl_ prefix so as not to pollute the official macro
namespace with my silly inventions.  I was flamed for this of course
(I wasn't aware of just how widely used some of the macros had become
and I made life a little harder for some people).   


-- 
http://www.iki.fi/vl/




From MAILER-DAEMON Tue Jan 07 23:21:24 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Vwwk-00063M-00
	for mharc-autoconf@gnu.org; Tue, 07 Jan 2003 11:51:22 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VeYb-0003iS-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 16:13:13 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VeYR-0003Wq-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 16:13:05 -0500
Received: from adsl-155-94-87.mia.bellsouth.net ([68.155.94.87]
	helo=yourwebsite.com)
	by monty-python.gnu.org with smtp (Exim 4.10.13)	id 18VeYG-0003Ie-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 16:12:52 -0500
From: tvprojectorkit@aol.com
To: autoconf@gnu.org
Sender: tvprojectorkit@aol.com
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Mon, 6 Jan 2003 16:14:06 -0500
Message-Id: <E18VeYG-0003Ie-00@monty-python.gnu.org>
Subject: BIG SCREEN TV FOR PENNIES
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: tvprojectorkit@aol.com
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 06 Jan 2003 21:13:24 -0000

<p>THANK YOU SO MUCH FOR TAKING THE TIME TO READ THIS 
EMAIL! PLEASE CHECK OUT THIS WEBSITE FOR A COOL INVENTION THAT CAN TURN YOUR EVERYDAY TV INTO A MOVIE PROJECTOR</p>

<p>http://www.geocities.com/tvprojectorkit</p>

<p>HAVE YOU EVER DREAMED OF OWNING A BIG SCREEN 
TV BUT COULDN'T AFFORD THE HEFTY $1000.00+PLUS  
PRICE TAG?</p>

<p>WELL HERE IS YOUR CHANCE TO RECEIVE 
VALUABLE INFORMATION ON HOW TO BUILD YOUR OWN 
PROJECTOR THAT CAN TURN YOUR STANDARD TV 
INTO 
A PROJECTOR CAPABLE OF CREATING A SCREEN 
ANYWHERE FROM 
50 inches- 150 inches.</p> 

<p>WITHOUT OPENING OR DAMAGING YOUR EXISTING 
TV!</p>

<p>YOU MUST BE ASKING, HOW MUCH ARE THESE 
PLANS, THAT ARE WORTH THEIR WEIGHT IN 
GOLD?</p> 

<p>A SIMPLE  $.50  (fifty cents)</p> 

<p>FOR APPROXIAMATELY 14 PAGES OF 
DETAILED INFORMATION INCLUDING PICTURES TO 
ACHIEVING THIS.</p> 

<p>IF YOU ARE INTERESTED PLEASE VISIT MY 
OFFICIAL WEBSITE FOR THIS PRODUCT 
AT</p>

<p>http://www.geocities.com/tvprojectorkit</p>


<p>THANK YOU AGAIN FOR YOUR TIME!</p>



From MAILER-DAEMON Tue Jan 07 23:25:07 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Vwuy-0005vF-00
	for mharc-autoconf@gnu.org; Tue, 07 Jan 2003 11:49:32 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VZyL-0000ao-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 11:19:29 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VZwy-0008Px-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 11:18:06 -0500
Received: from gnudist.gnu.org ([199.232.41.7])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18VYY7-0002sb-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 09:48:19 -0500
Received: from hutcs.cs.hut.fi ([130.233.192.7])
	by gnudist.gnu.org with esmtp (Exim 4.10.13)
	id 18VUgA-0007Wg-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 05:40:22 -0500
Received: from vlaurika by hutcs.cs.hut.fi with local (Exim 4.10)
	id 18VUbJ-0006pN-00; Mon, 06 Jan 2003 12:35:21 +0200
Date: Mon, 6 Jan 2003 12:35:21 +0200
From: Ville Laurikari <vlaurika@hutcs.cs.hut.fi>
To: Guido Draheim <guidod-2003-@gmx.de>
Message-ID: <20030106103521.GA25673@hutcs.cs.hut.fi>
References: <3E18DDE5.7020900@gmx.de> <20030106094527.GA28548@hutcs.cs.hut.fi>
	<3E1959D8.4060504@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3E1959D8.4060504@gmx.de>
User-Agent: Mutt/1.4i
Sender: Ville Laurikari <vlaurika@cs.hut.fi>
cc: autoconf@gnu.org
Subject: Re: ac-archive: ax_cflags_<option> macros...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 06 Jan 2003 16:20:24 -0000


> That makes it not the best choice to limit oneself to a list of compiler
> names and choose the options by that - it is the very same scheme why
> autoconf people have always argued against using "case $host" sequences
> and have generic feature tests all around. In real life, well, we use
> a mixed style - but a real feature test should always be preferred, and
> I was hoping that the presented scheme is good enough in this respect.

Agreed.  Not only is your scheme more robust (it works on a larger set
of compilers with no changes), but the code is also a lot shorter and
more concise.  Bravo :-)

-- 
http://www.iki.fi/vl/




From MAILER-DAEMON Tue Jan 07 23:36:10 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Vwsh-0005oe-00
	for mharc-autoconf@gnu.org; Tue, 07 Jan 2003 11:47:11 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VZBz-0007vU-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 10:29:31 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VZ3j-0006iF-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 10:21:02 -0500
Received: from pop.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18VYwv-0005sL-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 10:13:57 -0500
Received: (qmail 20028 invoked by uid 0); 6 Jan 2003 10:14:39 -0000
Received: from pd9e83c47.dip.t-dialin.net (HELO gmx.de) (217.232.60.71)
  by mail.gmx.net (mp015-rz3) with SMTP; 6 Jan 2003 10:14:39 -0000
Message-ID: <3E195771.6030506@gmx.de>
Date: Mon, 06 Jan 2003 11:16:17 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: autoconf@gnu.org
References: <3E18E761.9020200@gmx.de>
	<200301060943.h069hS328448@green.twinsun.com>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: ac-archive: ac_sys_largefile and libraries...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 06 Jan 2003 15:34:40 -0000

Paul Eggert schrieb:
> I don't think we should worry about supporting mixed 32- and 64-bit
> off_t.  All sane programs will use plain 64-bit off_t on modern
> platforms.  Libraries should be built in 64-bit mode as well.  If you
> really need a 32-bit off_t library for some strange reason, build it
> separately; that's easy to do.
> 
> People who want to spend time building libraries that support both 32-
> and 64-bit off_t simultaneously are obviously free to do so, but I
> wouldn't make Autoconf any more complicated than it already is to help
> them maintain their chimeras.
> 

The problem is in call-mismatch: the library is compiled as 64bit off_t
which makes a call like "lseek (int,off_t,int)" to be actually an
"lseek (int,off64_t,int)". When an application is compiled without the
largefile-macro, it will be including the header files however as 32bit
off_t, ie. the callframe is build as "lseek (int,off32_t,int)". That's
a callframe mismatch between the shared library and user application.

A library maker should therefore put in efforts to defend itself from
these problems - detecting a LARGEFILE_SENSITIVE system is therefore
desperatly needed. If it makes any sense to support dualmode chimeras,
well, that's verrry questionable indeed, I just wanted to show that
it is possible as soon as one detects a LARGEFILE_SENSITIVE system ;-)

thanks, and have fun, guido              http://ac-archive.sf.net




From MAILER-DAEMON Tue Jan 07 23:37:49 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Vwth-0005qu-00
	for mharc-autoconf@gnu.org; Tue, 07 Jan 2003 11:48:13 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VZh0-0003hD-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 11:01:34 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VZZT-0002hp-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 10:53:49 -0500
Received: from pop.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18VZ6q-0007C3-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 10:24:12 -0500
Received: (qmail 8916 invoked by uid 0); 6 Jan 2003 10:24:53 -0000
Received: from pd9e83c47.dip.t-dialin.net (HELO gmx.de) (217.232.60.71)
  by mail.gmx.net (mp013-rz3) with SMTP; 6 Jan 2003 10:24:53 -0000
Message-ID: <3E1959D8.4060504@gmx.de>
Date: Mon, 06 Jan 2003 11:26:32 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Ville Laurikari <vlaurika@hutcs.cs.hut.fi>
References: <3E18DDE5.7020900@gmx.de> <20030106094527.GA28548@hutcs.cs.hut.fi>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: ac-archive: ax_cflags_<option> macros...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 06 Jan 2003 16:02:31 -0000

Ville Laurikari schrieb:
>>
>>The reason: some compilers will happily accept "-v" or "+w1" for
>>something not intended - they are valid but they do not do what
>>we want, to just enable additional warning-options.
> 
> 
> Have there been problems with the way vl_prog_cc_warnings works?  At
> least I haven't heard about it... :)
> 
> I'm not 100% sure now but I remember seeing a compiler somewhere that
> basically ignored any options it didn't recognize (gave a warning
> message about them though) and went ahead with whatever options it
> found.  So even with selector tests we cannot be sure that some
> compiler somewhere doesn't do something weird when being tested for
> options.  This is why I decided to go with grepping version strings
> first to avoid trouble since there are less chances of getting "cc -v"
> to do something drastic than "cc -some -option -for -some -compiler".
> 

Not quite ;-) ... but you weren't actually grepping version
strings since a lot of "cc" compilers out there do not say
anything to describe themselves ;-) .. just to state a
matter of fact *sigh*

> 
> 
>>With this scheme, I have reworked the existing macros that I do
>>use widely to pick up this detection, and furthermore I did change
>>them all to a common result-scheme - they add to CFLAGS or CXXFLAGS
>>when no output-variable has been given as an argument. Note that
>>each of the following files contains two macros, one for adding to
>>CFLAGS (AX_CFLAGS_...) and one for C++ flags (AX_CXXFLAGS_...)
> 
> 
> Seems good to me.  Maybe we could go one step further and just
> generate some generic compiler identifier string which could then be
> used for anything, be it compiler options or something else...
> AX_PROG_CC_FLAVOR or something, sort of like config.guess but for
> compilers.   This could then be used in other macros to do the dirty
> work, and there would be only one place to update when compilers
> change.

Yes, I was thinking about that too - with one exception. If you read
the icc documention (intel's linux c/c++ compiler) then you will note
that the latest incarnation has started to pick up long-options of
the same name as gcc long-options and the very same meaning. It can be
furthermore noted that there exist specialized compilers for some
embedded systems that are derivatives from another one - they would
however identify themselves as being a different breed, whereas
they would still share a lot of commandline options with its parenting
compiler.

That makes it not the best choice to limit oneself to a list of compiler
names and choose the options by that - it is the very same scheme why
autoconf people have always argued against using "case $host" sequences
and have generic feature tests all around. In real life, well, we use
a mixed style - but a real feature test should always be preferred, and
I was hoping that the presented scheme is good enough in this respect.

thanks, and have fun, guido                    http://ac-archive.sf.net





From MAILER-DAEMON Wed Jan 08 00:26:41 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VwxX-000674-00
	for mharc-autoconf@gnu.org; Tue, 07 Jan 2003 11:52:11 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VhgV-0002CU-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 19:33:35 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VhgJ-00022a-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 19:33:24 -0500
Received: from pop.gmx.net ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18VhgC-0001mZ-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 19:33:16 -0500
Received: (qmail 31165 invoked by uid 0); 7 Jan 2003 00:33:10 -0000
Received: from pd9e83c47.dip.t-dialin.net (HELO gmx.de) (217.232.60.71)
  by mail.gmx.net (mp020-rz3) with SMTP; 7 Jan 2003 00:33:10 -0000
Message-ID: <3E1A20A9.2020800@gmx.de>
Date: Tue, 07 Jan 2003 01:34:49 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: autoconf@gnu.org
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: test (and gmane)
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 07 Jan 2003 00:34:10 -0000

has gnu.org eaten our mails?

I know atleast of four mails that have been sent but not coming
back through the mail loop to me, nor do they pop up at gmane
within the last dozen hours. Pretty irritating that is... well,
atleast here's the link to gmane in case you have not come across
this greatest new thing on the internet in the last months...;-)

http://news.gmane.org/thread.php?group=gmane.comp.sysutils.autoconf.general

actually, who has started this one? the libtool mailinglist has
made it to comp.gnu which I think is much more logical...

http://news.gmane.org/thread.php?group=gmane.comp.gnu.libtool.general




From MAILER-DAEMON Wed Jan 08 01:08:05 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VwuG-0005tO-00
	for mharc-autoconf@gnu.org; Tue, 07 Jan 2003 11:48:48 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VZYM-0002bb-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 10:52:38 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VZSP-0001k6-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 10:46:31 -0500
Received: from gnudist.gnu.org ([199.232.41.7])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18VYZS-0002tC-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 09:49:42 -0500
Received: from alcor.twinsun.com ([198.147.65.9])
	by gnudist.gnu.org with esmtp (Exim 4.10.13)
	id 18VTs2-0007RH-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 04:48:34 -0500
Received: from green.twinsun.com ([192.54.239.71])
	by alcor.twinsun.com (8.12.1/8.12.1) with ESMTP id h069hSfn000264;
	Mon, 6 Jan 2003 01:43:28 -0800 (PST)
Received: from shade.twinsun.com (shade.twinsun.com [192.54.239.27])
	by green.twinsun.com (8.11.6+Sun/8.11.6) with SMTP id h069hS028452;
	Mon, 6 Jan 2003 01:43:28 -0800 (PST)
Received: from green.twinsun.com ([192.54.239.71])
 by shade.twinsun.com (SAVSMTP 3.0.0.44) with SMTP id M2003010601432731590
 ; Mon, 06 Jan 2003 01:43:27 -0800
Received: (from eggert@localhost)
	by green.twinsun.com (8.11.6+Sun/8.11.6) id h069hS328448;
	Mon, 6 Jan 2003 01:43:28 -0800 (PST)
Date: Mon, 6 Jan 2003 01:43:28 -0800 (PST)
From: Paul Eggert <eggert@twinsun.com>
Message-Id: <200301060943.h069hS328448@green.twinsun.com>
To: guidod-2003-@gmx.de
In-reply-to: <3E18E761.9020200@gmx.de> (guidod-2003-@gmx.de)
References: <3E18E761.9020200@gmx.de>
cc: autoconf@gnu.org
Subject: Re: ac-archive: ac_sys_largefile and libraries...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 06 Jan 2003 16:09:44 -0000

I don't think we should worry about supporting mixed 32- and 64-bit
off_t.  All sane programs will use plain 64-bit off_t on modern
platforms.  Libraries should be built in 64-bit mode as well.  If you
really need a 32-bit off_t library for some strange reason, build it
separately; that's easy to do.

People who want to spend time building libraries that support both 32-
and 64-bit off_t simultaneously are obviously free to do so, but I
wouldn't make Autoconf any more complicated than it already is to help
them maintain their chimeras.



From MAILER-DAEMON Wed Jan 08 01:11:26 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18VwuL-0005tZ-00
	for mharc-autoconf@gnu.org; Tue, 07 Jan 2003 11:48:53 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VZpT-0006KN-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 11:10:19 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VYwu-0005sG-00
	for autoconf@gnu.org; Mon, 06 Jan 2003 10:14:02 -0500
Received: from gnudist.gnu.org ([199.232.41.7])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18VYWe-0002tF-00; Mon, 06 Jan 2003 09:46:48 -0500
Received: from mx12.arcor-online.net ([151.189.8.88])
	by gnudist.gnu.org with esmtp (Exim 4.10.13)
	id 18VVXl-0008Vc-00; Mon, 06 Jan 2003 06:35:45 -0500
Received: from gareth (dialin-212-144-151-141.arcor-ip.net [212.144.151.141])
	by mx12.arcor-online.net (Postfix) with SMTP
	id 62CA81D090; Mon,  6 Jan 2003 12:32:39 +0100 (CET)
Message-ID: <3E19693D.5E4F@nexgo.de>
Date: Mon, 06 Jan 2003 12:32:13 +0100
From: Andreas Buening <andreas.buening@nexgo.de>
X-Mailer: Mozilla 2.02 [de] (OS/2; I)
MIME-Version: 1.0
To: Paul Eggert <eggert@twinsun.com>
References: <3E0250F2.1749@nexgo.de><3E070E3C.6AFC@nexgo.de>
	<200212240024.gBO0O2b02755@green.twinsun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
cc: bug-automake@gnu.org
Subject: Re: mdate-sh
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 06 Jan 2003 16:11:20 -0000

Paul Eggert wrote:
> 
> > Date: Mon, 23 Dec 2002 14:23:08 +0100
> > From: Andreas Buening <andreas.buening@nexgo.de>
> 
> > +# Get the extended ls output of the root directory.
> > +set - x`eval $ls_command /`
> 
> The "eval " shouldn't be needed here, so it's better to remove it.
> 
> > +# Get the extended ls output of the file or directory.
> > +set - x`eval $ls_command "\"$save_arg1\""`
> 
> Better would be
> 
> set - x`eval "$ls_command \"\$save_arg1\""`
> 
> as this will handle arguments that contain metacharacters like space
> or '"'.

Thanks.

------------------------------------
--- old/mdate-sh	Tue Jul 17 06:00:36 2001
+++ new/mdate-sh	Mon Jan  6 12:05:14 2003
@@ -30,24 +30,27 @@
 LC_TIME=C
 export LC_TIME
 
-# Get the extended ls output of the file or directory.
+save_arg1="$1"
+
+# Find out how to get the extended ls output of a file or directory.
 # On HPUX /bin/sh, "set" interprets "-rw-r--r--" as options, so the "x" below.
 if ls -L /dev/null 1>/dev/null 2>&1; then
-  set - x`ls -L -l -d $1`
+  ls_command='ls -L -l -d'
 else
-  set - x`ls -l -d $1`
+  ls_command='ls -l -d'
 fi
-# The month is at least the fourth argument
-# (3 shifts here, the next inside the loop).
-shift
-shift
-shift
 
-# Find the month.  Next argument is day, followed by the year or time.
+# Get the extended ls output of the root directory.
+set - x`$ls_command /`
+
+# Find which argument is the month.
 month=
+command=
 until test $month
 do
   shift
+  # Add another shift to the command.
+  command="$command shift;"
   case $1 in
     Jan) month=January; nummonth=1;;
     Feb) month=February; nummonth=2;;
@@ -63,6 +66,28 @@
     Dec) month=December; nummonth=12;;
   esac
 done
+
+# Get the extended ls output of the file or directory.
+set - x`eval "$ls_command \"\$save_arg1\""`
+
+# Remove all preceding arguments
+eval $command
+
+# Get the month.  Next argument is day, followed by the year or time.
+case $1 in
+  Jan) month=January; nummonth=1;;
+  Feb) month=February; nummonth=2;;
+  Mar) month=March; nummonth=3;;
+  Apr) month=April; nummonth=4;;
+  May) month=May; nummonth=5;;
+  Jun) month=June; nummonth=6;;
+  Jul) month=July; nummonth=7;;
+  Aug) month=August; nummonth=8;;
+  Sep) month=September; nummonth=9;;
+  Oct) month=October; nummonth=10;;
+  Nov) month=November; nummonth=11;;
+  Dec) month=December; nummonth=12;;
+esac
 
 day=$2
 
------------------------------------


> Also, when you resubmit the patch, can you please submit a proper
> ChangeLog entry?  See the ChangeLog file for examples.  Thanks.

Sure. Unfortunately, I tend to forget this part. ;-)

ChangeLog:
2003-01-06  Andreas Buening  <andreas.buening@nexgo.de>

	* lib/mdate-sh: Find out which column of the ls -l output contains
	the month. Do not assume it is at least the fifth column.


Bye,
Andreas



From MAILER-DAEMON Wed Jan 08 07:40:51 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WFU5-00040s-00
	for mharc-autoconf@gnu.org; Wed, 08 Jan 2003 07:39:01 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WFRN-0001pR-00
	for autoconf@gnu.org; Wed, 08 Jan 2003 07:36:13 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WFPj-0001MF-00
	for autoconf@gnu.org; Wed, 08 Jan 2003 07:35:02 -0500
Received: from smtp012.mail.yahoo.com ([216.136.173.32])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18WF7x-0003Mm-00
	for autoconf@gnu.org; Wed, 08 Jan 2003 07:16:09 -0500
Received: from gate1.lci.net (HELO yahoo.com) (earnie?boyd@150.159.224.8 with
	plain)
	by smtp.mail.vip.sc5.yahoo.com with SMTP; 8 Jan 2003 12:16:08 -0000
Message-ID: <3E1C1686.6000401@yahoo.com>
Date: Wed, 08 Jan 2003 07:16:06 -0500
From: Earnie Boyd <earnie_boyd@yahoo.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Guido Draheim <guidod-2003-@gmx.de>
References: <3E1A20A9.2020800@gmx.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: test (and gmane)
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: autoconf@gnu.org
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 08 Jan 2003 12:38:59 -0000

Guido Draheim wrote:
> has gnu.org eaten our mails?
> 
> I know atleast of four mails that have been sent but not coming
> back through the mail loop to me, nor do they pop up at gmane
> within the last dozen hours. Pretty irritating that is... well,
> atleast here's the link to gmane in case you have not come across
> this greatest new thing on the internet in the last months...;-)
> 

Perhaps the forwarding account for gmane has been purged from the 
autoconf list.  For gmane to work, it must maintain an active account 
with the autoconf list.

> http://news.gmane.org/thread.php?group=gmane.comp.sysutils.autoconf.general
> 
> actually, who has started this one? the libtool mailinglist has
> made it to comp.gnu which I think is much more logical...
> 
> http://news.gmane.org/thread.php?group=gmane.comp.gnu.libtool.general
> 

So complain to the gmane maintainers they might do something, they might 
not.  Some interested fourth party (a single individual) creates the 
mail <-> news via a request to gmane.  Gmane administrators then create 
the link by joining the mail list.

Earnie.




From MAILER-DAEMON Wed Jan 08 09:41:23 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WHOU-0005sy-00
	for mharc-autoconf@gnu.org; Wed, 08 Jan 2003 09:41:22 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WHOR-0005oq-00
	for autoconf@gnu.org; Wed, 08 Jan 2003 09:41:19 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WHNv-0005Ma-00
	for autoconf@gnu.org; Wed, 08 Jan 2003 09:41:18 -0500
Received: from mail.polimi.it ([131.175.12.67])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18WHMO-0004fJ-00
	for autoconf@gnu.org; Wed, 08 Jan 2003 09:39:13 -0500
Received: from nero (paolob@nero.rett.polimi.it [131.175.6.122])
	h08Eco317580;	Wed, 8 Jan 2003 15:38:51 +0100 (MET)
Content-Type: text/plain;
  charset="us-ascii"
From: Paolo Bonzini <paolo.bonzini@polimi.it>
To: dkegel@ixiacom.com
Date: Wed, 8 Jan 2003 15:36:34 +0100
User-Agent: KMail/1.4.2
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200301081536.34952.paolo.bonzini@polimi.it>
cc: autoconf@gnu.org
Subject: libtool incompatible with current autoconf
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: bonzini@gnu.org
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 08 Jan 2003 14:41:20 -0000

You can autoupdate libltdl safely.  You can also extract it from a GNU=20
Smalltalk tarball, for example:

ftp://alpha.gnu.org/gnu/smalltalk/smalltalk-2.0.11.tar.gz

--
|_  _  _ __
|_)(_)| ),'
         `-'




From MAILER-DAEMON Wed Jan 08 22:41:49 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WTJC-0005gZ-00
	for mharc-autoconf@gnu.org; Wed, 08 Jan 2003 22:24:42 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WTCQ-0003xY-00
	for autoconf@gnu.org; Wed, 08 Jan 2003 22:17:42 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WTBv-0003jx-00
	for autoconf@gnu.org; Wed, 08 Jan 2003 22:17:12 -0500
Received: from n11z105207.broadband.ctm.net ([202.175.105.207]
	helo=deskway.com)	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18WT7O-0002fw-00
	for autoconf@gnu.org; Wed, 08 Jan 2003 22:12:31 -0500
From: "Chan Chi Pan" <chan@deskway.com>
To: autoconf@gnu.org
Content-Type: text/html;charset="US-ASCII"
Date: Thu, 9 Jan 2003 11:12:28 +0800
X-Priority: 3
X-Mailer: FoxMail 3.11 Release [cn]
Message-Id: <E18WT7O-0002fw-00@monty-python.gnu.org>
Subject: About DeskWay.
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 09 Jan 2003 03:24:40 -0000

<html>

<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta http-equiv="Content-Language" content="en-us">
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>DeskWay 1</title>
</head>

<body topmargin="0">

<div align="left">
  <table border="1" cellspacing="1" bordercolorlight="#BDC5FB" bordercolordark="#BDC5FB" width="653" height="1">
    <tr>
      <td width="647" height="19" bgcolor="#0066CC" bordercolor="#BDC5FB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>&nbsp;<font color="#FFFFFF">
        DeskWay 1.1---- </font></b><font color="#FFFFFF"><b style="mso-bidi-font-weight: normal"><span lang="EN-US">G</span></b></font><b style="mso-bidi-font-weight:
     normal"><span lang="EN-US"><font color="#FFFFFF">reat
            utility and an excellent companion to
            Windows.</font><span style="mso-spacerun: yes"><font color="#FFFFFF">&nbsp;</font>&nbsp;</span></span></b></td>
    </tr>
    <tr>
      <td width="642" height="1" valign="top" align="left" nowrap>
        <div>
          <div>
        <ul type="disc">
          <li class="MsoNormal" style="color:blue;mso-margin-top-alt:auto;mso-margin-bottom-alt:
     auto;mso-list:l0 level1 lfo1;tab-stops:list 36.0pt"><font size="3"><span class="150152616-20112002"><b><font color="#000080">Hello,</font></b><font color="#000080" size="3"><b>I'm
            Chan Chi Pan, the author of &quot;THE DESKWAY PROGRAM&quot;. I&nbsp;
            introducing you to my software ,After you try my program,</b></font></span>&nbsp;<span class="150152616-20112002"><font color="#000080"><b>
            I think&nbsp; you will agree it will save you time.&nbsp;</b></font></span>
            </font>
          </li>
          <li class="MsoNormal" style="color:blue;mso-margin-top-alt:auto;mso-margin-bottom-alt:
     auto;mso-list:l0 level1 lfo1;tab-stops:list 36.0pt"><b style="mso-bidi-font-weight:
     normal"><span lang="EN-US"><font color="#000080" size="3">DeskWay is a great
            utility and an excellent companion to
            Windows.<span style="mso-spacerun: yes">&nbsp;&nbsp;</span></font></span></b></li>
          <li class="MsoNormal" style="color:blue;mso-margin-top-alt:auto;mso-margin-bottom-alt:
     auto;mso-list:l0 level1 lfo1;tab-stops:list 36.0pt"><b><span lang="EN-US"><font color="#000080" size="3">DeskWay
            collects the most commonly used and
            repeated words for fast input.</font></span></b></li>
          <li class="MsoNormal" style="color:blue;mso-margin-top-alt:auto;mso-margin-bottom-alt:
     auto;mso-list:l0 level1 lfo1;tab-stops:list 36.0pt"><font color="#000080" size="3"><b><span lang="EN-US">With
            DeskWay you will not have to&nbsp; re-key the same words over and over.&nbsp;</span></b><span lang="EN-US">
            <o:p>
            </span></font></li>
          <li class="MsoNormal" style="color:blue;mso-margin-top-alt:auto;mso-margin-bottom-alt:
     auto;mso-list:l0 level1 lfo1;tab-stops:list 36.0pt"><font color="#000080" size="3"><b><span lang="EN-US">DeskWay
            allows you to type 10 to 100 times
            faster.</span></b><span lang="EN-US"> <o:p></span></font></li>
          <li class="MsoNormal" style="color:blue;mso-margin-top-alt:auto;mso-margin-bottom-alt:
     auto;mso-list:l0 level1 lfo1;tab-stops:list 36.0pt"><b><span lang="EN-US"><font color="#000080" size="3">DeskWay
            saves you money, because you are
            saving time.</font></span></b><span lang="EN-US">
            <font color="#000080" size="3">
            <o:p>&nbsp;</font></span>&nbsp; <font color="#000080" size="3"><span lang="EN-US"></o:p>
            </span></font></li>
        </ul>
          </div>
        </div>
        <p><img border="0" src="http://www.deskway.com/DeskWayHelp/DeskWaySceen9.gif"></p>
        <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
        <a href="http://www.deskway.com/DeskWayHelp.htm">Screenshots</a><font color="#000080" size="3"><span lang="EN-US">
            &nbsp;</span></font></p>
      </td>
    </tr>
    <tr>
      <td width="726" height="19" bgcolor="#BDC5FB"><b><font color="#FFFFFF">Free
        to use&nbsp;</font><font color="#FF0000">&nbsp;&nbsp; </font></b></td>
    </tr>
    <tr>
      <td width="647" height="208" nowrap valign="top">
        <div style="width: 613; height: 46">
          <div>
            <span class="150152616-20112002"><font color="#000080" size="4"><span style="LETTER-SPACING: 0px">File
            size: 638KB.&nbsp; It is Free to use.&nbsp;</span></font></span>
          </div>
          <div>
            <span class="150152616-20112002" style="letter-spacing: 0px">
            <font size="4"><font color="#000080">&nbsp;Click here to</font><font color="#FF0000">
            </font></font><a href="http://www.deskway.com/DeskWayHomePage/DeskWaySetup1.1.exe"><b><font color="#FF0066" size="4">Download
            Now</font></b></a><font color="#FF0066" size="4"><b>&nbsp;&nbsp;&nbsp;&nbsp;</b></font></span>
          </div>
          <p><span style="letter-spacing: 0"><font color="#000080" size="3">operating
          system: WinMe,Win2000,WinXP</font></span>
        </div>
        <div>
          <font size="3" color="#000080">Must&nbsp; update ODBC database drive
          In Win98,WinNT system.&nbsp;</font>
          <p>
          <span class="560324206-28112002"><font size="4"><span style="letter-spacing: 0"><font color="#000080">Welcome
          to Visit</font>&nbsp; <a href="http://www.deskway.com/">www.deskway.com</a></span></font></span>
        </div>
        <div>
          <p><span class="150152616-20112002"><font size="2"> Thanks and Warmest Regards!&nbsp;<br>
          &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Chan Chi Pan </font></span>
        </div>
      </td>
    </tr>
  </table>
</div>

</body>

</html>



From MAILER-DAEMON Thu Jan 09 15:02:02 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WisM-0002z0-00
	for mharc-autoconf@gnu.org; Thu, 09 Jan 2003 15:02:02 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WisJ-0002xo-00
	for autoconf@gnu.org; Thu, 09 Jan 2003 15:01:59 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Wigp-0000ij-00
	for autoconf@gnu.org; Thu, 09 Jan 2003 14:50:19 -0500
Received: from p508bdf51.dip.t-dialin.net ([80.139.223.81]
	helo=schnaeppchenwaren.de)
	by monty-python.gnu.org with smtp (Exim 4.10.13)	id 18WeBB-0007Bl-00
	for autoconf@gnu.org; Thu, 09 Jan 2003 10:01:09 -0500
From: "schnaeppchenwaren.de" <info@schnaeppchenwaren.de>
To: <autoconf@gnu.org>
Sender: "schnaeppchenwaren.de" <info@schnaeppchenwaren.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Date: Thu, 9 Jan 2003 15:58:25 +0100
Message-Id: <E18WeBB-0007Bl-00@monty-python.gnu.org>
Subject:  =?iso-8859-1?q?Schnaeppchen=2C_die_wirklich_g=FCnstig_sind=2E?=
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: "schnaeppchenwaren.de" <info@schnaeppchenwaren.de>
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 09 Jan 2003 20:02:00 -0000

Wir m�chten Sie herzlich willkommen hei�en zu unserem
Schn�ppchenNewsletter 01/2003.

Alles Gute im Neuen Jahr!

Wir haben wieder tolle Angebote f�r Sie.

===================================================
- Die Universalfernbedienung rapide gesenkt von 29.00 Euro auf 10.90 Euro.

Der absolute Renner:
- Das kleinste funkferngesteuerte Micro-Miniauto der Welt nur 18.00 Euro
statt 22.00 Euro.

Nicht zu verachten ist nat�rlich unser Musikinstrumentbereich. Nur
orginall von Casio. Alles mu� weg!
Hammer Preise, vorbeischauen lohnt. Preise auf alle Instrumente gesenkt!

Auch unsere Kosmetikabteilung d�rfte sehr interessant geworden sein f�r
unsere Damen.
Die Firma AA-Oceanic wird in vielen L�ndern, vor allem in den USA, sehr
gesch�tzt. Jetzt auch in Deutschland!
Testen Sie doch mit, bis zum 31.01.2003 gibt es keine Versandkosten auf
alle AA-Oceanic Kosmetika.
Unser OnlineShop wird Ihnen nat�rlich Versandkosten berechnen, aber wir
schreiben diese Ihnen wieder gut.
(Betrifft nur reine Kosmetikbestellungen!)

- Die g�nstigste Telefonkarte f�r Festnetz und Handy in die meisten L�nder
der Welt.
===================================================

Es findet sich bestimmt auch was f�r Sie.

Unsere Produktpalette wird st�ndig erweitert, also kommen Sie doch wieder.
http://www.schnaeppchenwaren.de

Surftip: Das Reiseportal http://www.yalix.de


Mit freundlichen Gr廻en
Ihr Schnaeppchenwaren Team

----------------------------------------------------------------------------
If this reached you by error, or you do not wish to receive this
information or type of information in the future, 
please send this message to unsubscribe@schnaeppchenwaren.de and you will
be taken off our list immediately and NEVER receive any emails from us.
----------------------------------------------------------------------------
Falls diese Nachricht Sie unerw�nscht erreicht hat, so bitten wir Sie
diese Nachricht an unsubscribe@schnaeppchenwaren.de zur�ckzusenden und Sie
werden nie 
wieder bel�stigt.
----------------------------------------------------------------------------





From MAILER-DAEMON Thu Jan 09 17:31:58 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WlDS-00071v-00
	for mharc-autoconf@gnu.org; Thu, 09 Jan 2003 17:31:58 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WkHL-00088j-00
	for autoconf@gnu.org; Thu, 09 Jan 2003 16:31:55 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WkH5-00081S-00
	for autoconf@gnu.org; Thu, 09 Jan 2003 16:31:50 -0500
Received: from ftp.ilog.fr ([81.80.162.195])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18WkH5-00081F-00
	for autoconf@gnu.org; Thu, 09 Jan 2003 16:31:39 -0500
Received: from laposte.ilog.fr (cerbere-qe0 [81.80.162.193])
	by ftp.ilog.fr (8.12.7/8.12.7) with ESMTP id h09LVcEl019204
	for <autoconf@gnu.org>; Thu, 9 Jan 2003 22:31:38 +0100 (MET)
Received: from honolulu.ilog.fr ([172.16.15.121])
	by laposte.ilog.fr (8.11.6/8.11.6) with ESMTP id h09LVaE07270;
	Thu, 9 Jan 2003 22:31:36 +0100 (MET)
Received: (from haible@localhost)
	by honolulu.ilog.fr (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id VAA09259;
	Thu, 9 Jan 2003 21:47:43 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15901.57326.950053.235725@honolulu.ilog.fr>
Date: Thu, 9 Jan 2003 21:47:42 +0100 (CET)
From: Bruno Haible <bruno@clisp.org>
To: autoconf@gnu.org
X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid
Subject: comma separated lists
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 09 Jan 2003 22:31:56 -0000

Hi,

AC_CHECK_HEADERS wants a whitespace separated list.
AC_CHECK_FUNCS wants a whitespace separated list.
AC_CHECK_DECLS wants a comma separated list.
AC_LIBSOURCES wants a comma separated list.

Why?! In m4 commas are used delimit things with different semantics, for
example the first and the second argument of a macro invocation, or the name
and the body of a macro. Whereas in m4 traditionally when things are
separated only by spaces you know that they will be treated the same way.

Such gratuitous syntactic unconsistencies make it harder to write autoconf
macros.

So I would suggest that you get back to the usual m4 syntax and change
AC_CHECK_DECLS and AC_LIBSOURCES to allow a whitespace separated list, and
no longer document that it also accepts a comma separated list.

Bruno



From MAILER-DAEMON Thu Jan 09 17:43:27 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WlOZ-00027T-00
	for mharc-autoconf@gnu.org; Thu, 09 Jan 2003 17:43:27 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WlOW-00026X-00
	for autoconf@gnu.org; Thu, 09 Jan 2003 17:43:24 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WlOL-00023m-00
	for autoconf@gnu.org; Thu, 09 Jan 2003 17:43:23 -0500
Received: from xinit.lug.org.uk ([195.92.253.3] helo=lug.org.uk)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18WlOK-00022Y-00
	for autoconf@gnu.org; Thu, 09 Jan 2003 17:43:12 -0500
Received: from andy   by lug.org.uk with local (Exim 3.33 #2)
	 id 18WlOH-0006ce-00 
	for autoconf@gnu.org; Thu, 09 Jan 2003 22:43:09 +0000
Date: Thu, 9 Jan 2003 22:43:09 +0000
From: Andy Smith <andy@strugglers.net>
To: autoconf@gnu.org
Message-ID: <20030109224309.GJ4603@lug.org.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Uptime: 29 days
X-URL: http://www.strugglers.net/~andy/
User-Agent: Mutt/1.5.1i
Sender: Andy Smith <andy@lug.org.uk>
Subject: AC_LIBOBJ
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 09 Jan 2003 22:43:25 -0000

Hi folks,

apologies if I have missed something obvious, but I don't seem to
understand how one should use AC_LIBOBJ?

I have taken the AC_FUNC_SNPRINTF macro from the ac-archive and put
it in acsite.m4.  This macro calls AC_LIBOBJ(snprintf) if the
system's snprintf is missing or broken.  In my project's src
directory I have snprintf.c which I want to compile if it is needed.

So, what do I need to put into the src/Makefile.am?  I thought I
just needed:

lib_LTLIBRARIES = libfoo.la

libfoo_la_SOURCES = foo.c foo.h foo_error.h foo_types.h foo_common.h

include_HEADERS = foo.h foo_error.h foo_types.h foo_common.h

libfoo_la_LIBADD = @LTLIBOBJS@

noinst_PROGRAMS = test test_debug
test_SOURCES = test.c
test_LDADD = libfoo.la @LIBOBJS@

# An easier-to-debug version of test

test_debug_SOURCES = test.c
test_debug_LDADD = libfoo.la @LIBOBJS@
test_debug_LDFLAGS = -static


But when I do "autoconf && automake" I get:

src/Makefile.am:9: @LTLIBOBJS@ seen but never set in `configure.in'
src/Makefile.am:13: @LIBOBJS@ seen but never set in `configure.in'
src/Makefile.am:18: @LIBOBJS@ seen but never set in `configure.in'

What am I missing?



From MAILER-DAEMON Fri Jan 10 02:38:54 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WtkI-00068M-00
	for mharc-autoconf@gnu.org; Fri, 10 Jan 2003 02:38:26 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18WtkD-0005vV-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 02:38:21 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Wtjy-0005P8-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 02:38:08 -0500
Received: from xinit.lug.org.uk ([195.92.253.3] helo=lug.org.uk)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Wtjt-0005C4-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 02:38:01 -0500
Received: from andy   by lug.org.uk with local (Exim 3.33 #2)
	 id 18Wtjp-0003eO-00 
	for autoconf@gnu.org; Fri, 10 Jan 2003 07:37:57 +0000
Date: Fri, 10 Jan 2003 07:37:57 +0000
From: Andy Smith <andy@strugglers.net>
To: autoconf@gnu.org
Message-ID: <20030110073757.GR4603@lug.org.uk>
References: <20030109224309.GJ4603@lug.org.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030109224309.GJ4603@lug.org.uk>
X-Uptime: 29 days
X-URL: http://www.strugglers.net/~andy/
User-Agent: Mutt/1.5.1i
Sender: Andy Smith <andy@lug.org.uk>
Subject: Re: AC_LIBOBJ
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 10 Jan 2003 07:38:24 -0000

On Thu, Jan 09, 2003 at 10:43:09PM +0000, Andy Smith wrote:
> Hi folks,
> 
> apologies if I have missed something obvious, but I don't seem to
> understand how one should use AC_LIBOBJ?

Sorry to reply to my own email, but I've discoevered two things:

Firstly, by accident, I got it working by doing "acinclude -I .".  I
am sure I used just "aclocal" before and it didn't work then, I
don't see why adding the "-I ." should make it work but oh well.

The second thing is, because I am using libtool it seems to want me
to use LTLIBOBJS instead for libfoo_la_LDADD line.  I understand why
I need to do this, but when I try that I get this during make:

make[5]: *** No rule to make target `@LTLIBOBJS@', needed by `libfoo.la'.  Stop.

So, please could someone point me to the documentation I am missing
out on?  I've read the autoconf, automake and libtool manuals and
all seem to say that it should be as simple as just using LTLIBOBJS.
I am using:

autoconf (GNU Autoconf) 2.53
automake (GNU automake) 1.6.3
ltmain.sh (GNU libtool) 1.4.2 (1.922.2.54 2001/09/11 03:33:37)




From MAILER-DAEMON Fri Jan 10 05:03:56 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Ww0n-0008Pd-00
	for mharc-autoconf@gnu.org; Fri, 10 Jan 2003 05:03:37 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Ww0a-0008Bv-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 05:03:24 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WvwV-0005MN-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 04:59:12 -0500
Received: from postfix4-2.free.fr ([213.228.0.176])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Wvu7-0004TY-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 04:56:43 -0500
Received: from localhost (nas-cbv-4-62-147-141-177.dial.proxad.net
	[62.147.141.177])	by postfix4-2.free.fr (Postfix) with ESMTP
	id C685BC19D; Fri, 10 Jan 2003 10:56:37 +0100 (CET)
Received: from adl by localhost with local (Exim 3.35 #1 (Debian))
	id 18Wvu8-0000nB-00; Fri, 10 Jan 2003 10:56:44 +0100
To: Andy Smith <andy@strugglers.net>
From: Alexandre Duret-Lutz <duret_g@lrde.epita.fr>
Mail-Followup-To: autoconf@gnu.org
X-Home-Page: http://gadl.free.fr/
X-GPG-Keyserver: http://pgp.mit.edu/
X-GPG-Fingerprint: FCA0 8615 0211 941A 2AB9  FA66 3859 C03B 2E23 6E47
X-Face: "Oky^obn}f(.QOV"RB7#1O@U^~rO6%5z5OrIm#nt{Fa4=cNRK@@e9rR$asU][QE[)7Pge8(
	kMx|^?!6wA~)0f1OmxROafMwBt9eDt(h[7F&qrs|Otp\ChrfJPH9A'&k$0@tl)1Lx
Date: Fri, 10 Jan 2003 10:56:43 +0100
In-Reply-To: <20030109224309.GJ4603@lug.org.uk> (Andy Smith's message of
 "Thu, 9 Jan 2003 22:43:09 +0000")
User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386-pc-linux-gnu)
References: <20030109224309.GJ4603@lug.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Message-ID: <2003-01-10-10-56-44+3050+duret_g@lrde.epita.fr>
X-Attribution: adl
Sender: Alexandre Duret-Lutz <duret_g@lrde.epita.fr>
cc: autoconf@gnu.org
Subject: Re: AC_LIBOBJ
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: autoconf@gnu.org
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 10 Jan 2003 10:03:36 -0000

>>> "Andy" == Andy Smith <andy@strugglers.net> writes:

[...]

 Andy> But when I do "autoconf && automake" I get:

 Andy> src/Makefile.am:9: @LTLIBOBJS@ seen but never set in `configure.in'
 Andy> src/Makefile.am:13: @LIBOBJS@ seen but never set in `configure.in'
 Andy> src/Makefile.am:18: @LIBOBJS@ seen but never set in `configure.in'

In the past Automake would not allow you to use these variables
before it sees AC_LIBOBJ, AC_LIBSOURCE, AC_LIBSOURCES, or
AC_SUBST([LIBOBJS]) and AC_SUBST([LTLIBOBJS]) in configure.in or
aclocal.m4.

Starting with Automake 1.7 you no longer have to do this,
because Automake sees that LIBOBJS and LTLIBOBJS are always
defined in the Autoconf guts.

In other words you could get rid of these diagnostics using
AC_SUBST([LIBOBJS]) and AC_SUBST([LTLIBOBJS]), or by upgrading
to a recent Automake.
-- 
Alexandre Duret-Lutz




From MAILER-DAEMON Fri Jan 10 09:11:17 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18WzhN-0001WT-00
	for mharc-autoconf@gnu.org; Fri, 10 Jan 2003 08:59:49 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Wzh9-0001TI-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 08:59:35 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18WzgW-00017M-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 08:58:56 -0500
Received: from cmailm3.svr.pol.co.uk ([195.92.193.19])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Wzfj-0000JU-00; Fri, 10 Jan 2003 08:58:07 -0500
Received: from modem-121.desitin.dialup.pol.co.uk ([62.136.89.121]
	helo=phekda.freeserve.co.uk)
	by cmailm3.svr.pol.co.uk with esmtp (Exim 3.35 #1)
	id 18Wzfh-0001dv-00; Fri, 10 Jan 2003 13:58:06 +0000
Received: from iolanthe.int.phekda.freeserve.co.uk
	([192.168.1.1] helo=phekda.freeserve.co.uk ident=rich)
	by phekda.freeserve.co.uk with esmtp (Exim 3.22 #1)
	id 18WzCK-0000kJ-00; Fri, 10 Jan 2003 13:27:44 +0000
Sender: rich@phekda.freeserve.co.uk
Message-ID: <3E1ECA50.BE218B69@phekda.freeserve.co.uk>
Date: Fri, 10 Jan 2003 13:27:44 +0000
From: Richard Dawe <rich@phekda.freeserve.co.uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: bug-automake@gnu.org, autoconf@gnu.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: Richard Dawe <rich@phekda.freeserve.co.uk>
cc: Tim Van Holder <tim.van.holder@pandora.be>
Subject: auto{conf,make} & DJGPP: DESTDIR
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 10 Jan 2003 13:59:47 -0000

Hello.

I've ported autoconf 2.57 and automake 1.7.2 to DJGPP, based on Tim van
Holder's work.

Unfortunately DESTDIR support is currently broken for DJGPP.
The reason is that the generated Makefiles do things like
$(DESTDIR)$(binprefix). $(binprefix) could be something like c:/djgpp/bin and
$(DESTDIR) could be, say, d:/put/packages/here/. So $(DESTDIR)$(binprefix)
becomes d:/put/packages/here/c:/djgpp/bin, which doesn't make sense.

DJGPP supports referring to c: as /dev/c. So one possible solution to this
problem is to ensure that $(prefix) and its derivatives are always mapped to
/dev/<letter>/ paths from <letter>: paths. But where would this mapping take
place? In autoconf alone? Or would both autoconf and automake require
modification?

Please CC me on any replies, because I'm not subscribed to autoconf or
bug-automake.

Thanks, regards,

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]



From MAILER-DAEMON Fri Jan 10 09:25:24 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18X050-0007r9-00
	for mharc-autoconf@gnu.org; Fri, 10 Jan 2003 09:24:14 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18X04i-0007Rk-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 09:23:56 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18X02b-0004na-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 09:21:46 -0500
Received: from smtp013.mail.yahoo.com ([216.136.173.57])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18X027-0003xw-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 09:21:15 -0500
Received: from gate1.lci.net (HELO yahoo.com) (earnie?boyd@150.159.224.8 with
	plain)
	by smtp.mail.vip.sc5.yahoo.com with SMTP; 10 Jan 2003 14:21:14 -0000
Message-ID: <3E1ED6D8.8080408@yahoo.com>
Date: Fri, 10 Jan 2003 09:21:12 -0500
From: Earnie Boyd <earnie_boyd@yahoo.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Richard Dawe <rich@phekda.freeserve.co.uk>
References: <3E1ECA50.BE218B69@phekda.freeserve.co.uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: Tim Van Holder <tim.van.holder@pandora.be>
cc: autoconf@gnu.org
cc: bug-automake@gnu.org
Subject: Re: auto{conf,make} & DJGPP: DESTDIR
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 10 Jan 2003 14:24:12 -0000

Richard Dawe wrote:
> Hello.
> 
> I've ported autoconf 2.57 and automake 1.7.2 to DJGPP, based on Tim van
> Holder's work.
> 
> Unfortunately DESTDIR support is currently broken for DJGPP.
> The reason is that the generated Makefiles do things like
> $(DESTDIR)$(binprefix). $(binprefix) could be something like c:/djgpp/bin and
> $(DESTDIR) could be, say, d:/put/packages/here/. So $(DESTDIR)$(binprefix)
> becomes d:/put/packages/here/c:/djgpp/bin, which doesn't make sense.
> 
> DJGPP supports referring to c: as /dev/c. So one possible solution to this
> problem is to ensure that $(prefix) and its derivatives are always mapped to
> /dev/<letter>/ paths from <letter>: paths. But where would this mapping take
> place? In autoconf alone? Or would both autoconf and automake require
> modification?
> 

That sounds as if it's a modification to the way you define prefix 
during the configure process.  ./configure --prefix=/dev/c/djgpp.  But 
that still sounds bothersome when combining DESTDIR.  Check out: 
http;//www.mingw.org/msys.shtml for a Minimal SYStem alternative that 
can cope with this problem.  Curious, what does DJGPP return for ``uname 
-s''?

Earnie.




From MAILER-DAEMON Fri Jan 10 10:16:09 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18X0sx-0000ik-00
	for mharc-autoconf@gnu.org; Fri, 10 Jan 2003 10:15:51 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18X0qm-0008WG-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 10:13:36 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18X0pd-0007rq-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 10:12:26 -0500
Received: from cmailm4.svr.pol.co.uk ([195.92.193.211])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18X0OH-0006vj-00; Fri, 10 Jan 2003 09:44:09 -0500
Received: from modem-15.hydrogen.dialup.pol.co.uk ([62.136.0.15]
	helo=phekda.freeserve.co.uk)
	by cmailm4.svr.pol.co.uk with esmtp (Exim 3.35 #1)
	id 18X0OF-0004DE-00; Fri, 10 Jan 2003 14:44:07 +0000
Received: from iolanthe.int.phekda.freeserve.co.uk
	([192.168.1.1] helo=phekda.freeserve.co.uk ident=rich)
	by phekda.freeserve.co.uk with esmtp (Exim 3.22 #1)
	id 18X0OC-0000wF-00; Fri, 10 Jan 2003 14:44:04 +0000
Sender: rich@phekda.freeserve.co.uk
Message-ID: <3E1EDC33.1C3A4D23@phekda.freeserve.co.uk>
Date: Fri, 10 Jan 2003 14:44:03 +0000
From: Richard Dawe <rich@phekda.freeserve.co.uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: Earnie Boyd <earnie_boyd@yahoo.com>
References: <3E1ECA50.BE218B69@phekda.freeserve.co.uk>
	<3E1ED6D8.8080408@yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: Tim Van Holder <tim.van.holder@pandora.be>
cc: autoconf@gnu.org
cc: bug-automake@gnu.org
Subject: Re: auto{conf,make} & DJGPP: DESTDIR
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 10 Jan 2003 15:15:48 -0000

Hello.

Earnie Boyd wrote:
> 
> Richard Dawe wrote:
> > Hello.
> >
> > I've ported autoconf 2.57 and automake 1.7.2 to DJGPP, based on Tim van
> > Holder's work.
> >
> > Unfortunately DESTDIR support is currently broken for DJGPP.
> > The reason is that the generated Makefiles do things like
> > $(DESTDIR)$(binprefix). $(binprefix) could be something like c:/djgpp/bin
> > and $(DESTDIR) could be, say, d:/put/packages/here/. So
> > $(DESTDIR)$(binprefix) becomes d:/put/packages/here/c:/djgpp/bin, which
> > doesn't make sense.
> >
> > DJGPP supports referring to c: as /dev/c. So one possible solution to this
> > problem is to ensure that $(prefix) and its derivatives are always mapped
> > to /dev/<letter>/ paths from <letter>: paths. But where would this mapping
> > take place? In autoconf alone? Or would both autoconf and automake require
> > modification?
> >
> 
> That sounds as if it's a modification to the way you define prefix
> during the configure process.  ./configure --prefix=/dev/c/djgpp.  But
> that still sounds bothersome when combining DESTDIR.

I thought about that. But it'd be nice to automagically protect autoconf
against the user specifying a path with <letter>: paths.

Are there other paths that get written into Makefiles and used when
installing, etc.?

(We also have /dev/env/DJDIR, which expands to the contents of DJDIR from the
environment at runtime. In fact, /dev/env/foo expands to foo from the
environment for all foo.)

> Check out: http;//www.mingw.org/msys.shtml for a Minimal SYStem alternative
> that can cope with this problem.

I'll check that out sometime.

> Curious, what does DJGPP return for ``uname -s''?

MS-DOS

Thanks, regards,

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]



From MAILER-DAEMON Fri Jan 10 11:04:09 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18X1cd-0001rj-00
	for mharc-autoconf@gnu.org; Fri, 10 Jan 2003 11:03:03 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18X1bm-0001CC-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 11:02:10 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18X1aH-0000Y2-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 11:00:38 -0500
Received: from iceage.anubex.com ([194.78.64.234])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18X1aC-0000DR-00; Fri, 10 Jan 2003 11:00:33 -0500
Received: from leeloo.anubex.com (unknown [192.168.14.202])
	by iceage.anubex.com (Anubex Mail Server) with ESMTP
	id 2B67C1C004F; Fri, 10 Jan 2003 17:00:24 +0100 (CET)
From: Tim Van Holder <tim.van.holder@pandora.be>
To: Richard Dawe <rich@phekda.freeserve.co.uk>
In-Reply-To: <3E1ECA50.BE218B69@phekda.freeserve.co.uk>
References: <3E1ECA50.BE218B69@phekda.freeserve.co.uk>
Content-Type: text/plain
Organization: 
Message-Id: <1042214547.14887.162.camel@leeloo>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.1 
Date: 10 Jan 2003 17:02:27 +0100
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
cc: bug-automake@gnu.org
Subject: Re: auto{conf,make} & DJGPP: DESTDIR
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 10 Jan 2003 16:03:00 -0000

On Fri, 2003-01-10 at 14:27, Richard Dawe wrote:
> Hello.
> 
> I've ported autoconf 2.57 and automake 1.7.2 to DJGPP, based on Tim van
> Holder's work.
> 
> Unfortunately DESTDIR support is currently broken for DJGPP.
> The reason is that the generated Makefiles do things like
> $(DESTDIR)$(binprefix). $(binprefix) could be something like c:/djgpp/bin and
> $(DESTDIR) could be, say, d:/put/packages/here/. So $(DESTDIR)$(binprefix)
> becomes d:/put/packages/here/c:/djgpp/bin, which doesn't make sense.
> 
> DJGPP supports referring to c: as /dev/c. So one possible solution to this
> problem is to ensure that $(prefix) and its derivatives are always mapped to
> /dev/<letter>/ paths from <letter>: paths. But where would this mapping take
> place? In autoconf alone? Or would both autoconf and automake require
> modification?
> 
> Please CC me on any replies, because I'm not subscribed to autoconf or
> bug-automake.
> 
> Thanks, regards,

I don't think this is autoconf/automake's job really.  There's plenty of
places where using dos style paths can break things (usually because the
':' in the drivespec gets seen as a list separator), and fixes for that
are usually disruptive (those that aren't tend to have been integrated
by now).  As such, any fixes for this would tend to be the domain of
the specific ports.
On DJGPP, prefixes should generally use /dev/env/DJDIR -style paths
(and our autoconf port defaults to /dev/env/DJDIR instead of /usr/local
for this reason as well).
AFAIK, there is only one platform really affected, and that's OS/2; the
two other main DOSish platforms (cygwin and djgpp) both have systems
to deal with path in a more POSIX way (/cygdrive/c/... and /dev/c/...
respectively).  Admittedly, it would be nice if (ports of) autoconf
complained if they saw a DOS-style path in a prefix var (and suggest
an alternative), but often those vars are user-defined, and
autoconf/configure can't automagically know when to complain or not.

-- 
Tim Van Holder <tim.van.holder@pandora.be>




From MAILER-DAEMON Fri Jan 10 16:57:08 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18X79I-0001qY-00
	for mharc-autoconf@gnu.org; Fri, 10 Jan 2003 16:57:08 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18X79F-0001po-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 16:57:05 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18X79E-0001pV-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 16:57:04 -0500
Received: from imap.gmx.net ([213.165.65.60] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18X77a-0001Wy-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 16:55:22 -0500
Received: (qmail 30287 invoked by uid 0); 10 Jan 2003 21:55:06 -0000
Received: from pd902f0c1.dip0.t-ipconnect.de (217.2.240.193)
  by mail.gmx.net (mp004-rz3) with SMTP; 10 Jan 2003 21:55:06 -0000
Date: Fri, 10 Jan 2003 23:03:33 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
X-X-Sender: peter@localhost.localdomain
To: Bruno Haible <bruno@clisp.org>
In-Reply-To: <15901.57326.950053.235725@honolulu.ilog.fr>
Message-ID: <Pine.LNX.4.44.0301102017540.29178-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: autoconf@gnu.org
Subject: Re: comma separated lists
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 10 Jan 2003 21:57:06 -0000

Bruno Haible writes:

> AC_CHECK_HEADERS wants a whitespace separated list.
> AC_CHECK_FUNCS wants a whitespace separated list.
> AC_CHECK_DECLS wants a comma separated list.
> AC_LIBSOURCES wants a comma separated list.
>
> Why?!

The advantage of comma-separated lists are that they can be processed
naturally as lists in m4, whereas the whitespace-separated lists are just
passed through as a blob of data, usually to shell loop.  Eventually, all
macros will use the comma style.

-- 
Peter Eisentraut   peter_e@gmx.net




From MAILER-DAEMON Fri Jan 10 23:04:14 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XCs8-0006VN-00
	for mharc-autoconf@gnu.org; Fri, 10 Jan 2003 23:03:48 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XCs4-0006Pt-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 23:03:44 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XCrq-00069o-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 23:03:31 -0500
Received: from xinit.lug.org.uk ([195.92.253.3] helo=lug.org.uk)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18XCri-0005lz-00
	for autoconf@gnu.org; Fri, 10 Jan 2003 23:03:22 -0500
Received: from andy   by lug.org.uk with local (Exim 3.33 #2)
	 id 18XCrX-0004ZS-00 
	for autoconf@gnu.org; Sat, 11 Jan 2003 04:03:11 +0000
Date: Sat, 11 Jan 2003 04:03:11 +0000
From: Andy Smith <andy@strugglers.net>
To: autoconf@gnu.org
Message-ID: <20030111040311.GT4603@lug.org.uk>
References: <20030109224309.GJ4603@lug.org.uk>
	<2003-01-10-10-56-44+3050+duret_g@lrde.epita.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2003-01-10-10-56-44+3050+duret_g@lrde.epita.fr>
X-Uptime: 29 days
X-URL: http://www.strugglers.net/~andy/
User-Agent: Mutt/1.5.1i
Sender: Andy Smith <andy@lug.org.uk>
Subject: Re: AC_LIBOBJ
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 04:03:46 -0000

On Fri, Jan 10, 2003 at 10:56:43AM +0100, Alexandre Duret-Lutz wrote:
> >>> "Andy" == Andy Smith <andy@strugglers.net> writes:
> 
> [...]
> 
>  Andy> But when I do "autoconf && automake" I get:
> 
>  Andy> src/Makefile.am:9: @LTLIBOBJS@ seen but never set in `configure.in'
>  Andy> src/Makefile.am:13: @LIBOBJS@ seen but never set in `configure.in'
>  Andy> src/Makefile.am:18: @LIBOBJS@ seen but never set in `configure.in'

[...]

> In other words you could get rid of these diagnostics using
> AC_SUBST([LIBOBJS]) and AC_SUBST([LTLIBOBJS]), or by upgrading
> to a recent Automake.

As mentioned in the previous email, I found I did not need to use
AC_SUBST([LIBOBJS]) and my Makefile.am lines that include @LIBOBJS@
now work correctly.

However, the libfoo_la_LIBADD line that needed @LTLIBOBJS@ doesn't
work (I get the above error).  I tried doing as you suggest and
added:

AC_SUBST([LTLIBOBJS])

to my configure.in, which made the diagnostic go away, however it
just replaces @LTLIBOBJS@ with nothing.  I need it to replace it
with snprintf.lo.

As a long shot I tried using @LIBOBJS@ on that line instead.  That
does actually works but gives dire warnings during build (as
expected) about how using libtool to link against object files that
end in .o is not portable.  The whole reason for doing this is
portability, so I don't really want to leave it there.

Where am I going wrong?  How does LTLIBOBJS get built from LIBOBJS
and how do I get that to happen since I'm unable to do it myself
(autoconf will exit with an error if I try to mention LIBOBJS
myself)?

If upgrading automake will fix this then I'm prepared to do it, but
it won't make me popular with my fellow developers.



From MAILER-DAEMON Sat Jan 11 04:23:13 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XHrF-0008ER-00
	for mharc-autoconf@gnu.org; Sat, 11 Jan 2003 04:23:13 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XHrC-00088r-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 04:23:10 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XHqP-0007Rf-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 04:22:22 -0500
Received: from alcor.twinsun.com ([198.147.65.9])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18XHpN-0007B6-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 04:21:17 -0500
Received: from green.twinsun.com ([192.54.239.71])
	by alcor.twinsun.com (8.12.1/8.12.1) with ESMTP id h0B9LCfn010459;
	Sat, 11 Jan 2003 01:21:12 -0800 (PST)
Received: from shade.twinsun.com (shade.twinsun.com [192.54.239.27])
	by green.twinsun.com (8.11.6+Sun/8.11.6) with SMTP id h0B9LB003469;
	Sat, 11 Jan 2003 01:21:11 -0800 (PST)
Received: from sic.twinsun.com ([192.54.239.17])
 by shade.twinsun.com (SAVSMTP 3.0.0.44) with SMTP id M2003011101211110087
 ; Sat, 11 Jan 2003 01:21:11 -0800
Received: (from eggert@localhost)
	by sic.twinsun.com (8.11.6+Sun/8.11.6) id h0B9LB503549;
	Sat, 11 Jan 2003 01:21:11 -0800 (PST)
Date: Sat, 11 Jan 2003 01:21:11 -0800 (PST)
From: Paul Eggert <eggert@twinsun.com>
Message-Id: <200301110921.h0B9LB503549@sic.twinsun.com>
To: guidod-2003-@gmx.de
In-reply-to: <3E195771.6030506@gmx.de> (guidod-2003-@gmx.de)
References: <3E18E761.9020200@gmx.de><3E195771.6030506@gmx.de>
cc: autoconf@gnu.org
Subject: Re: ac-archive: ac_sys_largefile and libraries...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 09:23:11 -0000

> Date: Mon, 06 Jan 2003 11:16:17 +0100
> From: Guido Draheim <guidod-2003-@gmx.de>
> 
> The problem is in call-mismatch: the library is compiled as 64bit off_t
> which makes a call like "lseek (int,off_t,int)" to be actually an
> "lseek (int,off64_t,int)". When an application is compiled without the
> largefile-macro,

Yes, that's the problem.  Don't mix 32-bit applications with 64-bit
libraries.  It's that simple.

It's just like you shouldn't mix x86 applications with sparc
libraries.  They're different flavors of executable code.  Don't try
to link them together.

> A library maker should therefore put in efforts to defend itself

I disagree.  Should an x86 library maker defend against being linked
to a sparc application?

Of course, I realize that one _can_ build mixed 32-and-64 bit apps --
just as one _can_ link x86 code to sparc code.  However, generally
speaking it's a bad idea, as it is much more trouble than it's worth.

I'll go even further and say that if you have an application that uses
file offsets and you don't invoke AC_SYS_LARGEFILE or its equivalent,
you're not serious about building portable code.  Apps that don't use
AC_SYS_LARGEFILE aren't worth worrying about.



From MAILER-DAEMON Sat Jan 11 05:00:38 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XIR0-0001ow-00
	for mharc-autoconf@gnu.org; Sat, 11 Jan 2003 05:00:10 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XIQj-0001E0-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 04:59:53 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XIQJ-0000tK-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 04:59:28 -0500
Received: from mail.gmx.net ([213.165.65.60])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18XIQ3-0000WF-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 04:59:12 -0500
Received: (qmail 5536 invoked by uid 0); 11 Jan 2003 09:59:09 -0000
Received: from pd9e82075.dip.t-dialin.net (HELO gmx.de) (217.232.32.117)
  by mail.gmx.net (mp003-rz3) with SMTP; 11 Jan 2003 09:59:09 -0000
Message-ID: <3E1FEB59.2080806@gmx.de>
Date: Sat, 11 Jan 2003 11:00:57 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Paul Eggert <eggert@twinsun.com>
References: <3E18E761.9020200@gmx.de>
	<200301060943.h069hS328448@green.twinsun.com> <3E195771.6030506@gmx.de>
	<200301110921.h0B9LB503549@sic.twinsun.com>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: ac-archive: ac_sys_largefile and libraries...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 10:00:08 -0000

Paul Eggert schrieb:
>>Date: Mon, 06 Jan 2003 11:16:17 +0100
>>From: Guido Draheim <guidod-2003-@gmx.de>
>>
>>The problem is in call-mismatch: the library is compiled as 64bit off_t
>>which makes a call like "lseek (int,off_t,int)" to be actually an
>>"lseek (int,off64_t,int)". When an application is compiled without the
>>largefile-macro,
> 
> 
> Yes, that's the problem.  Don't mix 32-bit applications with 64-bit
> libraries.  It's that simple.

Simple as that - it's a realworld problem. I have just submitted
a bug report to the zlib people (!!!!) as they are compiling their
library as 32bit off_t - and gzip itself gets compiled as a
largefile 64bit off_t application. Yes, and only by luck, they do
not use the gztell()/gzseek() pair which is affected.

$ objdump -T /usr/lib/libz.so | grep fopen
00000000      DF *UND*  00000099  GLIBC_2.1   fopen

$ objdump -T /usr/bin/gzip | grep open
08048c30      DF *UND*  0000003b  GLIBC_2.1   open64

$ grep off_t /usr/include/zconf.h /usr/include/zlib.h
/usr/include/zconf.h:#  include <sys/types.h> /* for off_t */
/usr/include/zconf.h:#  include <unistd.h>    /* for SEEK_* and off_t */
/usr/include/zconf.h:#  define z_off_t  off_t
/usr/include/zconf.h:#ifndef z_off_t
/usr/include/zconf.h:#  define  z_off_t long
/usr/include/zlib.h:ZEXTERN z_off_t ZEXPORT    gzseek OF((gzFile file,
/usr/include/zlib.h:                                  z_off_t offset, int whence));
/usr/include/zlib.h:ZEXTERN z_off_t ZEXPORT    gztell OF((gzFile file));

> 
> It's just like you shouldn't mix x86 applications with sparc
> libraries.  They're different flavors of executable code.  Don't try
> to link them together.

Well, the linker would tell you in this example - but it is a
little different with mixing libs/apps compiled for the same
system with the same compiler and the same compile-flags but
just with a different -Ddefine for off_t-size - the linker can
not know the difference, it does not even have _chance_ to
mark the libraries with different bits. They are just plain
identical (unless the library makers renames functions like
it is usually done, making up a gztell64/gzseek64 pair).

> 
> 
>>A library maker should therefore put in efforts to defend itself
> 
> 
> I disagree.  Should an x86 library maker defend against being linked
> to a sparc application?

wrong argument, see above.

> 
> Of course, I realize that one _can_ build mixed 32-and-64 bit apps --
> just as one _can_ link x86 code to sparc code.  However, generally
> speaking it's a bad idea, as it is much more trouble than it's worth.

That's an opinion - the problem is not whether we would like such
things to happen - they _are_ happening, and all I'm asking is for
means to "defend" oneself. That can be as simple as

#if defined LARGFILE_SENSITIVE && ! defined _LARGEFILE_SOURCE
#error using this library requires to enable largefile mode
#endif

> 
> I'll go even further and say that if you have an application that uses
> file offsets and you don't invoke AC_SYS_LARGEFILE or its equivalent,
> you're not serious about building portable code.  Apps that don't use
> AC_SYS_LARGEFILE aren't worth worrying about.
> 

Sometimes it's deeper - the application may simply be not aware that
some libraries make use of an off_t in their exported headers. For
example, I did just submit a bug report to the kde guys where such
thing exists in kio, and where I do also noticed that some plugins
are compiled 64bit-off_t while others are 32bit-off_t.

The end of the discussion can only be to change the compilation
behaviour globally - making 64bit off_t the default if that is
supported by the system, and dropping the settable off_t altogether.
So, if the system is not clean for 64bit off_t (like linux before
2.4 and glibc before 2.2) then do not allow a global redefine for
off_t, and let the application maker call explicitly the func64
symbols and off64_t type if that is supposed to be the intent.

Yes, I am aware that there might be compatibilty problems with
binary-only software, but that is only an administrative task.
The deeper problem is for the casual opensource programmers who
might simply be not aware of the problems he might run in when picking
up off_t _anywhere_ in the public headeras, it is quite probably that
he did never hear of  largefile linking problems, and to strengthen
this opinion, see the http://bugs.kde.org/show_bug.cgi?id=52843
that gets  assigned to stephan kulow himself which I would regard
as a very experienced programmer - and it still crept in.

cheers, guido                               http://ac-archive.sf.net





From MAILER-DAEMON Sat Jan 11 07:04:26 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XKHB-0000Pj-00
	for mharc-autoconf@gnu.org; Sat, 11 Jan 2003 06:58:09 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XKFo-0007rQ-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 06:56:44 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XKFT-0007fp-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 06:56:23 -0500
Received: from cmailm3.svr.pol.co.uk ([195.92.193.19])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18XKAm-0006Tr-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 06:51:32 -0500
Received: from modem-123.dextroamphetam.dialup.pol.co.uk ([62.136.90.123]
	helo=phekda.freeserve.co.uk)
	by cmailm3.svr.pol.co.uk with esmtp (Exim 3.35 #1)
	id 18XKAi-0002kQ-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 11:51:28 +0000
Received: from iolanthe.int.phekda.freeserve.co.uk
	([192.168.1.1] helo=phekda.freeserve.co.uk ident=rich)
	by phekda.freeserve.co.uk with esmtp (Exim 3.22 #1)
	id 18XJyP-0000eO-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 11:38:45 +0000
Sender: rich@phekda.freeserve.co.uk
Message-ID: <3E200245.1D4ADC87@phekda.freeserve.co.uk>
Date: Sat, 11 Jan 2003 11:38:45 +0000
From: Richard Dawe <rich@phekda.freeserve.co.uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: autoconf@gnu.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: autoconf 2.57: Typo in tests/atspecific.m4
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 11:57:58 -0000

Hello.

There's a typo in the description of AT_CHECK_CONFIGURE in
tests/atspecific.m4: SDOUT should be STDOUT. ChangeLog and patch below.

Thanks, regards,

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]

2003-01-11  Richard Dawe  <rich@phekda.freeserve.co.uk>

	*  tests/atspecific.m4: Fix typo in description
	of AT_CHECK_CONFIGURE.

--- /dev/c/develop/ports/orig/autoconf-2.57/tests/atspecific.m4	2002-10-31
13:57:36.000000000 +0000
+++ /dev/c/develop/ports/gnu.dev/autoconf-2.57/tests/atspecific.m4	2003-01-04
19:05:46.000000000 +0000
@@ -221,7 +221,7 @@ m4_define([AT_CHECK_AUTOHEADER],
 
 # AT_CHECK_CONFIGURE(END-COMMAND,
 #                    [EXIT-STATUS = 0],
-#                    [SDOUT = IGNORE], STDERR)
+#                    [STDOUT = IGNORE], STDERR)
 # --------------------------------------------
 # `abs_top_srcdir' is needed so that `./configure' finds install-sh.
 # Using --srcdir is more expensive.



From MAILER-DAEMON Sat Jan 11 07:08:47 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XKRT-0004V7-00
	for mharc-autoconf@gnu.org; Sat, 11 Jan 2003 07:08:47 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XKPg-0003QD-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 07:06:56 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XKFU-0007fx-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 06:56:24 -0500
Received: from cmailg3.svr.pol.co.uk ([195.92.195.173])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18XKAm-0006Tt-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 06:51:33 -0500
Received: from modem-123.dextroamphetam.dialup.pol.co.uk ([62.136.90.123]
	helo=phekda.freeserve.co.uk)
	by cmailg3.svr.pol.co.uk with esmtp (Exim 3.35 #1)
	id 18XKAj-00030E-00; Sat, 11 Jan 2003 11:51:30 +0000
Received: from iolanthe.int.phekda.freeserve.co.uk
	([192.168.1.1] helo=phekda.freeserve.co.uk ident=rich)
	by phekda.freeserve.co.uk with esmtp (Exim 3.22 #1)
	id 18XJkc-0000e7-00; Sat, 11 Jan 2003 11:24:30 +0000
Sender: rich@phekda.freeserve.co.uk
Message-ID: <3E1FFEEE.5A1B8BE5@phekda.freeserve.co.uk>
Date: Sat, 11 Jan 2003 11:24:30 +0000
From: Richard Dawe <rich@phekda.freeserve.co.uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: autoconf@gnu.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: Tim Van Holder <tim.van.holder@pandora.be>
Subject: autoconf 2.57 and DJGPP: $ENV{'TMPDIR'} may contain slashes
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 12:08:45 -0000

Hello.

$ENV{'TMPDIR'} may contain backward slashes in it under DJGPP. Below is a
ChangeLog and patch to make autom4te cope with this.

(I'm subscribed to the autoconf mailing list now.)

Thanks, regards,

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]

2003-01-11  Richard Dawe  <rich@phekda.freeserve.co.uk>

	*  lib/Autom4te/General.pm: $ENV{'TMPDIR'} may have backward slashes
	in it under DJGPP.

--- /dev/c/develop/ports/orig/autoconf-2.57/lib/Autom4te/General.pm 2002-10-16
06:38:50.000000000 +0000
+++ /dev/c/develop/ports/gnu.dev/autoconf-2.57/lib/Autom4te/General.pm
2003-01-05 13:06:56.000000000 +0000
@@ -324,6 +324,10 @@ sub mktmpdir ($)
   my ($signature) = @_;
   my $TMPDIR = $ENV{'TMPDIR'} || '/tmp';
 
+  # <rich@phekda.freeserve.co.uk>: Forward-slashify TMPDIR.
+  # TMPDIR may have backward slashes in it under DJGPP.
+  $TMPDIR =~ s,\\,/,g;
+
   # If mktemp supports dirs, use it.
   $tmp = `(umask 077 &&
            mktemp -d -q "$TMPDIR/${signature}XXXXXX") 2>/dev/null`;



From MAILER-DAEMON Sat Jan 11 07:09:37 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XKNA-0002Gp-00
	for mharc-autoconf@gnu.org; Sat, 11 Jan 2003 07:04:20 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XKN6-0002EP-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 07:04:16 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XKFJ-0007dl-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 06:56:14 -0500
Received: from cmailg3.svr.pol.co.uk ([195.92.195.173])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18XKAq-0006X6-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 06:51:36 -0500
Received: from modem-123.dextroamphetam.dialup.pol.co.uk ([62.136.90.123]
	helo=phekda.freeserve.co.uk)
	by cmailg3.svr.pol.co.uk with esmtp (Exim 3.35 #1)
	id 18XKAp-00034W-00; Sat, 11 Jan 2003 11:51:35 +0000
Received: from iolanthe.int.phekda.freeserve.co.uk
	([192.168.1.1] helo=phekda.freeserve.co.uk ident=rich)
	by phekda.freeserve.co.uk with esmtp (Exim 3.22 #1)
	id 18XK8P-0000ed-00; Sat, 11 Jan 2003 11:49:05 +0000
Sender: rich@phekda.freeserve.co.uk
Message-ID: <3E2004B1.E33D999A@phekda.freeserve.co.uk>
Date: Sat, 11 Jan 2003 11:49:05 +0000
From: Richard Dawe <rich@phekda.freeserve.co.uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: autoconf@gnu.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: Tim Van Holder <tim.van.holder@pandora.be>
Subject: autoconf 2.57 and DJGPP: POSIX::WEXITSTATUS doesn't work under DJGPP
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 12:04:18 -0000

Hello.

The DJGPP port of Perl 5.6.1 has a POSIX::WEXITSTATUS module that doesn't
work. It always seems to return 0. I don't know why - I haven't investigated
it yet. But this causes lib/Autom4te/General.pm to think that 'm4
--fatal-warnings' has succeeded sometimes, when it has failed.

The solution I adopted for the DJGPP port was to use the return value of
system >> 8 instead. This seems to work fine.

I see that POSIX::WEXITSTATUS is used, because it's portable. So this message
is a heads-up about the problem.

Thanks, regards,

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]



From MAILER-DAEMON Sat Jan 11 07:12:24 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XKQF-0003bi-00
	for mharc-autoconf@gnu.org; Sat, 11 Jan 2003 07:07:31 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XKNH-0002JB-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 07:04:27 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XKGx-0000JR-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 06:57:57 -0500
Received: from cmailg4.svr.pol.co.uk ([195.92.195.174])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18XKAo-0006Tx-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 06:51:34 -0500
Received: from modem-123.dextroamphetam.dialup.pol.co.uk ([62.136.90.123]
	helo=phekda.freeserve.co.uk)
	by cmailg4.svr.pol.co.uk with esmtp (Exim 3.35 #1)
	id 18XKAl-0002cA-00; Sat, 11 Jan 2003 11:51:31 +0000
Received: from iolanthe.int.phekda.freeserve.co.uk
	([192.168.1.1] helo=phekda.freeserve.co.uk ident=rich)
	by phekda.freeserve.co.uk with esmtp (Exim 3.22 #1)
	id 18XJpQ-0000eC-00; Sat, 11 Jan 2003 11:29:28 +0000
Sender: rich@phekda.freeserve.co.uk
Message-ID: <3E200018.66942551@phekda.freeserve.co.uk>
Date: Sat, 11 Jan 2003 11:29:28 +0000
From: Richard Dawe <rich@phekda.freeserve.co.uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: autoconf@gnu.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: Tim Van Holder <tim.van.holder@pandora.be>
Subject: autoconf 2.57 and DJGPP: Test for 'make -C' setting $(MAKE)
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 12:07:30 -0000

Hello.

The test to check whether 'make -C' sets $(MAKE) doesn't quite work if $(MAKE)
is an absolute DOS path like c:/djgpp/bin/make.exe. Below is a ChangeLog and
patch to cope with DOS paths in this test. We translate ':' in $(MAKE) to '_'.

Thanks, regards,

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]

2003-01-11  Richard Dawe  <rich@phekda.freeserve.co.uk>

	*  lib/autoconf/programs.m4: Translate colons, to cope
	with DOS file names, when constructing ${ac_make}.

--- /dev/c/develop/ports/orig/autoconf-2.57/lib/autoconf/programs.m4
2002-10-31 13:15:02.000000000 +0000
+++ /dev/c/develop/ports/gnu.dev/autoconf-2.57/lib/autoconf/programs.m4
2003-01-04 13:08:14.000000000 +0000
@@ -458,7 +460,7 @@ AN_MAKEVAR([MAKE], [AC_PROG_MAKE_SET])
 AN_PROGRAM([make], [AC_PROG_MAKE_SET])
 AC_DEFUN([AC_PROG_MAKE_SET],
 [AC_MSG_CHECKING([whether ${MAKE-make} sets \$(MAKE)])
-set dummy ${MAKE-make}; ac_make=`echo "$[2]" | sed 'y,./+-,__p_,'`
+set dummy ${MAKE-make}; ac_make=`echo "$[2]" | sed 'y,:./+-,___p_,'`
 AC_CACHE_VAL(ac_cv_prog_make_${ac_make}_set,
 [cat >conftest.make <<\_ACEOF
 all:



From MAILER-DAEMON Sat Jan 11 07:16:42 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XKVR-00089c-00
	for mharc-autoconf@gnu.org; Sat, 11 Jan 2003 07:12:53 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XKVK-00087H-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 07:12:46 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XKSp-0006Mg-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 07:10:13 -0500
Received: from cmailm1.svr.pol.co.uk ([195.92.193.18])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18XKAq-0006Wx-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 06:51:36 -0500
Received: from modem-123.dextroamphetam.dialup.pol.co.uk ([62.136.90.123]
	helo=phekda.freeserve.co.uk)
	by cmailm1.svr.pol.co.uk with esmtp (Exim 3.35 #1)
	id 18XKAm-0004Mo-00; Sat, 11 Jan 2003 11:51:32 +0000
Received: from iolanthe.int.phekda.freeserve.co.uk
	([192.168.1.1] helo=phekda.freeserve.co.uk ident=rich)
	by phekda.freeserve.co.uk with esmtp (Exim 3.22 #1)
	id 18XJwF-0000eJ-00; Sat, 11 Jan 2003 11:36:31 +0000
Sender: rich@phekda.freeserve.co.uk
Message-ID: <3E2001BF.B77708D6@phekda.freeserve.co.uk>
Date: Sat, 11 Jan 2003 11:36:31 +0000
From: Richard Dawe <rich@phekda.freeserve.co.uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: autoconf@gnu.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: Tim Van Holder <tim.van.holder@pandora.be>
Subject: autoconf 2.57 and DJGPP: IFS=: and constructing paths
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 12:12:47 -0000

Hello.

Some code in autoconf 2.57 constructs paths and then outputs them using echo.
Unfortunately this is done with IFS=: and there is not enough quoting to
ensure that DOS absolute paths are not split on the colon. Below is a
ChangeLog and patch for a fix.

I have seen the "# Absolute (can't be DOS-style, as IFS=:)" comment. This
problem is nothing to do with that, since I hit problems with IFS splitting
the path when the directories were relative.

I had a quick look at CVS and it seems that there is another place where IFS=:
is used now. It looks like that needs fixing too.

Thanks, regards,

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]

2003-01-11  Richard Dawe  <rich@phekda.freeserve.co.uk>

	*  lib/autoconf/status.m4: Quote constructed paths when IFS=:,
	so that DOS absolute paths are not split on the colon.

--- /dev/c/develop/ports/orig/autoconf-2.57/lib/autoconf/status.m4	2002-11-12
10:54:46.000000000 +0000
+++ /dev/c/develop/ports/gnu.dev/autoconf-2.57/lib/autoconf/status.m4
2003-01-04 18:15:58.000000000 +0000
@@ -523,14 +523,14 @@ for ac_file in : $CONFIG_HEADERS; do tes
       [[\\/$]]*)
          # Absolute (can't be DOS-style, as IFS=:)
          test -f "$f" || AC_MSG_ERROR([cannot find input file: $f])
-         echo $f;;
+         echo "$f";;
       *) # Relative
          if test -f "$f"; then
            # Build tree
-           echo $f
+           echo "$f"
          elif test -f "$srcdir/$f"; then
            # Source tree
-           echo $srcdir/$f
+           echo "$srcdir/$f"
          else
            # /dev/null tree
            AC_MSG_ERROR([cannot find input file: $f])
@@ -979,14 +976,14 @@ AC_PROVIDE_IFELSE([AC_PROG_INSTALL],
       [[\\/$]]*)
          # Absolute (can't be DOS-style, as IFS=:)
          test -f "$f" || AC_MSG_ERROR([cannot find input file: $f])
-         echo $f;;
+         echo "$f";;
       *) # Relative
          if test -f "$f"; then
            # Build tree
-           echo $f
+           echo "$f"
          elif test -f "$srcdir/$f"; then
            # Source tree
-           echo $srcdir/$f
+           echo "$srcdir/$f"
          else
            # /dev/null tree
            AC_MSG_ERROR([cannot find input file: $f])



From MAILER-DAEMON Sat Jan 11 09:39:32 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XMnL-00066j-00
	for mharc-autoconf@gnu.org; Sat, 11 Jan 2003 09:39:31 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XMnJ-00066X-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 09:39:29 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XMnH-00066L-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 09:39:28 -0500
Received: from eos.telenet-ops.be ([195.130.132.40])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18XMnH-00063F-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 09:39:27 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eos.telenet-ops.be (Postfix) with SMTP
	id 3319520E38; Sat, 11 Jan 2003 15:39:26 +0100 (CET)
Received: from dualzastai (d51520877.kabel.telenet.be [81.82.8.119])
	by eos.telenet-ops.be (Postfix) with ESMTP
	id 11643207D0; Sat, 11 Jan 2003 15:39:26 +0100 (CET)
From: "Tim Van Holder" <tim.van.holder@pandora.be>
To: <rich@phekda.freeserve.co.uk>, <autoconf@gnu.org>
Date: Sat, 11 Jan 2003 15:38:49 +0100
Message-ID: <000201c2b97f$27d682f0$2302a8c0@dualzastai>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <3E2001BF.B77708D6@phekda.freeserve.co.uk>
Subject: Re: autoconf 2.57 and DJGPP: IFS=: and constructing paths
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 14:39:30 -0000

> 2003-01-11  Richard Dawe  <rich@phekda.freeserve.co.uk>
> 
> 	*  lib/autoconf/status.m4: Quote constructed paths when IFS=:,
> 	so that DOS absolute paths are not split on the colon.

Unfortunately, this is one place in autoconf where dos paths simply
cannot be handled - IFS=: is NEEDED here, as $CONFIG_HEADERS has
entries of the form

   <header>[:<template>]

For example: config.h:config.hin

I tried adding logic here to cope, but IIRC I failed to make it work.





From MAILER-DAEMON Sat Jan 11 10:13:39 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XNKM-0004pT-00
	for mharc-autoconf@gnu.org; Sat, 11 Jan 2003 10:13:38 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XNKL-0004p8-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 10:13:37 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XNKJ-0004ox-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 10:13:36 -0500
Received: from cmailg2.svr.pol.co.uk ([195.92.195.172])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18XNKJ-0004os-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 10:13:35 -0500
Received: from modem-54.oxygen.dialup.pol.co.uk ([62.136.7.54]
	helo=phekda.freeserve.co.uk)
	by cmailg2.svr.pol.co.uk with esmtp (Exim 3.35 #1)
	id 18XNKH-0003r8-00; Sat, 11 Jan 2003 15:13:33 +0000
Received: from iolanthe.int.phekda.freeserve.co.uk
	([192.168.1.1] helo=phekda.freeserve.co.uk ident=rich)
	by phekda.freeserve.co.uk with esmtp (Exim 3.22 #1)
	id 18XNKC-00015c-00; Sat, 11 Jan 2003 15:13:28 +0000
Sender: rich@phekda.freeserve.co.uk
Message-ID: <3E203498.9514AA29@phekda.freeserve.co.uk>
Date: Sat, 11 Jan 2003 15:13:28 +0000
From: Richard Dawe <rich@phekda.freeserve.co.uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: Tim Van Holder <tim.van.holder@pandora.be>
References: <000201c2b97f$27d682f0$2302a8c0@dualzastai>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: autoconf 2.57 and DJGPP: IFS=: and constructing paths
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 15:13:37 -0000

Hello.

Tim Van Holder wrote:
> 
> > 2003-01-11  Richard Dawe  <rich@phekda.freeserve.co.uk>
> >
> >       *  lib/autoconf/status.m4: Quote constructed paths when IFS=:,
> >       so that DOS absolute paths are not split on the colon.
> 
> Unfortunately, this is one place in autoconf where dos paths simply
> cannot be handled - IFS=: is NEEDED here, as $CONFIG_HEADERS has
> entries of the form
> 
>    <header>[:<template>]
> 
> For example: config.h:config.hin
> 
> I tried adding logic here to cope, but IIRC I failed to make it work.

I think you misunderstand the patch.

It's not to cope with colons in filenames on input - it leaves the the
splitting of <header>[:<template>] alone. I can't see how that can be made to
work with DOS absolute paths.

After parsing <header>[:<template>], the code then may prefix the
header/template with the source directory, $srcdir.

If $srcdir contains a colon, then:

    IFS=: echo $srcdir/foo

will split the output on the colon. But if we quote it:

    IFS=: echo "$srcdir/foo"

then it won't be split.

The patch uses more quoting to protect the paths from IFS=: splitting. If
these paths are then split later using IFS=: then the patch is broken, but I
don't think that's the case.

Bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]



From MAILER-DAEMON Sat Jan 11 12:32:33 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XPTz-00073B-00
	for mharc-autoconf@gnu.org; Sat, 11 Jan 2003 12:31:43 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XPTt-00070F-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 12:31:37 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XPTe-0006pv-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 12:31:22 -0500
Received: from alcor.twinsun.com ([198.147.65.9])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18XPSW-00068p-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 12:30:12 -0500
Received: from green.twinsun.com ([192.54.239.71])
	by alcor.twinsun.com (8.12.1/8.12.1) with ESMTP id h0BHU9fn007300;
	Sat, 11 Jan 2003 09:30:09 -0800 (PST)
Received: from shade.twinsun.com (shade.twinsun.com [192.54.239.27])
	by green.twinsun.com (8.11.6+Sun/8.11.6) with SMTP id h0BHU9004913;
	Sat, 11 Jan 2003 09:30:09 -0800 (PST)
Received: from sic.twinsun.com ([192.54.239.17])
 by shade.twinsun.com (SAVSMTP 3.0.0.44) with SMTP id M2003011109300910525
 ; Sat, 11 Jan 2003 09:30:09 -0800
Received: (from eggert@localhost)
	by sic.twinsun.com (8.11.6+Sun/8.11.6) id h0BHU9506360;
	Sat, 11 Jan 2003 09:30:09 -0800 (PST)
Date: Sat, 11 Jan 2003 09:30:09 -0800 (PST)
From: Paul Eggert <eggert@twinsun.com>
Message-Id: <200301111730.h0BHU9506360@sic.twinsun.com>
To: guidod-2003-@gmx.de
In-reply-to: <3E1FEB59.2080806@gmx.de> (guidod-2003-@gmx.de)
References: <3E18E761.9020200@gmx.de>
	<200301060943.h069hS328448@green.twinsun.com> <3E195771.6030506@gmx.de>
	<200301110921.h0B9LB503549@sic.twinsun.com> <3E1FEB59.2080806@gmx.de>
cc: autoconf@gnu.org
Subject: Re: ac-archive: ac_sys_largefile and libraries...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 17:31:41 -0000

> Date: Sat, 11 Jan 2003 11:00:57 +0100
> From: Guido Draheim <guidod-2003-@gmx.de>
> 
> The end of the discussion can only be to change the compilation
> behaviour globally - making 64bit off_t the default if that is
> supported by the system, and dropping the settable off_t altogether.

I suppose we could change Autoconf so that largefile-mode is the
default, and you need to invoke a new macro AC_SYS_SMALLFILE if you
want 32-bit off_t applications on 64-bit off_t hosts.  That wouldn't
solve the problem in general, but it would solve it for programs that
use Autoconf.



From MAILER-DAEMON Sat Jan 11 12:37:32 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XPWd-0000AK-00
	for mharc-autoconf@gnu.org; Sat, 11 Jan 2003 12:34:27 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XPVb-00087n-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 12:33:23 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XPVB-0007q9-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 12:32:58 -0500
Received: from alcor.twinsun.com ([198.147.65.9])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18XPOS-0003wq-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 12:26:00 -0500
Received: from green.twinsun.com ([192.54.239.71])
	by alcor.twinsun.com (8.12.1/8.12.1) with ESMTP id h0BHPufn029287;
	Sat, 11 Jan 2003 09:25:56 -0800 (PST)
Received: from shade.twinsun.com (shade.twinsun.com [192.54.239.27])
	by green.twinsun.com (8.11.6+Sun/8.11.6) with SMTP id h0BHPu004896;
	Sat, 11 Jan 2003 09:25:56 -0800 (PST)
Received: from sic.twinsun.com ([192.54.239.17])
 by shade.twinsun.com (SAVSMTP 3.0.0.44) with SMTP id M2003011109255629640
 ; Sat, 11 Jan 2003 09:25:56 -0800
Received: (from eggert@localhost)
	by sic.twinsun.com (8.11.6+Sun/8.11.6) id h0BHPud06357;
	Sat, 11 Jan 2003 09:25:56 -0800 (PST)
Date: Sat, 11 Jan 2003 09:25:56 -0800 (PST)
From: Paul Eggert <eggert@twinsun.com>
Message-Id: <200301111725.h0BHPud06357@sic.twinsun.com>
To: guidod-2003-@gmx.de
In-reply-to: <3E1FEB59.2080806@gmx.de> (guidod-2003-@gmx.de)
References: <3E18E761.9020200@gmx.de><3E195771.6030506@gmx.de>
	<200301110921.h0B9LB503549@sic.twinsun.com> <3E1FEB59.2080806@gmx.de>
cc: autoconf@gnu.org
Subject: Re: ac-archive: ac_sys_largefile and libraries...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 17:34:26 -0000

> Date: Sat, 11 Jan 2003 11:00:57 +0100
> From: Guido Draheim <guidod-2003-@gmx.de>

> > It's just like you shouldn't mix x86 applications with sparc
> > libraries.  They're different flavors of executable code.  Don't try
> > to link them together.
> 
> Well, the linker would tell you in this example

Then fix your linker so that it also tells you about off_t linkage
screwups.  But don't contort every other tool in the toolchain to add
support for misconfigured programs.

> The end of the discussion can only be to change the compilation
> behaviour globally - making 64bit off_t the default if that is
> supported by the system, and dropping the settable off_t altogether.

Yes, that's the only sane solution.  And it's the solution we should
be striving for.  We should not waste our time trying to support mixed
32- and 64-bit chimeras.

One good way to head in that direction is to make 64-bit off_t the
default, with 32-bit off_t available only by explicit request.  POSIX
allows this behavior, and I don't see why more people don't do it that
way these days.

> let the application maker call explicitly the func64
> symbols and off64_t type if that is supposed to be the intent.

No, no, that is a misguided approach.  Applications and libraries
should be written portably, and should work regardless of the width of
off_t.  Applications should work even if off_t is 128 bits.  It is a
mistake to hardwire off64_t, fseek64, etc., into applications and
libraries.  They are meant only for temporary conversions in
closed-source applications (e.g., you have a 32-bit 3rd-party library
that you can't recompile).  They have little real utility in the
open-source world.



From MAILER-DAEMON Sat Jan 11 12:45:44 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XPgH-0002HO-00
	for mharc-autoconf@gnu.org; Sat, 11 Jan 2003 12:44:25 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XPfw-0001e4-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 12:44:04 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XPfo-0001Hs-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 12:43:56 -0500
Received: from imap.gmx.net ([213.165.65.60] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18XPfb-0000nN-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 12:43:43 -0500
Received: (qmail 1625 invoked by uid 0); 11 Jan 2003 17:43:41 -0000
Received: from pd9e82075.dip.t-dialin.net (HELO gmx.de) (217.232.32.117)
  by mail.gmx.net (mp007-rz3) with SMTP; 11 Jan 2003 17:43:41 -0000
Message-ID: <3E20583A.2080501@gmx.de>
Date: Sat, 11 Jan 2003 18:45:30 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Paul Eggert <eggert@twinsun.com>
References: <3E18E761.9020200@gmx.de>
	<200301060943.h069hS328448@green.twinsun.com> <3E195771.6030506@gmx.de>
	<200301110921.h0B9LB503549@sic.twinsun.com> <3E1FEB59.2080806@gmx.de>
	<200301111730.h0BHU9506360@sic.twinsun.com>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: ac-archive: ac_sys_largefile and libraries...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 17:44:24 -0000

Paul Eggert schrieb:
>>Date: Sat, 11 Jan 2003 11:00:57 +0100
>>From: Guido Draheim <guidod-2003-@gmx.de>
>>
>>The end of the discussion can only be to change the compilation
>>behaviour globally - making 64bit off_t the default if that is
>>supported by the system, and dropping the settable off_t altogether.
> 
> 
> I suppose we could change Autoconf so that largefile-mode is the
> default, and you need to invoke a new macro AC_SYS_SMALLFILE if you
> want 32-bit off_t applications on 64-bit off_t hosts.  That wouldn't
> solve the problem in general, but it would solve it for programs that
> use Autoconf.
> 

See the note about zlib - it might screw you up.

To reiterate in the matter - it is okay for an application (!!) to
enable largefile as default, it is even okay for a library to do
so as long as the usage is hidden in the .c sources itself - and
never exported in a header file (e.g. gtk does it right). The
problem only exists when off_t creeps into public headers usable
by third party applications, as most library makers are not
aware that off_t is *not* a fixed type. (I'll leave out applications
that install header files used by "plugins" here, same problem
there, it's in the public headers, included with another config.h).

Well, still I'd like to pick up your idea, just differently - as
to extend AC_TYPE_OFF_T to check whether the local system is a
largefile sensitive one - and issue a hint message on the user
screen and config log. Just a hint, not even a warning or some
such, just changing the answer

-checking for off_t... yes
+checking for off_t... yes (largefile sensitive)

A developer will surely see it and try to get the answer as to
what that actually means - and be more knowledgable afterwards
and ready to avoid the problemspace that is hidden in it.

WDYT, cheers, guido




From MAILER-DAEMON Sat Jan 11 13:08:37 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XQ3E-00040Y-00
	for mharc-autoconf@gnu.org; Sat, 11 Jan 2003 13:08:08 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XQ34-0003TR-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 13:07:58 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XQ2t-0002wK-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 13:07:51 -0500
Received: from alcor.twinsun.com ([198.147.65.9])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18XQ2n-0002Y4-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 13:07:41 -0500
Received: from green.twinsun.com ([192.54.239.71])
	by alcor.twinsun.com (8.12.1/8.12.1) with ESMTP id h0BI7bfn016710;
	Sat, 11 Jan 2003 10:07:37 -0800 (PST)
Received: from shade.twinsun.com (shade.twinsun.com [192.54.239.27])
	by green.twinsun.com (8.11.6+Sun/8.11.6) with SMTP id h0BI7b005082;
	Sat, 11 Jan 2003 10:07:37 -0800 (PST)
Received: from sic.twinsun.com ([192.54.239.17])
 by shade.twinsun.com (SAVSMTP 3.0.0.44) with SMTP id M2003011110073630728
 ; Sat, 11 Jan 2003 10:07:36 -0800
Received: (from eggert@localhost)
	by sic.twinsun.com (8.11.6+Sun/8.11.6) id h0BI7bM06606;
	Sat, 11 Jan 2003 10:07:37 -0800 (PST)
Date: Sat, 11 Jan 2003 10:07:37 -0800 (PST)
From: Paul Eggert <eggert@twinsun.com>
Message-Id: <200301111807.h0BI7bM06606@sic.twinsun.com>
To: guidod-2003-@gmx.de
In-reply-to: <3E20583A.2080501@gmx.de> (guidod-2003-@gmx.de)
References: <3E18E761.9020200@gmx.de>
	<200301060943.h069hS328448@green.twinsun.com> <3E195771.6030506@gmx.de>
	<200301110921.h0B9LB503549@sic.twinsun.com> <3E1FEB59.2080806@gmx.de>
	<200301111730.h0BHU9506360@sic.twinsun.com> <3E20583A.2080501@gmx.de>
cc: autoconf@gnu.org
Subject: Re: ac-archive: ac_sys_largefile and libraries...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 18:08:07 -0000

> Date: Sat, 11 Jan 2003 18:45:30 +0100
> From: Guido Draheim <guidod-2003-@gmx.de>
> 
> See the note about zlib - it might screw you up.

We cannot eliminate the possibility of screwups.  We can only make
them less likely, in the normal cases by ordinary developers.

The simplest way to do this is to make 64-bit off_t the default, and
to make people have to go out of their way to use 32-bit off_t.

> The problem only exists when off_t creeps into public headers usable
> by third party applications,

Not true.  The problem can exist even if the public headers export
only 'int'.  For example, libraries can export large-file-aware file
descriptors into non-large-file-aware applications.  And it can also
exist even if the public headers export only 'long'; ftell is an
example of this problem.

The problem of supporting mixed-mode applications is much more
complicated than what you seem to be suggesting.  We should not
suggest to developers that they take that path.  It is a long, hard,
and bug-prone road, and there's little payoff at the end.

We should instead tell people the much simpler solution: don't mix
object modules compiled in different modes.  This is easy to
understand, and it works.

> +checking for off_t... yes (largefile sensitive)
> 
> A developer will surely see it and try to get the answer as to
> what that actually means

I'm skeptical.  Most people don't read or understand those messages,
unless perhaps the compilation fails.

How about if we change AC_TYPE_OFF_T to invoke AC_SYS_LARGEFILE by
default?  If you want a small-file program, you'd have to invoke
AC_CHECK_TYPE(off_t, long) instead.  That might help a bit.

But I'm becoming more inclined to think that we should invoke
AC_SYS_LARGEFILE by default, unless the user explicitly says he wants
32-bit off_t.



From MAILER-DAEMON Sat Jan 11 13:31:12 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XQOP-0002EU-00
	for mharc-autoconf@gnu.org; Sat, 11 Jan 2003 13:30:01 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XQNz-0001hQ-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 13:29:35 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XQNe-0001CE-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 13:29:24 -0500
Received: from mail.gmx.net ([213.165.65.60])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18XQNX-00016g-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 13:29:07 -0500
Received: (qmail 21118 invoked by uid 0); 11 Jan 2003 18:29:06 -0000
Received: from pd9e82075.dip.t-dialin.net (HELO gmx.de) (217.232.32.117)
  by mail.gmx.net (mp003-rz3) with SMTP; 11 Jan 2003 18:29:06 -0000
Message-ID: <3E2062DE.9050608@gmx.de>
Date: Sat, 11 Jan 2003 19:30:54 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Paul Eggert <eggert@twinsun.com>
References: <3E18E761.9020200@gmx.de>
	<200301060943.h069hS328448@green.twinsun.com> <3E195771.6030506@gmx.de>
	<200301110921.h0B9LB503549@sic.twinsun.com> <3E1FEB59.2080806@gmx.de>
	<200301111730.h0BHU9506360@sic.twinsun.com> <3E20583A.2080501@gmx.de>
	<200301111807.h0BI7bM06606@sic.twinsun.com>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: ac-archive: ac_sys_largefile and libraries...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 18:29:59 -0000

Paul Eggert schrieb:
>>Date: Sat, 11 Jan 2003 18:45:30 +0100
>>From: Guido Draheim <guidod-2003-@gmx.de>
> 
>>The problem only exists when off_t creeps into public headers usable
>>by third party applications,
> 
> 
> Not true.  The problem can exist even if the public headers export
> only 'int'.  For example, libraries can export large-file-aware file
> descriptors into non-large-file-aware applications.  And it can also
> exist even if the public headers export only 'long'; ftell is an
> example of this problem.

I don't see the point - the largefile specification describes
that libc calls must check whether the filedescriptor has been
opened as an O_LARGEFILE one, and act accordingly. The only
thing is a new error-code, EOVERFLOW, that might result from
some operations done in the non-large-file-aware application.

As for ftell, again, it _must_ result in an EOVERFLOW if the
result does not fit - it does make for a callframe mismatch
or structsize mismatch resulting from differently sized
off_t types in the sharedlib and application code.

> 
> The problem of supporting mixed-mode applications is much more
> complicated than what you seem to be suggesting.  We should not
> suggest to developers that they take that path.  It is a long, hard,
> and bug-prone road, and there's little payoff at the end.
> 
> We should instead tell people the much simpler solution: don't mix
> object modules compiled in different modes.  This is easy to
> understand, and it works.

That's an administrative task - because the original author
can not quite decide how plugin modules get compiled...
$ objdump -T /usr/lib/kde3/*.so | grep " f*open"
in here, it is not that simple anymore - it is dependent on
humans an their skills and varying intents. The best way is
still to find a technical means which is not easy either.

> 
> 
>>+checking for off_t... yes (largefile sensitive)
>>
>>A developer will surely see it and try to get the answer as to
>>what that actually means
> 
> 
> I'm skeptical.  Most people don't read or understand those messages,
> unless perhaps the compilation fails.

if they ignore it, fine, but they've been warned - and when there
is a problem, people will check that one more closely :-)=)

> 
> How about if we change AC_TYPE_OFF_T to invoke AC_SYS_LARGEFILE by
> default?  If you want a small-file program, you'd have to invoke
> AC_CHECK_TYPE(off_t, long) instead.  That might help a bit.

It's a change in behaviour. Perhaps introduce AC_TYPE_OFF64_T
instead that #defines to off_t if the current system is neither
largefile-sensitive and has off_t available. The AC_SYS_LARGEFILE
is not used that often, just probably because people don't ever
noticed the problemspace of non-fixed-size off_t - with some
sister macro AC_TYPE_OFF64_T being found next to AC_TYPE_OFF_T,
well that might change things. Slightly.

> 
> But I'm becoming more inclined to think that we should invoke
> AC_SYS_LARGEFILE by default, unless the user explicitly says he 
 > wants 32-bit off_t.
> 

Hmmm, depracate ac_type_off_t and make up two new macros? See,
I don't like behaviour changes in the middle of life, it's a
pain for people who are about to upgrade their software tools
and have (silent!) changes in the behaviour of their software.

Atleast, I'm with you in the preference of using 64bit off_t
as soon as it is available, and somehow guide the developer
to go with it.

Anyway, what do other autoconf people think about this
matter? It seems we two have just differing views on how
easy it is to force people into the 64bit off_t world.

-- cheers, guido






From MAILER-DAEMON Sat Jan 11 13:43:17 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XQbF-0000N0-00
	for mharc-autoconf@gnu.org; Sat, 11 Jan 2003 13:43:17 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XQXn-0007ZX-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 13:39:43 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XQWK-0006bY-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 13:38:14 -0500
Received: from alcor.twinsun.com ([198.147.65.9])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18XQVo-0006DL-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 13:37:40 -0500
Received: from green.twinsun.com ([192.54.239.71])
	by alcor.twinsun.com (8.12.1/8.12.1) with ESMTP id h0BIbbfn004389;
	Sat, 11 Jan 2003 10:37:37 -0800 (PST)
Received: from shade.twinsun.com (shade.twinsun.com [192.54.239.27])
	by green.twinsun.com (8.11.6+Sun/8.11.6) with SMTP id h0BIba005192;
	Sat, 11 Jan 2003 10:37:36 -0800 (PST)
Received: from sic.twinsun.com ([192.54.239.17])
 by shade.twinsun.com (SAVSMTP 3.0.0.44) with SMTP id M2003011110373618213
 ; Sat, 11 Jan 2003 10:37:36 -0800
Received: (from eggert@localhost)
	by sic.twinsun.com (8.11.6+Sun/8.11.6) id h0BIbaX06887;
	Sat, 11 Jan 2003 10:37:36 -0800 (PST)
Date: Sat, 11 Jan 2003 10:37:36 -0800 (PST)
From: Paul Eggert <eggert@twinsun.com>
Message-Id: <200301111837.h0BIbaX06887@sic.twinsun.com>
To: guidod-2003-@gmx.de
In-reply-to: <3E2062DE.9050608@gmx.de> (guidod-2003-@gmx.de)
References: <3E18E761.9020200@gmx.de>
	<200301060943.h069hS328448@green.twinsun.com> <3E195771.6030506@gmx.de>
	<200301110921.h0B9LB503549@sic.twinsun.com> <3E1FEB59.2080806@gmx.de>
	<200301111730.h0BHU9506360@sic.twinsun.com> <3E20583A.2080501@gmx.de>
	<200301111807.h0BI7bM06606@sic.twinsun.com> <3E2062DE.9050608@gmx.de>
cc: autoconf@gnu.org
Subject: Re: ac-archive: ac_sys_largefile and libraries...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 18:43:15 -0000

> Date: Sat, 11 Jan 2003 19:30:54 +0100
> From: Guido Draheim <guidod-2003-@gmx.de>

> > The problem can exist even if the public headers export only
> > 'int'.

> I don't see the point - the largefile specification describes
> that libc calls must check whether the filedescriptor has been
> opened as an O_LARGEFILE one, and act accordingly. The only
> thing is a new error-code, EOVERFLOW

The point is that older applications may not know about EOVERFLOW, or
may assume that a failure means that a file is not accessible, or
whatever.  The mismatch will break the program.  I've seen it happen.

> As for ftell, again, it _must_ result in an EOVERFLOW if the
> result does not fit

And old programs (reasonably) assume that ftell cannot fail under
ordinary circumstances, and break when it does fail.  The breakage
is just as real as callframe mismatch.

> > We should instead tell people the much simpler solution: don't mix
> > object modules compiled in different modes.  This is easy to
> > understand, and it works.
> 
> That's an administrative task

Yes, and it's a much easier administrative task than to tell
application and library authors about mixed-mode programs.  Mixed-mode
programs are a mistake, regardless of whether you consider them to be
an administrative task or a technical task.  For free software,
mixed-mode is way too-much work for way too-little benefit.

For closed software, mixed-mode makes more technical sense in some
cases; but Autoconf maintainers shouldn't waste their time supporting
features that are useful only for closed software.

> Perhaps introduce AC_TYPE_OFF64_T

That is not a good name, because that should define off64_t, and the
whole point is to avoid the use of off64_t entirely.



From MAILER-DAEMON Sat Jan 11 13:46:16 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XQdw-00033N-00
	for mharc-autoconf@gnu.org; Sat, 11 Jan 2003 13:46:04 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XQbu-0001M2-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 13:43:58 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XQbp-0001Co-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 13:43:56 -0500
Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18XQY8-0007gR-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 13:40:04 -0500
Received: (qmail 28180 invoked by uid 0); 11 Jan 2003 18:40:01 -0000
Received: from pd902f095.dip0.t-ipconnect.de (217.2.240.149)
  by mail.gmx.net (mp023-rz3) with SMTP; 11 Jan 2003 18:40:01 -0000
Date: Sat, 11 Jan 2003 19:49:11 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
X-X-Sender: peter@localhost.localdomain
To: autoconf@gnu.org
Message-ID: <Pine.LNX.4.44.0301111946250.29178-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Header guards for config.h
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 18:46:04 -0000

Would it make sense to have autoheader create header guards against double
inclusion into its output file?

-- 
Peter Eisentraut   peter_e@gmx.net




From MAILER-DAEMON Sat Jan 11 14:09:17 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XQy5-000782-00
	for mharc-autoconf@gnu.org; Sat, 11 Jan 2003 14:06:53 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XQwH-0006dr-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 14:05:01 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XQvp-0006FM-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 14:04:37 -0500
Received: from mail.gmx.net ([213.165.65.60])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18XQv2-0005ka-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 14:03:44 -0500
Received: (qmail 24388 invoked by uid 0); 11 Jan 2003 19:03:42 -0000
Received: from pd9e82075.dip.t-dialin.net (HELO gmx.de) (217.232.32.117)
  by mail.gmx.net (mp007-rz3) with SMTP; 11 Jan 2003 19:03:42 -0000
Message-ID: <3E206AFA.5090605@gmx.de>
Date: Sat, 11 Jan 2003 20:05:30 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Paul Eggert <eggert@twinsun.com>
References: <3E18E761.9020200@gmx.de>
	<200301060943.h069hS328448@green.twinsun.com> <3E195771.6030506@gmx.de>
	<200301110921.h0B9LB503549@sic.twinsun.com> <3E1FEB59.2080806@gmx.de>
	<200301111730.h0BHU9506360@sic.twinsun.com> <3E20583A.2080501@gmx.de>
	<200301111807.h0BI7bM06606@sic.twinsun.com> <3E2062DE.9050608@gmx.de>
	<200301111837.h0BIbaX06887@sic.twinsun.com>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: ac-archive: ac_sys_largefile and libraries...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 19:06:50 -0000

Paul Eggert schrieb:
>>Date: Sat, 11 Jan 2003 19:30:54 +0100
>>From: Guido Draheim <guidod-2003-@gmx.de>
> 
> 
>>>The problem can exist even if the public headers export only
>>>'int'.
>>
> 
>>I don't see the point - the largefile specification describes
>>that libc calls must check whether the filedescriptor has been
>>opened as an O_LARGEFILE one, and act accordingly. The only
>>thing is a new error-code, EOVERFLOW
> 
> 
> The point is that older applications may not know about EOVERFLOW, or
> may assume that a failure means that a file is not accessible, or
> whatever.  The mismatch will break the program.  I've seen it happen.
> 
> 
>>As for ftell, again, it _must_ result in an EOVERFLOW if the
>>result does not fit
> 
> 
> And old programs (reasonably) assume that ftell cannot fail under
> ordinary circumstances, and break when it does fail.  The breakage
> is just as real as callframe mismatch.

hmmm.

A.1.1.4 Holes in the Protection Mechanism

The following holes in the protection mechanism are discussed in other
sections of this document:

    * While a "small" application has a file open another "large" application
      can extend the file (see A.1.2.1 Offset Maximum).
    * The fcntl() function may inadvertently clear O_LARGEFILE (see A.3.1.1.1
      fcntl()).
    * The lseek() failure may result in corruption of log file or database
      (see A.2.1.1.6 fgetpos(), fseek(), ftell(), lseek()).
    * An open file description with a "large" offset maximum may be inherited
      by a "small" application (see A.1.2.2 Inheritance).

A.2.1.1.6 fgetpos(), fseek(), ftell(), lseek()

These functions will fail if the resulting file offset would exceed the
largest value that can be represented correctly in the related type which is
in use for the call, and will set errno to EOVERFLOW (permitted by PASC
Interpretation 1003.1-90 #75).

Programs typically, but incorrectly, fail to check the return value of these
functions, which renders the error return less useful. On the other hand,
returning an incorrect offset can result in serious malfunction as well.

 >>Perhaps introduce AC_TYPE_OFF64_T
 >
 >
 > That is not a good name, because that should define off64_t, and the
 > whole point is to avoid the use of off64_t entirely.
 >
Yes that was the point - it *should* declare off64_t, even on systems
that have only 32bit off_t and where there is no largefile support at
all. Those are pre-unix98 actually, since unix98-compatible systems
are required to have largefile support.


> 
> 
>>>We should instead tell people the much simpler solution: don't mix
>>>object modules compiled in different modes.  This is easy to
>>>understand, and it works.
>>
>>That's an administrative task
> 
> 
> Yes, and it's a much easier administrative task than to tell
> application and library authors about mixed-mode programs.  Mixed-mode
> programs are a mistake, regardless of whether you consider them to be
> an administrative task or a technical task.  For free software,
> mixed-mode is way too-much work for way too-little benefit.
> 
> For closed software, mixed-mode makes more technical sense in some
> cases; but Autoconf maintainers shouldn't waste their time supporting
> features that are useful only for closed software.
> 

I am coming to the conclusion to approach distro makers - the rpm
packaging script do currently chrpath the .so libraries atleast
(as they are usually installed in a DESTDIR staging area, and
libtool does relink them up there) - so, why not let those scripts
check for spurious instances of fopen/lseek and friends and warn
at them - so that libraries and modules are compiled 64bit always
(using the alternate symbols fopen64/lseek64 instead, ye know).

Perhaps... even let them check any other ELF binary around and
suggested to be packaged into an rpm (or any other packaging format).
That might get us rid of the problem altogether and with the help of
technical tools that will bark at anything not compiled 64bit-off_t.
That would have also detected the zlib to be 32bit-off_t and this
whole thread probably to have never existed since the problem would
only exist in theory (for software compiled from sources and get
into the bin areas) as any software of some importance would have
been checked at some point of getting compiled as largefile by
default - simply for the correlation that any mildly important
software gets to be distributed in a binary package at some point.

what about that one?






From MAILER-DAEMON Sat Jan 11 14:12:44 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XR3k-0001QG-00
	for mharc-autoconf@gnu.org; Sat, 11 Jan 2003 14:12:44 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XR3g-0001O5-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 14:12:40 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XR3e-0001NC-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 14:12:39 -0500
Received: from mail.gmx.net ([213.165.65.60])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18XR28-0001Be-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 14:11:04 -0500
Received: (qmail 15917 invoked by uid 0); 11 Jan 2003 19:11:02 -0000
Received: from pd9e82075.dip.t-dialin.net (HELO gmx.de) (217.232.32.117)
  by mail.gmx.net (mp008-rz3) with SMTP; 11 Jan 2003 19:11:02 -0000
Message-ID: <3E206CB2.9000100@gmx.de>
Date: Sat, 11 Jan 2003 20:12:50 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Peter Eisentraut <peter_e@gmx.net>
References: <Pine.LNX.4.44.0301111946250.29178-100000@localhost.localdomain>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: Header guards for config.h
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 19:12:41 -0000

Peter Eisentraut schrieb:
> Would it make sense to have autoheader create header guards against double
> inclusion into its output file?
> 

No. Do not include config.h from a header file, unless it is again the
only single wrapper around it to be included by the rest of your
software - and don't install it. There should no multiple include-config.h
around. Writing a wrapper might also solve your current problem as well ;-)

The reason: there have been problems with third-area compilations
to have their own config.h being somewhat differently, and people
do not notice it. To guard on it, use again AX_PREFIX_CONFIG_H and
shift dependencies on those prefixed symbols - that prefix-config.h
is guarded and in my opinion that makes sense.

-- cheers, guido                            hptt://ac-archive.sf.net




From MAILER-DAEMON Sat Jan 11 14:51:01 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XReY-0002kq-00
	for mharc-autoconf@gnu.org; Sat, 11 Jan 2003 14:50:46 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XRdx-0002AA-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 14:50:09 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XRdH-0001Pl-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 14:49:29 -0500
Received: from alcor.twinsun.com ([198.147.65.9])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18XRcp-0000mx-00
	for autoconf@gnu.org; Sat, 11 Jan 2003 14:48:59 -0500
Received: from green.twinsun.com ([192.54.239.71])
	by alcor.twinsun.com (8.12.1/8.12.1) with ESMTP id h0BJmtfn018190;
	Sat, 11 Jan 2003 11:48:56 -0800 (PST)
Received: from shade.twinsun.com (shade.twinsun.com [192.54.239.27])
	by green.twinsun.com (8.11.6+Sun/8.11.6) with SMTP id h0BJmt005405;
	Sat, 11 Jan 2003 11:48:55 -0800 (PST)
Received: from sic.twinsun.com ([192.54.239.17])
 by shade.twinsun.com (SAVSMTP 3.0.0.44) with SMTP id M2003011111485518407
 ; Sat, 11 Jan 2003 11:48:55 -0800
Received: (from eggert@localhost)
	by sic.twinsun.com (8.11.6+Sun/8.11.6) id h0BJmt606921;
	Sat, 11 Jan 2003 11:48:55 -0800 (PST)
Date: Sat, 11 Jan 2003 11:48:55 -0800 (PST)
From: Paul Eggert <eggert@twinsun.com>
Message-Id: <200301111948.h0BJmt606921@sic.twinsun.com>
To: guidod-2003-@gmx.de
In-reply-to: <3E206AFA.5090605@gmx.de> (guidod-2003-@gmx.de)
References: <3E18E761.9020200@gmx.de><3E195771.6030506@gmx.de>
	<200301110921.h0B9LB503549@sic.twinsun.com> <3E1FEB59.2080806@gmx.de>
	<200301111730.h0BHU9506360@sic.twinsun.com> <3E20583A.2080501@gmx.de>
	<200301111807.h0BI7bM06606@sic.twinsun.com> <3E2062DE.9050608@gmx.de>
	<200301111837.h0BIbaX06887@sic.twinsun.com> <3E206AFA.5090605@gmx.de>
cc: autoconf@gnu.org
Subject: Re: ac-archive: ac_sys_largefile and libraries...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 11 Jan 2003 19:50:44 -0000

> Date: Sat, 11 Jan 2003 20:05:30 +0100
> From: Guido Draheim <guidod-2003-@gmx.de>

>  >>Perhaps introduce AC_TYPE_OFF64_T
>  >
>  >
>  > That is not a good name, because that should define off64_t, and the
>  > whole point is to avoid the use of off64_t entirely.
>  >
> Yes that was the point - it *should* declare off64_t, even on systems
> that have only 32bit off_t and where there is no largefile support at
> all.

Sorry, I'm lost.  If programs should not use off64_t, why should
config.h define it?  And why define the type on a host that doesn't
actually support it?

It's better to avoid off64_t entirely in source code.

> why not let those scripts check for spurious instances of
> fopen/lseek and friends and warn at them - so that libraries and
> modules are compiled 64bit always (using the alternate symbols
> fopen64/lseek64 instead, ye know).

That sounds like a reasonable approach, yes.



From MAILER-DAEMON Sun Jan 12 10:45:51 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XkJ5-0007ly-00
	for mharc-autoconf@gnu.org; Sun, 12 Jan 2003 10:45:51 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XkIz-0007gl-00
	for autoconf@gnu.org; Sun, 12 Jan 2003 10:45:45 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XkIx-0007e3-00
	for autoconf@gnu.org; Sun, 12 Jan 2003 10:45:44 -0500
Received: from alcor.twinsun.com ([198.147.65.9])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18XkIw-0007Zr-00
	for autoconf@gnu.org; Sun, 12 Jan 2003 10:45:42 -0500
Received: from green.twinsun.com ([192.54.239.71])
	by alcor.twinsun.com (8.12.1/8.12.1) with ESMTP id h0CFjbfn023292;
	Sun, 12 Jan 2003 07:45:38 -0800 (PST)
Received: from shade.twinsun.com (shade.twinsun.com [192.54.239.27])
	by green.twinsun.com (8.11.6+Sun/8.11.6) with SMTP id h0CFjb006938;
	Sun, 12 Jan 2003 07:45:37 -0800 (PST)
Received: from sic.twinsun.com ([192.54.239.17])
 by shade.twinsun.com (SAVSMTP 3.0.0.44) with SMTP id M2003011207453615024
 ; Sun, 12 Jan 2003 07:45:36 -0800
Received: (from eggert@localhost)
	by sic.twinsun.com (8.11.6+Sun/8.11.6) id h0CFjai09017;
	Sun, 12 Jan 2003 07:45:36 -0800 (PST)
Date: Sun, 12 Jan 2003 07:45:36 -0800 (PST)
From: Paul Eggert <eggert@twinsun.com>
Message-Id: <200301121545.h0CFjai09017@sic.twinsun.com>
To: guidod-2003-@gmx.de
In-reply-to: <3E1A20A9.2020800@gmx.de> (guidod-2003-@gmx.de)
References: <3E1A20A9.2020800@gmx.de>
cc: autoconf@gnu.org
Subject: Re: test (and gmane)
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 12 Jan 2003 15:45:48 -0000

> Date: Tue, 07 Jan 2003 01:34:49 +0100
> From: Guido Draheim <guidod-2003-@gmx.de>
> 
> has gnu.org eaten our mails?

mail.gnu.org has recently redone the mail server and archive, and mail
now can take quite some time to get through it, presumably for
antispam reasons.  Archived mail has vanished and reappeared (after
some delay) under different names.  I'm waiting for things to settle
down before complaining again about it.



From MAILER-DAEMON Sun Jan 12 10:59:25 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XkVG-0000cP-00
	for mharc-autoconf@gnu.org; Sun, 12 Jan 2003 10:58:26 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XkUx-0000GD-00
	for autoconf@gnu.org; Sun, 12 Jan 2003 10:58:07 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XkTV-0007RH-00
	for autoconf@gnu.org; Sun, 12 Jan 2003 10:56:39 -0500
Received: from cmailm4.svr.pol.co.uk ([195.92.193.211])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18XkSh-0005Zr-00
	for autoconf@gnu.org; Sun, 12 Jan 2003 10:55:47 -0500
Received: from modem-96.flunitrazepam.dialup.pol.co.uk ([62.136.95.224]
	helo=phekda.freeserve.co.uk)
	by cmailm4.svr.pol.co.uk with esmtp (Exim 3.35 #1)
	id 18XkSf-0003qb-00; Sun, 12 Jan 2003 15:55:46 +0000
Received: from iolanthe.int.phekda.freeserve.co.uk
	([192.168.1.1] helo=phekda.freeserve.co.uk ident=rich)
	by phekda.freeserve.co.uk with esmtp (Exim 3.22 #1)
	id 18Xjek-0000j7-00; Sun, 12 Jan 2003 15:04:10 +0000
Sender: rich@phekda.freeserve.co.uk
Message-ID: <3E2183E9.31971EB4@phekda.freeserve.co.uk>
Date: Sun, 12 Jan 2003 15:04:09 +0000
From: Richard Dawe <rich@phekda.freeserve.co.uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: autoconf@gnu.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: Tim Van Holder <tim.van.holder@pandora.be>
Subject: autoconf 2.57 and DJGPP: autoconf Perl programs & $ENV{'SHELL'}
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 12 Jan 2003 15:58:24 -0000

[Resend: I sent this to automake@gnu.org by mistake the first time.]

Hello.

One problem that I found when porting autoconf 2.57 to DJGPP, based on Tim van
Holder's work, is that some of the Perl programs failed, because they were
using command.com, the Windows command-line shell (*). command.com does not
support the redirection constructs supported by Unix /bin/sh.

(*) on Windows versions before Windows NT

The solution I adopted is to hardcode the setting of $SHELL, as detected by
the configure script, into the Perl scripts. An example patch is below. In
reality you may wish to do this based on the setting of a DJGPP-specific
environment variable, e.g. DJDIR, the path to the main DJGPP directory, which
corresponds roughly to /usr on Unices & Linux. This approach has been used in
tests/Fetish.pm, from the fileutils test suite:

    # When running in a DJGPP environment, make $ENV{SHELL} point to bash.
    # Otherwise, a bad shell might be used (e.g. command.com) and many
    # tests would fail.
    defined $ENV{DJDIR}
      and $ENV{SHELL} = "$ENV{DJDIR}/bin/bash.exe";

Thanks, regards,

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]

--- /dev/c/develop/ports/orig/autoconf-2.57/bin/autoheader.in	2002-10-22
11:14:44.000000000 +0000
+++ /dev/c/develop/ports/gnu.dev/autoconf-2.57/bin/autoheader.in 2003-01-04
12:58:50.000000000 +0000
@@ -29,6 +29,11 @@ eval 'case $# in 0) exec @PERL@ -S "$0";
 
 BEGIN
 {
+  # <rich@phekda.freeserve.co.uk>: We need to use bash as the shell,
+  # to support command-line redirection. $ENV{SHELL} may be set
+  # to COMMAND.COM, which will not work.
+  $ENV{'SHELL'} = "@SHELL@";
+
   my $perllibdir = $ENV{'autom4te_perllibdir'} || '@datadir@';
   unshift @INC, "$perllibdir";
 }



From MAILER-DAEMON Sun Jan 12 17:26:07 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XqXI-0007ZC-00
	for mharc-autoconf@gnu.org; Sun, 12 Jan 2003 17:24:56 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XqWy-0006ct-00
	for autoconf@gnu.org; Sun, 12 Jan 2003 17:24:36 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XqWo-0006DP-00
	for autoconf@gnu.org; Sun, 12 Jan 2003 17:24:29 -0500
Received: from mail.gmx.net ([213.165.64.20])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18XqWd-0005lQ-00
	for autoconf@gnu.org; Sun, 12 Jan 2003 17:24:15 -0500
Received: (qmail 16246 invoked by uid 0); 12 Jan 2003 22:24:13 -0000
Received: from pd9e81d65.dip.t-dialin.net (HELO gmx.de) (217.232.29.101)
  by mail.gmx.net (mp016-rz3) with SMTP; 12 Jan 2003 22:24:13 -0000
Message-ID: <3E21EB7B.9040100@gmx.de>
Date: Sun, 12 Jan 2003 23:26:03 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: autoconf@gnu.org
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: ac-archive.sf.net/largefile - ac_sys_largefile and libraries...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 12 Jan 2003 22:24:53 -0000

Paul Eggert schrieb:
 >>Date: Sat, 11 Jan 2003 20:05:30 +0100
 >>From: Guido Draheim <guidod-2003-@gmx.de>
 >
 >>why not let those scripts check for spurious instances of
 >>fopen/lseek and friends and warn at them - so that libraries and
 >>modules are compiled 64bit always (using the alternate symbols
 >>fopen64/lseek64 instead, ye know).
 >
 >
 > That sounds like a reasonable approach, yes.
 >

http://ac-archive.sf.net/largefile/

There is a perl script that will check for off_t mismatches in
your current software - let that be run on your /usr/bin/ and
see how many problems your distro has :-)=)

comments are very welcome (hey, it took a day to set up the
website, so it'd be great to make it even better ;-))

-- cheers, guido                       counter.li.org #81555




From MAILER-DAEMON Mon Jan 13 07:38:51 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Y3rf-0000ra-00
	for mharc-autoconf@gnu.org; Mon, 13 Jan 2003 07:38:51 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Y3rD-0000Y6-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 07:38:23 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Y3qD-0008Gw-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 07:37:21 -0500
Received: from ftp.ilog.fr ([81.80.162.195])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Y3pr-0007dC-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 07:36:59 -0500
Received: from laposte.ilog.fr (cerbere-qe0 [81.80.162.193])
	by ftp.ilog.fr (8.12.7/8.12.7) with ESMTP id h0DCauEl001243;
	Mon, 13 Jan 2003 13:36:57 +0100 (MET)
Received: from honolulu.ilog.fr ([172.16.15.122])
	by laposte.ilog.fr (8.11.6/8.11.6) with ESMTP id h0DCarE18297;
	Mon, 13 Jan 2003 13:36:53 +0100 (MET)
Received: (from haible@localhost)
	by honolulu.ilog.fr (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id NAA20762;
	Mon, 13 Jan 2003 13:35:01 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15906.45685.88367.803191@honolulu.ilog.fr>
Date: Mon, 13 Jan 2003 13:35:01 +0100 (CET)
From: Bruno Haible <bruno@clisp.org>
To: Peter Eisentraut <peter_e@gmx.net>
In-Reply-To: <Pine.LNX.4.44.0301102017540.29178-100000@localhost.localdomain>
References: <15901.57326.950053.235725@honolulu.ilog.fr>
	<Pine.LNX.4.44.0301102017540.29178-100000@localhost.localdomain>
X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid
cc: autoconf@gnu.org
Subject: Re: comma separated lists
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 13 Jan 2003 12:38:49 -0000

Peter Eisentraut writes:
> The advantage of comma-separated lists are that they can be processed
> naturally as lists in m4, whereas the whitespace-separated lists are just
> passed through as a blob of data, usually to shell loop.

This advantage that you mention is not visible to the user. (I don't
care about one or two percent of speed in autoconf execution.) Whereas
the second disadvantage of comma-separated lists is that it doesn't
support computing the list at configure time:

funcs="malloc, free, foobar"
AC_CHECK_DECLS([$funcs])

funcs="getenv foobar"
AC_CHECK_DECLS([$funcs])

Doesn't work!

> Eventually, all macros will use the comma style.

Hopefully not.

Bruno



From MAILER-DAEMON Mon Jan 13 09:37:36 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Y5ia-0004df-00
	for mharc-autoconf@gnu.org; Mon, 13 Jan 2003 09:37:36 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Y5iY-0004cx-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 09:37:34 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Y5iW-0004ch-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 09:37:33 -0500
Received: from 212-123-14-226.ifiber.telenet-ops.be ([212.123.14.226]
	helo=gr.mtecgroup.com)
	by monty-python.gnu.org with smtp (Exim 4.10.13)	id 18Y5eX-0003iT-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 09:33:25 -0500
Received: (qmail 20883 invoked by uid 505); 13 Jan 2003 16:37:59 -0000
Received: from jan.vermaete@mtecwireless.com by gr.mtecgroup.com with
	qmail-scanner- http://www.astaro.com  (Version 3.0build 135|Known records:
	62254. . Clean.); 13/01/2003 16:37:57
Received: from unknown (HELO volta.mtecgroup) (192.168.129.201)
  by gr.mtec with SMTP; 13 Jan 2003 16:37:56 -0000
Received: from pluto.mtecgroup ([172.19.10.3]) by volta.mtecgroup with
	Microsoft SMTPSVC(5.0.2195.2966);	 Mon, 13 Jan 2003 15:33:37 +0100
From: Jan Vermaete <jan.vermaete@mtecwireless.com>
To: autoconf@gnu.org
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="=-yShdauHSmTeZeDoVJ9t5"
Organization: M-TEC WIRELESS N.V.
Message-Id: <1042468338.11200.36.camel@pluto.mtecgroup>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.1 
Date: 13 Jan 2003 15:32:18 +0100
X-OriginalArrivalTime: 13 Jan 2003 14:33:37.0451 (UTC)
	FILETIME=[C25C87B0:01C2BB10]
Subject: AM_INIT_AUTOMAKE - > AC_INIT
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 13 Jan 2003 14:37:34 -0000


--=-yShdauHSmTeZeDoVJ9t5
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hello,
A long time ago, I wrote this code into a configure.in file:
  dnl Extract VERSION from the CVS tag
  VERSION=3D[`echo '$Name:  $' | sed -e 's/^\$//' -e 's/ \$$//' -e
's/^Name: //' -e 's/v_//' -e 's/[\_\.]/./g' `]
  AM_INIT_AUTOMAKE("mcas", $VERSION)
It extracte a cvs tag ( like v_0_1_1) to 0.1.1 .

I recently upgrade my automake, autoconf and libtool to the latest stable v=
ersions.
So, I have changed AM_INIT_AUTOMAKE to AC_INIT.
  AC_INIT([mcas], $VERSION , [bug@mtecwireless.com])
But autoheader give me following error:
   configure.in:27: warning: AC_INIT: not a literal: $VERSION

What's wrong, and how can I fix this.

--=-yShdauHSmTeZeDoVJ9t5
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQA+Is3yiR1sWztcs7sRAm9YAKDZqfWB2vaRY5yZZQXYHIL9zLsNxwCfaFdF
JXDPHSplh31fmT7joTGvHiU=
=c0fP
-----END PGP SIGNATURE-----

--=-yShdauHSmTeZeDoVJ9t5--




From MAILER-DAEMON Mon Jan 13 09:44:37 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Y5pN-0000Yf-00
	for mharc-autoconf@gnu.org; Mon, 13 Jan 2003 09:44:37 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Y5pL-0000Wl-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 09:44:35 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Y5pJ-0000V3-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 09:44:34 -0500
Received: from atrey.karlin.mff.cuni.cz ([195.113.31.123])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Y5ni-0007zE-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 09:42:54 -0500
Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 17307)
	id 914C34FCDE; Mon, 13 Jan 2003 15:42:34 +0100 (CET)
Date: Mon, 13 Jan 2003 15:42:34 +0100
From: Karel Kulhavy <clock@atrey.karlin.mff.cuni.cz>
To: autoconf@gnu.org
Message-ID: <20030113144234.GA10308@atrey.karlin.mff.cuni.cz>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
Subject: conditional AC_PROG_CXX
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 13 Jan 2003 14:44:35 -0000

autoconf 2.57 still has the bug that manifests when configure.in calls
C_PROG_CXX then the resulting configure will crash with this message:
# configure: error: conditional "am__fastdepCXX" was never defined.
# Usually this means the macro was only invoked conditionally.

Clock




From MAILER-DAEMON Mon Jan 13 10:12:47 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Y6Fp-0004j7-00
	for mharc-autoconf@gnu.org; Mon, 13 Jan 2003 10:11:57 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Y6FT-0004W0-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 10:11:35 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Y6FP-0004TF-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 10:11:32 -0500
Received: from abyssinian.sleepycat.com ([199.103.242.18])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Y6F7-0004IC-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 10:11:13 -0500
Received: (from bostic@localhost)
	by abyssinian.sleepycat.com (8.11.6/8.11.6) id h0DFB5205481
	for autoconf@gnu.org; Mon, 13 Jan 2003 10:11:05 -0500 (EST)
Date: Mon, 13 Jan 2003 10:11:05 -0500 (EST)
From: Keith Bostic <bostic@sleepycat.com>
Message-Id: <200301131511.h0DFB5205481@abyssinian.sleepycat.com>
To: autoconf@gnu.org
Subject: AH_TEMPLATE feature
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 13 Jan 2003 15:11:50 -0000

Hi, my name is Keith Bostic and I'm with Sleepycat Software.
We use the GNU autoconf software to configure Berkeley DB.

Something we've occasionally needed is the ability to set
specific configuration defines.

For example, we use HAVE_O_DIRECT to configure open's O_DIRECT
flag.  Sometimes, users are building Berkeley DB for use on
file systems different from the ones on which they're running
the configure script, and they want to turn the option on even
though the test we've written for autoconf will fail.

Obviously, we could add a specific configuration option, but
we have around 100 or so HAVE_XXX defines, and that solution
would get out of hand quickly.

The way we tell users to do this is by editing their config.h
files in their configuration directory, which isn't easy to
do -- a lot of users get confused when you say "editor". :-)

It occurred to me it might be reasonable to connect the autoconf
argument macros to the AH_TEMPLATE macro, creating a standard
configuration argument for all HAVE_XXX declarations.  So, if
there's a:

	AH_TEMPLATE(DIAGNOSTIC,
	[Define to 1 if you want a version with run-time diagnostic checking.])

that would imply the existence of the:

	--override-diagnostic=XXX

argument, that would allow users to override the behavior of
the configuration script at a basic level.

I'm not sure how such a flag should behave: overriding the value
during the creation of the config.h file?  Or, supplying an
initial cached value for the AC_CACHE_CHECK([]) macro?

I don't think it would make sense to add this to the help
message, but it might make field support easier.  Telling users
to configure with

	--override-o_direct=1

is simpler than telling them to edit their config.h file.

It's more difficult to edit config.h files programmatically,
too, that is, users building packages for multiple systems
would be happier with a set of config arguments than editing
config.h files.

Anyway, I know very little about how autoconf is put together,
and this may be an awful idea.  If there's a better way to do
this, I would appreciate any feedback, since it's a problem I
have to solve on a regular basis.

Regards,
--keith

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Keith Bostic			bostic@sleepycat.com
Sleepycat Software Inc.		keithbosticim (ymsgid)
118 Tower Rd.			+1-781-259-3139
Lincoln, MA 01773		http://www.sleepycat.com



From MAILER-DAEMON Mon Jan 13 10:25:27 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Y6Sd-0004k1-00
	for mharc-autoconf@gnu.org; Mon, 13 Jan 2003 10:25:11 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Y6RL-0003vt-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 10:23:51 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Y6R1-0003hT-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 10:23:32 -0500
Received: from mail.uklinux.net ([80.84.72.21] helo=s1.uklinux.net)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Y6Qn-0003WB-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 10:23:17 -0500
Received: from whinlatter.uklinux.net (bts-0454.dialup.zetnet.co.uk
	[194.247.49.198])
	by s1.uklinux.net (8.11.6/8.11.6) with ESMTP id h0DFN7I27633;
	Mon, 13 Jan 2003 15:23:07 GMT
Received: from roger by whinlatter.uklinux.net with local (Exim 3.35 #1
	(Debian))	id 18Y4OT-0002Z3-00; Mon, 13 Jan 2003 13:12:45 +0000
To: Bruno Haible <bruno@clisp.org>
References: <15901.57326.950053.235725@honolulu.ilog.fr>
	<Pine.LNX.4.44.0301102017540.29178-100000@localhost.localdomain>
	<15906.45685.88367.803191@honolulu.ilog.fr>
From: Roger Leigh <roger@whinlatter.uklinux.net>
Date: 13 Jan 2003 13:12:45 +0000
In-Reply-To: <15906.45685.88367.803191@honolulu.ilog.fr>
Message-ID: <87znq59os2.fsf@whinlatter.uklinux.net>
Lines: 29
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: autoconf@gnu.org
cc: Peter Eisentraut <peter_e@gmx.net>
Subject: Re: comma separated lists
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 13 Jan 2003 15:25:09 -0000

Bruno Haible <bruno@clisp.org> writes:

> Peter Eisentraut writes:
> > The advantage of comma-separated lists are that they can be processed
> > naturally as lists in m4, whereas the whitespace-separated lists are just
> > passed through as a blob of data, usually to shell loop.

However, you can easily use m4_translit to convert the spaces to
commas, so spaces can have the same advantages as commas.

> This advantage that you mention is not visible to the user. (I don't
> care about one or two percent of speed in autoconf execution.) Whereas
> the second disadvantage of comma-separated lists is that it doesn't
> support computing the list at configure time:

True.

When passing multiple arguments into a single m4 macro argument,
commas only make things more confusing (is this a list, or a set of
separate arguments?).  What the macro actually does with the list is
not relevant (it could use them as arguments to another macro, or as a
list), but the interface to the user of the macro is.


-- 
Roger Leigh

                Printing on GNU/Linux?  http://gimp-print.sourceforge.net/
                GPG Public Key: 0x25BFB848 available on public keyservers



From MAILER-DAEMON Mon Jan 13 16:09:28 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18YBpJ-0006gs-00
	for mharc-autoconf@gnu.org; Mon, 13 Jan 2003 16:08:57 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18YBoh-0005hZ-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 16:08:19 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18YBoV-0005Qw-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 16:08:14 -0500
Received: from imap.gmx.net ([213.165.65.60] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18YBoQ-0005AD-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 16:08:02 -0500
Received: (qmail 10194 invoked by uid 0); 13 Jan 2003 21:08:00 -0000
Received: from pd902f0e1.dip0.t-ipconnect.de (217.2.240.225)
  by mail.gmx.net (mp006-rz3) with SMTP; 13 Jan 2003 21:08:00 -0000
Date: Mon, 13 Jan 2003 22:17:23 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
X-X-Sender: peter@localhost.localdomain
To: Bruno Haible <bruno@clisp.org>
In-Reply-To: <15906.45685.88367.803191@honolulu.ilog.fr>
Message-ID: <Pine.LNX.4.44.0301132016250.32525-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: autoconf@gnu.org
Subject: Re: comma separated lists
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 13 Jan 2003 21:08:55 -0000

Bruno Haible writes:

> This advantage that you mention is not visible to the user. (I don't
> care about one or two percent of speed in autoconf execution.)

The difference between space-separated lists and comma-separated lists is
approximately like writing in C func("arg1 arg2 arg3") rather than
func(arg1, arg2, arg3).  It is not "proper" for the language being used.
It is a historical mistake that is being phased out.  The new style will
make the system more robust, which is not immediately visible to user, of
course, but ultimately for his benefit.

> Whereas the second disadvantage of comma-separated lists is that it
> doesn't support computing the list at configure time:
>
> funcs="malloc, free, foobar"
> AC_CHECK_DECLS([$funcs])
>
> funcs="getenv foobar"
> AC_CHECK_DECLS([$funcs])
>
> Doesn't work!

This approach is already dysfunctional right now, because if you write it
that way it's not traceable and autoheader and other tools that depend on
tracing, such as automake, will screw up.  There is an easy fix.  You can
write

if condition1; then
AC_CHECK_DECLS(getenv)
fi

if condition2; then
AC_CHECK_DECLS(foobar)
fi

-- 
Peter Eisentraut   peter_e@gmx.net




From MAILER-DAEMON Mon Jan 13 16:13:15 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18YBq6-0007ld-00
	for mharc-autoconf@gnu.org; Mon, 13 Jan 2003 16:09:46 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18YBpc-0007BA-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 16:09:16 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18YBpC-0006Sy-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 16:08:52 -0500
Received: from mail.gmx.de ([213.165.65.60] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18YBp6-0006Bw-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 16:08:44 -0500
Received: (qmail 5819 invoked by uid 0); 13 Jan 2003 21:08:41 -0000
Received: from pd902f0e1.dip0.t-ipconnect.de (217.2.240.225)
  by mail.gmx.net (mp011-rz3) with SMTP; 13 Jan 2003 21:08:41 -0000
Date: Mon, 13 Jan 2003 22:18:05 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
X-X-Sender: peter@localhost.localdomain
To: Jan Vermaete <jan.vermaete@mtecwireless.com>
In-Reply-To: <1042468338.11200.36.camel@pluto.mtecgroup>
Message-ID: <Pine.LNX.4.44.0301132024290.32525-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: autoconf@gnu.org
Subject: Re: AM_INIT_AUTOMAKE - > AC_INIT
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 13 Jan 2003 21:09:39 -0000

Jan Vermaete writes:

>   AC_INIT([mcas], $VERSION , [bug@mtecwireless.com])
> But autoheader give me following error:
>    configure.in:27: warning: AC_INIT: not a literal: $VERSION

You can use the esyscmd macro to make calls to shell commands at the time
configure is run and compute the version number.  For example:

AC_INIT([xxx], esyscmd([echo -n `date +%Y%m%d`]), [yyy])

(Extra work needed to remove the newline.)

-- 
Peter Eisentraut   peter_e@gmx.net




From MAILER-DAEMON Mon Jan 13 17:42:05 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18YDGf-0007Kr-00
	for mharc-autoconf@gnu.org; Mon, 13 Jan 2003 17:41:17 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18YDFW-0006oA-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 17:40:06 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18YDF9-00065l-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 17:39:50 -0500
Received: from mail.gmx.net ([213.165.64.20])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18YDEn-0005df-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 17:39:21 -0500
Received: (qmail 19793 invoked by uid 0); 13 Jan 2003 22:39:19 -0000
Received: from pd902f0ee.dip0.t-ipconnect.de (217.2.240.238)
  by mail.gmx.net (mp023-rz3) with SMTP; 13 Jan 2003 22:39:19 -0000
Date: Mon, 13 Jan 2003 23:48:43 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
X-X-Sender: peter@localhost.localdomain
To: Karel Kulhavy <clock@atrey.karlin.mff.cuni.cz>
In-Reply-To: <20030113144234.GA10308@atrey.karlin.mff.cuni.cz>
Message-ID: <Pine.LNX.4.44.0301132348230.789-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: autoconf@gnu.org
Subject: Re: conditional AC_PROG_CXX
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 13 Jan 2003 22:41:16 -0000

Karel Kulhavy writes:

> autoconf 2.57 still has the bug that manifests when configure.in calls
> C_PROG_CXX then the resulting configure will crash with this message:
> # configure: error: conditional "am__fastdepCXX" was never defined.
> # Usually this means the macro was only invoked conditionally.

This appears to be an automake problem.  Please post a full test case.

-- 
Peter Eisentraut   peter_e@gmx.net




From MAILER-DAEMON Mon Jan 13 17:50:07 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18YDM8-00025m-00
	for mharc-autoconf@gnu.org; Mon, 13 Jan 2003 17:46:56 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18YDJv-0001eM-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 17:44:39 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18YDJY-0000tP-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 17:44:22 -0500
Received: from mailout6-1.nyroc.rr.com ([24.92.226.177]
	helo=mailout6-0.nyroc.rr.com)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18YDJP-0000WF-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 17:44:07 -0500
Received: from doctormoo (syr-24-24-16-193.twcny.rr.com [24.24.16.193])
	h0DMi6k00216
	for <autoconf@gnu.org>; Mon, 13 Jan 2003 17:44:06 -0500 (EST)
Received: from neroden by doctormoo with local (Exim 3.36 #1 (Debian))
	id 18YDJJ-00005r-00
	for <autoconf@gnu.org>; Mon, 13 Jan 2003 17:44:01 -0500
Date: Mon, 13 Jan 2003 17:44:01 -0500
To: autoconf@gnu.org
Message-ID: <20030113224401.GA360@doctormoo>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
From: Nathanael Nerode <neroden@twcny.rr.com>
Subject: Patch for improvement of AC_CHECK_TOOL
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 13 Jan 2003 22:46:55 -0000

I sent, to autoconf-patches@gnu.org, a patch for improving AC_CHECK_TOOL 
and introducing AC_CHECK_TARGET_TOOL.

Whee, as the saying goes.

I'd appreciate quick feedback on what changes (if any) would be 
necessary to get it into mainline autoconf.

(I'm also sending this message because I'm suspicious that something is 
eating my messages to autoconf-patches....)

--Nathanael




From MAILER-DAEMON Mon Jan 13 17:54:55 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18YDTn-000682-00
	for mharc-autoconf@gnu.org; Mon, 13 Jan 2003 17:54:51 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18YDSX-0004xR-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 17:53:33 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18YDSK-0004r0-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 17:53:21 -0500
Received: from mailout6-0.nyroc.rr.com ([24.92.226.125])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18YDRw-0004jE-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 17:52:56 -0500
Received: from doctormoo (syr-24-24-16-193.twcny.rr.com [24.24.16.193])
	h0DMqtk15598
	for <autoconf@gnu.org>; Mon, 13 Jan 2003 17:52:55 -0500 (EST)
Received: from neroden by doctormoo with local (Exim 3.36 #1 (Debian))
	id 18YDRq-000069-00
	for <autoconf@gnu.org>; Mon, 13 Jan 2003 17:52:50 -0500
Date: Mon, 13 Jan 2003 17:52:50 -0500
To: autoconf@gnu.org
Message-ID: <20030113225250.GA373@doctormoo>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
From: Nathanael Nerode <neroden@twcny.rr.com>
Subject: Expanding 'history' section of manual...
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 13 Jan 2003 22:54:50 -0000

After Deuteronomy, comes...
Joshua.

OK, maybe that's inappropriate, given that nobody named Joshua has ever
worked on autoconf.

After that comes...
Judges.

That's pretty good, eh?  Even appropriate.

--Nathanael



From MAILER-DAEMON Mon Jan 13 22:20:03 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18YHc4-0001Dt-00
	for mharc-autoconf@gnu.org; Mon, 13 Jan 2003 22:19:40 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18YHbw-00017l-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 22:19:32 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18YHbt-0000zQ-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 22:19:30 -0500
Received: from mailout6-1.nyroc.rr.com ([24.92.226.177]
	helo=mailout6-0.nyroc.rr.com)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18YHbi-0000lT-00
	for autoconf@gnu.org; Mon, 13 Jan 2003 22:19:18 -0500
Received: from twcny.rr.com (syr-66-66-30-119.twcny.rr.com [66.66.30.119])
	h0E3JFk29063;	Mon, 13 Jan 2003 22:19:15 -0500 (EST)
Message-ID: <3E2381AD.1040104@twcny.rr.com>
Date: Mon, 13 Jan 2003 22:19:09 -0500
From: Nathanael Nerode <neroden@twcny.rr.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.3b) Gecko/20030113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Eggert <eggert@CS.UCLA.EDU>
References: <20030113224401.GA360@doctormoo> <vi8fzrwhd3l.fsf@cs.ucla.edu>
In-Reply-To: <vi8fzrwhd3l.fsf@cs.ucla.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Mailing list archive status? (was Re: Patch for improvement of
 AC_CHECK_TOOL)
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 14 Jan 2003 03:19:38 -0000

Paul Eggert wrote:
> Nathanael Nerode <neroden@twcny.rr.com> writes:
> 
> 
>>(I'm also sending this message because I'm suspicious that something is 
>>eating my messages to autoconf-patches....)
> 
> 
> You can check that sort of thing at:
> 
> http://mail.gnu.org/archive/html/autoconf-patches/
> 
...or can you?  My messages haven't shown up in the archives, although 
they evidently made it to the lists.

--Nathanael




From MAILER-DAEMON Tue Jan 14 11:09:33 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18YTcq-0004gD-00
	for mharc-autoconf@gnu.org; Tue, 14 Jan 2003 11:09:16 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18YTc9-0004Nm-00
	for autoconf@gnu.org; Tue, 14 Jan 2003 11:08:33 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18YTbv-0003zZ-00
	for autoconf@gnu.org; Tue, 14 Jan 2003 11:08:24 -0500
Received: from zok.sgi.com ([204.94.215.101])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18YTQx-0007P6-00
	for autoconf@gnu.org; Tue, 14 Jan 2003 10:56:59 -0500
Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193])
	id h0EF32Kp014431
	for <autoconf@gnu.org>; Tue, 14 Jan 2003 07:03:02 -0800
Received: from sgihud.hudson.sgi.com (sgihud.hudson.sgi.com [169.238.41.4])
	h0EFuvQb33734689	for <@relay.sgi.com:autoconf@gnu.org>;
	Tue, 14 Jan 2003 07:56:57 -0800 (PST)
Received: from sgi.com (cf-vpn-hw-drk-1.corp.sgi.com [134.15.81.98]) by
	sgihud.hudson.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id
	KAA84957; Tue, 14 Jan 2003 10:56:54 -0500 (EST)
Sender: drk@sgi.com
Message-ID: <3E243346.3D4F307C@sgi.com>
Date: Tue, 14 Jan 2003 10:56:54 -0500
From: David Kaelbling <drk@sgi.com>
Organization: Silicon Graphics, Inc.
X-Mailer: Mozilla 4.8C-SGI [en] (X11; U; IRIX64 6.5 IP30)
X-Accept-Language: en
MIME-Version: 1.0
To: autoconf@gnu.org, drk@sgi.com
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: configure info entry problems
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 14 Jan 2003 16:09:14 -0000

autoconf and gdb (and probably other GNU packages) both attempt to
create a "configure" entry in the top level info dir file.  This is a
problem, because only one will succeed -- install-info will fail for
whichever is run second.

	David

-- 
David KAELBLING <drk@sgi.com>	    Silicon Graphics Computer Systems
1 Cabot Rd, suite 250; Hudson, MA 01749	    781.839.2157, fax ...2357



From MAILER-DAEMON Tue Jan 14 17:23:49 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18YZRZ-0004mL-00
	for mharc-autoconf@gnu.org; Tue, 14 Jan 2003 17:22:01 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18YZQK-00047V-00
	for autoconf@gnu.org; Tue, 14 Jan 2003 17:20:44 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18YZQB-0003q5-00
	for autoconf@gnu.org; Tue, 14 Jan 2003 17:20:36 -0500
Received: from sunny.pacific.net.au ([203.25.148.40])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18YZQ1-0003ig-00
	for autoconf@gnu.org; Tue, 14 Jan 2003 17:20:25 -0500
Received: from wisma.pacific.net.au (wisma.pacific.net.au [210.23.129.72])
          by sunny.pacific.net.au with ESMTP
          id h0EMKAKR023526; Wed, 15 Jan 2003 09:20:10 +1100 (EST)
Received: from localhost (ppp61.dyn228.pacific.net.au [203.143.228.61])
        by wisma.pacific.net.au with ESMTP
        id JAA19177; Wed, 15 Jan 2003 09:20:08 +1100 (EST)
Received: from gg by localhost with local (Exim 3.35 #1 (Debian))
	id 18YZPR-0000bh-00; Wed, 15 Jan 2003 08:19:49 +1000
To: Karel Kulhavy <clock@atrey.karlin.mff.cuni.cz>
From: Kevin Ryde <user42@zip.com.au>
Mail-Copies-To: never
Date: Wed, 15 Jan 2003 08:19:47 +1000
In-Reply-To: <20030113144234.GA10308@atrey.karlin.mff.cuni.cz> (Karel
 Kulhavy's message of "Mon, 13 Jan 2003 15:42:34 +0100")
Message-ID: <8765srcr24.fsf@zip.com.au>
User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.1
 (i386-debian-linux-gnu)
References: <20030113144234.GA10308@atrey.karlin.mff.cuni.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: autoconf@gnu.org
Subject: Re: conditional AC_PROG_CXX
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 14 Jan 2003 22:22:00 -0000

Karel Kulhavy <clock@atrey.karlin.mff.cuni.cz> writes:
>
> # configure: error: conditional "am__fastdepCXX" was never defined.
> # Usually this means the macro was only invoked conditionally.

Automake appends an AM_CONDITIONAL to AC_PROG_CXX, and is then unhappy
when it's expanded but not actually executed.

You can avoid the problem by adding "no-dependencies" to
AM_INIT_AUTOMAKE, if you don't mind losing the automated dependency
tracking.  Perhaps there's a better way, but this was enough for me.



From MAILER-DAEMON Tue Jan 14 23:37:18 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18YfIQ-0004Ux-00
	for mharc-autoconf@gnu.org; Tue, 14 Jan 2003 23:36:58 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18YfHH-0003IZ-00
	for autoconf@gnu.org; Tue, 14 Jan 2003 23:35:47 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18YfGU-00034R-00
	for autoconf@gnu.org; Tue, 14 Jan 2003 23:35:01 -0500
Received: from mardy.hank.org ([63.205.225.170])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18YfG8-0002pU-00
	for autoconf@gnu.org; Tue, 14 Jan 2003 23:34:36 -0500
Received: from localhost (moseley@localhost)h0F4YZY27636
	for <autoconf@gnu.org>; Tue, 14 Jan 2003 20:34:35 -0800
Date: Tue, 14 Jan 2003 20:34:35 -0800 (PST)
From: Bill Moseley <moseley@hank.org>
To: autoconf@gnu.org
Message-ID: <Pine.LNX.4.10.10301142008230.24988-100000@mardy.hank.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Segfault with unset
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 15 Jan 2003 04:36:57 -0000


A user of our package wrote to say ./configure was segfaulting.

 >./configure
./configure
Segmentation fault

I suspected old shell so I tested on a shell server at he.net and could
repeat it (turns out the user was testing on he.net, too).

What's causing the segfault is this line in the ./configure script:

  $as_unset ENV MAIL MAILPATH

Here's the version of bash that's running:

/bin/sh --version
GNU bash, version 2.01.0(23)-release (i686-pc-linux-gnu)
Copyright 1996 Free Software Foundation, Inc.

The configure script was built with autoconf 2.57, but this isn't really
an Autoconf problem, but I hope someone has seen this before:

>cat test
#! /bin/sh

# Support unset when possible.
if (FOO=FOO; unset FOO) >/dev/null 2>&1; then
  as_unset=unset
else
  as_unset=false
fi

echo "\$as_unset = $as_unset"

# Work around bugs in pre-3.0 UWIN ksh.
$as_unset ENV MAIL MAILPATH

>./test
$as_unset = unset
Segmentation fault



Thanks,


-- 
Bill Moseley moseley@hank.org





From MAILER-DAEMON Wed Jan 15 03:36:55 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Yj2a-0003ta-00
	for mharc-autoconf@gnu.org; Wed, 15 Jan 2003 03:36:52 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Yj1T-0001uD-00
	for autoconf@gnu.org; Wed, 15 Jan 2003 03:35:43 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Yj1C-0001Fg-00
	for autoconf@gnu.org; Wed, 15 Jan 2003 03:35:30 -0500
Received: from sherlock.holmes.nl ([195.169.99.99])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Yj19-00015g-00
	for autoconf@gnu.org; Wed, 15 Jan 2003 03:35:23 -0500
Received: by sherlock.holmes.nl (Postfix, from userid 8)
	id 6E097109F; Wed, 15 Jan 2003 09:35:18 +0100 (CET)
Comments: Passed Amavis/Sophos Anti-Virus for Unix (sherlock.holmes.nl)
Received: from theta.holmes.nl (theta.holmes.nl [10.5.0.12])
	by sherlock.holmes.nl (Postfix) with ESMTP id 6C14D108D
	for <autoconf@gnu.org>; Wed, 15 Jan 2003 09:35:16 +0100 (CET)
Received: from holmes.nl (xhystos.holmes.nl [10.5.2.240]) by theta.holmes.nl
	with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id CM8YJ1KH; Wed, 15 Jan 2003 09:35:12 +0100
Message-ID: <3E252B4E.9080308@holmes.nl>
Date: Wed, 15 Jan 2003 09:35:10 +0000
From: Martijn Ras <ras@holmes.nl>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
X-Accept-Language: nl, en-us, en
MIME-Version: 1.0
To: autoconf@gnu.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: is it possible to build multiple configurations in one go?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 15 Jan 2003 08:36:50 -0000

Heya Folks,

Reading this and other mailing lists of configuration & building tools 
helped me automating the build process of a number of projects i
'm maintaining. However, i'm having difficulty solving the last step and 
hope you may help me out.

I used to duplicate my source into a number of copies, with a specific 
name. I'd then work my way through the configuration and make files, 
renaming the targets accordingly and setting the correct configuration 
options.

I want to perform the whole process in one go on the main source, to 
reduce the risk of having to keep the different copies synchronised.

I've updated my source structure in such a way that a directory is 
created under the 'src' directory for every configuration. Each of these 
directories contains an automake file that builds the correctly named 
targets for that configuration.

So far so good, however, this results in a bunch of files with different 
names but all with exactly the same configuration ...

I need each target to have it's own specific configuration. Is there a 
way to set up the configuration so that per directory a different 
configuration will be generated.

For instance, i'd run autogen.sh --enable-configuration1 on the 
myProject_configuration1 copy and autogen.sh --enable-configuration2 on 
the myProject_configuration2 copy.

I was thinking that perhaps the way to automate this is by having the 
configuration determine the necessary options by looking at the 
directories name, but i fail to see how to actually get it to do so ...

Mazzel,

Martijn.




From MAILER-DAEMON Wed Jan 15 04:25:16 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Yjn5-0001j9-00
	for mharc-autoconf@gnu.org; Wed, 15 Jan 2003 04:24:55 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18YjmQ-0000nN-00
	for autoconf@gnu.org; Wed, 15 Jan 2003 04:24:14 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Yjlt-0000QM-00
	for autoconf@gnu.org; Wed, 15 Jan 2003 04:23:51 -0500
Received: from pop.gmx.net ([213.165.65.60] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18Yji6-0006AE-00
	for autoconf@gnu.org; Wed, 15 Jan 2003 04:19:46 -0500
Received: (qmail 27779 invoked by uid 0); 15 Jan 2003 09:19:44 -0000
Received: from pd9e8354f.dip.t-dialin.net (HELO gmx.de) (217.232.53.79)
  by mail.gmx.net (mp007-rz3) with SMTP; 15 Jan 2003 09:19:44 -0000
Message-ID: <3E252822.5080007@gmx.de>
Date: Wed, 15 Jan 2003 10:21:38 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Martijn Ras <ras@holmes.nl>
References: <3E252B4E.9080308@holmes.nl>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: is it possible to build multiple configurations in one go?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 15 Jan 2003 09:24:53 -0000

Martijn Ras schrieb:
> Heya Folks,
> 
> Reading this and other mailing lists of configuration & building tools 
> helped me automating the build process of a number of projects i
> 'm maintaining. However, i'm having difficulty solving the last step and 
> hope you may help me out.
> 
> I used to duplicate my source into a number of copies, with a specific 
> name. I'd then work my way through the configuration and make files, 
> renaming the targets accordingly and setting the correct configuration 
> options.
> 
> I want to perform the whole process in one go on the main source, to 
> reduce the risk of having to keep the different copies synchronised.
> 
> I've updated my source structure in such a way that a directory is 
> created under the 'src' directory for every configuration. Each of these 
> directories contains an automake file that builds the correctly named 
> targets for that configuration.
> 
> So far so good, however, this results in a bunch of files with different 
> names but all with exactly the same configuration ...
> 
> I need each target to have it's own specific configuration. Is there a 
> way to set up the configuration so that per directory a different 
> configuration will be generated.
> 
> For instance, i'd run autogen.sh --enable-configuration1 on the 
> myProject_configuration1 copy and autogen.sh --enable-configuration2 on 
> the myProject_configuration2 copy.
> 
> I was thinking that perhaps the way to automate this is by having the 
> configuration determine the necessary options by looking at the 
> directories name, but i fail to see how to actually get it to do so ...
> 
> Mazzel,
> 
> Martijn.
> 

put the real configure.ac into the src/ directory
and make up a configure helper in the top-dir with
something like

if $enabled ; then
    mkdir $builddir
    (cd $builddir && sh ../src/configure $specificoptions)
fi

plus:
    write a toplevel makefile that does recurse into
    the various builddirs just created. it's easy but
    mostly project specific (`cp Makefile.all Makefile`).

background:
    discussed a bit more in the region of `variant builds`
    on the mailing list (libtool one I guess). The trick
    is the vpath emulation of automake that allows the
    source files to live in another directory than the
    build files will end up.

extra task:
    try with sharing a common cache-file among the various
    sub-configures to speed up the processing.

for your amusement:
    http://ac-archive.sf.net/guidod/ax_builddir_default.html
    it does atleast help to not see error messages saying
    some in-source-dir configuration was found. Not tested.

-- HTH, have fun, guido            http://ac-archive.sf.net




From MAILER-DAEMON Fri Jan 17 08:48:10 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZWqk-0007qq-00
	for mharc-autoconf@gnu.org; Fri, 17 Jan 2003 08:47:58 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZWp5-0006jU-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 08:46:15 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZWma-00054K-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 08:43:40 -0500
Received: from main.gmane.org ([80.91.224.249])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZWl3-00043Y-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 08:42:05 -0500
Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18ZWjg-0005bh-00
	for <autoconf@gnu.org>; Fri, 17 Jan 2003 14:40:40 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: autoconf@gnu.org
Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18ZWcw-0005Gi-00
	for <gmane-comp-sysutils-autoconf-general@m.gmane.org>;
	Fri, 17 Jan 2003 14:33:42 +0100
Path: not-for-mail
From: Peter Simons <simons@cryp.to>
Date: 17 Jan 2003 14:35:04 +0100
Organization: private
Lines: 163
Message-ID: <873cnrgarb.fsf@overkill.cryp.to>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@main.gmane.org
Sender: news <news@main.gmane.org>
Subject: Macro Archive Relaunch
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 17 Jan 2003 13:47:57 -0000

Hi everybody,

in a staggering example of over-engineering, I rewrote the
infrastructure that maintains and builds the GNU Autoconf Macro
Archive, which is available at:

    http://www.gnu.org/software/ac-archive/

There are numerous changes that allow for a much better archive than
we have today. To list the highlights:

 - The new "genarchive" tool can read macros in both the old format
   and in a new XML-based format, for which a DTD is available.

 - Macros in the XML format are validated using an SGML/XML parser
   before they're processed, thus greatly reducing the amount of
   manual effort involved in verifying the submissions.

 - The generated web pages of the archive are again being validated by
   a full SGML parser in order to assure that the HTML pages have a
   maximum of standard conformance and maximum availability on all
   kinds of HTML-capable devices.

 - Through the use of "style sheets", the visual appearance of the
   archive can be improved.

 - The "genarchive" tool allows for easy and painless additions such
   as new categories, etc.

 - The XML format allows for easy addition of meta information, which
   the old format cannot easily express. I could imagine, for
   instance, information about related macros (packages),
   dependencies, appliance to certain Autoconf versions, etc.

Everything is merry and well ... But I do need help in order to make
the whole thing take off. Before I go into the gory details, let me
show you what a macro submission in the NEW format looks like:

 | <?xml version="1.0" encoding="ISO-8859-1"?>
 | <!DOCTYPE acmacro PUBLIC "-//Peter Simons//DTD Autoconf Macro XML 1.0//EN"
 |     "http://gnu.org/software/ac-archive/dtd/acmacro1-xml.dtd">
 |
 | <acmacro category="misc">
 |   <name>PETI_ENABLE_DYNAMIC_LINK</name>
 |
 |   <synopsis>PETI_ENABLE_DYNAMIC_LINK</synopsis>
 |
 |   <version>$Id: peti_enable_dynamic_link.xml,v 1.2 2003/01/15 23:48:53 simons Exp $</version>
 |
 |   <author>
 |     <name>Peter Simons</name>
 |     <email>simons@gnu.org</email>
 |   </author>
 |
 |   <summary>Add a command-line flag to enable/disable dynamic linking.</summary>
 |
 |   <description>
 |     <p>Calling this macro adds the flag
 | <code>--enable-dynamic-link</code> to the command-line options
 | supported by the configure script. This option effectively
 | controls whether the compiler/linker flag <code>-static</code> is
 | added to <code>$LDFLAGS</code> or not. The default is to link
 | dynamically.</p>
 |   </description>
 |
 |   <m4source>
 | AC_DEFUN([PETI_ENABLE_DYNAMIC_LINK], [
 | AC_MSG_CHECKING(what kind of binaries we shall create)
 | AC_ARG_ENABLE(dynamic-link,
 | [  --enable-dynamic-link   Create dynamically-linked binaries (default)],
 | if test "$enableval" = "yes"; then
 |     AC_MSG_RESULT(dynamically linked)
 | else
 |     LDFLAGS="$LDFLAGS -static"
 |     AC_MSG_RESULT(statically linked)
 | fi,
 | AC_MSG_RESULT(dynamically linked))
 | ]]></m4source>
 | </acmacro>

The formatted web page generated from this can be seen at:

    http://www.gnu.org/software/ac-archive/peti_enable_dynamic_link.html

Compared to the old mark-up format, this has the following significant
advantages:

 - A short description of the macro (summary) is visible on the index
   page.

 - Authors can be formatted into a real <a href="mailto:...">name</a>
   element on the web page.

 - The description may include (a reduced set of) HTML 4.01 tags to
   create fancier layout.

 - The synopsis may include <br/> tags to allow for multi-line
   formatting.

 - The submitter can decide into which category the macro is going to
   be included (note the attribute "category") rather than me deciding
   that.

The <name> tag, which appears to be pointless, is used to determine
how the macro's file is to be called. It can be used to generate macro
packages -- something many people have missed badly in the past.
Effectively, you include multiple macros in the <m4source>, you
describe them in the <synopsis>, <summary>, and <description> tags,
and you set the <name> to something like "my_java_package" and there
you are.

Of course, I can automatically convert macros from the old format into
the new one. At the moment, though, I chose to retain all macros in
the format in which they were submitted.

Having outlined this, let me come to the part where I beg for
assistance. :-) I need help with the following tasks:

 (1) Work out some cool layout, formatting, style sheet, etc.

 (2) Major clean-up of the macro submissions included so far!

     Some macros have been obsoleted by newer Autoconf versions, some
     macros contain bugs or very poor formatting of the documentation,
     and some macros are outright stupid. (Like a few of my own
     submissions, which I removed with a slightly red head because of
     the shame.)

 (3) Clearly, the current set of categories is inadequate. We need to
     work out a new categorization ... And then we need to
     re-categorize the macros contained in the archive so far.

 (4) General ideas what to do and how to improve the archive.

 (5) Set-up a mechanism how submitters can easily validate their XML
     files. I would love to have a web-page where you just upload your
     submission and get all errors produced by the XML validator back
     right away. When the macro does not produce any errors, it should
     be submitted into a queue right away for addition to the archive.

 (6) Lot's of additional documentation must be written.

 (7) Work out a good way to show a list of most recent changes. (We DO
     have this information thanks to CVS, I am just not sure how to
     visualize it in a good way.)

 (8) Think of a good way to distribute the macros in a meaningful way
     so that Linux distributions can include them. (I do have a
     volunteer for creating RPM packages already, but I am just not
     sure how to organize things in the release archive.)

This is certainly getting over my head by now (as some submitters have
noticed by my poor response times) and I could really use some HELP!
:-)

Anyone interested? Any comments? Any suggestions?

Peter


P. S.: The whole thing is publicly available through Savannah. Take a
look at <https://savannah.gnu.org/projects/ac-archive/> if you're
interested.




From MAILER-DAEMON Fri Jan 17 10:07:57 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZY51-0005zi-00
	for mharc-autoconf@gnu.org; Fri, 17 Jan 2003 10:06:47 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZY4F-00050d-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 10:05:59 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZY3v-0004b1-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 10:05:43 -0500
Received: from pop.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18ZY0b-0001ic-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 10:02:13 -0500
Received: (qmail 14830 invoked by uid 0); 17 Jan 2003 15:02:10 -0000
Received: from pd9e82770.dip.t-dialin.net (HELO gmx.de) (217.232.39.112)
  by mail.gmx.net (mp022-rz3) with SMTP; 17 Jan 2003 15:02:10 -0000
Message-ID: <3E281B67.1010803@gmx.de>
Date: Fri, 17 Jan 2003 16:04:07 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Peter Simons <simons@cryp.to>,  autoconf@gnu.org
References: <873cnrgarb.fsf@overkill.cryp.to>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Macro Archive Relaunch
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 17 Jan 2003 15:06:45 -0000

Peter Simons schrieb:
> Compared to the old mark-up format, this has the following significant
> advantages:
> 
>  - A short description of the macro (summary) is visible on the index
>    page.

I did try that lately too - but dumped it as it did clutter the index
page with information not really helpful. Do you have an example and
a guidelines helppage to show the benefits? In most cases the macro
name itself should be self-descriptive and it seems to be sufficient.

> 
>  - Authors can be formatted into a real <a href="mailto:...">name</a>
>    element on the web page.

Usual textual author reference does usually follow a common format that
can easily be recognized and turned into a mailto-href. Personally, I
do have some politic problems whether it is actually a wish of the
original author be scanned by bots, so I did decide not to turn that
feature on without asking each and every submitter.

> 
>  - The description may include (a reduced set of) HTML 4.01 tags to
>    create fancier layout.

which can be helpful indeed.

> 
>  - The synopsis may include <br/> tags to allow for multi-line
>    formatting.

which I never have been thinking of - if the synopsis happens to
be too long than something may be wrong anyway. In parts it stems
from the fact that the gnu ac-archive uses h2 tags - using some
smaller layout tags improves the situation, see the new style in
the sfnet ac-archive for reference.

> 
>  - The submitter can decide into which category the macro is going to
>    be included (note the attribute "category") rather than me deciding
>    that.

That's a great thing - while it should be easy to do that with an
extra option for the old textual format as well (@category or some
such).

> 
> The <name> tag, which appears to be pointless, is used to determine
> how the macro's file is to be called. It can be used to generate macro
> packages -- something many people have missed badly in the past.
> Effectively, you include multiple macros in the <m4source>, you
> describe them in the <synopsis>, <summary>, and <description> tags,
> and you set the <name> to something like "my_java_package" and there
> you are.

That might be not easy to grasp - I think you mean `macro bundles`
as to have multiple macros in one submission file, right?

> 
> Of course, I can automatically convert macros from the old format into
> the new one. At the moment, though, I chose to retain all macros in
> the format in which they were submitted.

good. Do you start a new cvs with it? I have some automatic
routines to sync my branch with the gnu ac-archive's cvs
which would need to follow up with it. Since I'm doing xml
almost daily these day, I don't see a problem to blend the
new parts into the sfnet branch (as long as the sfnet branch
is needed, perhaps (hopefully?) it's obsolete some day)

> 
> Having outlined this, let me come to the part where I beg for
> assistance. :-) I need help with the following tasks:
> 
>  (1) Work out some cool layout, formatting, style sheet, etc.
> 
>  (2) Major clean-up of the macro submissions included so far!
> 
>      Some macros have been obsoleted by newer Autoconf versions, some
>      macros contain bugs or very poor formatting of the documentation,
>      and some macros are outright stupid. (Like a few of my own
>      submissions, which I removed with a slightly red head because of
>      the shame.)
> 
>  (3) Clearly, the current set of categories is inadequate. We need to
>      work out a new categorization ... And then we need to
>      re-categorize the macros contained in the archive so far.

I did have another idea in this respect, since some macros might
be valid to live in two or more categories. In a way I was always
thinking of having a set of keywords for categorization and let
the macros be browsable by keywords - not much unlike the
software categorization at freshmeat or sourceforge.

> 
>  (4) General ideas what to do and how to improve the archive.
> 
>  (5) Set-up a mechanism how submitters can easily validate their XML
>      files. I would love to have a web-page where you just upload your
>      submission and get all errors produced by the XML validator back
>      right away. When the macro does not produce any errors, it should
>      be submitted into a queue right away for addition to the archive.
> 
>  (6) Lot's of additional documentation must be written.
> 
>  (7) Work out a good way to show a list of most recent changes. (We DO
>      have this information thanks to CVS, I am just not sure how to
>      visualize it in a good way.)
> 
>  (8) Think of a good way to distribute the macros in a meaningful way
>      so that Linux distributions can include them. (I do have a
>      volunteer for creating RPM packages already, but I am just not
>      sure how to organize things in the release archive.)

The sfnet branch may have some hints here - it's been the primary
reason to split up since I did desperatly need packaging and transfer
of versioned files for my work. You did throw out the relevant parts
years back. AFAICS, rpms of the macros of the ac-archive do already
exist, it's just the topic of inventing a new one that fits in with
the new webpage style, right.

> 
> This is certainly getting over my head by now (as some submitters have
> noticed by my poor response times) and I could really use some HELP!
> :-)
> 

Yes, I had to make up a kill list so that my automatic sync-scripts do
not try to back-update macros where I have already the newer version
in the archive. As to critize here: quick and nice response to users
and their submission are much higher needed than great new software to
format the submissions. Let's hope you have some more time now for
your people, and of course nice documentation to make it easy for them
to get a benefit from the new format instead of being just burdened
with problems that thy don't actually have with an ac-macro - possibly
making the resistance level higher to actually submit a new ac-macro.

wish you well, cheers, guido                   http://ac-archive.sf.net
p.s. I own ac-archive freshmeat entry - please give me sign as to when
it is time to announce it to the world so that people can have a look.




From MAILER-DAEMON Fri Jan 17 14:40:02 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZcLS-0002ey-00
	for mharc-autoconf@gnu.org; Fri, 17 Jan 2003 14:40:02 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZcLP-0002dO-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 14:39:59 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZcLO-0002cz-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 14:39:58 -0500
Received: from adele.gerwinski.de ([217.69.76.193])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZcDE-0005up-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 14:31:32 -0500
Received: from localhost ([127.0.0.1] helo=gnu.de)
	by adele.gerwinski.de with smtp (Exim 3.35 #1 (Debian))
	id 18ZcDo-0000NP-00
	for <autoconf@gnu.org>; Fri, 17 Jan 2003 20:32:08 +0100
Content-Type: multipart/mixed; boundary="----------=_1042831928-1448-0"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.411 (Entity 5.404)
To: autoconf <autoconf@gnu.org>
From: majordomo-owner@gnu.de
X-Loop: majordomo
Precedence: bulk
Message-Id: <E18ZcDo-0000NP-00@adele.gerwinski.de>
Date: Fri, 17 Jan 2003 20:32:08 +0100
Subject: Majordomo results: The Garden of Eden
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Reply-To: majordomo@gnu.de
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 17 Jan 2003 19:40:00 -0000

This is a multi-part message in MIME format...

------------=_1042831928-1448-0
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
Content-Description: Ignored part.

Ignoring part of type text/html.

------------=_1042831928-1448-0
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
Content-Description: Ignored part.

Ignoring part of type audio/x-midi.

------------=_1042831928-1448-0
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
Content-Description: Results from part 2 of toplevel

>>>> Content-Type: application/octet-stream;
**** Illegal command!

**** Skipped 105 lines of trailing unparseable text.

No valid commands processed.

------------=_1042831928-1448-0--



From MAILER-DAEMON Fri Jan 17 17:10:28 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Zeah-0006N6-00
	for mharc-autoconf@gnu.org; Fri, 17 Jan 2003 17:03:55 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZeR7-0002IZ-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 16:54:01 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZeJV-0005r5-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 16:46:09 -0500
Received: from karman.lufmech.rwth-aachen.de ([134.130.177.1])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZeIw-0005fT-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 16:45:35 -0500
Received: from web.de (tresca.lufmech.RWTH-Aachen.DE [134.130.177.109]) by
	karman.lufmech.rwth-aachen.de with ESMTP (8.9.3 (PHNE_18979)/8.7.1) id
	WAA14841 for <autoconf@gnu.org>; Fri, 17 Jan 2003 22:45:33 +0100 (MET)
Sender: markus@karman.lufmech.rwth-aachen.de
Message-ID: <3E28797C.DC09ACA8@web.de>
Date: Fri, 17 Jan 2003 22:45:32 +0100
From: Markus Werle <numerical.simulation@web.de>
X-Mailer: Mozilla 4.79 [en] (X11; U; HP-UX B.11.11 9000/785)
X-Accept-Language: en
MIME-Version: 1.0
To: autoconf@gnu.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Makefile variables depending on configure args - how?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 17 Jan 2003 22:03:48 -0000

Sorry folks,

this question seemed so simple, but obviously thinking "auto"
differs a lot from what I was used to. Shame on me, but the docs
did not reveal an answer.

Consider my configure.in contains
----------------------------------
# diet headers?
AC_MSG_CHECKING([path to diet headers (http://diet.sf.net/)])
AC_ARG_WITH(diet,
    AC_HELP_STRING([--with-diet=DIET_PREFIX],
            [place where diet headers reside]),
    [ DIETDIR="$withval"; echo $withval; ],
    AC_MSG_ERROR([Please rerun using flag --with-diet=DIET_PREFIX ]) )

CPPFLAGS="-I$DIETDIR $CPPFLAGS"
--------------------------------------


Now in my Makefile.am I want to do 2 things:

First of all I want to add $DIET to VPATH
Second: I want to use $DIET e.g in other definitions:

test_linalg_SOURCES = $(DIET)/demos/linalg/TestLinalg.C

But somehow variable DIET is not propagated from configure.in
to Makefile.am. Is there a workaround for this?

Any solutions welcome,

best regards,

Markus




From MAILER-DAEMON Fri Jan 17 17:23:53 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Zeu0-00009f-00
	for mharc-autoconf@gnu.org; Fri, 17 Jan 2003 17:23:52 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Zety-00006b-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 17:23:50 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Zetx-00006E-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 17:23:49 -0500
Received: from host217-44-174-254.range217-44.btcentralplus.com
	([217.44.174.254] helo=paul.home)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18Zetx-000067-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 17:23:49 -0500
Received: from localhost.localdomain (localhost [127.0.0.1])
	by paul.home (Postfix) with ESMTP
	id 25BE0E4B61; Fri, 17 Jan 2003 22:23:47 +0000 (GMT)
From: Paul Brook <paul@nowt.org>
To: Markus Werle <numerical.simulation@web.de>, autoconf@gnu.org
Date: Fri, 17 Jan 2003 22:23:46 +0000
User-Agent: KMail/1.5
References: <3E28797C.DC09ACA8@web.de>
In-Reply-To: <3E28797C.DC09ACA8@web.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200301172223.46901.paul@nowt.org>
Subject: Re: Makefile variables depending on configure args - how?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 17 Jan 2003 22:23:51 -0000

> Now in my Makefile.am I want to do 2 things:
>
> First of all I want to add $DIET to VPATH

Dunno about this one.

> Second: I want to use $DIET e.g in other definitions:
>
> test_linalg_SOURCES = $(DIET)/demos/linalg/TestLinalg.C
>
> But somehow variable DIET is not propagated from configure.in
> to Makefile.am. Is there a workaround for this?

I think you need to add

AC_SUBST([DIET], [${DIETDIR}])

Paul



From MAILER-DAEMON Fri Jan 17 17:38:24 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Zf80-0002t2-00
	for mharc-autoconf@gnu.org; Fri, 17 Jan 2003 17:38:20 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Zf7g-0002Nm-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 17:38:00 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Zf7N-0001fE-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 17:37:42 -0500
Received: from 64-60-75-69.cust.telepacific.net ([64.60.75.69]
	helo=racerx.ixiacom.com)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18Zf74-0000nH-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 17:37:22 -0500
Received: by racerx.ixiacom.com with Internet Mail Service (5.5.2653.19)
	id <C5QN6XFM>; Fri, 17 Jan 2003 14:37:20 -0800
Message-ID: <15FDCE057B48784C80836803AE3598D53B8A74@racerx.ixiacom.com>
From: Dan Kegel <dkegel@ixiacom.com>
To: 'Markus Werle ' <numerical.simulation@web.de>, "'autoconf@gnu.org '"
	 <autoconf@gnu.org>
Date: Fri, 17 Jan 2003 14:37:19 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Makefile variables depending on configure args - how?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 17 Jan 2003 22:38:18 -0000

Markus wrote:
> Now in my Makefile.am I want to ...
> test_linalg_SOURCES = $(DIET)/demos/linalg/TestLinalg.C

I usually use autoconf variables for that, e.g.

foo = @DIET@/demos/linalg/TestLinalg.C

though I'm not sure automake will be happy with that.




From MAILER-DAEMON Fri Jan 17 21:44:29 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZiyD-0005UZ-00
	for mharc-autoconf@gnu.org; Fri, 17 Jan 2003 21:44:29 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Ziy7-0005Go-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 21:44:23 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Ziy4-0005Fy-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 21:44:21 -0500
Received: from main.gmane.org ([80.91.224.249])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Ziy4-0005Fu-00
	for autoconf@gnu.org; Fri, 17 Jan 2003 21:44:20 -0500
Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18Ziwg-0003FN-00
	for <autoconf@gnu.org>; Sat, 18 Jan 2003 03:42:54 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: autoconf@gnu.org
Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18Ziwf-0003FD-00
	for <gmane-comp-sysutils-autoconf-general@m.gmane.org>;
	Sat, 18 Jan 2003 03:42:53 +0100
Path: not-for-mail
From: Peter Simons <simons@cryp.to>
Date: 18 Jan 2003 03:44:17 +0100
Organization: private
Lines: 162
Message-ID: <87y95jdvni.fsf@overkill.cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@main.gmane.org
Sender: news <news@main.gmane.org>
Subject: Re: Macro Archive Relaunch
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 18 Jan 2003 02:44:27 -0000

Guido Draheim writes:

 >> - A short description of the macro (summary) is visible on the
 >> index page.

 > I did try that lately too - but dumped it as it did clutter the
 > index page with information not really helpful.

There is no need to force the summary onto the index page. It is
absolutely feasible to let the user chose one with short descriptions
or one without them. Nor is it necessary to provide a short
description for macros where the name itself is descriptive enough.
The current index page of the archive shows it for the macros that
provide one and it does not look too bad to me. But again, any number
of presentations can be generated without significant effort.


 >> - Authors can be formatted into a real <a href="mailto:...">name</a>
 >> element on the web page.

 > [...] Personally, I do have some politic problems whether it is
 > actually a wish of the original author be scanned by bots [...].

If the author does not wish to have his e-mail address made public, he
doesn't need to provide one. The <email> tag is optional.


 >> - The synopsis may include <br/> tags to allow for multi-line
 >> formatting.

 > [...] if the synopsis happens to be too long than something may be
 > wrong anyway.

For complex macros, the number of variations may be big enough that it
is easier to list the major "branches" of syntax separately rather
than fitting all of them into one line with tons of brackets thrown
in. Also, packages of macros, which list several macros in one page,
might need this feature. Besides, anyone who doesn't need it should
simply not use it.


 > In parts it stems from the fact that the gnu ac-archive uses h2
 > tags - using some smaller layout tags improves the situation [...]

There is no way to predict the size of an <h2> tag -- or _any_
character on the page, for that matter -- unless you hard-code the
font sizes, what is the last thing I want to do.


 >> The <name> tag [...]

 > [...] I think you mean `macro bundles` as to have multiple macros
 > in one submission file, right?

Sort of. Some submitters have complained that their macros depend so
much on each other that it is hard to break them up into separate
submissions. And even if they did, the user had to download pretty
much all of them anyway. Thus, I wanted to add a concept of
"packages", where macros can be presented (and downloaded) in one
batch, but are nonetheless described individually. The <name> tag is a
first attempt at providing this capability.


 > Do you start a new cvs with it?

No. I re-used the repository original repository. That's what version
control is about, right? :-) I did replace the infrastructure itself,
though.


 > I don't see a problem to blend the new parts into the sfnet branch
 > (as long as the sfnet branch is needed, perhaps (hopefully?) it's
 > obsolete some day)

I never saw the point of the "sfnet branch" having its own macro
repository anyway, to be perfectly honest. I don't mind it the least
that you want to provide another presentation, different release
archive philosophy, etc., but having separate repositories of the
actual macros is, IMHO, counter-productive.


 > [...] some macros might be valid to live in two or more categories.

That is correct, indeed. In the old format, where the location of the
macro in the directory tree determined its category, having a macro in
more than one category was problematic, but in the new format we can
classify them into as many categories as we see fit.


 > Yes, I had to make up a kill list so that my automatic sync-scripts
 > do not try to back-update macros where I have already the newer
 > version in the archive.

What is obviously much less of an effort than helping me to UPDATE the
original repository ...


 > As to critize here: quick and nice response to users and their
 > submission are much higher needed than great new software to format
 > the submissions.

Since you've taken the liberty to criticize my work (throughout this
e-mail), let me say that perhaps me not being really responsive to
YOUR requests has something to do with you committing macros like this
classic example:

 | dnl @synopsis AC_NEED_TARGET_H [(PREFIX, [HEADER-FILE])]           -*- sh -*-
 | dnl
 | dnl  ---------------> superseded by AC_CREATE_TARGET_H <---------------------
 | dnl http://ac-archive.sf.net/guidod/ac_create_target_h.html          USE IT!!
 | [...]

>From CVS log:

    revision 1.3
    date: 2001/08/25 20:12:18;  author: guidod;  state: Exp;  lines: +65 -58

I guess the fact that you deliberately commit an obsolete version into
the archive (at the time you still _had_ CVS commit rights), which
clearly says that it is obsolete and directs users to your "version"
of the archive does understandably annoy me just a bit. I furthermore
assume that the fact that you formatted the macro in a way that breaks
my parser and produces incorrect output on the web page was complete
and utterly unintentional, right?

Let me remind you that the vast majority of content in your archive is
there BECAUSE of the fact that I DO respond to submissions.

>From where I am standing, it looks as if you mostly grab other
people's work, modify it a tiny bit, and then sell it to the world as
your achievement. The infrastructure I wrote is one example, the macro
repository I maintain is another. I am particularly fond of the mighty
"acinclude" tool, about which you say on your web site:

 | To overcome this problem area, Guido Draheim did develop the
 | "acinclude" tool recently - which is actually a copy of "aclocal"
 | modified for the needs of the "ac-archive"

Now, looking at the source code of your powerful tool we read:

 | ## HERE IS THE ONLY DIFFERENCE of $aclocal instead of original aclocal,
 | ## we scan the subdirectories for m4 files instead of the directory itself.

That is certainly an immense development effort and certainly you
should release your "recently developed tool" to the world under a new
name rather than ... uh, sending the fucking 20 line "diff" to the
authors of "aclocal" so that they can incorporate the feature,
shouldn't you?

I swore to myself that I would not get into this issue in this public
forum, but the incredible self-righteous tone in which you go ahead
and have the nerve to criticize me for the work that YOU COPY just
blew my fuse. Just because you legally have the right to re-use my
work doesn't mean that actually doing so (without giving proper
credit) will earn you a class A degree in style.

To summarize: If you have _useful_ comments, ideas for improvements,
or spare time to donate to this project, I'll be the first to welcome
you aboard and to work with you. But I am not willing to take this
kind of bullshit. Alright?

Peter




From MAILER-DAEMON Sat Jan 18 00:03:48 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Zl8w-000813-00
	for mharc-autoconf@gnu.org; Sat, 18 Jan 2003 00:03:42 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Zl8o-0007gC-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 00:03:34 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Zl8Y-00072N-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 00:03:19 -0500
Received: from parcival.faw.uni-ulm.de ([134.60.100.20]
	helo=gawain.faw.uni-ulm.de)
	by monty-python.gnu.org with smtp (Exim 4.10.13)	id 18Zl8X-0006N5-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 00:03:17 -0500
Received: (qmail 25293 invoked from network); 18 Jan 2003 05:03:35 -0000
Received: from dialin54.faw.uni-ulm.de (172.18.1.54)
  by mailserv1.faw.uni-ulm.de with SMTP; 18 Jan 2003 05:03:34 -0000
From: Ralf Corsepius <corsepiu@faw.uni-ulm.de>
To: Autoconf List <autoconf@gnu.org>
In-Reply-To: <200301172223.46901.paul@nowt.org>
References: <3E28797C.DC09ACA8@web.de>  <200301172223.46901.paul@nowt.org>
Content-Type: text/plain
Organization: FAW Ulm
Message-Id: <1042866337.29339.18146.camel@mccallum.corsepiu.faw.uni-ulm.de>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.1 
Date: 18 Jan 2003 06:05:40 +0100
Content-Transfer-Encoding: 7bit
X-Spam: Pruefung durchlaufen
Subject: Re: Makefile variables depending on configure args - how?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 18 Jan 2003 05:03:41 -0000

Am Fre, 2003-01-17 um 23.23 schrieb Paul Brook:
> > Now in my Makefile.am I want to do 2 things:
> >
> > First of all I want to add $DIET to VPATH
> 
> Dunno about this one.

Using Make-variables (e.g. $(DIET)) in $VPATH is non-portable,
error-prone and (somewhat) dangerous, nevertheless it should work with
gnu-make, if you know what you are doing.

IIRC, there is a section in autoconf.info or automake.info which
decribes the details.

Ralf





From MAILER-DAEMON Sat Jan 18 09:19:02 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Zto4-00063Y-00
	for mharc-autoconf@gnu.org; Sat, 18 Jan 2003 09:18:44 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Ztnw-0005iM-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 09:18:36 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZtnI-0003od-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 09:18:13 -0500
Received: from mail.gmx.net ([213.165.64.20])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18ZtnB-0003T2-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 09:17:50 -0500
Received: (qmail 1545 invoked by uid 0); 18 Jan 2003 14:17:47 -0000
Received: from pd9e80cbf.dip.t-dialin.net (HELO gmx.de) (217.232.12.191)
  by mail.gmx.net (mp023-rz3) with SMTP; 18 Jan 2003 14:17:47 -0000
Message-ID: <3E296283.5080208@gmx.de>
Date: Sat, 18 Jan 2003 15:19:47 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Peter Simons <simons@cryp.to>,  autoconf@gnu.org
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Macro Archive Relaunch
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 18 Jan 2003 14:18:41 -0000

Peter Simons schrieb:
> Guido Draheim writes:
> 
>  >> - A short description of the macro (summary) is visible on the
>  >> index page.
> 
>  > I did try that lately too - but dumped it as it did clutter the
>  > index page with information not really helpful.
> 
> There is no need to force the summary onto the index page. It is
> absolutely feasible to let the user chose one with short descriptions
> or one without them. Nor is it necessary to provide a short
> description for macros where the name itself is descriptive enough.
> The current index page of the archive shows it for the macros that
> provide one and it does not look too bad to me. But again, any number
> of presentations can be generated without significant effort.

hmmm, just to get that straight - the index item has only a default
for the filename stem and the user may replace it with its own
one-liner. That might impose problems to readability if that does
not follow a certain scheme but I am quite confident that it does
work out somehow. Just needs someone to look over it ;-)

> 
> 
>  >> - Authors can be formatted into a real <a href="mailto:...">name</a>
>  >> element on the web page.
> 
>  > [...] Personally, I do have some politic problems whether it is
>  > actually a wish of the original author be scanned by bots [...].
> 
> If the author does not wish to have his e-mail address made public, he
> doesn't need to provide one. The <email> tag is optional.

Ahmm, it's all about the converting the classic ones, if the user
knows about having a href to get into the webpage layout, that is
all perfectly well.

> 
> 
>  >> - The synopsis may include <br/> tags to allow for multi-line
>  >> formatting.
> 
>  > [...] if the synopsis happens to be too long than something may be
>  > wrong anyway.
> 
> For complex macros, the number of variations may be big enough that it
> is easier to list the major "branches" of syntax separately rather
> than fitting all of them into one line with tons of brackets thrown
> in. Also, packages of macros, which list several macros in one page,
> might need this feature. Besides, anyone who doesn't need it should
> simply not use it.

aaaah! now that's a very good one - alternative synpsis. I am not
sure however if it is best to use <br> instead of a proper list that
gets visuallized with as a the list combined with <br> between
them.

> 
> 
>  > In parts it stems from the fact that the gnu ac-archive uses h2
>  > tags - using some smaller layout tags improves the situation [...]
> 
> There is no way to predict the size of an <h2> tag -- or _any_
> character on the page, for that matter -- unless you hard-code the
> font sizes, what is the last thing I want to do.

well, one can usually have a try, and it is quite big someplace ;-)

> 
> 
>  >> The <name> tag [...]
> 
>  > [...] I think you mean `macro bundles` as to have multiple macros
>  > in one submission file, right?
> 
> Sort of. Some submitters have complained that their macros depend so
> much on each other that it is hard to break them up into separate
> submissions. And even if they did, the user had to download pretty
> much all of them anyway. Thus, I wanted to add a concept of
> "packages", where macros can be presented (and downloaded) in one
> batch, but are nonetheless described individually. The <name> tag is a
> first attempt at providing this capability.

good.

> 
> 
>  > Do you start a new cvs with it?
> 
> No. I re-used the repository original repository. That's what version
> control is about, right? :-) I did replace the infrastructure itself,
> though.
> 
> 
>  > I don't see a problem to blend the new parts into the sfnet branch
>  > (as long as the sfnet branch is needed, perhaps (hopefully?) it's
>  > obsolete some day)
> 
> I never saw the point of the "sfnet branch" having its own macro
> repository anyway, to be perfectly honest. I don't mind it the least
> that you want to provide another presentation, different release
> archive philosophy, etc., but having separate repositories of the
> actual macros is, IMHO, counter-productive.

just so there is a versioning for the sfnet webpage and packaging,
it is not some original intent to have one, and can be dump as
well if that is feasible.

> 
> 
>  > [...] some macros might be valid to live in two or more categories.
> 
> That is correct, indeed. In the old format, where the location of the
> macro in the directory tree determined its category, having a macro in
> more than one category was problematic, but in the new format we can
> classify them into as many categories as we see fit.
> 
> 
>  > Yes, I had to make up a kill list so that my automatic sync-scripts
>  > do not try to back-update macros where I have already the newer
>  > version in the archive.
> 
> What is obviously much less of an effort than helping me to UPDATE the
> original repository ...

I would well do so, but you threw me out of cvs access, and having
a dozen macros send by mail is a tedious task, especially if that
is not rewarded by immediate response.

> 
> 
>  > As to critize here: quick and nice response to users and their
>  > submission are much higher needed than great new software to format
>  > the submissions.
> 
> Since you've taken the liberty to criticize my work (throughout this
> e-mail), 

... to help in the matter...


> let me say that perhaps me not being really responsive to
> YOUR requests has something to do with you committing macros like this
> classic example:
> 
>  | dnl @synopsis AC_NEED_TARGET_H [(PREFIX, [HEADER-FILE])]           -*- sh -*-
>  | dnl
>  | dnl  ---------------> superseded by AC_CREATE_TARGET_H <---------------------
>  | dnl http://ac-archive.sf.net/guidod/ac_create_target_h.html          USE IT!!
>  | [...]
> 
>>From CVS log:
> 
>     revision 1.3
>     date: 2001/08/25 20:12:18;  author: guidod;  state: Exp;  lines: +65 -58
> 
> I guess the fact that you deliberately commit an obsolete version into
> the archive (at the time you still _had_ CVS commit rights), which
> clearly says that it is obsolete and directs users to your "version"
> of the archive does understandably annoy me just a bit. I furthermore
> assume that the fact that you formatted the macro in a way that breaks
> my parser and produces incorrect output on the web page was complete
> and utterly unintentional, right?

It must have been unintentional, and since the sfnet website did use the
very same formatter, it would have broken the webpage on sfnet as well.
No need to spawn conspiracy theories here, there are none about.

I am well astonished by the means of communication you choose, you did
not tell me about this exact problem you had with submissions, I would
surely have fixed that right away if you've told me. Neither did you
say it was a reason to kill write-access and not let me help you to
keep the gnu macro archive in the most uptodate form as possible.

It was quite obvious that there might have gone something wrong, so
I did ask you three times to have a chat, I gave you my telephone number
and asked for talk to clear up anything that might have become
misunderstood. You did just ignored these attempts. And to say it
loud, I do _not_ like it that problems in personal interrelations are
going to a public mailing list.

> 
> Let me remind you that the vast majority of content in your archive is
> there BECAUSE of the fact that I DO respond to submissions.

I did never say anything else.

> 
>>From where I am standing, it looks as if you mostly grab other
> people's work, modify it a tiny bit, and then sell it to the world as
> your achievement. 

you do grab other people's macros, and sell them to world.

There we have conspiracies coming up again - look back in history,
I did have a completely different backgrond: I did work up a
packaging system for my own series of autoconf macros so that
I could carry them between the different workplaces (home, univesity,
employer) and have them properly installed and versioned. When
the ac-archive came up as a topic, I was happy to see that there
was a wider approach of autoconf extensions. So I came on you
asking whether it would be fair to merge packaging into the
ac-archive infrastructure. You said yes and gave me the key.

When the work was done, I asked you if that was okay for you.
You said no, and threw it out - I was trying to ask you _what_
was wrong and to help me to fix it so that it does suit your
taste. No response. That was the moment the sfnet branch
sprang up, so I could continue with a combined approach of
the ac-archive and the packaging idea that I was in need so
desperatly in real life.

Of course, it does pick up the ac-archive macros. And at that
time I was thinking that it is just a temporary means as to
keep on the work and merge the branches a few weeks later.
That's the only reason it calls itself `ac-archive` too,
otherwise it would have been called `ac-packaging` or
some such - and perhaps that would not have given you the
idea of any intents to diminish your work. There was no
such original intent, please acknowledge that to my honour.


 > The infrastructure I wrote is one example, the macro
> repository I maintain is another. I am particularly fond of the mighty
> "acinclude" tool, about which you say on your web site:

sarcasm? ;-)

> 
>  | To overcome this problem area, Guido Draheim did develop the
>  | "acinclude" tool recently - which is actually a copy of "aclocal"
>  | modified for the needs of the "ac-archive"
> 
> Now, looking at the source code of your powerful tool we read:
> 
>  | ## HERE IS THE ONLY DIFFERENCE of $aclocal instead of original aclocal,
>  | ## we scan the subdirectories for m4 files instead of the directory itself.
> 
> That is certainly an immense development effort and certainly you
> should release your "recently developed tool" to the world under a new
> name rather than ... uh, sending the fucking 20 line "diff" to the
> authors of "aclocal" so that they can incorporate the feature,
> shouldn't you?

aahm, would you please be fair - the announcment itself says that it is
derived from the `aclocal` tool. Later on, some more lines were added,
there are now a bit more differences that those marked as "THE ONLY"
(I probably should clean that). Yes, it would have been nice to merge
some functionality back, but `aclocal` has evolved ever since and it
is now using the infrastructure of later automake with their own
perl packages and config log scanning (is that the right term?).
Actually, I did not want to have a dependency on later automake
infrastructure so that the acinclude tool does still follow the
implementation of the one from 1.4.

> 
> I swore to myself that I would not get into this issue in this public
> forum, but the incredible self-righteous tone in which you go ahead
> and have the nerve to criticize me for the work that YOU COPY just
> blew my fuse. Just because you legally have the right to re-use my
> work doesn't mean that actually doing so (without giving proper
> credit) will earn you a class A degree in style.

yes, you did explode. The comments in the prior mail were on facts,
and it would have been okay to just comment on the facts in public
and make an extra private mail to me to communicate the personal
problems. I do not like to see it dragged into a public list, and
be in the need to respond to it in public.

> 
> To summarize: If you have _useful_ comments, ideas for improvements,
> or spare time to donate to this project, I'll be the first to welcome
> you aboard and to work with you. But I am not willing to take this
> kind of bullshit. Alright?
> 

Well, so far my incredible self-righteous tone would only say that
this was just the `last paragraph`. I've been always willing to help,
and the prior mail was an attempt to give _useful_ comments, both
for improvements and telling of experiences that I have made in
my own attempts with developing the project. The only personalizing
part is with the speed that you usually respond to e-mails and
the interactions with contributors about possible problems - and
that made you explode or so it seems. I maintain there was no
bullshit intended, and if you need more credit markers on the sfnet
webpages, that's no problem with me.

I would please ask you to kill any signs of conpiracy theories from
your mind - as that the sfnet branch had been an attempt to snatch
away your work, close to theft or something. It's been about to
extend your work and have it ready to get merged back as soon as
possible - even today, the `make rpm` will create a number of files
including ac-archive-doc-gnuorg-*.rpm, as an attempt to show that
the makesystem is still capable of making the gnu.org webpages, so
it can be picked up as is. It seems it got unnoticed by you. Since
it was always the intent to have the makesystem ready to get back to
gnu servers anytime soon, I did not chose to copy the gnu ac-archive
macros from  remote but to keep a local copy of them `as if` the
makesystem would run locally on the gnu repository.

Only later it came to be that the macros were updated independently,
as it turned out to seem them being sometimes more uptodate and the
gnu ac-archive to follow weeks and weeks later. That time skew and
depending workstyle put a stress on to me to think over what the
project will come to be in the forseeable future, and if it was still
okay to wait for you. It is good that now, years later, the topic
gets finally put-into-words by you as well, I was waiting for that
so long.

Let's put it straight and in a few words: I do not see a benefit in
trying to maintain projects uneccesarily if there is a volunteer
around who is doing it, also to _my_ benefit, and where I do only
need to _add_ some effort to help. The existance of the sfnet
branch is over the day that the gnu org ac-archive is capable of
doing what I need. It doesn't. So stop complaining that I am
doing something seperately.

looking forward to your response,
and surely it does _not_ need to be public, it is fairly okay with
me to explode on side channels - or on the phone. The lines are
still open, and to make it easier, I'll (re)send you my phone
number off-mailinglist the next minute. Let's get this done once
and for all, pleeeaassse.
-- cheers, guido




From MAILER-DAEMON Sat Jan 18 11:17:15 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Zvdn-0005Hi-00
	for mharc-autoconf@gnu.org; Sat, 18 Jan 2003 11:16:15 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZvdZ-0004eP-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 11:16:01 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZvdA-0003ST-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 11:15:39 -0500
Received: from main.gmane.org ([80.91.224.249])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18Zvcx-0002qQ-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 11:15:23 -0500
Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18ZvbY-0001mA-00
	for <autoconf@gnu.org>; Sat, 18 Jan 2003 17:13:56 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: autoconf@gnu.org
Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18ZvbX-0001lz-00
	for <gmane-comp-sysutils-autoconf-general@m.gmane.org>;
	Sat, 18 Jan 2003 17:13:55 +0100
Path: not-for-mail
From: Peter Simons <simons@cryp.to>
Date: 18 Jan 2003 17:15:21 +0100
Organization: private
Lines: 17
Message-ID: <87adhyph7q.fsf@overkill.cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@main.gmane.org
Sender: news <news@main.gmane.org>
Subject: Re: Macro Archive Relaunch
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 18 Jan 2003 16:16:13 -0000

Guido Draheim writes:

 > I am not sure however if it is best to use <br> instead of a proper
 > list that gets visuallized with as a the list combined with <br>
 > between them.

IMHO the only viable alternative would be to use an abstract
description of "macro parameters", which describes semantics. The
Docbook format does provide something like that, for instance, but I
thought that this would be excessively complicated for the submitter
and would probably never be used anyway.

So ... any ideas on the list of topics I posted in the first article,
anyone? New categories? Automatic submission and validation processes?
Web site design? Anything?

Peter




From MAILER-DAEMON Sat Jan 18 11:59:51 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZwJz-0008JG-00
	for mharc-autoconf@gnu.org; Sat, 18 Jan 2003 11:59:51 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZwJx-0008Ip-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 11:59:49 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZwJu-0008EP-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 11:59:48 -0500
Received: from main.gmane.org ([80.91.224.249])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZwJu-0008DF-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 11:59:46 -0500
Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18ZwIV-00040O-00
	for <autoconf@gnu.org>; Sat, 18 Jan 2003 17:58:19 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: autoconf@gnu.org
Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18ZwIT-000405-00
	for <gmane-comp-sysutils-autoconf-general@m.gmane.org>;
	Sat, 18 Jan 2003 17:58:17 +0100
Path: not-for-mail
From: Peter Simons <simons@cryp.to>
Date: 18 Jan 2003 17:59:42 +0100
Organization: private
Lines: 158
Message-ID: <873cnqpf5t.fsf_-_@overkill.cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@main.gmane.org
Sender: news <news@main.gmane.org>
Subject: [OT] Guido Draheim vs. Peter Simons vs. Rest of the World  (was:
 Macro Archive Relaunch)
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 18 Jan 2003 16:59:49 -0000

Let me summarize the statements you made in your e-mail:

 (1) You cannot commit new versions of macros into the GNU archive
     because I revoked your CVS access:

      > I would well do so, but you threw me out of cvs access, and
      > having a dozen macros send by mail is a tedious task [...]

    Also:

      > [You would] kill write-access and not let me help you to keep
      > the gnu macro archive in the most uptodate form as possible.


 (2) I am suffering from delusions assuming that you could possibly
     commit macros with broken formatting intentionally:

      > It must have been unintentional, and since the sfnet website
      > did use the very same formatter, it would have broken the
      > webpage on sfnet as well. No need to spawn conspiracy theories
      > here, there are none about.


 (3) I am dragging personal matters into the public:

      > [...] I do _not_ like it that problems in personal
      > interrelations are going to a public mailing list.


 (4) I threw away your efforts to contribute to the Autoconf Macro
     Archive:

      > [...] I came on you asking whether it would be fair to merge
      > packaging into the ac-archive infrastructure. You said yes and
      > gave me the key.

      > When the work was done, I asked you if that was okay for you.
      > You said no, and threw it out - I was trying to ask you _what_
      > was wrong and to help me to fix it so that it does suit your
      > taste. No response.


So let's get this over with:

You say that could not update the macros in the original archive
because I revoked your commit rights. This is contrary to the facts:
You DID commit obsolete macros into the archive. Looking at

http://savannah.gnu.org/cgi-bin/viewcvs/ac-archive/ac-archive/macros/legacy/misc/ac_need_target_h.m4?rev=1.3&content-type=text/vnd.viewcvs-markup

will confirm that. Clearly, you stopped updating the archive while you
still had CVS access.


You furthermore say that the broken formatting must have been a
mistake, arguing:

 > It must have been unintentional, and since the sfnet website
 > did use the very same formatter, it would have broken the
 > webpage on sfnet as well.

You forget that you committed the broken macro into the original
archive, while the new one, which apparently worked perfectly with the
"macro2html" tool, went into your own repository. If nothing else, you
did not bother to check that your additions to the archive even work
-- which is the whole point of having a maintainer. Given the comment
at the top of the macro (that the link above will show), I don't think
assuming intention is an outlandish thing to do. For the record I
admit that I cannot prove intent, so -- if you prefer that -- I will
reduce my statement to you being careless.


You complain that I drag personal matters into the public. First of
all, this is not a personal matter. I don't know you. For all I know,
you might be the sweetest guy in the world. It doesn't really matter
either. I don't have a problem with you personally.

I have a problem with you copying my infrastructure, the archive I
maintain, the web page I created around it (verbatim, word by word) --
but you don't give any credit about it at all. Even better, you
actually bash the effort I am putting into it. (On this list, on your
web site, and in the commit messages of your CVS repository.)

I have a problem with you misleading the users of your archive. On
your web page you say:

 | If you want to contribute ...
 |
 | then please don't hesitate a second! Just send the m4 source to
 | Guido Draheim <guidod@gnu.org> via electronic mail. [...] Note that
 | the two ac-archive repositories (sourceforge and savannah) are
 | constantly kept in sync [...].

The two archives are NOT kept "in sync". You download the macros from
the GNU archive and add them into yours -- but not the other way
round, because I do not accept submissions unless they come from the
AUTHOR of the macro, since he is the only person who can license his
intellectual property according to the terms described on my page. You
make it look as if it really doesn't matter where authors send their
macros to, because they will end up in both archives anyway, right?
The truth is, that if someone submits a macro to the GNU archive, it
will end up in both archives. If he sends it to you, it will be
available in yours only.

I furthermore have a problem with you advertising your archive as
being the cool one, which "offers space for experimental extras",
while you call the original one the "basic archive". What exactly does
that mean? Do you have evidence of me ever rejecting a submission
because it was too "experimental"?

I have a problem with you -- through intent or carelessness --
breaking the build mechanism of the GNU archive, as I have said
repeatedly.

My impression is that you have a _personal_ problem with me. Not the
other way round. When I posted my original article to this list, I
knew that you would JUMP at it, and that you wouldn't have many
positive things to say about what I do. Surprise! Here we are.

To address the other part of your statement: I reply to e-mails I
receive through a public forum in the same public forum. Sending an
e-mail to this list, which makes false claims, and then telling me
that we should discuss this in private, is a half-assed way of trying
to get the last word.


Last but not least, let's look at your repeated claim that I threw
away your work. If you would kindly look at the commit message shown
here:

http://savannah.gnu.org/cgi-bin/viewcvs/ac-archive/legacy-ac-archive/Attic/Makefile.am?hideattic=0

you might remember that I was pretty busy moving the archive onto the
GNU server at the time, when you added LOADS of stuff. As the result,
I was not able to build the archive ON MY OWN MACHINE, because it
simply did not work. So I moved your changes into a branch. I did NOT
throw it away. But you chose to feel mortally offended, and that is
where the whole mess began.


I have no intention whatsoever of trying to "resolve" this issue. I do
not want to discuss this matter to a much greater extend than I did
already. It feels nice to have gotten this off my chest, finally, but
it is childish nonetheless. Anyone who is even remotely interested in
this topic can look at the publicly available web sites and CVS
repositories, to gather all the facts he would ever need to have an
opinion about this.

I did release the archive's infrastructure under the GPL license and I
am perfectly prepared for people to do with it whatever they want to
as long as they obey the license. It is not necessary for me to _like_
what they do with it.

Any further constructive discussion may, of course, take place in the
original thread, which I intentionally split off this stupid flame
fest of mine. :-|

Peter




From MAILER-DAEMON Sat Jan 18 13:58:50 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Zy9l-0002KK-00
	for mharc-autoconf@gnu.org; Sat, 18 Jan 2003 13:57:25 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Zy9O-0001c5-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 13:57:02 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Zy9I-0001M8-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 13:56:58 -0500
Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18Zy9G-0001BH-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 13:56:54 -0500
Received: (qmail 1534 invoked by uid 0); 18 Jan 2003 18:56:51 -0000
Received: from pd9e80cbf.dip.t-dialin.net (HELO gmx.de) (217.232.12.191)
  by mail.gmx.net (mp013-rz3) with SMTP; 18 Jan 2003 18:56:51 -0000
Message-ID: <3E29A3EC.3020105@gmx.de>
Date: Sat, 18 Jan 2003 19:58:52 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: autoconf@gnu.org
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<87adhyph7q.fsf@overkill.cryp.to>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Macro Archive Relaunch
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 18 Jan 2003 18:57:23 -0000

Peter Simons schrieb:
> Guido Draheim writes:
> 
>  > I am not sure however if it is best to use <br> instead of a proper
>  > list that gets visuallized with as a the list combined with <br>
>  > between them.
> 
> IMHO the only viable alternative would be to use an abstract
> description of "macro parameters", which describes semantics. The
> Docbook format does provide something like that, for instance, but I
> thought that this would be excessively complicated for the submitter
> and would probably never be used anyway.
> 

let me first state that it is a good idea to split the technical
parts off the original thread. ;-)

No, actually I would not think of making up a full parameter
description - it might be interesting to attempt such but in
the real world one might argue what effect it has to markup
things into machine-readable format when there is no benefit
from processing it. The invokation-description is surely
meant for the human reader, and a multi-line synopsis showing
examples of possible usage are just great.

However, each synopsis might need its own set of descriptions,
sometimes the number or existance of some argument can change
the actual processing of the macro - at the moment this is
described in prosa in the macro description (I am thinking of
the original autoconf project here) referring to the first
and second invokation format.

There might be the task to bind these more closely, or the
wish to serialize invokation formats into `important` or
`rare` as to omit the latter from some index formats. That
did spawn the idea to markup each invokation synopsis line
by itself as to be able to process it for actual index
formatting.

If such extra index formats are actully useful or currently
in the planning, that is all a different case tho ;-)

-- cheers, guido





From MAILER-DAEMON Sat Jan 18 14:52:29 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Zz0j-0000HA-00
	for mharc-autoconf@gnu.org; Sat, 18 Jan 2003 14:52:09 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18Zz0X-0008Fw-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 14:51:57 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18Zz0K-0007j2-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 14:51:45 -0500
Received: from pop.gmx.net ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18Zz0H-0007Z8-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 14:51:41 -0500
Received: (qmail 15363 invoked by uid 0); 18 Jan 2003 19:51:39 -0000
Received: from pd9e80cbf.dip.t-dialin.net (HELO gmx.de) (217.232.12.191)
  by mail.gmx.net (mp021-rz3) with SMTP; 18 Jan 2003 19:51:39 -0000
Message-ID: <3E29B0C3.3000306@gmx.de>
Date: Sat, 18 Jan 2003 20:53:39 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Peter Simons <simons@cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<873cnqpf5t.fsf_-_@overkill.cryp.to>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: [OT] Guido Draheim vs. Peter Simons vs. Rest of the World(was:
 Macro Archive Relaunch)
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 18 Jan 2003 19:52:07 -0000

Peter Simons schrieb:
> Let me summarize the statements you made in your e-mail:

Oh my... no phone call then.

Let me inject a short paragraph to the casual reader: flame wars
are nothing atypical in the opensource world, in fact it is thought
of being quite helpful as to clean up things and it can often help
clearing the minds of the contenders - and possibly leading to
better cooperation on the actual subject, the project work. Many
items spring up from the thin communication lines that the internet
presents - lots of what is `intended` or `done in error` happens
to be just speculation. These however are picked up and made up
into proper accusations, possibly extended with `evidence`
material. Such a thread usually meanders quite a time until the
silent readers of the mailinglist - and mostly partakers in the
original autoconf project - are fed up and make some noise
themselves which usually ends the discussion quickly thereafter.

In the current `case`, atleast four points are presented and
summed with a speech as to what that points at. I have some
`evidence` as well in my pocket which was not mentioned to this
point publically, - but there is hope that the flaming can be
ended more  quickly with the help of another argument chain that
follows up this quote:

> I have no intention whatsoever of trying to "resolve" this issue. I do
> not want to discuss this matter to a much greater extend than I did
> already. It feels nice to have gotten this off my chest, finally, but
> it is childish nonetheless. [...]
> 
> I did release the archive's infrastructure under the GPL license and I
> am perfectly prepared for people to do with it whatever they want to
> as long as they obey the license. It is not necessary for me to _like_
> what they do with it.
> 

Yes, putting work under GPL means to let it get extended by other
people - they can just take it even without asking. But that still
works out in the end since the original maintainer is always free
to take back, to pick up the material that was created by the
other one - the GPL ensures that all additions and modifications
are free to do such, even without asking, again. It goes both ways.

We see the effect that `merging` of projects is quite a natural
situation in the gnu world, there is nothing like longstanding
forks and branches since there is no point in doing doublework
as it happens to be with the maintainance of a common subset of
the two parts.

What I am pointing at: it is your own free will to not take any
benefit from the sfnet efforts, to diminish the work that is
presented there, to talk aggressivly about the other author of
those works, and culminate that there is no point in resolving
the issue, perhaps as  you just do not see anything worth in the
sfnet part (and possibly neither its author).

Many people have come to respect the works of the sfnet branch
and while you were starting your own extensions I was here on
the autoconf list, present to answer questions and to point to
possible solutions from the ac-archive. Surely, I did use the
link to the sfnet one since I knew it was up to date while it
became a common case the the gnu part was possibly a few weeks
thereafter.

As a result, more and more of the other people on the autoconf
mailing list did start to pick the sfnet branch when showing
references to ac-archive macros themselves. Perhaps it did
look to some as if the gnu site was not maintained in the way
that people might expect, and which they can get from the
sfnet branch. I was hoping that this effect lead to you to
strengthen your efforts with the gnu site.

That would have wiped the sfnet branch off the internet for it
can not catch up - it is in a minor position anyway since the
main autoconf site does point to the gnu ac-archive alone, and
you did never install a link to the sfnet branch either even
that you promised to do that, a year ago. It is therefore
interesting to see the sfnet branch is actually able to be
seen as a competitor by you that you need to come down badly on.

I am very dissatisfied that there is less hope in seeing the
two parts merged back anytime soon. Hopefully you can work out
a way for you to finally come to terms with me and the "Rest
of the world" that you involve in the subject of this thread.
The task should be cooperation, and that means communications,
and there was not enough of the latter during the last year,
and it is good that finally you started to talk about it, even
when that is done in public instead of doing it directly between
you and me, just presenting the results to the autoconf mailinglist.

best wishes, guido




From MAILER-DAEMON Sat Jan 18 15:06:03 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ZzE7-0004Sf-00
	for mharc-autoconf@gnu.org; Sat, 18 Jan 2003 15:05:59 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ZzE2-0004LY-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 15:05:54 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ZzDx-0004CU-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 15:05:51 -0500
Received: from main.gmane.org ([80.91.224.249])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ZzDr-00040w-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 15:05:44 -0500
Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18ZzCT-0003zT-00
	for <autoconf@gnu.org>; Sat, 18 Jan 2003 21:04:17 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: autoconf@gnu.org
Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18ZzCS-0003zI-00
	for <gmane-comp-sysutils-autoconf-general@m.gmane.org>;
	Sat, 18 Jan 2003 21:04:16 +0100
Path: not-for-mail
From: Peter Simons <simons@cryp.to>
Date: 18 Jan 2003 21:05:41 +0100
Organization: private
Lines: 62
Message-ID: <87of6enrze.fsf@overkill.cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<87adhyph7q.fsf@overkill.cryp.to> <3E29A3EC.3020105@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@main.gmane.org
Sender: news <news@main.gmane.org>
Subject: Re: Macro Archive Relaunch
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 18 Jan 2003 20:05:57 -0000

Guido Draheim writes:

 > [binding synopsis more closely to description]

Technically, the <synopsis> tag could contain legal XHTML 1.0.
element. I intentionally limited the number of valid tags to make the
format less confusing, but basically the DTD would allow for complete
XHTML a.k.a. HTML 4.01 to be used. Thus, we _could_ support
enumerations, anchors (with references to them), heck, we could even
support JavaScript if we had to. :-)

For the moment my intuition tells me that the XML format should be as
simple as humanly possible. I hope to be able to convince the AutoGen
guys that they adapt their _way_ _cool_ macro generation page to
output XML; then the submitters would most probably not have to bother
with writing XML at all. Many people seem to be reluctant to adopt
this standard. (Which is why I want to keep supporting the "legacy
format".)

As for the new categorization ... Currently we have these:

    C Support
        Properties of the C compiler.

    C++ Support
        Properties of the C++ compiler.

    Java Support
        Properties of the Java Environment.

    Cross Compilation
        Really advanced stuff.

    Installed Packages
        How to I link OpenGL? Where are the header files? And while
        we're at it ... What is OpenGL?

    Miscellaneous
        Catch all

New ones that I would consider to be useful are:

    System Headers
        Tests for the existence of "foobar.h", or whether it defines
        "foo_bar_t" or not, etc.

    System Utilities
        Does the "foo" program support the "--bar" flag? Is it
        installed at all? What version of the Intel C++ compiler do I
        have?

    Build Infrastructure
        Generate a "foobar-config" script, cool Autoconf extensions,
        etc. 

Can anyone think of others that would make sense? Would it be better
to merge "System Headers" and "System Utilities" into one great
"System Properties"? Or is that too generic? Would you split the
"System Headers" into "... Typedefs" and "... Structures" like the
Autoconf Manual does?

Comments?




From MAILER-DAEMON Sat Jan 18 16:04:02 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18a082-0001T9-00
	for mharc-autoconf@gnu.org; Sat, 18 Jan 2003 16:03:46 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18a07y-0001Ns-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 16:03:42 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18a07g-0001Cm-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 16:03:26 -0500
Received: from smtp.comcast.net ([24.153.64.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18a04L-0006op-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 15:59:57 -0500
Received: from [192.168.2.28]
 (pcp01203196pcs.nrockv01.md.comcast.net [68.50.219.54])
 by mtaout06.icomcast.net
 (iPlanet Messaging Server 5.2 HotFix 1.07 (built Nov 25 2002))
 with ESMTP id <0H8X00MR6GYLMS@mtaout06.icomcast.net> for autoconf@gnu.org;
 Sat, 18 Jan 2003 15:59:10 -0500 (EST)
Date: Sat, 18 Jan 2003 16:06:01 -0500
From: Braden McDaniel <braden@endoframe.com>
In-reply-to: <87of6enrze.fsf@overkill.cryp.to>
To: Peter Simons <simons@cryp.to>
Message-id: <1042923960.16849.53.camel@localhost.localdomain>
Organization: 
MIME-version: 1.0
X-Mailer: Ximian Evolution 1.2.1
Content-type: text/plain
Content-transfer-encoding: 7BIT
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
 <87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
 <87adhyph7q.fsf@overkill.cryp.to> <3E29A3EC.3020105@gmx.de>
 <87of6enrze.fsf@overkill.cryp.to>
cc: autoconf@gnu.org
Subject: Re: Macro Archive Relaunch
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 18 Jan 2003 21:03:44 -0000

On Sat, 2003-01-18 at 15:05, Peter Simons wrote:

[snip]

>     Installed Packages
>         How to I link OpenGL? Where are the header files? And while
>         we're at it ... What is OpenGL?

I'm gonna subvert this reference to OpenGL to an opportunity to jump in
and get some things off my own chest.

I recently submitted to Guido a couple of macros that do OpenGL
detection. I was unaware of the politics involved in the existence of
two ac-archives. I would just like to say: for heaven's sake,
gentlement, work this out. It's ridiculous for two completely separate
ac-archive projects to exist. autoconf has a steep enough learning curve
as it is. The ac-archive should be something that makes new users' lives
easier--not something that baffles them further.

>From my own point of view, there needs to be a single point of
submission. Otherwise, new macros are likely to go to each of you in a
haphazard fashion. I cannot imagine that to be a desirable situtation.

-- 
Braden McDaniel                           e-mail: <braden@endoframe.com>
<http://endoframe.com>                    Jabber: <braden@jabber.org>




From MAILER-DAEMON Sat Jan 18 19:41:44 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18a3Wy-00083J-00
	for mharc-autoconf@gnu.org; Sat, 18 Jan 2003 19:41:44 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18a3Wu-0007zg-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 19:41:40 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18a3VM-0007Jo-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 19:40:06 -0500
Received: from main.gmane.org ([80.91.224.249])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18a3VF-000792-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 19:39:57 -0500
Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18a3Tp-0006im-00
	for <autoconf@gnu.org>; Sun, 19 Jan 2003 01:38:29 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: autoconf@gnu.org
Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18a3Tp-0006ic-00
	for <gmane-comp-sysutils-autoconf-general@m.gmane.org>;
	Sun, 19 Jan 2003 01:38:29 +0100
Path: not-for-mail
From: Peter Simons <simons@cryp.to>
Date: 19 Jan 2003 01:39:54 +0100
Organization: private
Lines: 222
Message-ID: <87hec6nfad.fsf_-_@overkill.cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<873cnqpf5t.fsf_-_@overkill.cryp.to> <3E29B0C3.3000306@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@main.gmane.org
Sender: news <news@main.gmane.org>
Subject: Re: [OT] Guido Draheim vs. Peter Simons vs. Rest of the World
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 00:41:42 -0000

I am sorry to disturb your emotional "we should all be friends"-speech
with _facts_ once more. You wrote:

 > I did use the link to the sfnet [archive when answering questions,]
 > since I knew it was up to date while it became a common case the
 > the gnu part was possibly a few weeks thereafter.

You imply that the archive I maintain was lagging behind yours, right?
When I look at the complete list of CVS commits in your repository,
which one can generate in a checked-out copy with the rcs2log(1) tool
that comes with CVS, I see exactly three types of commits in the macro
area:

 (1) The ones that say: "sync with gnu ac-archive".

 (2) The ones that commit changes to files in the "guidod"
     subdirectory. (Or "rleigh", "braden", etc. to be accurate.)

 (3) The ones that commit changes to the directory tree used in
     original archive as well.

Everybody who's interested is invited to check this; the data is
publicly available.

If your archive was more up-to-date than mine -- and that is what you
claim --, we should see commits as evidence for that, right? Which
ones could that be ... I am sure we agree that group (1) does _not_
fall into this category. You were downloading content from the GNU
archive in this case.

How about group (2) then? The macros in the "guidod" directory are
doubtlessly ahead of the GNU archive simply because I never received
any updates from you. (We already talked about the ones in the GNU
archive that are _known_ to be obsolete.) The ones in the remaining
all-lower-caps directories could be in the GNU archive as well,
meaning that they were submitted to both of us. And you could possibly
have updated them faster than I did.

The macros is these areas that the GNU archive has too are:

    c_support/ac_func_mkdir.m4
    installed_packages/ac_config_libconfig_in.m4
    installed_packages/ac_config_pkgconfig_in.m4
    installed_packages/ac_path_lib.m4
    misc/normpath.m4
    misc/relpaths.m4
    misc/stdrelpaths.m4

All of these macros are identical in both archives today, meaning that
the last commit should be the one that added them -- unless someone
committed addition of empty lines or something. So here are the
respective CVS ID strings:

    $Id: ac_func_mkdir.m4,v 1.1 2001/03/02 11:39:22 simons Exp $
    $Id: ac_func_mkdir.m4,v 1.2 2001/08/25 20:16:41 guidod Exp $

    $Id: ac_config_libconfig_in.m4,v 1.2 2002/04/19 12:03:00 simons Exp $
    $Id: ac_config_libconfig_in.m4,v 1.4 2002/09/12 22:11:52 guidod Exp $

    $Id: ac_config_pkgconfig_in.m4,v 1.2 2002/05/06 11:47:30 simons Exp $
    $Id: ac_config_pkgconfig_in.m4,v 1.2 2002/09/12 22:11:38 guidod Exp $

    $Id: ac_path_lib.m4,v 1.2 2002/04/19 12:03:00 simons Exp $
    $Id: ac_path_lib.m4,v 1.3 2002/09/12 22:11:14 guidod Exp $

    $Id: normpath.m4,v 1.1 2001/05/25 08:38:31 simons Exp $
    $Id: normpath.m4,v 1.1 2001/07/26 01:12:10 guidod Exp $

    $Id: relpaths.m4,v 1.1 2001/05/25 08:38:31 simons Exp $
    $Id: relpaths.m4,v 1.1 2001/07/26 01:12:10 guidod Exp $

    $Id: stdrelpaths.m4,v 1.1 2001/05/25 08:38:31 simons Exp $
    $Id: stdrelpaths.m4,v 1.1 2001/07/26 01:12:10 guidod Exp $

Looks like my archive had _all_ of them before yours did. Conclusion:
None of the commits in group (2) were added to your site before they
were available on mine.

Ah ... you will love group (3). ALL of the commits in group (3)
are crystal clear evidence of you adding content to your archive that
was -- at the time -- not available in the GNU archive. So now guess
how many we have here:

    2002-12-13  guidod

        * Installed_Packages/adl_func_getopt_long.m4:
        update sent by Alexandre Duret-Lutz - obviously it seems the
         gnu ac-archive is dead as it has not been included there
         in the last weeks. Or may be that is the normal time span over there ?
         (adl_func_getopt_long.m4)
                                    (Formatting is yours, not mine.)

One macro in group (3). I actually took the time to check my mailbox
and guess what? I did not update the macro until today! I overlooked
the e-mail, I guess.

To summarize: There is ONE CASE where the SourceForge "branch" of the
macro archive was more up-to-date than the GNU archive. Let's recall
what you said above:

 > I did use the link to the sfnet [archive when answering questions,]
 > since I knew it was up to date while it became a common case the
 > the gnu part was possibly a few weeks thereafter.

Damn it. You were right! Technically, one example is enough so that I
cannot claim the opposite. Your archive WAS more up-to-date than mine
after all.


 > Such a thread usually meanders quite a time until the silent
 > readers of the mailinglist - and mostly partakers in the original
 > autoconf project - are fed up and make some noise themselves which
 > usually ends the discussion quickly thereafter.

Calling for help? :-)


 > Perhaps it did look to some as if the gnu site was not maintained
 > in the way that people might expect [...]

Which has probably nothing to do with the fact that you added fancy
layout to your pages in the time you saved by downloading the actual
contents from my site?


 > [...] and which they can get from the sfnet branch.

Another statement that we can actually verify. The complete list of
macros which are found on the SourceForge "branch" and _not_ in the
GNU archive is:

    ac_func_vsnprintf.m4
    ac_lib_readline.m4
    ac_prog_cc_warnings.m4
    ac_prog_fig2dev.m4

        All of these macros are duplicates. The author asked me to
        rename them to vl_<macro_name> to avoid conflicts with the
        "ac" prefix. I replaced them with the new versions, but your
        download scripts unfortunately didn't notice that.

    ag_check_allocated_ctime.m4
    ag_check_pathfind.m4
    ag_check_posix_regcomp.m4
    ag_check_posix_sysinfo.m4
    ag_check_strcspn.m4
    ag_check_strftime.m4
    ag_check_sys_siglist.m4
    ag_check_uname_syscall.m4

        These macros, which are all written by Bruce Korb ("bkorb"),
        where indeed never submitted to me.

    patch_libtool_on_darwin_zsh_overquoting.m4
    patch_libtool_sys_lib_search_path_spec.m4
    patch_libtool_to_add_host_cc.m4

        These were _removed_ from my site because these were _raw_
        macros without any sort of documentation or mark-up. Your
        script did not notice. (Let's play a little game: Can you
        guess who committed them to my CVS repository on 2001-08-25?)

To be fair: I omitted the macros that _you_ wrote yourself and which
mystically fail to make it into my submission queue. :-)

DAMN IT! I stand corrected again. Your site _does_ carry content that
mine does not have. 8 macros. Plus the duplicate and the junk ones.


 > It is therefore interesting to see THE SFNET BRANCH IS ACTUALLY
 > able to be seen as A COMPETITOR by you [...]
                                                  (Emphasis is mine.)

When I realized that I had actually "flamed" somebody on a public
mailing list, I was sort of disappointed with myself for having so
poor a self-control. But by now, this is starting to be real fun.
Please, by all means, go on!


 > Hopefully you can work out a way for you to finally come to terms
 > with me and the "Rest of the world" that you involve in the subject
 > of this thread.

Yeah ... I am a really disturbed person, you know. The sickest habits
I have (in reverse order of sickness):

 (3) Howling at the moon at night.

 (2) Not coming to terms with you and the rest of the world.

 (1) Writing my name _only_ on things I did myself.


Finally, one more comment to what you wrote right on top of your
e-mail:

 > Oh my... no phone call then.

What the heck should I call you for? Can you tell me that? Do you
assume that when we talked a bit, did some male bonding and stuff, the
facts would go away? Do you assume this perfectly crystal-clear
situation would change in any conceivable way during a phone call?

I will say it ONE LAST TIME: According to the GPL, under which I
licensed my work, you had every right to do what you did. I cannot
possibly hold grudges against you for using a right that I granted you
in the first place. There is no personal problem we have to discuss.
There is no issue to resolve. Everything is unbelievably alright.

If, upon reflection, you get the feeling that maybe -- just maybe --
you "sort of" did not win the Ethics Nobel Prize with the _way_ you
used the right that you have, then you should admit it and that's it.
There is no need to apologize for anything, there is no need to be
sorry for anything, there is no need to talk to me in private to
explain anything. Just, please!, stop making false claims about what
you really achieved and about what role I played in that.

Peter


P. S.: I won't even begin to think about how much work I could have
gotten done in the time I wrote those e-mails. :-(




From MAILER-DAEMON Sat Jan 18 20:03:37 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18a3qp-0000wy-00
	for mharc-autoconf@gnu.org; Sat, 18 Jan 2003 20:02:15 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18a3qX-0000Nf-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 20:01:57 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18a3oa-0005YJ-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 19:59:57 -0500
Received: from main.gmane.org ([80.91.224.249])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18a3nt-0005Br-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 19:59:14 -0500
Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18a3mV-0007Td-00
	for <autoconf@gnu.org>; Sun, 19 Jan 2003 01:57:47 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: autoconf@gnu.org
Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18a3mU-0007TT-00
	for <gmane-comp-sysutils-autoconf-general@m.gmane.org>;
	Sun, 19 Jan 2003 01:57:46 +0100
Path: not-for-mail
From: Peter Simons <simons@cryp.to>
Date: 19 Jan 2003 01:59:12 +0100
Organization: private
Lines: 33
Message-ID: <87d6munee7.fsf_-_@overkill.cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<873cnqpf5t.fsf_-_@overkill.cryp.to> <3E29B0C3.3000306@gmx.de>
	<87hec6nfad.fsf_-_@overkill.cryp.to>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@main.gmane.org
Sender: news <news@main.gmane.org>
Subject: Re: [OT] Guido Draheim vs. Peter Simons (Correction!)
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 01:02:08 -0000

I quoted, among others, the following CVS IDs:

 >     $Id: ac_config_libconfig_in.m4,v 1.2 2002/04/19 12:03:00 simons Exp $
 >     $Id: ac_config_libconfig_in.m4,v 1.4 2002/09/12 22:11:52 guidod Exp $

 >     $Id: ac_config_pkgconfig_in.m4,v 1.2 2002/05/06 11:47:30 simons Exp $
 >     $Id: ac_config_pkgconfig_in.m4,v 1.2 2002/09/12 22:11:38 guidod Exp $

 >     $Id: ac_path_lib.m4,v 1.2 2002/04/19 12:03:00 simons Exp $
 >     $Id: ac_path_lib.m4,v 1.3 2002/09/12 22:11:14 guidod Exp $

and upon inspection of the dates concluded:

 > Looks like my archive had _all_ of them before yours did.
 > Conclusion: None of the commits in group (2) were added to your
 > site before they were available on mine.

Unfortunately, the idea to check the older commits came to me only
after I had sent my mail already. Now I did check them, and it turned
out that you committed the new versions (of all of them) on
2002-03-23, and re-committed them when I performed the update.

So, to be fair, I must correct my statement:

 > To summarize: There is ONE CASE where the SourceForge "branch" of
 > the macro archive was more up-to-date than the GNU archive.

In fact, there are two cases (or four, depending on how you count it),
in which your site was more up-to-date. 

Sorry.

Peter




From MAILER-DAEMON Sat Jan 18 20:13:04 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18a41H-0004O1-00
	for mharc-autoconf@gnu.org; Sat, 18 Jan 2003 20:13:03 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18a41E-0004J3-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 20:13:00 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18a41D-0004Ii-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 20:12:59 -0500
Received: from mail.gmx.net ([213.165.65.60])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18a3zC-0003Qu-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 20:10:54 -0500
Received: (qmail 29008 invoked by uid 0); 19 Jan 2003 01:10:52 -0000
Received: from pd9e80cbf.dip.t-dialin.net (HELO gmx.de) (217.232.12.191)
  by mail.gmx.net (mp004-rz3) with SMTP; 19 Jan 2003 01:10:52 -0000
Message-ID: <3E29FB95.2020102@gmx.de>
Date: Sun, 19 Jan 2003 02:12:53 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Peter Simons <simons@cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<873cnqpf5t.fsf_-_@overkill.cryp.to> <3E29B0C3.3000306@gmx.de>
	<87hec6nfad.fsf_-_@overkill.cryp.to>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: [OT] Guido Draheim vs. Peter Simons vs. Rest of the World
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 01:13:01 -0000

Peter Simons schrieb:
> 
> If, upon reflection, you get the feeling that maybe -- just maybe --
> you "sort of" did not win the Ethics Nobel Prize with the _way_ you
> used the right that you have, then you should admit it and that's it.
> There is no need to apologize for anything, there is no need to be
> sorry for anything, there is no need to talk to me in private to
> explain anything. Just, please!, stop making false claims about what
> you really achieved and about what role I played in that.
> 

so, what do you think I have claimed as being `my achievement`
that does not belong to me - and what was your role in that.




From MAILER-DAEMON Sat Jan 18 20:25:12 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18a4Cr-0006qm-00
	for mharc-autoconf@gnu.org; Sat, 18 Jan 2003 20:25:02 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18a4Ch-0006Kj-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 20:24:51 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18a4CW-0005pL-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 20:24:44 -0500
Received: from mail.gmx.net ([213.165.65.60])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18a4CP-0005SG-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 20:24:33 -0500
Received: (qmail 3858 invoked by uid 0); 19 Jan 2003 01:24:32 -0000
Received: from pD9E80CBF.dip.t-dialin.net (HELO gmx.de) (217.232.12.191)
  by mail.gmx.net (mp002-rz3) with SMTP; 19 Jan 2003 01:24:32 -0000
Message-ID: <3E29FEC9.2050108@gmx.de>
Date: Sun, 19 Jan 2003 02:26:33 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Peter Simons <simons@cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<873cnqpf5t.fsf_-_@overkill.cryp.to> <3E29B0C3.3000306@gmx.de>
	<87hec6nfad.fsf_-_@overkill.cryp.to> <87d6munee7.fsf_-_@overkill.cryp.to>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: [OT] Guido Draheim vs. Peter Simons (Correction!)
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 01:24:58 -0000

Peter Simons schrieb:
> I quoted, among others, the following CVS IDs:
> 
>  >     $Id: ac_config_libconfig_in.m4,v 1.2 2002/04/19 12:03:00 simons Exp $
>  >     $Id: ac_config_libconfig_in.m4,v 1.4 2002/09/12 22:11:52 guidod Exp $
> 
>  >     $Id: ac_config_pkgconfig_in.m4,v 1.2 2002/05/06 11:47:30 simons Exp $
>  >     $Id: ac_config_pkgconfig_in.m4,v 1.2 2002/09/12 22:11:38 guidod Exp $
> 
>  >     $Id: ac_path_lib.m4,v 1.2 2002/04/19 12:03:00 simons Exp $
>  >     $Id: ac_path_lib.m4,v 1.3 2002/09/12 22:11:14 guidod Exp $
> 
> and upon inspection of the dates concluded:
> 
>  > Looks like my archive had _all_ of them before yours did.
>  > Conclusion: None of the commits in group (2) were added to your
>  > site before they were available on mine.
> 
> Unfortunately, the idea to check the older commits came to me only
> after I had sent my mail already. Now I did check them, and it turned
> out that you committed the new versions (of all of them) on
> 2002-03-23, and re-committed them when I performed the update.
> 
> So, to be fair, I must correct my statement:
> 
>  > To summarize: There is ONE CASE where the SourceForge "branch" of
>  > the macro archive was more up-to-date than the GNU archive.
> 
> In fact, there are two cases (or four, depending on how you count it),
> in which your site was more up-to-date. 
> 
> Sorry.
> 

The re-commit is fairly intentional - the `original directories`
should have been only copies of the ones in the gnu ac-archive,
it did turn out to be always problematic to check-in earlier
than the gnu part since my auto-sync scripts would claim for
an update to be present in the gnu part where there was none -
my scripts only check for a `diff` and when the one in the
sfnet ac-archive was never, wheeww. So, after that I did not
even try to update the `original directories` earlier and just
wait till the updates are there and ready to be copied. The
adl case is an exception herein since I did not wanted to
wait any longer.

The `user directories` (as I call them) are updated independently
however - it has been the intent of the sfnet branch to be
also a playground for experimental stuff that people go about
to delete perhaps but which they want to have packaged. I hand
out cvs access to the sfnet branch quite freely, and the
makesystem is ready to be used by third persons as well,
including uploads to the webserver. Actually, that extra
freedom was not used - my intention thereabout misled perhaps.
As a result, most of the updates in the `user directories`
are just... mine. Ooops. ;-)

-- cheers, guido




From MAILER-DAEMON Sat Jan 18 20:42:19 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18a4Ss-0002Z7-00
	for mharc-autoconf@gnu.org; Sat, 18 Jan 2003 20:41:34 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18a4SD-0001n1-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 20:40:53 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18a4RR-0001Ig-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 20:40:06 -0500
Received: from pop.gmx.de ([213.165.65.60] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18a4Qr-0001CK-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 20:39:29 -0500
Received: (qmail 20485 invoked by uid 0); 19 Jan 2003 01:39:28 -0000
Received: from pd9e80cbf.dip.t-dialin.net (HELO gmx.de) (217.232.12.191)
  by mail.gmx.net (mp003-rz3) with SMTP; 19 Jan 2003 01:39:28 -0000
Message-ID: <3E2A0249.8090906@gmx.de>
Date: Sun, 19 Jan 2003 02:41:29 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Peter Simons <simons@cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<873cnqpf5t.fsf_-_@overkill.cryp.to> <3E29B0C3.3000306@gmx.de>
	<87hec6nfad.fsf_-_@overkill.cryp.to>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: [OT] Guido Draheim vs. Peter Simons vs. Rest of the World
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 01:41:32 -0000

Peter Simons schrieb:
> 
> Another statement that we can actually verify. The complete list of
> macros which are found on the SourceForge "branch" and _not_ in the
> GNU archive is:
> 
>     ac_func_vsnprintf.m4
>     ac_lib_readline.m4
>     ac_prog_cc_warnings.m4
>     ac_prog_fig2dev.m4
> 
>         All of these macros are duplicates. The author asked me to
>         rename them to vl_<macro_name> to avoid conflicts with the
>         "ac" prefix. I replaced them with the new versions, but your
>         download scripts unfortunately didn't notice that.
> 

They did. And I was embaressed since this deletion BROKE some
projects of mine. I did talk to VL via e-mail how that came to
be and he later stated that he was not aware the macros were
used so widely that renaming could be a problem. The `acinclude`
tool is all about using some machinery to be uptodate with
extra macros but the acinclude tool is not intelligent enough to
detect renames. As a result, I did change my sync-scripts to skip
these files and to _not_ tell me they are deleted. Instead, I
did modify these old entries with a line saying "obsoleted", and
modified the acinclude tool to detect this extra line, and to
warn the `acinclude` user about the fact and hint them to the
name of the new macro. I need to add here that I did not cvs
commit those "additions of obsolete markers" to the sfnet cvs,
you can only see them in the tarballs or the formatted webpage
content on the sfnet site.

One might say that such a deletion/renaming was a bit careless
about the `acinclude` tool, and the problem of automatic
updates of extra macros and project management with locally
instealled copies of the ac-archive macros. - but actually there
is no such tool in the gnu branch, so that it can be guilty
as ammunition in a flame war ;-) just be noted that I was
not amused, as it meant some extra work for me to get away
with it and still have means to have auto-sync with the gnu
repository. It took some time but it is now in place.

-- cheers, guido





From MAILER-DAEMON Sat Jan 18 20:46:19 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18a4XT-0006FU-00
	for mharc-autoconf@gnu.org; Sat, 18 Jan 2003 20:46:19 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18a4Wn-0005kx-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 20:45:37 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18a4Vf-0005Dt-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 20:44:33 -0500
Received: from main.gmane.org ([80.91.224.249])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18a4Q1-0000eY-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 20:38:37 -0500
Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18a4Oc-0001Fj-00
	for <autoconf@gnu.org>; Sun, 19 Jan 2003 02:37:10 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: autoconf@gnu.org
Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18a4Ob-0001Fa-00
	for <gmane-comp-sysutils-autoconf-general@m.gmane.org>;
	Sun, 19 Jan 2003 02:37:09 +0100
Path: not-for-mail
From: Peter Simons <simons@cryp.to>
Date: 19 Jan 2003 02:38:35 +0100
Organization: private
Lines: 19
Message-ID: <877kd1or50.fsf_-_@overkill.cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<873cnqpf5t.fsf_-_@overkill.cryp.to> <3E29B0C3.3000306@gmx.de>
	<87d6munee7.fsf_-_@overkill.cryp.to> <3E29FEC9.2050108@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@main.gmane.org
Sender: news <news@main.gmane.org>
Subject: Re: [OT] Guido Draheim vs. Peter Simons (Surrender!)
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 01:46:16 -0000

Guido Draheim writes:

 > I hand out cvs access to the sfnet branch quite freely [...].

What, according to 

    http://sourceforge.net/project/memberlist.php?group_id=32081

accounts for the two developers:

    Bruce Korb  
    Guido Draheim

The ones, who's macros the GNU archive does not have.

Anyway, this is leading nowhere. I quit this thread and return to my
well-established "ignoring the users"-routine.

Peter




From MAILER-DAEMON Sat Jan 18 20:46:26 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18a4XZ-0006NS-00
	for mharc-autoconf@gnu.org; Sat, 18 Jan 2003 20:46:25 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18a4Wx-0005nw-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 20:45:47 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18a4Wj-0005iV-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 20:45:33 -0500
Received: from mail.gmx.net ([213.165.65.60])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18a4WZ-0005gu-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 20:45:23 -0500
Received: (qmail 3041 invoked by uid 0); 19 Jan 2003 01:45:22 -0000
Received: from pd9e80cbf.dip.t-dialin.net (HELO gmx.de) (217.232.12.191)
  by mail.gmx.net (mp005-rz3) with SMTP; 19 Jan 2003 01:45:22 -0000
Message-ID: <3E2A03AB.7070006@gmx.de>
Date: Sun, 19 Jan 2003 02:47:23 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<873cnqpf5t.fsf_-_@overkill.cryp.to> <3E29B0C3.3000306@gmx.de>
	<87hec6nfad.fsf_-_@overkill.cryp.to> <3E2A0249.8090906@gmx.de>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
cc: Peter Simons <simons@cryp.to>
Subject: Re: [OT] Guido Draheim vs. Peter Simons vs. Rest of the World
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 01:46:23 -0000

Guido Draheim schrieb:
- > is no such tool in the gnu branch, so that it can be guilty
+ > is no such tool in the gnu branch, so that it can not be guilty

(I hope that was obvious tho...)




From MAILER-DAEMON Sat Jan 18 21:32:39 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18a5D7-0000T7-00
	for mharc-autoconf@gnu.org; Sat, 18 Jan 2003 21:29:21 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18a5Cq-0000Ec-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 21:29:04 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18a5Cc-0008RU-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 21:28:51 -0500
Received: from mail.gmx.de ([213.165.65.60] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18a5CR-0008PI-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 21:28:39 -0500
Received: (qmail 25986 invoked by uid 0); 19 Jan 2003 02:28:37 -0000
Received: from pd9e80cbf.dip.t-dialin.net (HELO gmx.de) (217.232.12.191)
  by mail.gmx.net (mp008-rz3) with SMTP; 19 Jan 2003 02:28:37 -0000
Message-ID: <3E2A0DCE.7010701@gmx.de>
Date: Sun, 19 Jan 2003 03:30:38 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Peter Simons <simons@cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<873cnqpf5t.fsf_-_@overkill.cryp.to>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: [OT] Guido Draheim vs. Peter Simons vs. Rest of the World(was:
 Macro Archive Relaunch)
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 02:29:14 -0000

oh, sorry, just found the paragraph in an earlier one,...

Peter Simons schrieb:
> 
> I have a problem with you copying my infrastructure, the archive I
> maintain, the web page I created around it (verbatim, word by word) --
> but you don't give any credit about it at all. Even better, you
> actually bash the effort I am putting into it. (On this list, on your
> web site, and in the commit messages of your CVS repository.)

that's because my addition had been about packaging and local
installation. Of course it builds on top of your work, and
picks up large parts of the infrastructure. Only in the very
latest versions I did start with replacing the old infrastructure
with a new one but I would rather like to not do so since it
does lead to more doublework - that's not good IMO.

> 
> I have a problem with you misleading the users of your archive. On
> your web page you say:
> 
>  | If you want to contribute ...
>  |
>  | then please don't hesitate a second! Just send the m4 source to
>  | Guido Draheim <guidod@gnu.org> via electronic mail. [...] Note that
>  | the two ac-archive repositories (sourceforge and savannah) are
>  | constantly kept in sync [...].
> 
> The two archives are NOT kept "in sync". You download the macros from
> the GNU archive and add them into yours -- but not the other way
> round, because I do not accept submissions unless they come from the
> AUTHOR of the macro, since he is the only person who can license his
> intellectual property according to the terms described on my page. You
> make it look as if it really doesn't matter where authors send their
> macros to, because they will end up in both archives anyway, right?
> The truth is, that if someone submits a macro to the GNU archive, it
> will end up in both archives. If he sends it to you, it will be
> available in yours only.

well, there was a time that I had write access to the gnu cvs and
it was the time that the two ac-archives could be kept in sync
both ways even when the macro was sent to me first. It happens that
the respective document that you quote is verrry old as well. I do
not quite recall when you did revoke write-access but I guess it
was after the lines were written that you quote as evidence. sorry,
I might need to change that, it is clearly misleading.


> 
> I furthermore have a problem with you advertising your archive as
> being the cool one, which "offers space for experimental extras",
> while you call the original one the "basic archive". What exactly does
> that mean? Do you have evidence of me ever rejecting a submission
> because it was too "experimental"?

No - it is about the `user directories`. As said in an earlier
mail, I was hoping that the sfnet branch could not _just_ be
about packaging but used for something more like a playground
for a variety of sourceforge people and their macros, so they
can list their extra macros in a central place. It was not used
that widely, there was no intent to mark it as "the cool one",
in fact _I_ would associate with "experimental" something like
unstable and not that overly attractive, ye know.

(Nice plot however to turn that the other way, I didn't ever
  think about that mode, but indeed, some update-junkies in
  the opensource world might think that it is cool - in fact
  I do know some of these types, and now that you say it, hmm,
  it could be really seen as that...ooops *g*)

> 
> I have a problem with you -- through intent or carelessness --
> breaking the build mechanism of the GNU archive, as I have said
> repeatedly.
> 
> My impression is that you have a _personal_ problem with me. Not the
> other way round. When I posted my original article to this list, I
> knew that you would JUMP at it, and that you wouldn't have many
> positive things to say about what I do. Surprise! Here we are.

That's by another background - I do a lot of xml stuff and text
retrivial these days, and from my personal experience I do not
like that users edit xml text _manually_. It should really be
an intermediate format that can be fed from very different sides
like perhaps a script that turns the traditional format into
such an intermediate format. But there may even be other formats
for the `original source` - it opens the possibility to just
change the submission format and still be able to use the old
formatting chain of tools, or to attached a parallel formatting
chain of tools to target a different output media. The xml
world offers a great amount of tools, and that's surely the
greatest thing which did make for the sucess of xml - it is my
personal opinion that the success of the xml format is not in
its ability of being a nice format for human users to write
their original stuff with.

So, of course I would jump in and be critizing, as I have some
knowledge in xml, and I did express my doubts in an earlier
thread about the topic (a few months back?). So yes, no
surprise here, but that was not related to any personal problem
I might have with you. It's been about technical details, and
nothing else that made me jump in (minus the last paragraph
in the first response, to be fair)

> 
> To address the other part of your statement: I reply to e-mails I
> receive through a public forum in the same public forum. Sending an
> e-mail to this list, which makes false claims, and then telling me
> that we should discuss this in private, is a half-assed way of trying
> to get the last word.
> 
To give you my phone number in a private e-mail a year back, that
can not count as a half-assed way of trying to get the last word.
I did see problems coming up back then, and I did want to get them
out of the world as soon as possible. The same thing is on now,
a long time later, and to just have a talk on the phone is simply
the _fastest_ thing to do without bothering the rest of the mailing
list with it. Surely, the rest of the mailing list can not follow in
that, so you're right, we might need to let this thread meander to its
end just as every flame war has to be. ;-) ... that's no problem
with me either. :-)=) ... but I don't need to like it, and I still
don't think the situation is exactly the way that you describe as
"crystal-clear" in another mail. (btw, is "crystal-clear" a term
understood outside of german regions?).

anyway, let's stop this response here, it is quite long even
now, rest assured that I am ready to pick up any point if
there is a wish to handle it. Oh, perhaps this gem...

> 
> Last but not least, let's look at your repeated claim that I threw
> away your work. 

That's just how it felt - you do say now that there were problems
with the changes but you did not tell about these BACK THEN and
you did not respond to my attempts to resolve the issue BACK THEN
to make my `extra stuff` live along well with what you were
heading for. You did not use mail or phone BACK THEN. And NOW, we
have to go by that in public in a nice looooooong flaming session.
:-)

let's see where that ends, - btw, there are of course signs with
me being disgruntled and doing my own stuff independently, but
I was always trying to keep the door open for a merger so there
is little evidence to be found for real - only as of late I was
starting to think as to just move ahead and add stuff without
caring about compatibility with the gnu cvs infrastructure.
Perhaps it is lucky this thread started before the door for a
merger is shut for real.

cheers, guido




From MAILER-DAEMON Sat Jan 18 21:36:29 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18a5Jg-0000HL-00
	for mharc-autoconf@gnu.org; Sat, 18 Jan 2003 21:36:08 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18a5JU-0008IL-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 21:35:56 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18a5JP-000881-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 21:35:53 -0500
Received: from mail.gmx.net ([213.165.65.60])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18a5Ir-0007Bc-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 21:35:17 -0500
Received: (qmail 7659 invoked by uid 0); 19 Jan 2003 02:35:16 -0000
Received: from pd9e80cbf.dip.t-dialin.net (HELO gmx.de) (217.232.12.191)
  by mail.gmx.net (mp009-rz3) with SMTP; 19 Jan 2003 02:35:16 -0000
Message-ID: <3E2A0F5D.8060405@gmx.de>
Date: Sun, 19 Jan 2003 03:37:17 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Peter Simons <simons@cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<873cnqpf5t.fsf_-_@overkill.cryp.to> <3E29B0C3.3000306@gmx.de>
	<87d6munee7.fsf_-_@overkill.cryp.to> <3E29FEC9.2050108@gmx.de>
	<877kd1or50.fsf_-_@overkill.cryp.to>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: [OT] Guido Draheim vs. Peter Simons (Surrender!)
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 02:36:06 -0000

Peter Simons schrieb:
> Guido Draheim writes:
> 
>  > I hand out cvs access to the sfnet branch quite freely [...].
> 
> What, according to 
> 
>     http://sourceforge.net/project/memberlist.php?group_id=32081
> 
> accounts for the two developers:
> 
>     Bruce Korb  
>     Guido Draheim
> 
> The ones, who's macros the GNU archive does not have.
> 

Yes, it did not work - even Bruch Korb kept sending me the
ac-macros via mail. Later I realized that this is all too
human - why bother doing tarball upload and website upload
when there is someone around who'd do that within hours
after sending an e-mail. So again, it did not work, and
it was probably not that a good idea. :-/

cheers, guido
p.s. the full paragraph again...

Guido Draheim schrieb:
 >
 > The `user directories` (as I call them) are updated independently
 > however - it has been the intent of the sfnet branch to be
 > also a playground for experimental stuff that people go about
 > to delete perhaps but which they want to have packaged. I hand
 > out cvs access to the sfnet branch quite freely, and the
 > makesystem is ready to be used by third persons as well,
 > including uploads to the webserver. Actually, that extra
 > freedom was not used - my intention thereabout misled perhaps.
 > As a result, most of the updates in the `user directories`
 > are just... mine. Ooops. ;-)
 >





From MAILER-DAEMON Sat Jan 18 21:48:53 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18a5W0-0003CL-00
	for mharc-autoconf@gnu.org; Sat, 18 Jan 2003 21:48:52 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18a5Vy-0003C3-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 21:48:50 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18a5Vw-0003Br-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 21:48:49 -0500
Received: from pop.gmx.de ([213.165.65.60] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18a5Vw-0003Bm-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 21:48:48 -0500
Received: (qmail 32230 invoked by uid 0); 19 Jan 2003 02:48:46 -0000
Received: from pd9e80cbf.dip.t-dialin.net (HELO gmx.de) (217.232.12.191)
  by mail.gmx.net (mp009-rz3) with SMTP; 19 Jan 2003 02:48:46 -0000
Message-ID: <3E2A1288.8050100@gmx.de>
Date: Sun, 19 Jan 2003 03:50:48 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Peter Simons <simons@cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<873cnqpf5t.fsf_-_@overkill.cryp.to> <3E29B0C3.3000306@gmx.de>
	<87d6munee7.fsf_-_@overkill.cryp.to> <3E29FEC9.2050108@gmx.de>
	<877kd1or50.fsf_-_@overkill.cryp.to>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: [OT] Guido Draheim vs. Peter Simons (Surrender!)
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 02:48:51 -0000

Peter Simons schrieb:
> 
> Anyway, this is leading nowhere. I quit this thread and return to my
> well-established "ignoring the users"-routine.
> 

Hopefully not - we should really get this matter settled.
There is no point in doing strange politics and have
autoconf users wonder what that is about with two
instances of the ac-archive - in fact, there should be
only one - or a valid relation between the two, as a
form of cooperation. The status-quo is not satisfying,
never was to me, and I fear that you just leave and in
consequence the status-quo be kept.







From MAILER-DAEMON Sat Jan 18 21:58:50 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18a5em-0003PX-00
	for mharc-autoconf@gnu.org; Sat, 18 Jan 2003 21:57:56 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18a5ee-00038U-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 21:57:48 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18a5eZ-0002wq-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 21:57:45 -0500
Received: from xinit.lug.org.uk ([195.92.253.3] helo=lug.org.uk)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18a5du-0001zl-00
	for autoconf@gnu.org; Sat, 18 Jan 2003 21:57:02 -0500
Received: from andy   by lug.org.uk with local (Exim 3.33 #2)
	 id 18a5dt-0000RJ-00 ; Sun, 19 Jan 2003 02:57:01 +0000
Date: Sun, 19 Jan 2003 02:57:01 +0000
From: Andy Smith <andy@strugglers.net>
To: Guido Draheim <guidod-2003-@gmx.de>
Message-ID: <20030119025701.GY22669@lug.org.uk>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<873cnqpf5t.fsf_-_@overkill.cryp.to> <3E29B0C3.3000306@gmx.de>
	<87d6munee7.fsf_-_@overkill.cryp.to> <3E29FEC9.2050108@gmx.de>
	<877kd1or50.fsf_-_@overkill.cryp.to> <3E2A1288.8050100@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3E2A1288.8050100@gmx.de>
X-Uptime: 35 days
X-URL: http://www.strugglers.net/~andy/
User-Agent: Mutt/1.5.1i
Sender: Andy Smith <andy@lug.org.uk>
cc: autoconf@gnu.org
cc: Peter Simons <simons@cryp.to>
Subject: Re: [OT] Guido Draheim vs. Peter Simons (Surrender!)
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 02:57:53 -0000

On Sun, Jan 19, 2003 at 03:50:48AM +0100, Guido Draheim wrote:
> Peter Simons schrieb:
> >
> >Anyway, this is leading nowhere. I quit this thread and return to my
> >well-established "ignoring the users"-routine.
> >
> 
> Hopefully not - we should really get this matter settled.

I suggest that both of you just put a link to each other's sites
(perhaps in some "other useful sites" area) and get on with your
lives.

-- 
A: No.
Q: Should I include quotations after my reply?



From MAILER-DAEMON Sun Jan 19 05:31:55 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aCk6-0007tt-00
	for mharc-autoconf@gnu.org; Sun, 19 Jan 2003 05:31:54 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18aCk4-0007tc-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 05:31:52 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18aCk3-0007tR-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 05:31:52 -0500
Received: from postfix4-2.free.fr ([213.228.0.176])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18aCk3-0007rA-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 05:31:51 -0500
Received: from localhost (nas-cbv-9-62-147-163-61.dial.proxad.net
	[62.147.163.61])	by postfix4-2.free.fr (Postfix) with ESMTP
	id 5A6C7C12B; Sun, 19 Jan 2003 11:31:44 +0100 (CET)
Received: from adl by localhost with local (Exim 3.35 #1 (Debian))
	id 18aCgZ-0001Pr-00; Sun, 19 Jan 2003 11:28:15 +0100
To: Peter Simons <simons@cryp.to>
From: Alexandre Duret-Lutz <duret_g@lrde.epita.fr>
X-Home-Page: http://gadl.free.fr/
X-GPG-Keyserver: http://pgp.mit.edu/
X-GPG-Fingerprint: FCA0 8615 0211 941A 2AB9  FA66 3859 C03B 2E23 6E47
X-Face: "Oky^obn}f(.QOV"RB7#1O@U^~rO6%5z5OrIm#nt{Fa4=cNRK@@e9rR$asU][QE[)7Pge8(
	kMx|^?!6wA~)0f1OmxROafMwBt9eDt(h[7F&qrs|Otp\ChrfJPH9A'&k$0@tl)1Lx
Date: Sun, 19 Jan 2003 11:28:04 +0100
In-Reply-To: <873cnrgarb.fsf@overkill.cryp.to> (Peter Simons's message of
 "17 Jan 2003 14:35:04 +0100")
User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386-pc-linux-gnu)
References: <873cnrgarb.fsf@overkill.cryp.to>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Message-ID: <2003-01-19-11-28-05+5448+duret_g@lrde.epita.fr>
X-Attribution: adl
Sender: Alexandre Duret-Lutz <duret_g@lrde.epita.fr>
cc: autoconf@gnu.org
Subject: Re: Macro Archive Relaunch
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 10:31:53 -0000

>>> "Peter" == Peter Simons <simons@cryp.to> writes:

[...]

 Peter> - The XML format allows for easy addition of meta information, which
 Peter> the old format cannot easily express. I could imagine, for
 Peter> instance, information about related macros (packages),
 Peter> dependencies, appliance to certain Autoconf versions, etc.

My impression is that the macro submitter now has to maintain two files:
  - the m4 file, that should be readable by autoconf, and that
    he/she is using in his project
  - and a separate XML file, that duplicates the code

Is this correct?  If so I hope you'll continue to maintain the
old format.

I understand the former could be built from the latter, but as
far I'm concerned I maintain my macros *in* the project that
uses them and I'm not willing to complexify my projects'
building rules for the sake of the ac-archive (the autotools
infrastructure is already complex enough).  Adding some comments
in the file is fine, adding more files or Makefile rules isn't.

[...]
-- 
Alexandre Duret-Lutz




From MAILER-DAEMON Sun Jan 19 06:39:05 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aDio-0007Vt-00
	for mharc-autoconf@gnu.org; Sun, 19 Jan 2003 06:34:38 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18aDiT-0007Ap-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 06:34:17 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18aDgc-0006D3-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 06:32:24 -0500
Received: from main.gmane.org ([80.91.224.249])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18aDfQ-0005xQ-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 06:31:08 -0500
Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18aDe0-00021W-00
	for <autoconf@gnu.org>; Sun, 19 Jan 2003 12:29:40 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: autoconf@gnu.org
Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18aDdy-00021M-00
	for <gmane-comp-sysutils-autoconf-general@m.gmane.org>;
	Sun, 19 Jan 2003 12:29:38 +0100
Path: not-for-mail
From: Peter Simons <simons@cryp.to>
Date: 19 Jan 2003 12:31:05 +0100
Organization: private
Lines: 76
Message-ID: <8765sl74w6.fsf@overkill.cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to>
	<2003-01-19-11-28-05+5448+duret_g@lrde.epita.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@main.gmane.org
Sender: news <news@main.gmane.org>
Subject: Re: Macro Archive Relaunch
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 11:34:36 -0000

Alexandre Duret-Lutz writes:

 > My impression is that the macro submitter now has to maintain two files:
 >   - the m4 file, that should be readable by autoconf, and that
 >     he/she is using in his project
 >   - and a separate XML file, that duplicates the code

The XML file can reference the actual code. I'm currently writing a
new "how to contribute" document, that should shed some light onto the
different possibilities you have. To give you an overview:

 (1) The authoritative file for your macros is the XML file, which
     _contains_ the macro. Since you cannot use that for Autoconf
     itself, you would have to extract the m4 content as part of your
     build process. This can be achieved by a very simple shell
     script, which I can provide.

     Also, the capability to read the XML file could be added to
     "aclocal" or "autoconf" itself as well, but that is something
     that will happen in the future. (If at all ... So far we have no
     idea how popular the new format will be with the submitters.)

 (2) You have a separate m4 file and the XML file for documentation.
     Then you can process the macro with Autoconf and friends as
     usual. Since XML can reference external content, the XML file can
     be processed without changes as well. (For those who know
     XML/SGML: the keywords here or "system entity" or "XInclude".)

 (3) You use the legacy format and ignore the existence of XML
     altogether.

For the archives, XML has some significant benefits. It is easier to
parse, it is easier to process, and I can automatically _validate_ the
submissions. Thus, macro submissions (or updates to submissions) could
happen _instantaneous_ without having to wait for the maintainer to
catch up. It is virtually impossible to break the build.

For the submitter, XML has pros and cons. It certainly _is_ more
complicated to write than just throwing in a few comments at the top
of your m4 file. A web page that allows submitters to generate the XML
file through an interactive process would certainly help here. (Any
volunteers?) What you gain is much more power to format your synopsis
and your documentation. The "peti_*" macros, currently contained in
the archive, use links, block quotes, etc., for example. IMHO this is
a good thing.

In any case I have no intention of discontinuing support of the legacy
format. A parser for that format does exist, so there is no point in
throwing it away. Users of the legacy format might have to wait longer
for their submissions and updates to make it into the archive, though,
because a maintainer has to take a look at the file and test the
generated output, before it can be approved. (In the past, about half
of all submissions had to be edited manually before I could add them.)
 
Also, I have no intention of converting the existing legacy format
macros into XML. I want to keep the macros in the format that the
users chose when submitting it. (Unless some volunteer shows up to
help me with managing the archive. For me alone, the workload of
checking, converting, testing, and committing every single update in a
different format than the submitter used is too much.)

The XML format is an _option_. My prediction from experience is:

 (1) People will claim that it is doomed, bloated, and pointless.

 (2) People will realize that they can add formatting, links, colors,
     images, and tables to their macro documentation.

 (3) They will love it. 

:-)

The code is there, it is up and running, so I will document it and put
it on-line. Then we'll see what happens.

Peter




From MAILER-DAEMON Sun Jan 19 07:17:14 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aELg-0002qX-00
	for mharc-autoconf@gnu.org; Sun, 19 Jan 2003 07:14:48 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18aEL0-0001jo-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 07:14:06 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18aE9o-0003Yh-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 07:02:33 -0500
Received: from main.gmane.org ([80.91.224.249])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18aE9E-0003T1-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 07:01:56 -0500
Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18aE7n-0003CV-00
	for <autoconf@gnu.org>; Sun, 19 Jan 2003 13:00:27 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: autoconf@gnu.org
Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18aE7l-0003C6-00
	for <gmane-comp-sysutils-autoconf-general@m.gmane.org>;
	Sun, 19 Jan 2003 13:00:25 +0100
Path: not-for-mail
From: Peter Simons <simons@cryp.to>
Date: 19 Jan 2003 13:01:51 +0100
Organization: private
Lines: 36
Message-ID: <871y3973gw.fsf_-_@overkill.cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<87adhyph7q.fsf@overkill.cryp.to> <3E29A3EC.3020105@gmx.de>
	<87of6enrze.fsf@overkill.cryp.to>
	<1042923960.16849.53.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@main.gmane.org
Sender: news <news@main.gmane.org>
Subject: Unifying ac-archive.sf.net and gnu.org   (was: Macro Archive
	Relaunch)
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 12:14:46 -0000

Braden McDaniel writes:

 > It's ridiculous for two completely separate ac-archive projects to
 > exist.

I agree with you.

The following possible solutions come to my mind:

 (1) The SourceForge "branch" is shut down entirely. The macros it
     does have exclusively go into the GNU archive, where they will be
     continued in the future. The extra functionality it provides,
     namely the RPM packages, are provided on the GNU archive.

 (2) The GNU archive is shut down. The archive in all its glory is
     continued on SourceForge, or Guido takes over the project on
     Savannah.

 (3) The macro repository (and I mean just the actual macros) are
     maintained in the GNU archive, and the SourceForge archive goes
     on to provide an alternate _presentation_ of them as well as an
     alternative distribution of them. (This is, in my humble opinion,
     how it should have been right from the beginning.)

 (4) We leave everything as it is, the SourceForge archive continues
     to download the contents of the GNU archive, but clearly says so
     on its web pages so that submitters are _aware_ of the
     asymmetrical relationship between the two.

 (5) We leave everything as it is, and the GNU archive starts
     downloading the contents from the SourceForge archive as well. (I
     list this option for the sake of completeness. I do not want to
     include submissions into the GNU archive unless they come from
     the _author_ a.k.a. copyright holder of the macro.)

Peter




From MAILER-DAEMON Sun Jan 19 11:13:00 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aI2z-0003Ub-00
	for mharc-autoconf@gnu.org; Sun, 19 Jan 2003 11:11:45 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18aI2t-0003Jr-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 11:11:39 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18aI2J-0002L7-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 11:11:14 -0500
Received: from mail.gmx.de ([213.165.65.60] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18aI27-0001uQ-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 11:10:51 -0500
Received: (qmail 3503 invoked by uid 0); 19 Jan 2003 16:10:49 -0000
Received: from pd9e83577.dip.t-dialin.net (HELO gmx.de) (217.232.53.119)
  by mail.gmx.net (mp003-rz3) with SMTP; 19 Jan 2003 16:10:49 -0000
Message-ID: <3E2ACE82.9020400@gmx.de>
Date: Sun, 19 Jan 2003 17:12:50 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Peter Simons <simons@cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<87adhyph7q.fsf@overkill.cryp.to> <3E29A3EC.3020105@gmx.de>
	<87of6enrze.fsf@overkill.cryp.to>
	<1042923960.16849.53.camel@localhost.localdomain>
	<871y3973gw.fsf_-_@overkill.cryp.to>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: 
 Re: Unifying ac-archive.sf.net and gnu.org   (was: Macro Archive
 Relaunch)
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 16:11:43 -0000

Peter Simons schrieb:
> 
>  (5) We leave everything as it is, and the GNU archive starts
>      downloading the contents from the SourceForge archive as well. (I
>      list this option for the sake of completeness. I do not want to
>      include submissions into the GNU archive unless they come from
>      the _author_ a.k.a. copyright holder of the macro.)
> 

Well, it does really seem to be that (5) is only here for
completeness - I was just contacting you with a private
e-mail about ways to allow `upstream updates` so that you
could benefit directly from submissions that went into
the sfnet branch first. You did simply refuse to talk
about that person-to-person and pointed me back to the
mailinglist - I for one think that it is inappriate to
discuss technical details of how to copy macros from
one branch to the next.

The wording of (5) makes me believe that you are not
interested in symmetrical/cooperative relationship at
all. You are always free to pick anything from the
sfnet branch and use it for the benefit of the gnu
ac-archive - and I would like to help you in that as
well but it looks as if you choose to not accept that.

>  (4) We leave everything as it is, the SourceForge archive continues
>      to download the contents of the GNU archive, but clearly says so
>      on its web pages so that submitters are _aware_ of the
>      asymmetrical relationship between the two.
> 

It had always been my intent to not split up completly,
and I was dissatisfied with the situation as present.
To put the maintaince on two shoulders would be the
best, and no submitter would need to wait weeks and
weeks for a reply. It seems however that such is not
an option for you, and the list of points glooming with
proposals to separate the projects stronger than they
have ever been. I do not think that it is in the best
interest of the autoconf world however.

>  (3) The macro repository (and I mean just the actual macros) are
>      maintained in the GNU archive, and the SourceForge archive goes
>      on to provide an alternate _presentation_ of them as well as an
>      alternative distribution of them. (This is, in my humble opinion,
>      how it should have been right from the beginning.)
> 

That has been another question in the last e-mail to you,
how to go about classifications of macros - from past
experiences you do not handle macro submissions immediatly,
and it would be good have some status classification.
I do not want to limit that to just `non-gnu` or `experimental`
or some such, in fact I think that it should be some more
status levels - I am just not sure what model to take, as
examples it could be experimental, proposed, semi-standard,
or just alpha, beta, in-review. The ac_cxx_ macros are surely
in a state that they could even go into the main autoconf
distribtion but they are thought of to being a bit tooo
special for that.

(1)+(2)
I don't like to talk about (1) and (2) actually, you did slap
me multiple times asking for a `merger` and going to try to
maintain it _both_, sharing the workload where I could
concentrate one some parts while you'd do for another. It
does seem that a 'both' does not exist on your mind, even
that we do know both that there should really be only one
ac-archive, as that is what users expect it to be.

Still, I am ready to continue my presence on the autoconf
mailing list, pointing users to solutions from the ac-archive,
trying to handle extra macros on a daily basis, and proof
reading the m4 code to the best of my knowledge, just as it has
been in the last year with two ac-archive's being around. It
would have been better when such style would be present on
one ac-archive alone, as that is what users expect it to be.

-- cheers, guido
p.s. damn politics... we should concentrate on project work!




From MAILER-DAEMON Sun Jan 19 11:29:29 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aIIW-0006OK-00
	for mharc-autoconf@gnu.org; Sun, 19 Jan 2003 11:27:48 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18aII9-0005LS-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 11:27:25 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18aIHf-0003rm-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 11:27:00 -0500
Received: from imap.gmx.net ([213.165.65.60] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18aIHd-0003l2-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 11:26:53 -0500
Received: (qmail 6325 invoked by uid 0); 19 Jan 2003 16:26:51 -0000
Received: from pd9e83577.dip.t-dialin.net (HELO gmx.de) (217.232.53.119)
  by mail.gmx.net (mp004-rz3) with SMTP; 19 Jan 2003 16:26:51 -0000
Message-ID: <3E2AD245.1000806@gmx.de>
Date: Sun, 19 Jan 2003 17:28:53 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: autoconf@gnu.org
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: ac-archive: classic format
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 16:27:44 -0000

The instantiation of free classications on ac macros in the
ac-archive is a good approach, I was always interested in
being able to discriminate ac-macros in multiple ways but
the current repository and submission format was not
suited very well for that.

The xml format is surely not easy for users to handle
directly, and the processing in the gnu ac-archive
seems to be using tools that are not usually present
on user systems (some 'ghc' I have not have heard of,
the makesystem resources are currently not present
anymore in the savannah cvs). That makes it not easy
to format/preview macros locally on a user system.

I would like to attempt to define an extension to the
classic format that allows to classify macros in
multiple ways. We should here follow the classic format
as close as possibly and invent a new tex-like setting,
something like

@category Installed Packages, experimental

The point is just to get a list of proposed category
types that submitters shall pick from - reading and
formatting such a classic format can be done as simple
as with a perl macro like it is done in the sfnet
branch using macro2html.pl. Peter Simon did already
propose a very good choice which matches the current
situation of the ac-archive:

> As for the new categorization ... Currently we have these:
> 
>     C Support
>         Properties of the C compiler.
> 
>     C++ Support
>         Properties of the C++ compiler.
> 
>     Java Support
>         Properties of the Java Environment.
> 
>     Cross Compilation
>         Really advanced stuff.
> 
>     Installed Packages
>         How to I link OpenGL? Where are the header files? And while
>         we're at it ... What is OpenGL?
> 
>     Miscellaneous
>         Catch all
> 
> New ones that I would consider to be useful are:
> 
>     System Headers
>         Tests for the existence of "foobar.h", or whether it defines
>         "foo_bar_t" or not, etc.
> 
>     System Utilities
>         Does the "foo" program support the "--bar" flag? Is it
>         installed at all? What version of the Intel C++ compiler do I
>         have?
> 
>     Build Infrastructure
>         Generate a "foobar-config" script, cool Autoconf extensions,
>         etc. 
> 

Adding to that "topic" categorization, I would like to see
status types
    experimental
    updated
    reviewed
    ubiquitous

comments? proposals? critics?

-- cheers, guido








From MAILER-DAEMON Sun Jan 19 11:38:07 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aISU-00076f-00
	for mharc-autoconf@gnu.org; Sun, 19 Jan 2003 11:38:06 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18aISS-00075I-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 11:38:04 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18aISR-00074J-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 11:38:03 -0500
Received: from pop.gmx.de ([213.165.65.60] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18aISQ-00074C-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 11:38:02 -0500
Received: (qmail 27774 invoked by uid 0); 19 Jan 2003 16:38:01 -0000
Received: from pd9e83577.dip.t-dialin.net (HELO gmx.de) (217.232.53.119)
  by mail.gmx.net (mp010-rz3) with SMTP; 19 Jan 2003 16:38:01 -0000
Message-ID: <3E2AD4E3.6020504@gmx.de>
Date: Sun, 19 Jan 2003 17:40:03 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: autoconf@gnu.org
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: ac-archive: abbrevs for the classic format
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 16:38:05 -0000

The tex-like settings for the classic-format happen to be sometimes
a bit long - the synopsis can be quite long and sometimes we want
to have even some more of them (as we know from an earlier thread).

I would like to see abbreviations of the extra markup of macros in
the ac-archive classic format - on my mind I have something like:

dnl @* AX_CFLAGS_WHATEVER (synopsis)
dnl @* AX_CXXFLAGS_WHATEVER (alternative)
dnl @: Installed Packags, experimental
dnl
dnl description
dnl @= the author
dnl @$Id: version spec $

This would make the maintaince of macros in the classic format
a bit easier, even that it needs to be documented specially.

comments? critics? alternatives?
-- cheers, guido




From MAILER-DAEMON Sun Jan 19 12:20:41 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aJ7g-0006R1-00
	for mharc-autoconf@gnu.org; Sun, 19 Jan 2003 12:20:40 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18aJ6i-0005Er-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 12:19:40 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18aJ6T-0004ql-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 12:19:26 -0500
Received: from main.gmane.org ([80.91.224.249])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18aJ61-0004Xo-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 12:18:57 -0500
Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18aJ4a-00026R-00
	for <autoconf@gnu.org>; Sun, 19 Jan 2003 18:17:28 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: autoconf@gnu.org
Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18aJ4Y-00026F-00
	for <gmane-comp-sysutils-autoconf-general@m.gmane.org>;
	Sun, 19 Jan 2003 18:17:26 +0100
Path: not-for-mail
From: Peter Simons <simons@cryp.to>
Date: 19 Jan 2003 18:18:53 +0100
Organization: private
Lines: 82
Message-ID: <87k7h13vnm.fsf_-_@overkill.cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<87adhyph7q.fsf@overkill.cryp.to> <3E29A3EC.3020105@gmx.de>
	<87of6enrze.fsf@overkill.cryp.to>
	<1042923960.16849.53.camel@localhost.localdomain>
	<871y3973gw.fsf_-_@overkill.cryp.to> <3E2ACE82.9020400@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@main.gmane.org
Sender: news <news@main.gmane.org>
Subject: Re: Unifying ac-archive.sf.net and gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 17:20:38 -0000

Guido Draheim writes:

 >> (5) We leave everything as it is, and the GNU archive starts
 >> downloading the contents from the SourceForge archive as well. (I
 >> list this option for the sake of completeness. I do not want to
 >> include submissions into the GNU archive unless they come from the
 >> _author_ a.k.a. copyright holder of the macro.)

 > The wording of (5) makes me believe that you are not interested in
 > symmetrical/cooperative relationship at all.

The reading skills I learned in school suggest the wording of (5)
would make you believe that I do not want to include submissions
unless they come from the author of the macro. Downloading the macros
from a third-party site is not an option. Not to mention the fact that
two archives cross-updating each other is a maintenance nightmare.


 > To put the maintaince on two shoulders would be the best [...]. It
 > seems however that such is not an option for you [...].

If by "putting the maintenance on two shoulders" you mean that you get
commits rights to the GNU repository, then indeed, this is not an
option. I have had my share of experience with the quality of your
work on the archive, and I am reluctant to assume that everything will
be pretty and flowery from now on. You know how the saying goes:

    If you fool me once, _you_ must be ashamed.
    If you fool me twice, _I_ must be ashamed.


 >> (3) The macro repository (and I mean just the actual macros) are
 >> maintained in the GNU archive, and the SourceForge archive goes on
 >> to provide an alternate _presentation_ of them [...]

 > I do not want to limit that to just `non-gnu` or `experimental` or
 > some such, in fact I think that it should be some more status
 > levels [, ...] as examples it could be experimental, proposed,
 > semi-standard, or just alpha, beta, in-review.

You assume that there are macros that would be alright for the
SourceForge archive but not for the GNU archive. This is wrong. There
is no "quality standard" on the GNU archive that a macro must fulfill.
I include _everything_ that is submitted to me unless it is glaringly
obvious that the macro is useless. I do have neither the time nor the
competence to assess the quality of every submission. And I would be
very surprised if you did.

Thus, there is no need for an "experimental" area. There are no
"experimental" macros. Believe me, when I actually refuse a
submission, you would honestly not want it either.

As for the "status levels" that you speak of: In my opinion, the only
useful status information a macro can bear in the archive is
"peer-reviewed". But, if peer-reviewed macros are highlighted -- what
effectively makes them "better" than other macros is the eyes of the
user --, we need some standard process how a macro _is_ reviewed by
peers. We need rules, an open, public process to do it, we need a
review manager for each submission, and so on and so forth. And, to
make matters worse, we need to make sure that every submission has
chance to _be_ reviewed by peers. Meaning: we need reviewers.

Given the amount of feedback I receive today, I doubt that this will
happen. Unless, due to a staggering turn in evolution, the line "I
reviewed a macro in the GNU/SourceForge archive" is going to impress
chicks in the future.

Judging the quality of a macro in an arbitrary process is worse than
not to judge it at all. Thus, I accept _any_ submission as long as it
comes from the author.

A much better development of the events would be if the authors of the
macros received feedback from their users. But this is an different
story ...


 > I don't like to talk about (1) and (2) actually [...]

If I a got a penny for every paragraph in my postings, which you
refuse to address ... :-)

Peter




From MAILER-DAEMON Sun Jan 19 12:50:51 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aJZx-0001Lx-00
	for mharc-autoconf@gnu.org; Sun, 19 Jan 2003 12:49:53 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18aJZX-00009C-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 12:49:27 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18aJZ0-0006xM-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 12:49:03 -0500
Received: from pop.gmx.net ([213.165.65.60] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18aJYv-0006f4-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 12:48:49 -0500
Received: (qmail 25560 invoked by uid 0); 19 Jan 2003 17:48:47 -0000
Received: from pd9e83577.dip.t-dialin.net (HELO gmx.de) (217.232.53.119)
  by mail.gmx.net (mp011-rz3) with SMTP; 19 Jan 2003 17:48:47 -0000
Message-ID: <3E2AE579.6000907@gmx.de>
Date: Sun, 19 Jan 2003 18:50:49 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
CC: autoconf@gnu.org
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<87adhyph7q.fsf@overkill.cryp.to> <3E29A3EC.3020105@gmx.de>
	<87of6enrze.fsf@overkill.cryp.to>
	<1042923960.16849.53.camel@localhost.localdomain>
	<871y3973gw.fsf_-_@overkill.cryp.to> <3E2ACE82.9020400@gmx.de>
	<87k7h13vnm.fsf_-_@overkill.cryp.to>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Unifying ac-archive.sf.net and gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 17:49:51 -0000

Peter Simons schrieb:
> would make you believe that I do not want to include submissions
> unless they come from the author of the macro. Downloading the macros
> from a third-party site is not an option. Not to mention the fact that
> two archives cross-updating each other is a maintenance nightmare.

agreed - cross-updating is very problematic. It might be possible
to invent tools to help, but actually I do not want to do so
either - let's use the word "inappropriate" for what we want to
achieve after all.

> 
> 
>  > To put the maintaince on two shoulders would be the best [...]. It
>  > seems however that such is not an option for you [...].
> 
> If by "putting the maintenance on two shoulders" you mean that you get
> commits rights to the GNU repository, then indeed, this is not an
> option. I have had my share of experience with the quality of your
> work on the archive, and I am reluctant to assume that everything will
> be pretty and flowery from now on. You know how the saying goes:
> 
>     If you fool me once, _you_ must be ashamed.
>     If you fool me twice, _I_ must be ashamed.

The term `fool me` implies intent - there was no such thing.
When two people work on the same thing then there will be
errors at some place - you could have notified me back then
to let me correct it and be more careful afterwards. There
was no after that. You did not tell me, I knew of the fact
just now. It seems to be more by another saying that you
seem to be thinking of:

    too many cooks spoil the broth.

IMO, the means to overcome it is... communications. I see
that you do not think that it is worth it, or that I am not
worthy for you as to being talked to when you "know" sth.
(which there wasn't but you still keep with it, it seems).
You seem to think that you can do it all by yourself, hmmm,
well, that's an opinion - and I might say a valid one. The
workload is not that much that two guys are needed to
handle the submissions.

I still maintain however that there are differences in
the style that you and me handle submissions - you did
never answer the numerous times that I stated that you
were usually handling submissions weeks and weeks in
delay. I would be all too happy if you could promise
that it will turn to the better in the future.

My own standard is to try to handle it daily, and if
there are problems, atleast send out a reply within
a few days later, never more than a week.


> 
> 
>  >> (3) The macro repository (and I mean just the actual macros) are
>  >> maintained in the GNU archive, and the SourceForge archive goes on
>  >> to provide an alternate _presentation_ of them [...]
> 
>  > I do not want to limit that to just `non-gnu` or `experimental` or
>  > some such, in fact I think that it should be some more status
>  > levels [, ...] as examples it could be experimental, proposed,
>  > semi-standard, or just alpha, beta, in-review.
> 
> You assume that there are macros that would be alright for the
> SourceForge archive but not for the GNU archive. This is wrong. There
> is no "quality standard" on the GNU archive that a macro must fulfill.
> I include _everything_ that is submitted to me unless it is glaringly
> obvious that the macro is useless. I do have neither the time nor the
> competence to assess the quality of every submission. And I would be
> very surprised if you did.

Yes, I did. Always. - I might lack the competence to do a full
review but I can comment on the style that was picked - how to
name cache-variables, deploying AC_LANG changes around, to add
if-exec and if-not-exec, adding default values and documenting
them, and bunch of other things that do not need to be all too
close with the actual subject - but which can make it easier for
the actual "users" of that specific macro to get a read into it
and have nice experiences as it combines better with the macros
from the autoconf main project.

> 
> Judging the quality of a macro in an arbitrary process is worse than
> not to judge it at all. Thus, I accept _any_ submission as long as it
> comes from the author.

Actually, I was thinking of the original author to place an
attribution of status - and it does not need to be `experimental`
or some such. Speaking of my own experiences, I would like to
add something like `just-an-idea`, `used-in-one-released-project`,
or `used-in-many-projects-around`.

> 
> A much better development of the events would be if the authors of the
> macros received feedback from their users. But this is an different
> story ...
> 
> 
>  > I don't like to talk about (1) and (2) actually [...]
> 
> If I a got a penny for every paragraph in my postings, which you
> refuse to address ... :-)
> 

Well, I could counter that on the same lines :-)=)







From MAILER-DAEMON Sun Jan 19 16:48:52 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aNJE-0004XI-00
	for mharc-autoconf@gnu.org; Sun, 19 Jan 2003 16:48:52 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18aNJC-0004WI-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 16:48:50 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18aNIH-0003Ix-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 16:47:53 -0500
Received: from mail.trilos.de ([62.145.18.34] helo=candy.trilos.de)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18aNHv-0002GI-00; Sun, 19 Jan 2003 16:47:31 -0500
Received: from localhost (localhost [127.0.0.1])
	by candy.trilos.de (Postfix) with ESMTP
	id E1684F70E2; Sun, 19 Jan 2003 22:47:28 +0100 (CET)
Received: from orgc (p508F0D23.dip.t-dialin.net [80.143.13.35])
	by candy.trilos.de (Postfix) with SMTP
	id 04EDCF70E1; Sun, 19 Jan 2003 22:47:27 +0100 (CET)
Date: Sun, 19 Jan 2003 22:50:16 +0100
From: Dennis Heuer <dh@onclick.org>
To: bug-m4@gnu.org
Message-Id: <20030119225016.13dc47f9.dh@onclick.org>
X-Mailer: Sylpheed version 0.6.5 (GTK+ 1.2.10; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS new-20020517
X-Razor-id: bfdd4085b4ec515f314deffb9779aff50519147f
cc: autoconf@gnu.org
cc: bug-gnu-utils@prep.ai.mit.edu
Subject: profiling timer expired
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 21:48:51 -0000

Aehm, don't want to disturb but am in trouble with autoconf and/or m4.

When trying to configure some software packages I get the message:

profiling timer expired.

One example happens when configuring autoconf itself:

Making all in m4sugar
make[2]: Entering directory `/workspace/software/system/autoconf-2.57/lib/m4sugar'
../../tests/autom4te				\
	--language=m4sugar			\
	--freeze			\
	--output=m4sugar.m4f
make[2]: *** [m4sugar.m4f] profiling timer expired
make[2]: Leaving directory `/workspace/software/system/autoconf-2.57/lib/m4sugar'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/workspace/software/system/autoconf-2.57/lib'
make: *** [all-recursive] Error 1

I see this the first time and don't understand it. Please help.

Thanks

Dennis Heuer



From MAILER-DAEMON Sun Jan 19 18:30:37 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aOq8-0000KF-00
	for mharc-autoconf@gnu.org; Sun, 19 Jan 2003 18:26:56 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18aOpu-0008NB-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 18:26:42 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18aOpi-0007xr-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 18:26:31 -0500
Received: from main.gmane.org ([80.91.224.249])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18aOpc-0007mn-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 18:26:25 -0500
Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18aOoB-0002Ph-00
	for <autoconf@gnu.org>; Mon, 20 Jan 2003 00:24:55 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: autoconf@gnu.org
Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18aOo9-0002P5-00
	for <gmane-comp-sysutils-autoconf-general@m.gmane.org>;
	Mon, 20 Jan 2003 00:24:53 +0100
Path: not-for-mail
From: Peter Simons <simons@cryp.to>
Date: 20 Jan 2003 00:26:19 +0100
Organization: private
Lines: 47
Message-ID: <87ptqs7mck.fsf_-_@overkill.cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<87adhyph7q.fsf@overkill.cryp.to> <3E29A3EC.3020105@gmx.de>
	<87of6enrze.fsf@overkill.cryp.to>
	<1042923960.16849.53.camel@localhost.localdomain>
	<871y3973gw.fsf_-_@overkill.cryp.to> <3E2ACE82.9020400@gmx.de>
	<87k7h13vnm.fsf_-_@overkill.cryp.to> <3E2AE579.6000907@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@main.gmane.org
Sender: news <news@main.gmane.org>
Subject: Let's start over  (was: Unifying ac-archive.sf.net and gnu.org)
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 19 Jan 2003 23:26:54 -0000

Guido,

it appears that something has been going fundamentally wrong. So let's
take a step back and start over.

All personal matters aside, we both aim for the same goal: We want to
provide an useful service to the software development community. I am
sure that our pointless discussion has annoyed pretty much everybody
on this list by now, and the chances of _either_ of us getting
feedback and help are dropping rapidly towards zero with every further
hostile exchange.

That is not helping. Neither of us.

Whatever happened that set our relationship onto the wrong track, I am
sure that a good part of it was my fault, and I want to apologize if I
conveyed the impression that I would not appreciate your knowledge or
that I would not appreciate your help back then.

I would like to see the two archives merge as much as any of us, and I
realize that we will never see that happening unless we are able to
compromise. I requested help multiple times, and you have offered help
multiple times. So obviously we have a match.

The first and most difficult step of uniting the SourceForge archive
and the GNU archive is to have a common macro repository. Or, if that
is not feasible for any other reason, to have both repositories
synchronized. Thus, I have reinstalled your CVS commit rights on
Savannah and would ask you to please add the macros that you have and
I do not.

Independent of that, we should discuss the future development of both
archives. There are lot's of changes happening on the gnu.org site at
the moment, and I will try to make those changes in a way that does
not break your synchronization mechanism. Furthermore, I would
appreciate your feedback on whether those changes are good, bad, or
could be done better.

For this purpose, I have created a mailing list, to which I invite you
and _everybody_ else, who is interested in contributing to this
project, to subscribe. You can do so at:

    http://mail.gnu.org/mailman/listinfo/ac-archive-maintainers/

Hope to see you there.

Peter




From MAILER-DAEMON Sun Jan 19 19:08:10 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aPTc-0003ua-00
	for mharc-autoconf@gnu.org; Sun, 19 Jan 2003 19:07:44 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18aPTT-0003c0-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 19:07:35 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18aPTC-0002xr-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 19:07:19 -0500
Received: from smtp4.wanadoo.nl ([194.134.35.175])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18aPSI-0001Zt-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 19:06:22 -0500
Received: from steven.lr-s.tudelft.nl (3eea15de.cable.wanadoo.nl
	[62.234.21.222])	by smtp4.wanadoo.nl (Postfix) with ESMTP
	id EDBC23E32B; Mon, 20 Jan 2003 01:06:18 +0100 (CET)
From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: "Steven G. Johnson" <stevenj@alum.mit.edu>
In-Reply-To: <Pine.LNX.4.21.0301141414590.9747-100000@ab-initio.mit.edu>
References: <Pine.LNX.4.21.0301141414590.9747-100000@ab-initio.mit.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.5 
Date: 20 Jan 2003 01:07:03 +0100
Message-Id: <1043021224.754.78.camel@steven>
Mime-Version: 1.0
cc: GNU Fortran 95 development-mailing-list
	<gcc-g95-devel@lists.sourceforge.net>
cc: autoconf@gnu.org
Subject: Re: [G95] planned obsolescence?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 20 Jan 2003 00:07:41 -0000

Op di 14-01-2003, om 20:16 schreef Steven G. Johnson:
---- 8< ----
> Wouldn't it be advisable to use a
> generic name like "gfc" instead of a version-dependent one like "g95?"

While I don't think the decision has been made yet, it seems that
everybody involved here feels that it would indeed be the Right Thing to
change the name of the compiler from g95 to gfc (that is, at least the
driver program should be called gfc).

> 
> This is not entirely an abstract question for me, since I have done a lot
> of the maintainance work on Fortran support in GNU Autoconf.  Recently,
> I've proposed a patch to add support for newer Fortran dialects
> simultaneously with F77:
> 
> 	http://mail.gnu.org/archive/html/autoconf-patches/2002-11/msg00009.html
> 
> The basic viewpoint of this patch is that future Fortran support in
> Autoconf should not have a new set of macros for every revision of the
> standard; everything should be handled with $(FC), $(FCFLAGS), etcetera,
> just like e.g. C and C++, with the exception of F77 (which keeps a
> separate $F77 etc. for legacy code).
> 
> Since you guys are at the forefront of Fortran development, I'm curious to
> hear your perspective.

Suppose we do change the name, would this also mean that your patches
would be accepted to go into autoconf?

One of the things we're having trouble with all the time, is
autoconf/automake.  Right now, Paul Brook has to maintain is own set of
patches to autoconf[1] and automake to allow us to build our runtime
library  (which is partially written in Fortran 90).
This is obviously very inconvenient.  The sooner the support in the
official releases is there, the better[2].

It would certainly help if autoconf and automake would start supporting
$(FC).  The bulk of the work already exists, even for automake.  It's
just a matter of accepting it.

Greetz
Steven

[1] Available from http://sourceforge.net/projects/gcc-g95/
[2] Now if only GCC would move to a more recent autoconf soon ;-)





From MAILER-DAEMON Sun Jan 19 19:53:08 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aQA0-0004Rl-00
	for mharc-autoconf@gnu.org; Sun, 19 Jan 2003 19:51:32 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18aQ7j-0002VP-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 19:49:11 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18aQ75-0001oC-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 19:48:38 -0500
Received: from pop.gmx.net ([213.165.65.60] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18aQ6j-0001BZ-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 19:48:09 -0500
Received: (qmail 10545 invoked by uid 0); 20 Jan 2003 00:48:07 -0000
Received: from pd9e83577.dip.t-dialin.net (HELO gmx.de) (217.232.53.119)
  by mail.gmx.net (mp008-rz3) with SMTP; 20 Jan 2003 00:48:07 -0000
Message-ID: <3E2B47C1.3050803@gmx.de>
Date: Mon, 20 Jan 2003 01:50:09 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Peter Simons <simons@cryp.to>
References: <873cnrgarb.fsf@overkill.cryp.to> <3E281B67.1010803@gmx.de>
	<87y95jdvni.fsf@overkill.cryp.to> <3E296283.5080208@gmx.de>
	<87adhyph7q.fsf@overkill.cryp.to> <3E29A3EC.3020105@gmx.de>
	<87of6enrze.fsf@overkill.cryp.to>
	<1042923960.16849.53.camel@localhost.localdomain>
	<871y3973gw.fsf_-_@overkill.cryp.to> <3E2ACE82.9020400@gmx.de>
	<87k7h13vnm.fsf_-_@overkill.cryp.to> <3E2AE579.6000907@gmx.de>
	<87ptqs7mck.fsf_-_@overkill.cryp.to>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: Let's start over  (was: Unifying ac-archive.sf.net and gnu.org)
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 20 Jan 2003 00:51:30 -0000



Peter Simons schrieb:
> I would like to see the two archives merge as much as any of us, and I
> realize that we will never see that happening unless we are able to
> compromise. I requested help multiple times, and you have offered help
> multiple times. So obviously we have a match.
> 
> The first and most difficult step of uniting the SourceForge archive
> and the GNU archive is to have a common macro repository. Or, if that
> is not feasible for any other reason, to have both repositories
> synchronized. Thus, I have reinstalled your CVS commit rights on
> Savannah and would ask you to please add the macros that you have and
> I do not.

I will do so - at the moment I am not sure about your reorganizations
in the savannah cvs, so allow me to wait a few days. ;-)

> 
> Independent of that, we should discuss the future development of both
> archives. There are lot's of changes happening on the gnu.org site at
> the moment, and I will try to make those changes in a way that does
> not break your synchronization mechanism. Furthermore, I would
> appreciate your feedback on whether those changes are good, bad, or
> could be done better.
> 
> For this purpose, I have created a mailing list, to which I invite you
> and _everybody_ else, who is interested in contributing to this
> project, to subscribe. You can do so at:
> 
>     http://mail.gnu.org/mailman/listinfo/ac-archive-maintainers/
> 
> Hope to see you there.
> 

I will sure be there.

As for the unification - let me propose the following scheme:

- let us create a mailing list for macro submissions, perhaps
   ac-archive-macros@, that will be put on the webpage(s) to
   be used as the target to send macro submissions to.
- everyone is invited to subscribe and have a look at what is
   coming in, to comment on and discuss things with the
   submitter cc'ing the list (if that is needed at all). I am
   confident that everyone subscribed to autoconf-patches will
   also follow the ac-archive-macros@ list.
- when either of us commits a macro to the cvs repository, then
   it gets noted back on the list. That is also good as to know
   when it is time to update the website(s) or perhaps repackage
   things.
- the submitter does not need to care anymore that there are two
   websites at the moment - interactions happens with one
   counterpart alone, or so it feels atleast ;-)

There are more technical things to discuss but that should really
be on the -maintainers list. Specifically, I have never been
informed about the mode-d'emploi of updating the gnu webpages,
so I was careless committing macros back then - that should not
happen anymore.

so, let's start over, :-)
-- cheers, guido




From MAILER-DAEMON Sun Jan 19 21:32:41 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aRj0-00016C-00
	for mharc-autoconf@gnu.org; Sun, 19 Jan 2003 21:31:46 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18aRik-0000hd-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 21:31:30 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18aRhg-0007fx-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 21:30:25 -0500
Received: from ab-initio.mit.edu ([18.62.2.90])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18aRh2-00078K-00
	for autoconf@gnu.org; Sun, 19 Jan 2003 21:29:44 -0500
Received: from stevenj (helo=localhost)
	by ab-initio.mit.edu with local-esmtp (Exim 3.35 #1 (Debian))
	id 18aRgy-0005ex-00; Sun, 19 Jan 2003 21:29:40 -0500
Date: Sun, 19 Jan 2003 21:29:40 -0500 (EST)
From: "Steven G. Johnson" <stevenj@ab-initio.mit.edu>
To: Steven Bosscher <s.bosscher@student.tudelft.nl>
In-Reply-To: <1043021224.754.78.camel@steven>
Message-ID: <Pine.LNX.4.21.0301192105050.20544-100000@ab-initio.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: GNU Fortran 95 development-mailing-list
	<gcc-g95-devel@lists.sourceforge.net>
cc: autoconf@gnu.org
Subject: Re: [G95] planned obsolescence?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: "Steven G. Johnson" <stevenj@alum.mit.edu>
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 20 Jan 2003 02:31:40 -0000

On 20 Jan 2003, Steven Bosscher wrote:
> Suppose we do change the name, would this also mean that your patches
> would be accepted to go into autoconf?

My proposed patch for f9x support in autoconf does not depend upon whether
g95 chooses a more generic name (autoconf has to support compilers named
f90 etc. anyway), although of course we'll add support for whatever name
you choose.  Maybe it would demonstrate my godlike influence in the world
of Fortran, though, and convince Akim to do whatever I say.  =)

> It would certainly help if autoconf and automake would start supporting
> $(FC).  The bulk of the work already exists, even for automake.  It's
> just a matter of accepting it.

I agree that Fortran 9x+ support in autoconf is important pending issue
for 2003.  This issue has becoming more and more critical over the last
few years, although the need has been dampened somewhat by the lack of a
free f9x compiler.

> Right now, Paul Brook has to maintain is own set of
> patches to autoconf[1] and automake to allow us to build our runtime
> library  (which is partially written in Fortran 90).

Thanks, I took a look at the F95 patches for g95...it looks mainly like a
copy of fortran.m4 to f95.m4 with s/f77/f95/.  Is that accurate, or could
you point to any more substantive changes you needed to make?  My proposed
autoconf patch should do what you want, while sharing the fortran backends
between dialects.

(I'm a bit surprised that you needed this at all, since I would have
thought you could just use AC_PROG_F77(f90) and compile all Fortran xx
files with $F77, especially since the backend is equivalent anyway in your
implementation.  I've done this for existing projects of mine where I need
to compile f90 files, with no major problems.  The current autoconf f77
stuff works for newer dialects for most purposes, except when one needs to
mix f77 and f9x.  My patch does address one additional issue, the fact
that IBM's xlf does not accept .f9* extensions without a special flag,
grrr.)

Steven

PS. For those who are wondering what this thread is about, see the
"Fortran 9x" thread on this list from last fall:
	http://mail.gnu.org/archive/html/autoconf/2002-10/msg00188.html
and the proposed patch that I submitted based on that thread:
	http://mail.gnu.org/archive/html/autoconf-patches/2002-11/msg00009.html
I recently pinged the gcc-g95 developers to ask their opinion, and to also
suggest that they name their backend something less dialect tied, like
'gfc'.





From MAILER-DAEMON Mon Jan 20 02:24:07 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aWHY-0003NG-00
	for mharc-autoconf@gnu.org; Mon, 20 Jan 2003 02:23:44 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18aWH8-000237-00
	for autoconf@gnu.org; Mon, 20 Jan 2003 02:23:18 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18aWGq-0001Bb-00
	for autoconf@gnu.org; Mon, 20 Jan 2003 02:23:04 -0500
Received: from smtp5.wanadoo.nl ([194.134.35.176])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18aWGn-0000wR-00
	for autoconf@gnu.org; Mon, 20 Jan 2003 02:22:57 -0500
Received: from steven.lr-s.tudelft.nl (3eea149c.cable.wanadoo.nl
	[62.234.20.156])	by smtp5.wanadoo.nl (Postfix) with ESMTP
	id 77F917456A; Mon, 20 Jan 2003 08:22:52 +0100 (CET)
From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: "Steven G. Johnson" <stevenj@alum.mit.edu>
In-Reply-To: <Pine.LNX.4.21.0301192105050.20544-100000@ab-initio.mit.edu>
References: <Pine.LNX.4.21.0301192105050.20544-100000@ab-initio.mit.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.5 
Date: 20 Jan 2003 08:23:36 +0100
Message-Id: <1043047417.742.2.camel@steven>
Mime-Version: 1.0
cc: GNU Fortran 95 development-mailing-list
	<gcc-g95-devel@lists.sourceforge.net>
cc: autoconf@gnu.org
Subject: Re: [G95] planned obsolescence?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 20 Jan 2003 07:23:42 -0000

Op ma 20-01-2003, om 03:29 schreef Steven G. Johnson:
> On 20 Jan 2003, Steven Bosscher wrote:
> > It would certainly help if autoconf and automake would start supporting
> > $(FC).  The bulk of the work already exists, even for automake.  It's
> > just a matter of accepting it.
> 
> I agree that Fortran 9x+ support in autoconf is important pending issue
> for 2003.  This issue has becoming more and more critical over the last
> few years, although the need has been dampened somewhat by the lack of a
> free f9x compiler.

Well, that's a big of a chicken-and-egg problem, don't you think?

It really won't be *that* long before we'll see g95 included in gcc, I'd
certainly hope we get that over with before the end of 2003.  After all,
that still *is* one of the primary goals in the short term.

Greetz
Steven





From MAILER-DAEMON Mon Jan 20 03:17:01 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18aX6Q-0004Fp-00
	for mharc-autoconf@gnu.org; Mon, 20 Jan 2003 03:16:18 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18aX5w-0002xp-00
	for autoconf@gnu.org; Mon, 20 Jan 2003 03:15:48 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18aX5d-0002Xl-00
	for autoconf@gnu.org; Mon, 20 Jan 2003 03:15:31 -0500
Received: from karman.lufmech.rwth-aachen.de ([134.130.177.1])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18aX50-00025R-00
	for autoconf@gnu.org; Mon, 20 Jan 2003 03:14:50 -0500
Received: from web.de (tresca.lufmech.RWTH-Aachen.DE [134.130.177.109]) by
	karman.lufmech.rwth-aachen.de with ESMTP (8.9.3 (PHNE_18979)/8.7.1) id
	JAA15628; Mon, 20 Jan 2003 09:14:42 +0100 (MET)
Sender: markus@karman.lufmech.rwth-aachen.de
Message-ID: <3E2BAFF2.61F30B1E@web.de>
Date: Mon, 20 Jan 2003 09:14:42 +0100
From: Markus Werle <numerical.simulation@web.de>
X-Mailer: Mozilla 4.79 [en] (X11; U; HP-UX B.11.11 9000/785)
X-Accept-Language: en
MIME-Version: 1.0
To: Paul Brook <paul@nowt.org>
References: <3E28797C.DC09ACA8@web.de> <200301172223.46901.paul@nowt.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: Makefile variables depending on configure args - how?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 20 Jan 2003 08:16:14 -0000

Paul Brook wrote:

> I think you need to add
>
> AC_SUBST([DIET], [${DIETDIR}])

Thanks! I knew it was something very simple.

Another question: I thought configure.in was just a shell
script substitute, so I ommitted the "{}".
Also missing brackets around DIET do not disturb autoconf.
Is the follwing OK, or are there any issues (like portability)?

AC_SUBST(DIET, $DIETDIR)


best regards,


Markus





From MAILER-DAEMON Mon Jan 20 07:33:07 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ab6e-0006KE-00
	for mharc-autoconf@gnu.org; Mon, 20 Jan 2003 07:32:48 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ab6D-0005Na-00
	for autoconf@gnu.org; Mon, 20 Jan 2003 07:32:21 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ab3r-0002Kv-00
	for autoconf@gnu.org; Mon, 20 Jan 2003 07:29:58 -0500
Received: from smtp017.mail.yahoo.com ([216.136.174.114])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18ab3r-0002KA-00
	for autoconf@gnu.org; Mon, 20 Jan 2003 07:29:55 -0500
Received: from gate1.lci.net (HELO yahoo.com) (earnie?boyd@150.159.224.8 with
	plain)
	by smtp.mail.vip.sc5.yahoo.com with SMTP; 20 Jan 2003 12:29:53 -0000
Message-ID: <3E2BEBBF.7000909@yahoo.com>
Date: Mon, 20 Jan 2003 07:29:51 -0500
From: Earnie Boyd <earnie_boyd@yahoo.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Markus Werle <numerical.simulation@web.de>
References: <3E28797C.DC09ACA8@web.de> <200301172223.46901.paul@nowt.org>
	<3E2BAFF2.61F30B1E@web.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: Paul Brook <paul@nowt.org>
cc: autoconf@gnu.org
Subject: Re: Makefile variables depending on configure args - how?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: autoconf@gnu.org
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 20 Jan 2003 12:32:41 -0000

Markus Werle wrote:
> Paul Brook wrote:
> 
> 
>>I think you need to add
>>
>>AC_SUBST([DIET], [${DIETDIR}])
> 
> 
> Thanks! I knew it was something very simple.
> 
> Another question: I thought configure.in was just a shell
> script substitute, so I ommitted the "{}".
> Also missing brackets around DIET do not disturb autoconf.
> Is the follwing OK, or are there any issues (like portability)?
> 
> AC_SUBST(DIET, $DIETDIR)
> 

The rule of thumb is to quote.  The expansions may cause problems that 
quoting will avoid.  I.E.: It may work this time, but not the next.

Earnie.




From MAILER-DAEMON Tue Jan 21 13:53:15 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18b3WM-000194-00
	for mharc-autoconf@gnu.org; Tue, 21 Jan 2003 13:53:14 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18b3WJ-00017v-00
	for autoconf@gnu.org; Tue, 21 Jan 2003 13:53:11 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18b3WH-00015Z-00
	for autoconf@gnu.org; Tue, 21 Jan 2003 13:53:10 -0500
Received: from host217-44-175-28.range217-44.btcentralplus.com
	([217.44.175.28] helo=paul.home)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18b3WG-00012a-00
	for autoconf@gnu.org; Tue, 21 Jan 2003 13:53:09 -0500
Received: from localhost.localdomain (localhost [127.0.0.1])
	by paul.home (Postfix) with ESMTP
	id D4346E48CF; Tue, 21 Jan 2003 18:53:04 +0000 (GMT)
From: Paul Brook <paul@nowt.org>
To: "Steven G. Johnson" <stevenj@alum.mit.edu>
Date: Tue, 21 Jan 2003 18:53:04 +0000
User-Agent: KMail/1.5
References: <Pine.LNX.4.21.0301192105050.20544-100000@ab-initio.mit.edu>
In-Reply-To: <Pine.LNX.4.21.0301192105050.20544-100000@ab-initio.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200301211853.04644.paul@nowt.org>
cc: GNU Fortran 95 development-mailing-list
	<gcc-g95-devel@lists.sourceforge.net>
cc: autoconf@gnu.org
Subject: Re: [G95] planned obsolescence?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 21 Jan 2003 18:53:12 -0000

On Monday 20 January 2003 2:29 am, Steven G. Johnson wrote:
> > Right now, Paul Brook has to maintain is own set of
> > patches to autoconf[1] and automake to allow us to build our runtime
> > library  (which is partially written in Fortran 90).
>
> Thanks, I took a look at the F95 patches for g95...it looks mainly like a
> copy of fortran.m4 to f95.m4 with s/f77/f95/.  Is that accurate, or could
> you point to any more substantive changes you needed to make?  My
> proposed autoconf patch should do what you want, while sharing the
> fortran backends between dialects.

I think that's pretty much it.
I made some more substantial changes to automake, to allow dependency 
tracking of f9x modules. This is overkill for libgfor, which doesn't use 
modules, but I use it for some of my own programs. This is also the cause 
of most of the problems as I haven't ironed out all the bugs yet (I think I 
may also have uncovered a couple of automake bugs).

> (I'm a bit surprised that you needed this at all, since I would have
> thought you could just use AC_PROG_F77(f90) and compile all Fortran xx
> files with $F77, especially since the backend is equivalent anyway in
> your implementation.  I've done this for existing projects of mine where
> I need to compile f90 files, with no major problems.  The current
> autoconf f77 stuff works for newer dialects for most purposes, except
> when one needs to mix f77 and f9x.  My patch does address one additional
> issue, the fact that IBM's xlf does not accept .f9* extensions without a
> special flag, grrr.)

I can't remember if I tried this or not. Maybe I'll give it annother try, 
it'd be nuce if we could do without my hacks.

Paul




From MAILER-DAEMON Wed Jan 22 09:04:24 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bLTR-0002m1-00
	for mharc-autoconf@gnu.org; Wed, 22 Jan 2003 09:03:25 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bLTO-0002kF-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 09:03:22 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bLTM-0002i3-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 09:03:20 -0500
Received: from cm-mail.stanford.edu ([171.64.197.135])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18bLS8-0002GS-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 09:02:04 -0500
Received: from cmn14.stanford.edu (cmn14.stanford.edu [171.64.197.163])
	by cm-mail.stanford.edu (8.11.6/8.11.6) with ESMTP id h0ME22C13146
	for <autoconf@gnu.org>; Wed, 22 Jan 2003 06:02:02 -0800
Received: (from bil@localhost)
	by cmn14.stanford.edu (8.9.3/8.9.3) id GAA20117
	for autoconf@gnu.org; Wed, 22 Jan 2003 06:02:01 -0800 (PST)
Message-Id: <200301221402.GAA20117@cmn14.stanford.edu>
Content-Type: text/plain
MIME-Version: 1.0 (NeXT Mail 3.3 v148.2.1)
X-Nextstep-Mailer: Mail 3.3 [m68k] (Enhance 2.2p2)
Received: by NeXT.Mailer (1.148.2.1)
From: Bill Schottstaedt <bil@ccrma.Stanford.EDU>
Date: Wed, 22 Jan 2003 06:01:59 -0800
To: autoconf@gnu.org
Subject: AC_CHECK_HEADER, autoconf 2.57, includes problem
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 22 Jan 2003 14:03:23 -0000

My apologies if this has already been reported.

In autoconf 2.57 in AC_CHECK_HEADER, I think the gcc -E conftest
check for header usability needs to include the default includes
from the header presence test.  In my case,

        OLD_CFLAGS="$CFLAGS"
        CFLAGS="-I/usr/local/include/gtkglext-1.0 -I/usr/local/lib/gtkglext-1.0/include $GTK_CFLAGS $CFLAGS"
	AC_CHECK_HEADER(gtk/gtkgl.h,
	  [
            GL_LIBS="$GL_LIBS -lgdkglext-x11-1.0 -lgtkglext-x11-1.0"
            GL_FLAGS="$GL_FLAGS -I/usr/local/include/gtkglext-1.0 -I/usr/local/lib/gtkglext-1.0/include"
	  ],
	  [
            GL_LIBS="$GL_LIBS -lgdkglext-x11-0.x -lgtkglext-x11-0.x"
            GL_FLAGS="$GL_FLAGS -I/usr/local/include/gtkglext-0.x"
	  ])
	CFLAGS="$OLD_CFLAGS"

(yes I know it's ugly -- there's no config program for this library, so
I have to search for it by hand).  This gets:


checking gtk/gtkgl.h usability... yes
checking gtk/gtkgl.h presence... no
configure: WARNING: gtk/gtkgl.h: accepted by the compiler, rejected by the preprocessor!
configure: WARNING: gtk/gtkgl.h: proceeding with the preprocessor's result
configure: WARNING:     ## ------------------------------------ ##
configure: WARNING:     ## Report this to bug-autoconf@gnu.org. ##
configure: WARNING:     ## ------------------------------------ ##
checking for gtk/gtkgl.h... no


config.log at the bad spot is:

configure:12407: checking gtk/gtkgl.h usability
configure:12420: gcc -c -I/usr/local/include/gtkglext-1.0 -I/usr/local/lib/gtkglext-1.0/include   
-I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/include/Xft2  
-I/usr/include/freetype2 -I/usr/X11R6/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include   -g -O2  conftest.c  
>&5
configure:12423: $? = 0
configure:12426: test -s conftest.o
configure:12429: $? = 0
configure:12439: result: yes
configure:12443: checking gtk/gtkgl.h presence
configure:12454: gcc -E  conftest.c
configure:12523:23: gtk/gtkgl.h: No such file or directory
configure:12460: $? = 1
configure: failed program was:
| #line 12445 "configure"
| /* confdefs.h.  */
|
| #define PACKAGE_NAME "snd"
| #define PACKAGE_TARNAME "ftp://ccrma-ftp.stanford.edu/pub/Lisp/snd-6.tar.gz"
| #define PACKAGE_VERSION "6.6"
| #define PACKAGE_STRING "snd 6.6"
| #define PACKAGE_BUGREPORT "bil@ccrma.stanford.edu"
| #define STDC_HEADERS 1
| #define Float float
| #define HAVE_GSL 1
| #define GSL_VERSION "1.3"
| #define HAVE_LIBM 1
| #define HAVE_LIBC 1
| #define HAVE_LIBDL 1
| #define HAVE_DIRENT_H 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_FCNTL_H 1
| #define HAVE_LIMITS_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_STRING_H 1
| #define HAVE_SYS_SOUNDCARD_H 1
| #define HAVE_GSL_GSL_VERSION_H 1
| #define HAVE_SYS_VFS_H 1
| #define HAVE_SYS_STATFS_H 1
| #define HAVE_SYS_MOUNT_H 1
| #define HAVE_SETJMP_H 1
| #define HAVE_SCHED_H 1
| #define HAVE_PWD_H 1
| #define HAVE_LADSPA_H 1
| #define HAVE_LOCALE_H 1
| #define HAVE_DLFCN_H 1
| #define HAVE_SYS_PARAM_H 1
| #define HAVE_BYTESWAP_H 1
| #define HAVE_GNU_LIBC_VERSION_H 1
| #define TIME_WITH_SYS_TIME 1
| #define _FILE_OFFSET_BITS 64
| #define HAVE_STRINGIZE 1
| #define SIZEOF_INT 4
| #define SIZEOF_CHAR 1
| #define SIZEOF_SHORT 2
| #define SIZEOF_LONG 4
| #define SIZEOF_INT_P 4
| #define SIZEOF_FLOAT 4
| #define SIZEOF_VOID_P 4
| #define SIZEOF_OFF_T 8
| #define HAVE_LLONGS 1
| #define HAVE_ISNAN 1
| #define HAVE_FFTW 1
| #define RETSIGTYPE void
| #define HAVE_STRFTIME 1
| #define HAVE_GETCWD 1
| #define HAVE_STRERROR 1
| #define HAVE_READLINK 1
| #define HAVE_SETLOCALE 1
| #define HAVE_ACCESS 1
| #define HAVE_OPENDIR 1
| #define HAVE_SLEEP 1
| #define HAVE_SIGNAL 1
| #define HAVE_STRDUP 1
| #define HAVE_STATFS 1
| #define HAVE_CLOCK 1
| #define HAVE_VSNPRINTF 1
| #define HAVE_SNPRINTF 1
| #define HAVE_MEMMOVE 1
| #define HAVE_VPRINTF 1
| #define HAVE_X 1
| #define USE_GTK 1
| #define HAVE_GL 1
| #define JUST_GL 1
| /* end confdefs.h.  */
| #include <gtk/gtkgl.h>
configure:12479: result: no
configure:12485: WARNING: gtk/gtkgl.h: accepted by the compiler, rejected by the preprocessor!
configure:12487: WARNING: gtk/gtkgl.h: proceeding with the preprocessor's result
configure:12515: checking for gtk/gtkgl.h
configure:12522: result: no



From MAILER-DAEMON Wed Jan 22 09:34:11 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bLwS-0007HO-00
	for mharc-autoconf@gnu.org; Wed, 22 Jan 2003 09:33:24 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bLwD-0006wF-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 09:33:09 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bLw2-0006ms-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 09:32:59 -0500
Received: from iceage.anubex.com ([194.78.64.234])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18bLw0-0006ib-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 09:32:56 -0500
Received: from leeloo.anubex.com (unknown [192.168.14.202])
	by iceage.anubex.com (Anubex Mail Server) with ESMTP
	id 2F6E51C00B1; Wed, 22 Jan 2003 15:32:53 +0100 (CET)
From: Tim Van Holder <tim.van.holder@pandora.be>
To: Bill Schottstaedt <bil@ccrma.Stanford.EDU>
In-Reply-To: <200301221402.GAA20117@cmn14.stanford.edu>
References: <200301221402.GAA20117@cmn14.stanford.edu>
Content-Type: text/plain
Organization: 
Message-Id: <1043246166.22383.9.camel@leeloo>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.1 
Date: 22 Jan 2003 15:36:06 +0100
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: AC_CHECK_HEADER, autoconf 2.57, includes problem
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 22 Jan 2003 14:33:22 -0000

On Wed, 2003-01-22 at 15:01, Bill Schottstaedt wrote:
> My apologies if this has already been reported.

Similar things have been reported, so this _might_ be fixed in CVS
autoconf already.

> In autoconf 2.57 in AC_CHECK_HEADER, I think the gcc -E conftest
> check for header usability needs to include the default includes
> from the header presence test.  In my case,
> 
>         OLD_CFLAGS="$CFLAGS"
>         CFLAGS="-I/usr/local/include/gtkglext-1.0 -I/usr/local/lib/gtkglext-1.0/include $GTK_CFLAGS $CFLAGS"

Shouldn't you add the -I flags to CPPFLAGS, as those are precompiler
options? My guess is that this may fix the problem as well (assuming
the precompiler test run by configure uses $CPPFLAGS).
I'd certainly agree that it would be nice if configure tried to grok
CFLAGS and extract the options that could/should go into CPPFLAGS, but
I expect this would be quite error-prone.
At the very least, the docs for AC_CHECK_HEADER should probably be
expanded to mention this.

> 	AC_CHECK_HEADER(gtk/gtkgl.h,
> 	  [
>             GL_LIBS="$GL_LIBS -lgdkglext-x11-1.0 -lgtkglext-x11-1.0"
>             GL_FLAGS="$GL_FLAGS -I/usr/local/include/gtkglext-1.0 -I/usr/local/lib/gtkglext-1.0/include"
> 	  ],
> 	  [
>             GL_LIBS="$GL_LIBS -lgdkglext-x11-0.x -lgtkglext-x11-0.x"
>             GL_FLAGS="$GL_FLAGS -I/usr/local/include/gtkglext-0.x"
> 	  ])
> 	CFLAGS="$OLD_CFLAGS"
> 
> (yes I know it's ugly -- there's no config program for this library, so
> I have to search for it by hand).  This gets:

-- 
Tim Van Holder <tim.van.holder@pandora.be>




From MAILER-DAEMON Wed Jan 22 09:54:06 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bMGU-0000RF-00
	for mharc-autoconf@gnu.org; Wed, 22 Jan 2003 09:54:06 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bMGR-0000O1-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 09:54:03 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bMGO-0000Kq-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 09:54:02 -0500
Received: from cm-mail.stanford.edu ([171.64.197.135])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18bMFq-0008W6-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 09:53:26 -0500
Received: from cmn14.stanford.edu (cmn14.stanford.edu [171.64.197.163])
	by cm-mail.stanford.edu (8.11.6/8.11.6) with ESMTP id h0MErPC14076;
	Wed, 22 Jan 2003 06:53:25 -0800
Received: (from bil@localhost)
	by cmn14.stanford.edu (8.9.3/8.9.3) id GAA20174;
	Wed, 22 Jan 2003 06:53:24 -0800 (PST)
Message-Id: <200301221453.GAA20174@cmn14.stanford.edu>
Content-Type: text/plain
MIME-Version: 1.0 (NeXT Mail 3.3 v148.2.1)
In-Reply-To: <1043246166.22383.9.camel@leeloo>
X-Nextstep-Mailer: Mail 3.3 [m68k] (Enhance 2.2p2)
Received: by NeXT.Mailer (1.148.2.1)
From: Bill Schottstaedt <bil@ccrma.Stanford.EDU>
Date: Wed, 22 Jan 2003 06:53:22 -0800
To: Tim Van Holder <tim.van.holder@pandora.be>
References: <200301221402.GAA20117@cmn14.stanford.edu>
	<1043246166.22383.9.camel@leeloo>
cc: autoconf@gnu.org
cc: harinath@cs.umn.edu
Subject: Re: AC_CHECK_HEADER, autoconf 2.57, includes problem
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 22 Jan 2003 14:54:04 -0000

Thanks very much!  That explains some other problems I was
having as well.



From MAILER-DAEMON Wed Jan 22 09:58:34 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bMJR-0001Y2-00
	for mharc-autoconf@gnu.org; Wed, 22 Jan 2003 09:57:09 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bMEP-00086I-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 09:51:57 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bM7H-0004Bl-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 09:44:36 -0500
Received: from mail.cs.umn.edu ([128.101.35.202])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18bM4m-0002oL-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 09:42:00 -0500
Received: from bose.cs.umn.edu (bose.cs.umn.edu [128.101.35.195])
	by mail.cs.umn.edu (Postfix) with ESMTP
	id 7599F11326; Wed, 22 Jan 2003 08:41:59 -0600 (CST)
Received: by bose.cs.umn.edu (Postfix, from userid 818)
	id 06C1B3200; Wed, 22 Jan 2003 08:41:58 -0600 (CST)
To: Bill Schottstaedt <bil@ccrma.Stanford.EDU>
From: Raja R Harinath <harinath@cs.umn.edu>
Date: Wed, 22 Jan 2003 08:41:58 -0600
In-Reply-To: <200301221402.GAA20117@cmn14.stanford.edu> (Bill Schottstaedt's
 message of "Wed, 22 Jan 2003 06:01:59 -0800")
Message-ID: <d98yxdutzd.fsf@bose.cs.umn.edu>
User-Agent: Gnus/5.090013 (Oort Gnus v0.13) Emacs/21.3.50
 (i686-pc-linux-gnu)
References: <200301221402.GAA20117@cmn14.stanford.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: autoconf@gnu.org
Subject: Re: AC_CHECK_HEADER, autoconf 2.57, includes problem
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 22 Jan 2003 14:57:07 -0000

Hi,

Bill Schottstaedt <bil@ccrma.Stanford.EDU> writes:

> My apologies if this has already been reported.
>
> In autoconf 2.57 in AC_CHECK_HEADER, I think the gcc -E conftest
> check for header usability needs to include the default includes
> from the header presence test.  In my case,
>
>         OLD_CFLAGS="$CFLAGS"
>         CFLAGS="-I/usr/local/include/gtkglext-1.0
>         -I/usr/local/lib/gtkglext-1.0/include $GTK_CFLAGS $CFLAGS"

This is the actual bug, and it's in your configure.in.  Set CPPFLAGS
instead.

> checking gtk/gtkgl.h usability... yes
> checking gtk/gtkgl.h presence... no
> configure: WARNING: gtk/gtkgl.h: accepted by the compiler, rejected by the preprocessor!
> configure: WARNING: gtk/gtkgl.h: proceeding with the preprocessor's result
> configure: WARNING:     ## ------------------------------------ ##
> configure: WARNING:     ## Report this to bug-autoconf@gnu.org. ##
> configure: WARNING:     ## ------------------------------------ ##
> checking for gtk/gtkgl.h... no

A red herring.  GIGO ;-)  But, the warning does contain a hint that
the compiler and the preprocessor may be seeing things -- like search
paths -- differently.

- Hari
-- 
Raja R Harinath ------------------------------ harinath@cs.umn.edu



From MAILER-DAEMON Wed Jan 22 11:22:05 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bNbb-0003ra-00
	for mharc-autoconf@gnu.org; Wed, 22 Jan 2003 11:19:59 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bNb1-0003cl-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 11:19:23 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bNaw-0003at-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 11:19:19 -0500
Received: from dangermouse.ncsa.uiuc.edu ([141.142.96.46])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18bNaw-0003aH-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 11:19:18 -0500
Received: (from wendling@localhost)
	by dangermouse.ncsa.uiuc.edu (8.11.6/8.11.6) id h0MGJFZ17009
	for autoconf@gnu.org; Wed, 22 Jan 2003 10:19:15 -0600
Date: Wed, 22 Jan 2003 10:19:15 -0600
From: Bill Wendling <wendling@ncsa.uiuc.edu>
To: autoconf@gnu.org
Message-ID: <20030122161915.GA17002@ncsa.uiuc.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-PGP-Key: http://www.ncsa.uiuc.edu/~wendling/public_key.asc
X-PGP-Fingerprint: C169 5EB2 2F92 9C34 C9FA  E976 3C24 E3D3 EBE7 C80B
Subject: C99 Compiler Support Determination?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 22 Jan 2003 16:19:57 -0000

Hi,

Is there a way to determine if a compiler is C99 compliant during
configuration?

Thanks.

-- 
|| Bill Wendling            "Real Programmers have a Snoopy Calendar
|| wendling@ncsa.uiuc.edu    of '69 hanging on their wall"
|| Coding Simian                       -- Toon Moene



From MAILER-DAEMON Wed Jan 22 15:01:33 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bQz8-0002c0-00
	for mharc-autoconf@gnu.org; Wed, 22 Jan 2003 14:56:30 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bQxR-0001dL-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 14:54:45 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bQsQ-00007i-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 14:49:35 -0500
Received: from windlord.stanford.edu ([171.64.13.23])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18bQpW-0005ZJ-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 14:46:34 -0500
Received: (qmail 22260 invoked by uid 50); 22 Jan 2003 19:46:32 -0000
To: autoconf@gnu.org
References: <20030122161915.GA17002@ncsa.uiuc.edu>
In-Reply-To: <20030122161915.GA17002@ncsa.uiuc.edu> (Bill Wendling's message
 of "Wed, 22 Jan 2003 10:19:15 -0600")
From: Russ Allbery <rra@stanford.edu>
Organization: The Eyrie
Date: Wed, 22 Jan 2003 11:46:32 -0800
Message-ID: <yly95d6k87.fsf@windlord.stanford.edu>
Lines: 12
User-Agent: Gnus/5.090008 (Oort Gnus v0.08) XEmacs/21.4 (Honest Recruiter,
 sparc-sun-solaris2.6)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: C99 Compiler Support Determination?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 22 Jan 2003 19:56:29 -0000

Bill Wendling <wendling@ncsa.uiuc.edu> writes:

> Is there a way to determine if a compiler is C99 compliant during
> configuration?

You probably want to be more specific and check for C99 features that
you're using.  It's not clear that there are, as yet, any *fully*
compliant C99 environments, although one or two may have started to show
up.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>



From MAILER-DAEMON Wed Jan 22 15:34:57 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bRVh-0006Vt-00
	for mharc-autoconf@gnu.org; Wed, 22 Jan 2003 15:30:09 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bRSK-00052S-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 15:26:40 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bRRL-0004I8-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 15:25:39 -0500
Received: from dangermouse.ncsa.uiuc.edu ([141.142.96.46])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18bRQo-00045s-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 15:25:06 -0500
Received: (from wendling@localhost)
	by dangermouse.ncsa.uiuc.edu (8.11.6/8.11.6) id h0MKP5d17880
	for autoconf@gnu.org; Wed, 22 Jan 2003 14:25:05 -0600
Date: Wed, 22 Jan 2003 14:25:05 -0600
From: Bill Wendling <wendling@ncsa.uiuc.edu>
To: autoconf@gnu.org
Message-ID: <20030122202505.GA17854@ncsa.uiuc.edu>
References: <20030122161915.GA17002@ncsa.uiuc.edu>
	<yly95d6k87.fsf@windlord.stanford.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <yly95d6k87.fsf@windlord.stanford.edu>
User-Agent: Mutt/1.4i
X-PGP-Key: http://www.ncsa.uiuc.edu/~wendling/public_key.asc
X-PGP-Fingerprint: C169 5EB2 2F92 9C34 C9FA  E976 3C24 E3D3 EBE7 C80B
Subject: Re: C99 Compiler Support Determination?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 22 Jan 2003 20:30:07 -0000

Also sprach Russ Allbery:
} Bill Wendling <wendling@ncsa.uiuc.edu> writes:
} 
} > Is there a way to determine if a compiler is C99 compliant during
} > configuration?
} 
} You probably want to be more specific and check for C99 features that
} you're using.  It's not clear that there are, as yet, any *fully*
} compliant C99 environments, although one or two may have started to show
} up.
} 
Mostly, I want to check to see if the compiler *isn't* C99 compliant.
There's a weird problem I'm having with a non-gcc compiler sucking in
header files from gcc but this non-gcc compiler isn't C99 (I don't
think), so it produces errors. But only if you include the
"-I/usr/include" flag during compilation.

It's making me go bald :-)

-- 
|| Bill Wendling            "Real Programmers have a Snoopy Calendar
|| wendling@ncsa.uiuc.edu    of '69 hanging on their wall"
|| Coding Simian                       -- Toon Moene



From MAILER-DAEMON Wed Jan 22 18:09:18 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bTzi-0002Cj-00
	for mharc-autoconf@gnu.org; Wed, 22 Jan 2003 18:09:18 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bTzf-0002CG-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 18:09:15 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bTze-0002Bs-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 18:09:14 -0500
Received: from windlord.stanford.edu ([171.64.13.23])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18bTys-0001ki-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 18:08:26 -0500
Received: (qmail 23849 invoked by uid 50); 22 Jan 2003 23:08:22 -0000
To: autoconf@gnu.org
References: <20030122161915.GA17002@ncsa.uiuc.edu>
	<yly95d6k87.fsf@windlord.stanford.edu>
	<20030122202505.GA17854@ncsa.uiuc.edu>
In-Reply-To: <20030122202505.GA17854@ncsa.uiuc.edu> (Bill Wendling's message
 of "Wed, 22 Jan 2003 14:25:05 -0600")
From: Russ Allbery <rra@stanford.edu>
Organization: The Eyrie
Date: Wed, 22 Jan 2003 15:08:22 -0800
Message-ID: <yln0ls3hqx.fsf@windlord.stanford.edu>
Lines: 19
User-Agent: Gnus/5.090008 (Oort Gnus v0.08) XEmacs/21.4 (Honest Recruiter,
 sparc-sun-solaris2.6)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: C99 Compiler Support Determination?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 22 Jan 2003 23:09:16 -0000

Bill Wendling <wendling@ncsa.uiuc.edu> writes:

> Mostly, I want to check to see if the compiler *isn't* C99 compliant.
> There's a weird problem I'm having with a non-gcc compiler sucking in
> header files from gcc but this non-gcc compiler isn't C99 (I don't
> think), so it produces errors. But only if you include the
> "-I/usr/include" flag during compilation.

> It's making me go bald :-)

Well, GCC isn't C99-compliant either, so I'm not sure that's the check
that you really want to perform.

In general, -I/usr/include is always wrong.  It breaks GCC too.  If you
can find a way to get rid of that in your build system, that may fix the
problem.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>



From MAILER-DAEMON Wed Jan 22 19:37:55 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bVMU-0003Qp-00
	for mharc-autoconf@gnu.org; Wed, 22 Jan 2003 19:36:54 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bVHu-0001PA-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 19:32:10 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bVHl-0001Mn-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 19:32:01 -0500
Received: from parcival.faw.uni-ulm.de ([134.60.100.20]
	helo=gawain.faw.uni-ulm.de)
	by monty-python.gnu.org with smtp (Exim 4.10.13)	id 18bVFR-0000Iw-00
	for autoconf@gnu.org; Wed, 22 Jan 2003 19:29:37 -0500
Received: (qmail 3948 invoked from network); 23 Jan 2003 00:29:57 -0000
Received: from dialin19.faw.uni-ulm.de (172.18.1.19)
  by mailserv1.faw.uni-ulm.de with SMTP; 23 Jan 2003 00:29:55 -0000
From: Ralf Corsepius <corsepiu@faw.uni-ulm.de>
To: Autoconf List <autoconf@gnu.org>
Content-Type: text/plain
Organization: FAW Ulm
Message-Id: <1043281766.14516.51.camel@mccallum.corsepiu.faw.uni-ulm.de>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.1 
Date: 23 Jan 2003 01:29:26 +0100
Content-Transfer-Encoding: 7bit
X-Spam: Pruefung durchlaufen
Subject: checking if CC supports weak symbols
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 23 Jan 2003 00:36:52 -0000

Hi,

I am looking for an autoconf macro to check whether the CC in use
supports weak symbols.

More precisely, I am trying to detect whether a c-compiler supports
gcc's "function __attribute__((weak))" syntax or not.

TIA,

	Ralf






From MAILER-DAEMON Thu Jan 23 10:19:11 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bj7O-0003Jt-00
	for mharc-autoconf@gnu.org; Thu, 23 Jan 2003 10:18:14 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bj36-0001Vw-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 10:13:48 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bj2v-0001Qf-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 10:13:38 -0500
Received: from adsl-63-194-211-87.dsl.snfc21.pacbell.net ([63.194.211.87]
	helo=triplerock.olsons.net)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18bj2f-0001EC-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 10:13:21 -0500
Received: (from support@localhost)
	by triplerock.olsons.net (8.11.3/8.11.3) id h0NFD7o96037;
	Thu, 23 Jan 2003 07:13:07 -0800 (PST)
	(envelope-from support)
Date: Thu, 23 Jan 2003 07:13:07 -0800 (PST)
From: Sleepycat support <support@sleepycat.com>
Message-Id: <200301231513.h0NFD7o96037@triplerock.olsons.net>
To: autoconf@gnu.org
In-Reply-To: <200301131511.h0DFBjZ05502@abyssinian.sleepycat.com>
cc: bostic@sleepycat.com
Subject: Re: AH_TEMPLATE feature [#7250]
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 23 Jan 2003 15:18:08 -0000

I wanted to contact you regarding Support Request #7250 that you currently
have open with Sleepycat Software.  I believe we are waiting for additional
information from you before we can proceed on this Support Request, and I
just wanted to make sure that email has not been dropped somewhere and that
you are, instead, waiting on us.

Regards,
Sleepycat Software Support

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 
Sleepycat Software Inc.		support@sleepycat.com
				http://www.sleepycat.com




From MAILER-DAEMON Thu Jan 23 13:41:03 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bmHP-00075f-00
	for mharc-autoconf@gnu.org; Thu, 23 Jan 2003 13:40:47 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bmGS-0006Rq-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 13:39:48 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bmG5-0005kg-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 13:39:28 -0500
Received: from dangermouse.ncsa.uiuc.edu ([141.142.96.46])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18bmEU-0004QL-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 13:37:46 -0500
Received: (from wendling@localhost)
	by dangermouse.ncsa.uiuc.edu (8.11.6/8.11.6) id h0NIbio09830
	for autoconf@gnu.org; Thu, 23 Jan 2003 12:37:44 -0600
Date: Thu, 23 Jan 2003 12:37:44 -0600
From: Bill Wendling <wendling@ncsa.uiuc.edu>
To: autoconf@gnu.org
Message-ID: <20030123183744.GE9569@ncsa.uiuc.edu>
References: <20030122161915.GA17002@ncsa.uiuc.edu>
	<yly95d6k87.fsf@windlord.stanford.edu> <20030122202505.GA17854@ncsa.uiuc.edu>
	<yln0ls3hqx.fsf@windlord.stanford.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <yln0ls3hqx.fsf@windlord.stanford.edu>
User-Agent: Mutt/1.4i
X-PGP-Key: http://www.ncsa.uiuc.edu/~wendling/public_key.asc
X-PGP-Fingerprint: C169 5EB2 2F92 9C34 C9FA  E976 3C24 E3D3 EBE7 C80B
Subject: Re: C99 Compiler Support Determination?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 23 Jan 2003 18:40:45 -0000

Also sprach Russ Allbery:
} Bill Wendling <wendling@ncsa.uiuc.edu> writes:
} 
} > Mostly, I want to check to see if the compiler *isn't* C99 compliant.
} > There's a weird problem I'm having with a non-gcc compiler sucking in
} > header files from gcc but this non-gcc compiler isn't C99 (I don't
} > think), so it produces errors. But only if you include the
} > "-I/usr/include" flag during compilation.
} 
} > It's making me go bald :-)
} 
} Well, GCC isn't C99-compliant either, so I'm not sure that's the check
} that you really want to perform.
} 
Hmm...But it does have some C99 header files (like stdint.h and
inttypes.h, the two culprits in my problem above).

} In general, -I/usr/include is always wrong.  It breaks GCC too.  If you
} can find a way to get rid of that in your build system, that may fix the
} problem.
} 
Oh. I knew that -I/usr/include was essentially redundant, but I didn't
think that it was wrong. It would be easy to get rid of it in that case.
Thanks! :-)

-- 
|| Bill Wendling            "Real Programmers have a Snoopy Calendar
|| wendling@ncsa.uiuc.edu    of '69 hanging on their wall"
|| Coding Simian                       -- Toon Moene



From MAILER-DAEMON Thu Jan 23 13:46:46 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bmMr-0007jG-00
	for mharc-autoconf@gnu.org; Thu, 23 Jan 2003 13:46:25 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bmMY-00077l-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 13:46:06 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bmMO-0006gF-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 13:45:59 -0500
Received: from dangermouse.ncsa.uiuc.edu ([141.142.96.46])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18bmMK-0006VY-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 13:45:53 -0500
Received: (from wendling@localhost)
	by dangermouse.ncsa.uiuc.edu (8.11.6/8.11.6) id h0NIjpU09883
	for autoconf@gnu.org; Thu, 23 Jan 2003 12:45:51 -0600
Date: Thu, 23 Jan 2003 12:45:51 -0600
From: Bill Wendling <wendling@ncsa.uiuc.edu>
To: autoconf@gnu.org
Message-ID: <20030123184551.GA9864@ncsa.uiuc.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-PGP-Key: http://www.ncsa.uiuc.edu/~wendling/public_key.asc
X-PGP-Fingerprint: C169 5EB2 2F92 9C34 C9FA  E976 3C24 E3D3 EBE7 C80B
Subject: AC_HELP_STRING Help
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 23 Jan 2003 18:46:23 -0000

Hi all,

I want to produce a help string like this:

    --with-foo[=DIR]            Use the foo package

(note the []s around the =DIR bit). When I use the option like this:

AC_ARG_WITH([foo],
            [AC_HELP_STRING([--with-foo[=DIR]],
                            [Use the foo package])],,)

It produces:

    --with-foo=DIR            Use the foo package

Is there a way to make it produce the []s that I want?

Thanks.

-- 
|| Bill Wendling            "Real Programmers have a Snoopy Calendar
|| wendling@ncsa.uiuc.edu    of '69 hanging on their wall"
|| Coding Simian                       -- Toon Moene



From MAILER-DAEMON Thu Jan 23 14:34:06 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bn70-0003Fy-00
	for mharc-autoconf@gnu.org; Thu, 23 Jan 2003 14:34:06 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bn6y-0003EC-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 14:34:04 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bn6x-0003Dr-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 14:34:03 -0500
Received: from smtpzilla1.xs4all.nl ([194.109.127.137])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18bn6R-0002sB-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 14:33:31 -0500
Received: from infovore.xs4all.nl (213-84-180-111.adsl.xs4all.nl
	[213.84.180.111])
	by smtpzilla1.xs4all.nl (8.12.0/8.12.0) with ESMTP id h0NJXT5X029961;
	Thu, 23 Jan 2003 20:33:30 +0100 (CET)
Received: from olaf by infovore.xs4all.nl with local (Exim 3.36 #1 (Debian))
	id 18bn6P-0003tn-00; Thu, 23 Jan 2003 20:33:29 +0100
To: Bill Wendling <wendling@ncsa.uiuc.edu>
References: <20030123184551.GA9864@ncsa.uiuc.edu>
From: Olaf Weber <olaf@infovore.xs4all.nl>
Date: 23 Jan 2003 20:33:29 +0100
In-Reply-To: <20030123184551.GA9864@ncsa.uiuc.edu>
Message-ID: <87d6mnmzjq.fsf@infovore.xs4all.nl>
Lines: 26
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Military Intelligence)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: autoconf@gnu.org
Subject: Re: AC_HELP_STRING Help
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 23 Jan 2003 19:34:05 -0000

Bill Wendling writes:

> Hi all,
> I want to produce a help string like this:

>     --with-foo[=DIR]            Use the foo package

> (note the []s around the =DIR bit). When I use the option like this:

> AC_ARG_WITH([foo],
>             [AC_HELP_STRING([--with-foo[=DIR]],
>                             [Use the foo package])],,)

> It produces:

>     --with-foo=DIR            Use the foo package

> Is there a way to make it produce the []s that I want?

I think quadrigraphs should do it: [--with-foo@<:@=DIR@:>@]

-- 
Olaf Weber

               (This space left blank for technical reasons.)




From MAILER-DAEMON Thu Jan 23 14:49:11 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bnLK-0000BS-00
	for mharc-autoconf@gnu.org; Thu, 23 Jan 2003 14:48:54 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bnL3-00082k-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 14:48:37 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bnKr-0007lm-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 14:48:25 -0500
Received: from mail.gmx.net ([213.165.65.60])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18bnKd-0007Sy-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 14:48:11 -0500
Received: (qmail 9604 invoked by uid 0); 23 Jan 2003 19:48:08 -0000
Received: from pD9E83E5E.dip.t-dialin.net (HELO gmx.de) (217.232.62.94)
  by mail.gmx.net (mp004-rz3) with SMTP; 23 Jan 2003 19:48:08 -0000
Message-ID: <3E304779.8000606@gmx.de>
Date: Thu, 23 Jan 2003 20:50:17 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Bill Wendling <wendling@ncsa.uiuc.edu>
References: <20030123184551.GA9864@ncsa.uiuc.edu>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: AC_HELP_STRING Help
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 23 Jan 2003 19:48:52 -0000

Bill Wendling schrieb:
> Hi all,
> 
> I want to produce a help string like this:
> 
>     --with-foo[=DIR]            Use the foo package
> 
> (note the []s around the =DIR bit). When I use the option like this:
> 
> AC_ARG_WITH([foo],
>             [AC_HELP_STRING([--with-foo[=DIR]],
>                             [Use the foo package])],,)
> 
> It produces:
> 
>     --with-foo=DIR            Use the foo package
> 
> Is there a way to make it produce the []s that I want?
> 

Have you been trying double-[[ and triple-[[[ pairings? That is
the normal way to pass literal "[" around and used widely
within m4/autoconf. It is needed for such simple things as
passing sed-char-ranges around (AC_X([sed -e `/[[0-9]].......)




From MAILER-DAEMON Thu Jan 23 14:56:36 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bnQX-0005NH-00
	for mharc-autoconf@gnu.org; Thu, 23 Jan 2003 14:54:17 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bnQ3-0004QN-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 14:53:47 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bnPs-0004GH-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 14:53:40 -0500
Received: from dangermouse.ncsa.uiuc.edu ([141.142.96.46])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18bnPg-0003xl-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 14:53:24 -0500
Received: (from wendling@localhost)
	by dangermouse.ncsa.uiuc.edu (8.11.6/8.11.6) id h0NJqLo10272;
	Thu, 23 Jan 2003 13:52:21 -0600
Date: Thu, 23 Jan 2003 13:52:21 -0600
From: Bill Wendling <wendling@ncsa.uiuc.edu>
To: Olaf Weber <olaf@infovore.xs4all.nl>
Message-ID: <20030123195221.GA10144@ncsa.uiuc.edu>
References: <20030123184551.GA9864@ncsa.uiuc.edu>
	<87d6mnmzjq.fsf@infovore.xs4all.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87d6mnmzjq.fsf@infovore.xs4all.nl>
User-Agent: Mutt/1.4i
X-PGP-Key: http://www.ncsa.uiuc.edu/~wendling/public_key.asc
X-PGP-Fingerprint: C169 5EB2 2F92 9C34 C9FA  E976 3C24 E3D3 EBE7 C80B
cc: autoconf@gnu.org
Subject: Re: AC_HELP_STRING Help
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 23 Jan 2003 19:54:07 -0000

Also sprach Olaf Weber:
} Bill Wendling writes:
} 
} > Hi all,
} > I want to produce a help string like this:
} 
} >     --with-foo[=DIR]            Use the foo package
} 
} > (note the []s around the =DIR bit). When I use the option like this:
} 
} > AC_ARG_WITH([foo],
} >             [AC_HELP_STRING([--with-foo[=DIR]],
} >                             [Use the foo package])],,)
} 
} > It produces:
} 
} >     --with-foo=DIR            Use the foo package
} 
} > Is there a way to make it produce the []s that I want?
} 
} I think quadrigraphs should do it: [--with-foo@<:@=DIR@:>@]
} 
They place the []s in there, but it messes up the spacing :-(. So, I get
things like:

  --with-dmalloc[=DIR]
                          Use dmalloc memory debugging aid [default=no]
  --with-zlib[=DIR] Use GNU zlib compression [default=yes]
  --with-ssl[=LIB]  Use the SSL library [default=no]
  --with-gass[=DIR] Use the GASS library [default=no]
  --with-srb[=DIR]  Use the SRB Library [default=no]
  --with-pthread[=DIR]
                          Use the Pthreads library [default=no]


-- 
|| Bill Wendling            "Real Programmers have a Snoopy Calendar
|| wendling@ncsa.uiuc.edu    of '69 hanging on their wall"
|| Coding Simian                       -- Toon Moene



From MAILER-DAEMON Thu Jan 23 14:58:14 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bnUH-0001GA-00
	for mharc-autoconf@gnu.org; Thu, 23 Jan 2003 14:58:09 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bnTo-0000DH-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 14:57:40 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bnTi-0008U1-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 14:57:35 -0500
Received: from dangermouse.ncsa.uiuc.edu ([141.142.96.46])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18bnTF-00083g-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 14:57:05 -0500
Received: (from wendling@localhost)
	by dangermouse.ncsa.uiuc.edu (8.11.6/8.11.6) id h0NJv0610487;
	Thu, 23 Jan 2003 13:57:00 -0600
Date: Thu, 23 Jan 2003 13:57:00 -0600
From: Bill Wendling <wendling@ncsa.uiuc.edu>
To: Guido Draheim <guidod-2003-@gmx.de>
Message-ID: <20030123195700.GB10144@ncsa.uiuc.edu>
References: <20030123184551.GA9864@ncsa.uiuc.edu> <3E304779.8000606@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3E304779.8000606@gmx.de>
User-Agent: Mutt/1.4i
X-PGP-Key: http://www.ncsa.uiuc.edu/~wendling/public_key.asc
X-PGP-Fingerprint: C169 5EB2 2F92 9C34 C9FA  E976 3C24 E3D3 EBE7 C80B
cc: autoconf@gnu.org
Subject: Re: AC_HELP_STRING Help
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 23 Jan 2003 19:58:02 -0000

Also sprach Guido Draheim:
} Bill Wendling schrieb:
} >Hi all,
} >
} >I want to produce a help string like this:
} >
} >    --with-foo[=DIR]            Use the foo package
} >
} >(note the []s around the =DIR bit). When I use the option like this:
} >
} >AC_ARG_WITH([foo],
} >            [AC_HELP_STRING([--with-foo[=DIR]],
} >                            [Use the foo package])],,)
} >
} >It produces:
} >
} >    --with-foo=DIR            Use the foo package
} >
} >Is there a way to make it produce the []s that I want?
} >
} 
} Have you been trying double-[[ and triple-[[[ pairings? That is
} the normal way to pass literal "[" around and used widely
} within m4/autoconf. It is needed for such simple things as
} passing sed-char-ranges around (AC_X([sed -e `/[[0-9]].......)
} 
} 
It doesn't seem to work either. Here's what I get:

  --with-dmalloc=DIR  Use dmalloc memory debugging aid [default=no]
  --with-zlib=DIR     Use GNU zlib compression [default=yes]
  --with-ssl=LIB      Use the SSL library [default=no]
  --with-gass=DIR     Use the GASS library [default=no]
  --with-srb=DIR      Use the SRB Library [default=no]
  --with-pthread=DIR  Use the Pthreads library [default=no]

You can't see it, but the spacing is off in there. (The descriptions are
too close to the --with-* flags). The same thing happens if I use [[[.

I should mention that I'm using 2.53, so this may be a known deficiency
or something...not sure.

-- 
|| Bill Wendling            "Real Programmers have a Snoopy Calendar
|| wendling@ncsa.uiuc.edu    of '69 hanging on their wall"
|| Coding Simian                       -- Toon Moene



From MAILER-DAEMON Thu Jan 23 15:06:47 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bnag-00040K-00
	for mharc-autoconf@gnu.org; Thu, 23 Jan 2003 15:04:46 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bnW6-0002Jd-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 15:00:02 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bnUK-0001Lu-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 14:58:17 -0500
Received: from lutetium.btinternet.com ([194.73.73.116])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18bnUJ-0001GP-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 14:58:11 -0500
Received: from host213-1-63-189.in-addr.btopenworld.com ([213.1.63.189]
	helo=whinlatter.uklinux.net)
	by lutetium.btinternet.com with esmtp (Exim 3.22 #16)
	id 18bnU4-0007Nl-00; Thu, 23 Jan 2003 19:57:56 +0000
Received: from roger by whinlatter.uklinux.net with local (Exim 3.35 #1
	(Debian))	id 18bnUx-00029S-00; Thu, 23 Jan 2003 19:58:51 +0000
To: Bill Wendling <wendling@ncsa.uiuc.edu>
References: <20030123184551.GA9864@ncsa.uiuc.edu>
From: Roger Leigh <roger@whinlatter.uklinux.net>
Date: 23 Jan 2003 19:58:51 +0000
In-Reply-To: <20030123184551.GA9864@ncsa.uiuc.edu>
Message-ID: <878yxbr62s.fsf@whinlatter.uklinux.net>
Lines: 29
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: autoconf@gnu.org
Subject: Re: AC_HELP_STRING Help
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 23 Jan 2003 20:04:37 -0000

Bill Wendling <wendling@ncsa.uiuc.edu> writes:

> I want to produce a help string like this:
> 
>     --with-foo[=DIR]            Use the foo package
> 
> (note the []s around the =DIR bit). When I use the option like this:
> 
> AC_ARG_WITH([foo],
>             [AC_HELP_STRING([--with-foo[=DIR]],
>                             [Use the foo package])],,)
> 
> It produces:
> 
>     --with-foo=DIR            Use the foo package
> 
> Is there a way to make it produce the []s that I want?

I've used quadrigraphs in the past, but AC_HELP_STRING is doing
something wierd with the quoting (I've tried changing the quotes,
extra quoting, etc., but without success).  When I have managed to get
`[' and `]' to appear, the formatting is then broken...


-- 
Roger Leigh

                Printing on GNU/Linux?  http://gimp-print.sourceforge.net/
                GPG Public Key: 0x25BFB848 available on public keyservers



From MAILER-DAEMON Thu Jan 23 15:26:07 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bnuy-0007Ku-00
	for mharc-autoconf@gnu.org; Thu, 23 Jan 2003 15:25:44 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bnub-0006rs-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 15:25:21 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bnu3-000625-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 15:25:01 -0500
Received: from mail.gmx.de ([213.165.65.60] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18bntw-0005g3-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 15:24:40 -0500
Received: (qmail 2575 invoked by uid 0); 23 Jan 2003 20:24:39 -0000
Received: from pD9E83E5E.dip.t-dialin.net (HELO gmx.de) (217.232.62.94)
  by mail.gmx.net (mp009-rz3) with SMTP; 23 Jan 2003 20:24:39 -0000
Message-ID: <3E305007.4030905@gmx.de>
Date: Thu, 23 Jan 2003 21:26:47 +0100
From: Guido Draheim <guidod-2003-@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
X-Accept-Language: de-at, de, en-us, en
MIME-Version: 1.0
To: Roger Leigh <roger@whinlatter.uklinux.net>
References: <20030123184551.GA9864@ncsa.uiuc.edu>
	<878yxbr62s.fsf@whinlatter.uklinux.net>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
cc: Bill Wendling <wendling@ncsa.uiuc.edu>
Subject: Re: AC_HELP_STRING Help
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 23 Jan 2003 20:25:43 -0000

Roger Leigh schrieb:
> Bill Wendling <wendling@ncsa.uiuc.edu> writes:
> 
> 
>>I want to produce a help string like this:
>>
>>    --with-foo[=DIR]            Use the foo package
>>
>>(note the []s around the =DIR bit). When I use the option like this:
>>
>>AC_ARG_WITH([foo],
>>            [AC_HELP_STRING([--with-foo[=DIR]],
>>                            [Use the foo package])],,)
>>
>>It produces:
>>
>>    --with-foo=DIR            Use the foo package
>>
>>Is there a way to make it produce the []s that I want?
> 
> 
> I've used quadrigraphs in the past, but AC_HELP_STRING is doing
> something wierd with the quoting (I've tried changing the quotes,
> extra quoting, etc., but without success).  When I have managed to get
> `[' and `]' to appear, the formatting is then broken...
> 

exactly! I did just have a look into some of my projects and noticed
that every of those --with-off[=DIR] was done without AC_HELP_STRING.
I had just trying various combinations in the last hour, and it
seems that the "[" are counted for the length of the first argument
but they will not be printed - here is an example where I did only
try to change the first _WITH to use AC_HELP_STRING:

Optional Packages:
   --with-PACKAGE[=ARG]    use PACKAGE [ARG=yes]
   --without-PACKAGE       do not use PACKAGE (same as --with-PACKAGE=no)
   --with-gnu-ld           assume the C compiler uses GNU ld default=no
   --with-pic              try to use only PIC/non-PIC objects default=use both
   --with-pcre=prefix  compile xmlpcre part (via libpcre check)
   --with-pfe[=prefix]    scan pfe documentation (the C files)

That's actually quite weird - so the ac_help_string macro will count
the chars of the argument literal in full glory but the [] brackets get
interpreted as m4 quotations later - after the indent computations. hmmm.

(using 2.52...)




From MAILER-DAEMON Thu Jan 23 17:51:12 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bq5b-0004em-00
	for mharc-autoconf@gnu.org; Thu, 23 Jan 2003 17:44:51 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bq4z-0003Yc-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 17:44:13 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bq4u-0003Js-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 17:44:09 -0500
Received: from duck.doc.ic.ac.uk ([146.169.1.46])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18bq4e-0002us-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 17:43:52 -0500
Received: from kungfu.doc.ic.ac.uk ([146.169.6.1] ident=pgw99)
	by duck.doc.ic.ac.uk with esmtp (Exim 3.16 #7)
	id 18bq4c-0004wm-00; Thu, 23 Jan 2003 22:43:50 +0000
Date: Thu, 23 Jan 2003 22:43:50 +0000 (GMT)
From: Philip Willoughby <pgw99@doc.ic.ac.uk>
To: Guido Draheim <guidod-2003-@gmx.de>
In-Reply-To: <3E305007.4030905@gmx.de>
Message-ID: <Pine.LNX.4.50.0301232237260.31745-100000@kungfu.doc.ic.ac.uk>
References: <20030123184551.GA9864@ncsa.uiuc.edu>
	<878yxbr62s.fsf@whinlatter.uklinux.net> <3E305007.4030905@gmx.de>
X-hidden-message: Nothing to see here
X-beer: Tetley's Extra Smooth (With Floating Widget)
X-icq-number: 53659369
X-quote: I reserve the right to drink free beer.
X-Skanky: http://www.amazon.co.uk/exec/obidos/wishlist/3DBR2FB2SNEQ/ref=wl_em_to
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Bill Wendling <wendling@ncsa.uiuc.edu>
cc: autoconf@gnu.org
cc: Roger Leigh <roger@whinlatter.uklinux.net>
Subject: Re: AC_HELP_STRING Help
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 23 Jan 2003 22:44:43 -0000

Hi,

Today, Guido Draheim wrote:

>That's actually quite weird - so the ac_help_string macro will count
>the chars of the argument literal in full glory but the [] brackets get
>interpreted as m4 quotations later - after the indent computations. hmmm.

2.57 has the same problem.

A small amount of mining leads me to believe that the problem is in the
m4_text_wrap macro which is a part of m4sugar.  Could someone who knows
what they're doing have a look at this?

My random-hunch-generator thinks that adding m4_quote around the only place
it mentions [$3] ought to fix it -- can someone with no irate users likely
to hit them try this out please?

Regards,

Philip Willoughby

Systems Programmer, Department of Computing, Imperial College, London, UK
-- 
echo bzidd@nfo.ho.co.se | tr "bizndfohces" "pwgd9ociaku"

Why reinvent the wheel? . . . . . . . . . Because we can make it rounder...



From MAILER-DAEMON Thu Jan 23 18:43:26 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18br0I-0002EG-00
	for mharc-autoconf@gnu.org; Thu, 23 Jan 2003 18:43:26 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18br0F-0002CL-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 18:43:23 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18br0E-0002Br-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 18:43:23 -0500
Received: from imap.gmx.net ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18br0E-0002BV-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 18:43:22 -0500
Received: (qmail 14510 invoked by uid 0); 23 Jan 2003 23:43:21 -0000
Received: from pD902F08A.dip0.t-ipconnect.de (217.2.240.138)
  by mail.gmx.net (mp017-rz3) with SMTP; 23 Jan 2003 23:43:21 -0000
Date: Fri, 24 Jan 2003 00:53:32 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
X-X-Sender: peter@localhost.localdomain
To: Ralf Corsepius <corsepiu@faw.uni-ulm.de>
In-Reply-To: <1043281766.14516.51.camel@mccallum.corsepiu.faw.uni-ulm.de>
Message-ID: <Pine.LNX.4.44.0301240052290.789-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Autoconf List <autoconf@gnu.org>
Subject: Re: checking if CC supports weak symbols
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 23 Jan 2003 23:43:24 -0000

Ralf Corsepius writes:

> More precisely, I am trying to detect whether a c-compiler supports
> gcc's "function __attribute__((weak))" syntax or not.

Is there any reason to think that compilers other than GCC support this
syntax?

-- 
Peter Eisentraut   peter_e@gmx.net




From MAILER-DAEMON Thu Jan 23 18:44:56 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18br1f-0003BC-00
	for mharc-autoconf@gnu.org; Thu, 23 Jan 2003 18:44:51 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18br0i-0002UC-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 18:43:52 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bqys-0001h5-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 18:41:59 -0500
Received: from pop.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18bqyr-0001fp-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 18:41:57 -0500
Received: (qmail 13214 invoked by uid 0); 23 Jan 2003 23:41:54 -0000
Received: from pD902F08A.dip0.t-ipconnect.de (217.2.240.138)
  by mail.gmx.net (mp012-rz3) with SMTP; 23 Jan 2003 23:41:54 -0000
Date: Fri, 24 Jan 2003 00:51:48 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
X-X-Sender: peter@localhost.localdomain
To: Bill Wendling <wendling@ncsa.uiuc.edu>
In-Reply-To: <20030123184551.GA9864@ncsa.uiuc.edu>
Message-ID: <Pine.LNX.4.44.0301240050370.789-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: autoconf@gnu.org
Subject: Re: AC_HELP_STRING Help
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 23 Jan 2003 23:44:47 -0000

Bill Wendling writes:

> I want to produce a help string like this:
>     --with-foo[=DIR]            Use the foo package
> (note the []s around the =DIR bit). When I use the option like this:
> AC_ARG_WITH([foo],
>             [AC_HELP_STRING([--with-foo[=DIR]],
>                             [Use the foo package])],,)
> It produces:
>     --with-foo=DIR            Use the foo package
> Is there a way to make it produce the []s that I want?

Not with AC_HELP_STRING.  It can't handle that case and there's no
(obvious?, reasonable?) way to fix this.  It has been mentioned before;
search the archives if you're interested.

-- 
Peter Eisentraut   peter_e@gmx.net




From MAILER-DAEMON Thu Jan 23 22:03:20 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18bu7j-0004Uc-00
	for mharc-autoconf@gnu.org; Thu, 23 Jan 2003 22:03:19 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18bu7h-0004UG-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 22:03:17 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18bu7e-0004M6-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 22:03:15 -0500
Received: from parcival.faw.uni-ulm.de ([134.60.100.20]
	helo=gawain.faw.uni-ulm.de)
	by monty-python.gnu.org with smtp (Exim 4.10.13)	id 18bu7e-00043m-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 22:03:14 -0500
Received: (qmail 21912 invoked from network); 24 Jan 2003 02:56:51 -0000
Received: from dialin36.faw.uni-ulm.de (172.18.1.36)
  by mailserv1.faw.uni-ulm.de with SMTP; 24 Jan 2003 02:56:49 -0000
From: Ralf Corsepius <corsepiu@faw.uni-ulm.de>
To: Peter Eisentraut <peter_e@gmx.net>
In-Reply-To: <Pine.LNX.4.44.0301240052290.789-100000@localhost.localdomain>
References: <Pine.LNX.4.44.0301240052290.789-100000@localhost.localdomain>
Content-Type: text/plain
Organization: FAW Ulm
Message-Id: <1043376986.14495.1378.camel@mccallum.corsepiu.faw.uni-ulm.de>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.1 
Date: 24 Jan 2003 03:56:26 +0100
Content-Transfer-Encoding: 7bit
X-Spam: Pruefung durchlaufen
cc: Autoconf List <autoconf@gnu.org>
Subject: Re: checking if CC supports weak symbols
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 24 Jan 2003 03:03:18 -0000

On Fri, 2003-01-24 at 00:53, Peter Eisentraut wrote:
> Ralf Corsepius writes:
> 
> > More precisely, I am trying to detect whether a c-compiler supports
> > gcc's "function __attribute__((weak))" syntax or not.
> 
> Is there any reason to think that compilers other than GCC support this
> syntax?
Well, that's one of the aspects I wanted to find out. I suspect this
particular syntax to be specific to gcc, but I would expect other
compilers to support "weak symbols", too. (How about Intel's icc?)


For the moment, this is what I am using:

AC_CACHE_CHECK([whether $CC supports function __attribute__((weak))],
[ac_cv_gcc_attribute_weak],[
AS_IF([test $GCC = yes],[
  save_CFLAGS=$CFLAGS
  CFLAGS=-Werror
  AC_COMPILE_IFELSE([
    AC_LANG_PROGRAM(
    [void myfunc(char c) __attribute__ ((weak));
     void myfunc(char c) {}],
    [])],
    [ac_cv_gcc_attribute_weak=yes],
    [ac_cv_gcc_attribute_weak=no])
  CFLAGS=$save_CFLAGS
],[
  ac_cv_gcc_attribute_weak=no])
])

However, there are several aspects I don't like about this check:
* It is strictly tied to gcc.
* It evaluates a warning from gcc(gcc issues warnings if it doesn't
support this syntax)

May-be this less restrictive variant would be better:

AC_CACHE_CHECK([whether $CC accepts function __attribute__((weak))],
[ac_cv_cc_attribute_weak],[
  AS_IF([test $GCC = yes],[
    save_CFLAGS=$CFLAGS
    CFLAGS=-Werror])

  AC_COMPILE_IFELSE([
    AC_LANG_PROGRAM(
    [void myfunc(char c) __attribute__ ((weak));
     void myfunc(char c) {}],
    [])],
    [ac_cv_cc_attribute_weak=yes],
    [ac_cv_cc_attribute_weak=no])

  AS_IF([test $GCC = yes],[
    CFLAGS=$save_CFLAGS])
])

Actually, I would prefer a check to find out whether a
compiler/toolchain supports weak symbols and if necessary, to let it
find the syntax this compiler requires. (IIRC, some older gcc's used
#pragma weak)

Ralf





From MAILER-DAEMON Thu Jan 23 22:17:45 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18buK8-0002Fh-00
	for mharc-autoconf@gnu.org; Thu, 23 Jan 2003 22:16:08 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18buJo-0001bS-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 22:15:48 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18buJj-0001Qo-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 22:15:44 -0500
Received: from mail.cs.umn.edu ([128.101.33.102])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18buJf-0001Fb-00
	for autoconf@gnu.org; Thu, 23 Jan 2003 22:15:39 -0500
Received: from bose.cs.umn.edu (bose.cs.umn.edu [128.101.35.195])
	by mail.cs.umn.edu (Postfix) with ESMTP
	id 6D4F011376; Thu, 23 Jan 2003 21:15:38 -0600 (CST)
Received: by bose.cs.umn.edu (Postfix, from userid 818)
	id 824BA31FE; Thu, 23 Jan 2003 21:15:37 -0600 (CST)
To: Peter Eisentraut <peter_e@gmx.net>
From: Raja R Harinath <harinath@cs.umn.edu>
Date: Thu, 23 Jan 2003 21:15:37 -0600
In-Reply-To: <Pine.LNX.4.44.0301240052290.789-100000@localhost.localdomain>
	(Peter
	Eisentraut's message of "Fri, 24 Jan 2003 00:53:32 +0100 (CET)")
Message-ID: <d9smvjck6e.fsf@bose.cs.umn.edu>
User-Agent: Gnus/5.090014 (Oort Gnus v0.14) Emacs/21.3.50
 (i686-pc-linux-gnu)
References: <Pine.LNX.4.44.0301240052290.789-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: Autoconf List <autoconf@gnu.org>
cc: Ralf Corsepius <corsepiu@faw.uni-ulm.de>
Subject: Re: checking if CC supports weak symbols
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 24 Jan 2003 03:16:05 -0000

Hi,

Peter Eisentraut <peter_e@gmx.net> writes:

> Ralf Corsepius writes:
>
>> More precisely, I am trying to detect whether a c-compiler supports
>> gcc's "function __attribute__((weak))" syntax or not.
>
> Is there any reason to think that compilers other than GCC support this
> syntax?

I'm not Ralf, but I can see two different reasons:

  * not all versions may support the "weak" attribute

  * The Intel C compiler for Linux is supposed to be able to compile
    the Linux kernel.  New versions the Linux kernel do use weak
    symbols (possibly with this syntax) -- so maybe the Intel
    compiler would too.

The second is somewhat far-fetched.  Support for #pragma weak ... and
_Pragma("weak", ...) is likelier.

- Hari
-- 
Raja R Harinath ------------------------------ harinath@cs.umn.edu



From MAILER-DAEMON Fri Jan 24 08:24:15 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18c3l6-0004TY-00
	for mharc-autoconf@gnu.org; Fri, 24 Jan 2003 08:20:36 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18c3kl-0003oY-00
	for autoconf@gnu.org; Fri, 24 Jan 2003 08:20:15 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18c3jW-0002Yq-00
	for autoconf@gnu.org; Fri, 24 Jan 2003 08:19:01 -0500
Received: from [196.25.143.130] (helo=penguin.wetton.prism.co.za)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18c3jM-0002R7-00
	for autoconf@gnu.org; Fri, 24 Jan 2003 08:18:49 -0500
Received: (from berndj@localhost)
	by penguin.wetton.prism.co.za (8.9.3/8.9.3) id PAA29568;
	Fri, 24 Jan 2003 15:19:17 +0200
Date: Fri, 24 Jan 2003 15:19:17 +0200
From: Bernd Jendrissek <berndj@prism.co.za>
To: Bill Wendling <wendling@ncsa.uiuc.edu>
Message-ID: <20030124151917.R9237@prism.co.za>
References: <20030123184551.GA9864@ncsa.uiuc.edu> <3E304779.8000606@gmx.de>
	<20030123195700.GB10144@ncsa.uiuc.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3us
In-Reply-To: <20030123195700.GB10144@ncsa.uiuc.edu>
cc: autoconf@gnu.org
Subject: Re: AC_HELP_STRING Help
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 24 Jan 2003 13:20:29 -0000

On Thu, Jan 23, 2003 at 01:57:00PM -0600, Bill Wendling wrote:
> Also sprach Guido Draheim:
> } Bill Wendling schrieb:
> } >I want to produce a help string like this:
> } >
> } >    --with-foo[=DIR]            Use the foo package
> } >
> } >(note the []s around the =DIR bit). When I use the option like this:

[snip]

> I should mention that I'm using 2.53, so this may be a known deficiency
> or something...not sure.

I'm using 2.54 ATM, and I did notice that I now need considerably fewer
['s and ]'s to make them appear.  I recall having to write something crazy
like [[[[[default=/foo]]]]] up to 2.53 or so.

AC_ARG_ENABLE(dvchome,
              AC_HELP_STRING([--enable-dvchome=DIR],
                             [specify home directory of user dvc [[default=/home/dvc]]]),
              DVCHOME=$enableval,
              DVCHOME=/home/dvc)

Aargh, I guess I'll have to read up on the proper quoting rules some day...

-- 
berndfoobar@users.sourceforge.net is probably better to bookmark than any
employer-specific email address I may have appearing in the headers.
  Vanity page: http://www.tsct.co.za/~berndj/



From MAILER-DAEMON Fri Jan 24 09:35:32 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18c4tS-0004ij-00
	for mharc-autoconf@gnu.org; Fri, 24 Jan 2003 09:33:18 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18c4tM-0004dP-00
	for autoconf@gnu.org; Fri, 24 Jan 2003 09:33:12 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18c4sv-0004NN-00
	for autoconf@gnu.org; Fri, 24 Jan 2003 09:32:48 -0500
Received: from ns.suse.de ([213.95.15.193] helo=Cantor.suse.de)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18c4sb-0003Kr-00
	for autoconf@gnu.org; Fri, 24 Jan 2003 09:32:25 -0500
Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136])
	by Cantor.suse.de (Postfix) with ESMTP
	id 27FC21471C; Fri, 24 Jan 2003 15:32:23 +0100 (MET)
To: Raja R Harinath <harinath@cs.umn.edu>
X-Yow: If Robert Di Niro assassinates Walter Slezak, will
 Jodie Foster marry Bonzo??
From: Andreas Schwab <schwab@suse.de>
Date: Fri, 24 Jan 2003 15:32:21 +0100
In-Reply-To: <d9smvjck6e.fsf@bose.cs.umn.edu> (Raja R Harinath's message of
 "Thu, 23 Jan 2003 21:15:37 -0600")
Message-ID: <jelm1apqiy.fsf@sykes.suse.de>
User-Agent: Gnus/5.090013 (Oort Gnus v0.13) Emacs/21.3.50 (ia64-suse-linux)
References: <Pine.LNX.4.44.0301240052290.789-100000@localhost.localdomain>
	<d9smvjck6e.fsf@bose.cs.umn.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
cc: Autoconf List <autoconf@gnu.org>
cc: Peter Eisentraut <peter_e@gmx.net>
cc: Ralf Corsepius <corsepiu@faw.uni-ulm.de>
Subject: Re: checking if CC supports weak symbols
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 24 Jan 2003 14:33:17 -0000

Raja R Harinath <harinath@cs.umn.edu> writes:

|> Hi,
|> 
|> Peter Eisentraut <peter_e@gmx.net> writes:
|> 
|> > Ralf Corsepius writes:
|> >
|> >> More precisely, I am trying to detect whether a c-compiler supports
|> >> gcc's "function __attribute__((weak))" syntax or not.
|> >
|> > Is there any reason to think that compilers other than GCC support this
|> > syntax?
|> 
|> I'm not Ralf, but I can see two different reasons:
|> 
|>   * not all versions may support the "weak" attribute
|> 
|>   * The Intel C compiler for Linux is supposed to be able to compile
|>     the Linux kernel.  New versions the Linux kernel do use weak
|>     symbols (possibly with this syntax) -- so maybe the Intel
|>     compiler would too.
|> 
|> The second is somewhat far-fetched.  Support for #pragma weak ... and
|> _Pragma("weak", ...) is likelier.

The Linux kernel source already uses __attribute__ in other contexts, so
icc needs to grok the syntax anyway.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 N�rnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



From MAILER-DAEMON Fri Jan 24 12:41:25 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18c7oh-0000mw-00
	for mharc-autoconf@gnu.org; Fri, 24 Jan 2003 12:40:35 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18c7nx-0008UB-00
	for autoconf@gnu.org; Fri, 24 Jan 2003 12:39:49 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18c7j4-0005uo-00
	for autoconf@gnu.org; Fri, 24 Jan 2003 12:34:47 -0500
Received: from mail.cs.umn.edu ([128.101.32.202])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18c7j0-0005qk-00
	for autoconf@gnu.org; Fri, 24 Jan 2003 12:34:42 -0500
Received: from bose.cs.umn.edu (bose.cs.umn.edu [128.101.35.195])
	by mail.cs.umn.edu (Postfix) with ESMTP
	id 788F811346; Fri, 24 Jan 2003 11:34:42 -0600 (CST)
Received: by bose.cs.umn.edu (Postfix, from userid 818)
	id 11DD73202; Fri, 24 Jan 2003 11:34:41 -0600 (CST)
To: Andreas Schwab <schwab@suse.de>
From: Raja R Harinath <harinath@cs.umn.edu>
Date: Fri, 24 Jan 2003 11:34:41 -0600
In-Reply-To: <jelm1apqiy.fsf@sykes.suse.de> (Andreas Schwab's message of
 "Fri, 24 Jan 2003 15:32:21 +0100")
Message-ID: <d9r8b2ladq.fsf@bose.cs.umn.edu>
User-Agent: Gnus/5.090014 (Oort Gnus v0.14) Emacs/21.3.50
 (i686-pc-linux-gnu)
References: <Pine.LNX.4.44.0301240052290.789-100000@localhost.localdomain>
	<d9smvjck6e.fsf@bose.cs.umn.edu> <jelm1apqiy.fsf@sykes.suse.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: Autoconf List <autoconf@gnu.org>
cc: Peter Eisentraut <peter_e@gmx.net>
cc: Ralf Corsepius <corsepiu@faw.uni-ulm.de>
Subject: Re: checking if CC supports weak symbols
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 24 Jan 2003 17:40:32 -0000

Hi,

Andreas Schwab <schwab@suse.de> writes:

> Raja R Harinath <harinath@cs.umn.edu> writes:
[snip]
> |>   * The Intel C compiler for Linux is supposed to be able to compile
> |>     the Linux kernel.  New versions the Linux kernel do use weak
> |>     symbols (possibly with this syntax) -- so maybe the Intel
> |>     compiler would too.
> |> 
> |> The second is somewhat far-fetched.  Support for #pragma weak ... and
> |> _Pragma("weak", ...) is likelier.
>
> The Linux kernel source already uses __attribute__ in other contexts, so
> icc needs to grok the syntax anyway.

Yep.  But, the Linux kernel started using attribute ((weak, ...))
only recently.  So, icc may not do anything useful there.

- Hari
-- 
Raja R Harinath ------------------------------ harinath@cs.umn.edu



From MAILER-DAEMON Sun Jan 26 14:44:22 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18csX9-0002o9-00
	for mharc-autoconf@gnu.org; Sun, 26 Jan 2003 14:33:35 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18csWe-0002QU-00
	for autoconf@gnu.org; Sun, 26 Jan 2003 14:33:04 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18csVs-0001sW-00
	for autoconf@gnu.org; Sun, 26 Jan 2003 14:32:33 -0500
Received: from mtl.mit.edu ([18.62.0.45])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18csVN-0001UO-00
	for autoconf@gnu.org; Sun, 26 Jan 2003 14:31:46 -0500
Received: from bitter.mit.edu (BITTER.MIT.EDU [18.62.6.13])
	by mtl.mit.edu (8.9.3/8.9.3) with SMTP id OAA14716
	for <autoconf@gnu.org>; Sun, 26 Jan 2003 14:31:15 -0500 (EST)
Date: Sun, 26 Jan 2003 14:31:15 -0500 (EST)
From: mcmahill@mtl.mit.edu
X-Sender: mcmahill@bitter.mit.edu
To: autoconf@gnu.org
In-Reply-To: <Pine.SOL.3.96.1020713000844.19167B-100000@bitter.mit.edu>
Message-ID: <Pine.SOL.3.96.1030126142921.16188A-100000@bitter.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: how to get -R path set for X11?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: mcmahill@mtl.mit.edu
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 26 Jan 2003 19:33:19 -0000


whats the correct way to have autoconf add the -Wl.-R/usr/X11R6/lib stuff
thats needed?  I've tried AC_PATH_XTRA which gives me the
-I/usr/X11R6/include for compiling and -L/usr/X11R6/lib for linking, but I
don't get the -Wl,-R/usr/X11R6/lib part which I need so that the program
can find the X libraries at run time.

Thanks
-Dan





From MAILER-DAEMON Mon Jan 27 01:13:32 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18d2WB-0000q2-00
	for mharc-autoconf@gnu.org; Mon, 27 Jan 2003 01:13:15 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18d2Vp-0000kL-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 01:12:53 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18d2Up-0000aD-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 01:12:17 -0500
Received: from b.smtp-out.sonic.net ([208.201.224.39])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18d2US-0000VD-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 01:11:28 -0500
Received: (qmail 18512 invoked from network); 27 Jan 2003 06:11:01 -0000
Received: from turbo.sonic.net (208.201.224.26)
  by b.smtp-out.sonic.net with SMTP; 27 Jan 2003 06:11:01 -0000
Received: from thune.mrc-home.org (adsl-209-204-178-126.sonic.net
	[209.204.178.126])
	by turbo.sonic.net (8.11.6/8.8.5) with ESMTP id h0R6B1f32196
	for <autoconf@gnu.org>; Sun, 26 Jan 2003 22:11:01 -0800
X-envelope-info: <dalgoda@ix.netcom.com>
Received: by thune.mrc-home.org (8.11.4) id h0R6B1818877;
	Sun, 26 Jan 2003 22:11:01 -0800
Newsgroups: local.ml.gnu.autoconf
From: dalgoda@ix.netcom.com (Mike Castle)
Organization: House of Linux
X-Newsreader: trn 4.0-test76 (Apr 2, 2001)
Path: not-for-mail
Originator: nexus@thune.mrc.org (Mike Castle)
Date: Sun, 26 Jan 2003 22:11:00 -0800
Message-ID: <k4vegxpdi.ln2@thune.mrc-home.org>
To: autoconf@gnu.org
Subject: autoscan and AC_CHECK_DECLS
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 27 Jan 2003 06:13:03 -0000


Ok.  Strange interactions with autoscan and autom4te.cache.  And a possible
bug in autoscan otherwise.

Starting in a clean directory:

nexus@thune[10:06pm]~/foo(203) ls
nexus@thune[10:06pm]~/foo(204) echo "int sys_siglist;" > a.c
nexus@thune[10:06pm]~/foo(205) echo "int st_blksize;" >> a.c
nexus@thune[10:06pm]~/foo(206) touch configure.ac
nexus@thune[10:06pm]~/foo(207) autoscan
configure.ac: warning: missing AC_CHECK_DECLS([sys_siglist]) wanted by: a.c:1
configure.ac: warning: missing AC_CHECK_MEMBERS([struct stat.st_blksize]) wanted by: a.c:2
configure.ac: warning: missing AC_PREREQ wanted by: autoscan
configure.ac: warning: missing AC_PROG_CC wanted by: a.c
4.820u 0.380s 0:05.22 99.6%     0+0k 0+0io 1909pf+0w
nexus@thune[10:06pm]~/foo(208) mv -f configure.scan configure.ac
nexus@thune[10:07pm]~/foo(209) autoscan
configure.ac: warning: missing AC_CHECK_DECLS([sys_siglist]) wanted by: a.c:1
configure.ac: warning: missing AC_CHECK_MEMBERS([struct stat.st_blksize]) wanted by: a.c:2
configure.ac: warning: missing AC_PREREQ wanted by: autoscan
configure.ac: warning: missing AC_PROG_CC wanted by: a.c
4.810u 0.350s 0:05.19 99.4%     0+0k 0+0io 1797pf+0w
nexus@thune[10:07pm]~/foo(210) rm -rf autom4te.cache/
nexus@thune[10:07pm]~/foo(211) autoscan
configure.ac: warning: missing AC_CHECK_DECLS([sys_siglist]) wanted by: a.c:1
9.630u 0.420s 0:10.12 99.3%     0+0k 0+0io 1937pf+0w
nexus@thune[10:07pm]~/foo(213) grep siglist configure.ac
AC_CHECK_DECLS([sys_siglist])
nexus@thune[10:07pm]~/foo(215) autoscan -V
autoscan (GNU Autoconf) 2.57
Written by David J. MacKenzie and Akim Demaille.



So, why different results after nuking autom4te.cache?  Also, why is it
bitching about sys_siglist?

Thanks,
mrc
-- 
     Mike Castle      dalgoda@ix.netcom.com      www.netcom.com/~dalgoda/
    We are all of us living in the shadow of Manhattan.  -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc



From MAILER-DAEMON Mon Jan 27 05:26:05 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18d6MU-0006ED-00
	for mharc-autoconf@gnu.org; Mon, 27 Jan 2003 05:19:30 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18d6Lj-0005wH-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 05:18:43 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18d6Kv-0005h2-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 05:18:09 -0500
Received: from imo-d02.mx.aol.com ([205.188.157.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18d6KQ-0005Nu-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 05:17:22 -0500
Received: from JG8949@aol.com
	by imo-d02.mx.aol.com (mail_out_v34.13.) id 7.12a.21280273 (15886)
	 for <autoconf@gnu.org>; Mon, 27 Jan 2003 05:16:22 -0500 (EST)
Received: from  aol.com (mow-d18.webmail.aol.com [205.188.139.134]) by
	air-id08.mx.aol.com (v90.10) with ESMTP id MAILINID81-0127051622; Mon, 27 Jan
	2003 05:16:22 -0500
Date: Mon, 27 Jan 2003 05:16:22 -0500
From: JG8949@aol.com
To: autoconf@gnu.org
MIME-Version: 1.0
Message-ID: <05AC2ECD.751F8533.000456CF@aol.com>
X-Mailer: Atlas Mailer 2.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Subject: How to Setup Autoconf?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 27 Jan 2003 10:18:58 -0000

HELP!!!

well that's a good way to start the mail :D. I'm trying to compile apache 2.0. i need autoconf to make the configuration file. (I've never done this b4 so don't be surprised by the incomptence of the questions hehe). I have Borlands C++ text line compiler and autoconf 2.57.

How do i use autoconf??? howdo i setup autoconf, does it need compiling first??? what is a cpp file??? why haven't i got any cpp files in the autoconf download??? what other inane questions can i come up with???

Any comments greatly appreciated

Thanks

james



From MAILER-DAEMON Mon Jan 27 05:29:52 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18d6WE-0008TQ-00
	for mharc-autoconf@gnu.org; Mon, 27 Jan 2003 05:29:34 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18d6Vh-0008FM-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 05:29:01 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18d6Um-0007tP-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 05:28:20 -0500
Received: from [193.186.16.251] (helo=localhost.localdomain)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18d6UM-0007gQ-00; Mon, 27 Jan 2003 05:27:39 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (8.11.6/8.11.6) with ESMTP id h0RAQxu10652;
	Mon, 27 Jan 2003 11:26:59 +0100
Date: Mon, 27 Jan 2003 11:26:58 +0100 (CET)
Message-Id: <20030127.112658.41639491.jfasch@salomon.at>
To: automake@gnu.org, autoconf@gnu.org, confix-announce@lists.sourceforge.net
From: Joerg Faschingbauer <jfasch@salomon.at>
X-Mailer: Mew version 2.2 on Emacs 21.2 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [ANNOUNCE] Confix 1.0.1 released
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 27 Jan 2003 10:29:17 -0000

What the hell is Confix?
------------------------

Confix is a build tool for source code packages. It doesn't require
the package maintainer to write any build instructions at all by
hand. Instead, it examines the source code, guesses what's to be done
and writes the build instructions for the maintainer. Another
important feature - perhaps the most important - is the ability of
Confix to recognize and compute package dependencies. That is, it
relieves the package maintainer of the task of manually keeping track
of the order in which libraries appear on the link line of an
executable, for example, or of the build order inside the package.

Confix is built on top of the standard open source tool Automake. That
is, the build instructions generated by Confix are in fact Automake
input files. This way one uses the whole infrastructure supplied by
Automake, involving such things as the well-known "configure; make;
make install" sequence, or automatically building source distributions
by simply saying "make dist", just to mention a few.

What is Release 1.0.1?
----------------------

Release 1.0.1 is a bugfix release upon release 1.0.0. It adds no
functionality, only a handful of bugs were fixed. See the release
notes.

Where can I get it?
-------------------

Confix is hosted at Sourceforge.net. The project's summary page is
http://sourceforge.net/projects/confix, which is where you can
download releases. Confix's homepage is
http://confix.sourceforge.net. Documentation can be found in the
source release package, and is also available online from the
homepage.

Future directions
-----------------

- Better integration of explicit build instructions

  Confix's normal mode of operation is to generate build instructions
  automatically from the package source, without any explicit
  statements from the package maintainer. To make Confix recognize
  things unambiguously, a few rules are imposed on the package source
  code. Sometimes it is not possible to obey these rules, for example
  when you are converting the build process of existing code to use
  Confix. For this purpose Confix provides interfaces for the
  maintainer's explicitly written build instructions which override
  Confix's wild guesses.

  Currently, wild guesses and explicit statements do not integrate
  well. You cannot use both. The goal is to make it work as
  expected. For example it should be possible to let Confix guess
  basic properties, and then to override certain properties
  explicitly.

- Generating code with Confix

  Automake has the feature of handling generated source files (see the
  BUILT_SOURCES variable in Automake). However, you have to know the
  names and the number of the generated files to make use of this
  feature. When you generate, say, C++ header and implementation files
  from a UML diagram, you wouldn't want to keep your BUILT_SOURCES
  list consistent with the classes in the diagram. In other words,
  code generation like this is not easily handled with stock Automake
  features.

  The goal is to supply interfaces that make it easy to embed code
  generators of this type into Confix. The code generation would take
  place before Confix scans the package's source, and the generated
  files would look to the scanner as if the user had written them.




Comments, suggestions and laughter are greatly appreciated. Please
direct them to confix-devel@lists.sourceforge.net.

Joerg Faschingbauer



From MAILER-DAEMON Mon Jan 27 07:12:37 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18d87i-0007FZ-00
	for mharc-autoconf@gnu.org; Mon, 27 Jan 2003 07:12:22 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18d81Z-0005zi-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 07:06:01 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18d80c-0005kA-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 07:05:23 -0500
Received: from smtp017.mail.yahoo.com ([216.136.174.114])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18d80C-0005Xq-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 07:04:36 -0500
Received: from gate1.lci.net (HELO yahoo.com) (earnie?boyd@150.159.224.8 with
	plain)
	by smtp.mail.vip.sc5.yahoo.com with SMTP; 27 Jan 2003 12:04:10 -0000
Message-ID: <3E352034.4010509@yahoo.com>
Date: Mon, 27 Jan 2003 07:04:04 -0500
From: Earnie Boyd <earnie_boyd@yahoo.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: JG8949@aol.com
References: <05AC2ECD.751F8533.000456CF@aol.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: How to Setup Autoconf?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: autoconf@gnu.org
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 27 Jan 2003 12:12:11 -0000

JG8949@aol.com wrote:
> HELP!!!
> 
> well that's a good way to start the mail :D. I'm trying to compile apache 2.0. i need autoconf to make the configuration file. (I've never done this b4 so don't be surprised by the incomptence of the questions hehe). I have Borlands C++ text line compiler and autoconf 2.57.
> 
> How do i use autoconf??? howdo i setup autoconf, does it need compiling first??? what is a cpp file??? why haven't i got any cpp files in the autoconf download??? what other inane questions can i come up with???
> 
> Any comments greatly appreciated
> 

You shouldn't need autoconf, you should just execute the configure 
script.  Is this a MS windows environment?  Yes, see http://www.mingw.org.

Earnie.




From MAILER-DAEMON Mon Jan 27 07:33:20 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18d8Rk-0005Pz-00
	for mharc-autoconf@gnu.org; Mon, 27 Jan 2003 07:33:04 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18d8RE-0005Cw-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 07:32:32 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18d8QJ-0004uR-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 07:31:51 -0500
Received: from mailgate1.globalintranet.net ([194.206.181.245]
	helo=relais-int9.globalintranet.net)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18d8Pw-0004mZ-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 07:31:12 -0500
Received: from TERRE.alain-manoukian.fr ([10.255.7.40]) by
          relais-int9.globalintranet.net (Netscape Messaging Server 4.15)
          with ESMTP id H9DHHO02.PBX for <autoconf@gnu.org>; Mon, 27 Jan
          2003 13:32:12 +0100 
x-fsavag4mse-ts: 70c32150315c4463
Keywords: disclaimer
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2C5FF.BF62BD9B"
Content-Class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Date: Mon, 27 Jan 2003 13:29:33 +0100
Message-ID: <4F784025AB8A7B4C94A6BB574DA2314436B4BA@TERRE>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: =?iso-8859-1?Q?probl=E8me?=
thread-index: AcLGAOvc4xsEuTHVEdeByQABAhl7UA==
From: "Julien JEHL" <jjehl@alain-manoukian.fr>
To: <autoconf@gnu.org>
Subject:  =?iso-8859-1?q?probl=E8me?=
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 27 Jan 2003 12:32:48 -0000

C'est un message de format MIME en plusieurs parties.

------_=_NextPart_001_01C2C5FF.BF62BD9B
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

to install, i do sh ./configure=20
After i do make and i have the message :
=20
cd . && /bin/sh /root/autoconf-2.56/config/missing --run autoconf
autoconf: configure.in: No such file or directory
make: *** [configure] Erreur 1

Someone help me to understand ?

Julien JEHL=20
Webmanager
Direction Marketing
GROUPE ALAIN MANOUKIAN=20

jjehl@alain-manoukian.fr=20
04 75 07 51 48=20
http://www.alain-manoukian.fr <http://www.alain-manoukian.fr/>  (Site
consommateurs)
http://www.groupe-alain-manoukian.com
<http://www.groupe-alain-manoukian.com/>  (Site corporate)=20

=20
Les informations contenues dans ce courrier =E9lectronique sont
confidentielles et peuvent =EAtre prot=E9g=E9es l=E9galement. Elles ne =
sont
destin=E9es qu'au destinataire. L'acc=E8s =E0 ce courrier =E9lectronique =
par
toute autre personne n'est pas autoris=E9. Si vous n'=EAtes pas le
destinataire voulu, toute divulgation, copie ou diffusion de ce courrier
=E9lectronique est interdite et peut =EAtre ill=E9gale.
La pr=E9sence de cette note prouve =E9galement que ce message =
=E9lectronique a
=E9t=E9 v=E9rifi=E9 par un logiciel anti-virus.

The information contained in this electronic mail is confidential and
may be protected by law. It is intended solely for the addressee. Access
to this electronic mail by another person is prohibited. If you are not
the intended addressee, any divulgence, copy or dissemination of this
electronic mail is prohibited and may be illegal.
The presence of this note also attests that this electronique message
was checked by an anti-viral software.

------_=_NextPart_001_01C2C5FF.BF62BD9B
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D260473512-27012003>to =
install, i=20
do&nbsp;sh ./configure&nbsp;</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D260473512-27012003>After =
i do make and=20
i have the message :</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D260473512-27012003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D260473512-27012003>cd . =
&amp;&amp;=20
/bin/sh /root/autoconf-2.56/config/missing --run autoconf<BR>autoconf:=20
configure.in: No such file or directory<BR>make: *** [configure] Erreur=20
1<BR></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D260473512-27012003>Someone help me to=20
understand ?</DIV></SPAN></FONT>
<P><B><FONT face=3DVerdana size=3D2>Julien JEHL</FONT></B> <BR><FONT =
face=3DVerdana=20
size=3D2>Webmanager<BR></FONT><FONT face=3DVerdana color=3D#999999 =
size=3D2>Direction=20
Marketing<BR>GROUPE ALAIN MANOUKIAN </FONT></P>
<P><FONT face=3DVerdana size=3D2>jjehl@alain-manoukian.fr</FONT> =
<BR><FONT=20
face=3DVerdana size=3D2>04 75 07 51 48</FONT> <BR><FONT face=3DVerdana =
size=3D1><A=20
href=3D"http://www.alain-manoukian.fr/"=20
target=3D_blank>http://www.alain-manoukian.fr</A> (Site =
consommateurs)<BR><A=20
href=3D"http://www.groupe-alain-manoukian.com/"=20
target=3D_blank>http://www.groupe-alain-manoukian.com</A> (Site =
corporate)</FONT>=20
</P>
<DIV>&nbsp;</DIV></BODY></HTML>
<html><head></head><body>Les informations contenues dans ce courrier =
=E9lectronique sont confidentielles et peuvent =EAtre prot=E9g=E9es =
l=E9galement. Elles ne sont destin=E9es qu'au destinataire. L'acc=E8s =
=E0 ce courrier =E9lectronique par toute autre personne n'est pas =
autoris=E9. Si vous n'=EAtes pas le destinataire voulu, toute =
divulgation, copie ou diffusion de ce courrier =E9lectronique est =
interdite et peut =EAtre ill=E9gale.<br>La pr=E9sence de cette note =
prouve =E9galement que ce message =E9lectronique a =E9t=E9 v=E9rifi=E9 =
par un logiciel anti-virus.<br><br>The information contained in this =
electronic mail is confidential and may be protected by law. It is =
intended solely for the addressee. Access to this electronic mail by =
another person is prohibited. If you are not the intended addressee, any =
divulgence, copy or dissemination of this electronic mail is prohibited =
and may be illegal.<br>The presence of this note also attests that this =
electronique message was checked by an anti-viral software.</body></html>
------_=_NextPart_001_01C2C5FF.BF62BD9B--



From MAILER-DAEMON Mon Jan 27 10:28:29 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18dBBV-0006aK-00
	for mharc-autoconf@gnu.org; Mon, 27 Jan 2003 10:28:29 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18dAQj-0006zo-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 09:40:09 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18d9zx-00025y-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 09:12:51 -0500
Received: from imo-r03.mx.aol.com ([152.163.225.99])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18d9G3-00036n-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 08:25:03 -0500
Received: from JG8949@aol.com
	by imo-r03.mx.aol.com (mail_out_v34.13.) id 7.1e7.67e4af (15862)
	 for <autoconf@gnu.org>; Mon, 27 Jan 2003 08:24:22 -0500 (EST)
Received: from  aol.com (mow-d24.webmail.aol.com [205.188.139.140]) by
	air-id06.mx.aol.com (v90.10) with ESMTP id MAILINID61-0127082422; Mon, 27 Jan
	2003 08:24:22 -0500
Date: Mon, 27 Jan 2003 08:24:22 -0500
From: JG8949@aol.com
To: autoconf@gnu.org
MIME-Version: 1.0
Message-ID: <58E0C035.5904DE7B.000456CF@aol.com>
X-Mailer: Atlas Mailer 2.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Subject: Re: How to Setup Autoconf?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 27 Jan 2003 15:28:27 -0000

right now i'm complete lost! (remember your only talking to a sheltered windows user lol, linux was too much for my little brain). I've NEVER compiled anything before for command line I've never used bcc32, I'm completely and 100% confused.

yes this is a Windows NT4 platform on a Novell network.

I did just whack the apache binary on, but I wanted to compile it myself (i just had the urge, not to urble u understand, i oculd do with a hair cut but it doens't need wasking *g*). the main reason being i want SSL and php built in.

I bought a nice chunky book (usually i go for the 10 page ladybird A6 books *does some more grinning*) It explain that to configure Apache 2.0 for compiling I need to play with the configure scripty joby. It then says to do this i need autoconf, then assumes I have autoconf (bugerin buggery....)

All that stuff you wrote, Dirk, looked wonderful!!!! but it went straight over my head d'oh. i was asking about cpp, beacuse borland kept on sticking cpp on the end of any file (without an extension) and then complained that it didn't exist! wot on earth!

an existing code base??? well not as far as i'm aware. run autoscan, i ca't 'just' run autoscan, its not a program or batch file :o

ahh nuts this aint goin to well, like u hadn't noticed hehe.

Thanks

>HELP!!!
>
>well that's a good way to start the mail :D. I'm trying to compile apache 2.0. i need autoconf to make the configuration file. (I've never done this b4 so don't be surprised by the incomptence of the questions hehe). I have Borlands C++ text line compiler and autoconf 2.57.
>
>How do i use autoconf???
>
that depends.. if you have an existing codebase and would like to 
immigrate it to autoconf make sure you rename Makefile and confiog.h (if 
present) to Makefile.bak and config.h.bakl first..

then run

autoscan
rm configure.scan configure.in
autoconf
autoheader

autoconf will generate the configure script
autoheader will generate the config.h.in template

autoconf is all about the generation of scripts.. autoscan will search 
through your code for what functions or libs you envolve in your code 
and will gebnerate a cionfigure script.. that script is platform 
independend and tests the system on which you�'d like to compile the 
code for the presence of the functions and libraries you involve in your 
code.. doing that it uses the config.h.in template to define/undefine 
HAVE_BLA_H definesx which you can use in your code to enable/disable 
functions or libraries you involve in your code...

Your can make a template of the Makefile too.. rename Makefile to 
Makefile.in and check through configure.in..

> howdo i setup autoconf, does it need compiling first???
>
./configure && make && make install

> what is a cpp file???
>
sourcecode written in cpp

> why haven't i got any cpp files in the autoconf download???
>
why should you? do you prefer autoconf to be written in cpp?

> what other inane questions can i come up with???
>
>Any comments greatly appreciated
>
n.p. for further assistance try google with "autoconf tutorial"

>
>Thanks
>
>james
>
>
>
>  
>
Dirk




From MAILER-DAEMON Mon Jan 27 11:08:47 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18dBib-0000id-00
	for mharc-autoconf@gnu.org; Mon, 27 Jan 2003 11:02:41 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18dBgk-0008JH-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 11:00:46 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18dBdI-0006po-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 10:57:12 -0500
Received: from imo-d09.mx.aol.com ([205.188.157.41])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18dB9m-0006At-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 10:26:42 -0500
Received: from JG8949@aol.com
	by imo-d09.mx.aol.com (mail_out_v34.13.) id 7.1d9.f20e09 (16112)
	 for <autoconf@gnu.org>; Mon, 27 Jan 2003 10:26:05 -0500 (EST)
Received: from  aol.com (mow-m10.webmail.aol.com [64.12.184.138]) by
	air-id12.mx.aol.com (v90_r2.5) with ESMTP id MAILINID124-0127102605; Mon, 27
	Jan 2003 10:26:05 -0500
Date: Mon, 27 Jan 2003 10:26:04 -0500
From: JG8949@aol.com
To: autoconf@gnu.org
MIME-Version: 1.0
Message-ID: <257B04BC.4EB955F6.000456CF@aol.com>
X-Mailer: Atlas Mailer 2.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Subject: Re: How to Setup Autoconf?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 27 Jan 2003 16:02:40 -0000

Ok,

i've downloaded MinGW (i've tried this b4 unsucessfully, but then none of its worked yet, roflmao). How do i use this with the configure script???? (damn it i'm being dumb)



From MAILER-DAEMON Mon Jan 27 11:33:01 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18dCAP-0001z3-00
	for mharc-autoconf@gnu.org; Mon, 27 Jan 2003 11:31:25 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18dC7Y-0000vY-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 11:28:28 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18dC4R-00087u-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 11:25:16 -0500
Received: from smtp017.mail.yahoo.com ([216.136.174.114])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18dC2D-0007HK-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 11:22:57 -0500
Received: from gate1.lci.net (HELO yahoo.com) (earnie?boyd@150.159.224.8 with
	plain)
	by smtp.mail.vip.sc5.yahoo.com with SMTP; 27 Jan 2003 16:22:56 -0000
Message-ID: <3E355CDE.8000600@yahoo.com>
Date: Mon, 27 Jan 2003 11:22:54 -0500
From: Earnie Boyd <earnie_boyd@yahoo.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: JG8949@aol.com
References: <257B04BC.4EB955F6.000456CF@aol.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: autoconf@gnu.org
Subject: Re: How to Setup Autoconf?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: autoconf@gnu.org
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 27 Jan 2003 16:31:24 -0000

JG8949@aol.com wrote:
> Ok,
> 
> i've downloaded MinGW (i've tried this b4 unsucessfully, but then none of its worked yet, roflmao). How do i use this with the configure script???? (damn it i'm being dumb)
> 
> 

Install http://prdownloads.sf.net/mingw/MSYS-1.0.8.exe.  See 
http://www.mingw.org/msys.shtml for info.

BTW, you may need to see http://www.cygwin.com if this is a cygwin1.dll 
dependent version fo apache.

Earnie.




From MAILER-DAEMON Mon Jan 27 23:20:54 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18dNEq-0001el-00
	for mharc-autoconf@gnu.org; Mon, 27 Jan 2003 23:20:44 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18dNEm-0001Zw-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 23:20:40 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18dNEg-0001US-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 23:20:35 -0500
Received: from b.smtp-out.sonic.net ([208.201.224.39])
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18dNE5-000149-00
	for autoconf@gnu.org; Mon, 27 Jan 2003 23:19:57 -0500
Received: (qmail 12897 invoked from network); 28 Jan 2003 04:19:57 -0000
Received: from turbo.sonic.net (208.201.224.26)
  by b.smtp-out.sonic.net with SMTP; 28 Jan 2003 04:19:57 -0000
Received: from thune.mrc-home.org (adsl-209-204-178-126.sonic.net
	[209.204.178.126])
	by turbo.sonic.net (8.11.6/8.8.5) with ESMTP id h0S4Jur11440
	for <autoconf@gnu.org>; Mon, 27 Jan 2003 20:19:56 -0800
X-envelope-info: <dalgoda@ix.netcom.com>
Received: by thune.mrc-home.org (8.11.4) id h0S4JuD29652;
	Mon, 27 Jan 2003 20:19:56 -0800
Newsgroups: local.ml.gnu.autoconf
From: dalgoda@ix.netcom.com (Mike Castle)
References: <k4vegxpdi.ln2@thune.mrc-home.org>
Organization: House of Linux
X-Newsreader: trn 4.0-test76 (Apr 2, 2001)
Path: not-for-mail
Originator: nexus@thune.mrc.org (Mike Castle)
Date: Mon, 27 Jan 2003 20:19:56 -0800
Message-ID: <c0dhgxgus.ln2@thune.mrc-home.org>
To: autoconf@gnu.org
Subject: Re: autoscan and AC_CHECK_DECLS
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 28 Jan 2003 04:20:42 -0000

In article <k4vegxpdi.ln2@thune.mrc-home.org>,
Mike Castle <dalgoda@ix.netcom.com> wrote:
>Ok.  Strange interactions with autoscan and autom4te.cache.  And a possible
>bug in autoscan otherwise.


Hmmm.  The following patch seems to improve my system a little bit.  But
I'm not certain if they are correct.

Looks like, for autom4te.in, maybe the process SHOULD be automated.  Or at
least made possible for a sanity check before shipping.  Without that
update, the stuff in /usr/share/autoconf/autoscan also contains
AC_DECL_SYS_SIGLIST, which was a bit confusing at first.

mrc

patch -p1 << \EOF
diff -ru autoconf-2.57.orig/bin/autoscan.in autoconf-2.57/bin/autoscan.in
--- autoconf-2.57.orig/bin/autoscan.in	2002-11-07 06:11:31.000000000 -0800
+++ autoconf-2.57/bin/autoscan.in	2003-01-27 20:06:45.000000000 -0800
@@ -565,7 +565,7 @@
     {
       chomp;
       my ($file, $line, $macro, @args) = split (/:/, $_);
-      if ($macro =~ /^AC_CHECK_(HEADER|FUNC|TYPE|MEMBER)S$/)
+      if ($macro =~ /^AC_CHECK_(DECL|HEADER|FUNC|TYPE|MEMBER)S$/)
 	{
 	  # To be rigorous, we should distinguish between space and comma
 	  # separated macros.  But there is no point.
diff -ru autoconf-2.57.orig/lib/autom4te.in autoconf-2.57/lib/autom4te.in
--- autoconf-2.57.orig/lib/autom4te.in	2002-10-29 00:07:29.000000000 -0800
+++ autoconf-2.57/lib/autom4te.in	2003-01-27 20:04:16.000000000 -0800
@@ -84,15 +84,14 @@
 # which is what we are building :(  In fact we need three files, not
 # two (autom4te.pre -> autom4te.in -> autom4te.cfg).
 begin-language: "Autoscan-preselections"
+args: --preselect AC_CHECK_DECLS
 args: --preselect AC_CHECK_FUNCS
 args: --preselect AC_CHECK_HEADERS
-args: --preselect AC_CHECK_LIB
 args: --preselect AC_CHECK_MEMBERS
 args: --preselect AC_CHECK_TYPES
 args: --preselect AC_C_CONST
 args: --preselect AC_C_INLINE
 args: --preselect AC_C_VOLATILE
-args: --preselect AC_DECL_SYS_SIGLIST
 args: --preselect AC_FUNC_ALLOCA
 args: --preselect AC_FUNC_CHOWN
 args: --preselect AC_FUNC_CLOSEDIR_VOID
@@ -127,6 +126,7 @@
 args: --preselect AC_HEADER_DIRENT
 args: --preselect AC_HEADER_MAJOR
 args: --preselect AC_HEADER_STAT
+args: --preselect AC_HEADER_STDBOOL
 args: --preselect AC_HEADER_STDC
 args: --preselect AC_HEADER_SYS_WAIT
 args: --preselect AC_HEADER_TIME
EOF


-- 
     Mike Castle      dalgoda@ix.netcom.com      www.netcom.com/~dalgoda/
    We are all of us living in the shadow of Manhattan.  -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc



From MAILER-DAEMON Tue Jan 28 06:30:51 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18dTvh-0006z6-00
	for mharc-autoconf@gnu.org; Tue, 28 Jan 2003 06:29:25 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18dTvM-0006j4-00
	for autoconf@gnu.org; Tue, 28 Jan 2003 06:29:04 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18dTv5-0006EP-00
	for autoconf@gnu.org; Tue, 28 Jan 2003 06:28:52 -0500
Received: from imo-r08.mx.aol.com ([152.163.225.104])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18dTub-0005NF-00
	for autoconf@gnu.org; Tue, 28 Jan 2003 06:28:17 -0500
Received: from JG8949@aol.com
	by imo-r08.mx.aol.com (mail_out_v34.13.) id 7.130.1a26f081 (15886)
	 for <autoconf@gnu.org>; Tue, 28 Jan 2003 06:28:12 -0500 (EST)
Received: from  aol.com (mow-d22.webmail.aol.com [205.188.139.138]) by
	air-id08.mx.aol.com (v90.10) with ESMTP id MAILINID81-0128062811; Tue, 28 Jan
	2003 06:28:11 -0500
Date: Tue, 28 Jan 2003 06:28:11 -0500
From: JG8949@aol.com
To: autoconf@gnu.org
MIME-Version: 1.0
Message-ID: <5351CCE5.4E43D8A2.000456CF@aol.com>
X-Mailer: Atlas Mailer 2.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Subject: Re: How to Setup Autoconf?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 28 Jan 2003 11:29:23 -0000

I swear my brain has fried itself.

i had happily installed MinGW, my problem was how to use it??? I assume its all command line based. but how do i use it with the apache confogure script?

Thanks



From MAILER-DAEMON Tue Jan 28 07:26:24 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18dUcx-00079T-00
	for mharc-autoconf@gnu.org; Tue, 28 Jan 2003 07:14:07 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18dUcd-0006wj-00
	for autoconf@gnu.org; Tue, 28 Jan 2003 07:13:47 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18dUbK-00068A-00
	for autoconf@gnu.org; Tue, 28 Jan 2003 07:12:30 -0500
Received: from [217.112.227.117] (helo=localhost.localdomain)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18dU7K-0002Hk-00
	for autoconf@gnu.org; Tue, 28 Jan 2003 06:41:27 -0500
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (8.12.5/8.12.5) with ESMTP id h0SBlbXq000876;
	Tue, 28 Jan 2003 12:47:37 +0100
Received: from localhost (ronald@localhost)h0SBla6t000872;
	Tue, 28 Jan 2003 12:47:36 +0100
X-Authentication-Warning: localhost.localdomain: ronald owned process doing
	-bs
Date: Tue, 28 Jan 2003 12:47:36 +0100 (CET)
From: Ronald Landheer-Cieslak <ronald@landheer.com>
X-X-Sender: ronald@localhost.localdomain
To: JG8949@aol.com
In-Reply-To: <257B04BC.4EB955F6.000456CF@aol.com>
Message-ID: <Pine.LNX.4.44.0301281219460.770-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: autoconf@gnu.org
Subject: Re: How to Setup Autoconf?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 28 Jan 2003 12:14:05 -0000

On Mon, 27 Jan 2003 JG8949@aol.com wrote:
> Ok,
> i've downloaded MinGW (i've tried this b4 unsucessfully, but then none of 
> its worked yet, roflmao). How do i use this with the configure 
> script???? (damn it i'm being dumb)
If I get this correctly, you're only used to the Windows GUI, and it's the 
command-line is kinda scary, right?
If that's the case, there's not very much this list can do about that, but 
the people here can tell you which commands to execute to get to running 
configure..
When you have MSYS installed (which a previous mail pointed you to) you 
should have a baroque-like "M" somewhere on your desktop, and/or 
MinGW/MSYS/msys in your programs menu (under start) - click it. You now 
have a command-line.
If the sources to your apache are in C:\hello\apache type 
$ cd /c/hello/apache
to get there (don't type the dollar sign *)
You can now type ./configure if you want to run the configure script (or 
just follow the rest of the instructions in your book).
If you really want to edit "configure" (which I would not recommend as 
it's generated by autoconf, but from an earlier post of yours my guess 
is that you're doing it anyway), use a simple text editor to do it, not a 
Borland IDE.

Good luck :)

rlc

* if you hang around on lists like this one for a while, you will find 
  that often, when someone tells you to type something on the 
  command-line, there is a $ in front of what you're supposed to type, or 
  a % if you have to be a super-user to do it. This is kind of a 
  convention, which helps get more info into a single line - something 
  geeks seem to like a lot ;)




From MAILER-DAEMON Tue Jan 28 16:54:20 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18ddgR-00051T-00
	for mharc-autoconf@gnu.org; Tue, 28 Jan 2003 16:54:19 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18ddgQ-0004yo-00
	for autoconf@gnu.org; Tue, 28 Jan 2003 16:54:18 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18ddgO-0004yY-00
	for autoconf@gnu.org; Tue, 28 Jan 2003 16:54:17 -0500
Received: from sccrmhc02.attbi.com ([204.127.202.62])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18ddgH-0004nu-00
	for autoconf@gnu.org; Tue, 28 Jan 2003 16:54:09 -0500
Received: from kegel.com (c-24-126-73-164.we.client2.attbi.com[24.126.73.164])
          by sccrmhc02.attbi.com (sccrmhc02) with SMTP
          id <2003012821540900200i68h8e>; Tue, 28 Jan 2003 21:54:09 +0000
Message-ID: <3E3701DC.60707@kegel.com>
Date: Tue, 28 Jan 2003 14:19:08 -0800
From: Dan Kegel <dank@kegel.com>
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)
X-Accept-Language: de-de, en
MIME-Version: 1.0
To: autoconf <autoconf@gnu.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: iffe.  bleh.
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 28 Jan 2003 21:54:18 -0000

I am faced with the pleasure of using an AT&T open source package
named 'cdt' in a cross-compilation environment.  It appears
they have an internal tool called 'iffe' somewhat similar to
autoconf.  This is old news to anyone who followed the Software Carpentry
competition, I suppose; see
http://sc-archive.codesourcery.com/entries/config/SapCat/SapCat.html

Still, it's worth a look.  Although iffe makes me want to vomit,
that's just my normal reaction to any complex new tool that
will be a pain for me to deal with, and they did something
that I've been wanting autoconf to do for some time:
they support the equivalent of AC_TRY_RUN when cross-compiling.
(I suspect it'll be too much of a pain for me to use, though...)

The doc's at http://www.research.att.com/~gsf/man/man1/iffe.html
It's an interesting window onto an alternate universe,
not unlike djb's world...

- Dan

-- 
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045




From MAILER-DAEMON Thu Jan 30 02:49:00 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18e9RT-0004KB-00
	for mharc-autoconf@gnu.org; Thu, 30 Jan 2003 02:48:59 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18e9JJ-0002fl-00
	for autoconf@gnu.org; Thu, 30 Jan 2003 02:40:33 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18e9H3-0001yR-00
	for autoconf@gnu.org; Thu, 30 Jan 2003 02:38:13 -0500
Received: from adsl-153-118-209.mia.bellsouth.net ([68.153.118.209]
	helo=mx10.gnu.org)	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 18e9FJ-0001jS-00
	for autoconf@gnu.org; Thu, 30 Jan 2003 02:36:25 -0500
From: "Vacations Tours" <telesurcom@msn.com>
Date: Thu, 30 Jan 2003 02:36:16
To: autoconf@gnu.org
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <E18e9FJ-0001jS-00@monty-python.gnu.org>
Subject: gano sus vacaciones gratis en un crucero!!!
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 30 Jan 2003 07:48:58 -0000


Usted y su familia ganaron sus vacaciones "GRATIS"

8 dias y 7 noches en un crucero por el caribe!!!!!!!!!!!!!!!!

Reclame su premio, su numero de confirmacion es 055

LLAME YA!!!!

Llame gratis desde los Estados Unidos y Puerto Rico 1800-806-3646

Desde del exterior 001-305-379-8877



From MAILER-DAEMON Thu Jan 30 13:23:30 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18eJLW-0004Pf-00
	for mharc-autoconf@gnu.org; Thu, 30 Jan 2003 13:23:30 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18eJLT-0004OT-00
	for autoconf@gnu.org; Thu, 30 Jan 2003 13:23:27 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18eJLS-0004NT-00
	for autoconf@gnu.org; Thu, 30 Jan 2003 13:23:27 -0500
Received: from dangermouse.ncsa.uiuc.edu ([141.142.96.46])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18eJLS-0004LZ-00
	for autoconf@gnu.org; Thu, 30 Jan 2003 13:23:26 -0500
Received: (from wendling@localhost)
	by dangermouse.ncsa.uiuc.edu (8.11.6/8.11.6) id h0UINOH17877
	for autoconf@gnu.org; Thu, 30 Jan 2003 12:23:24 -0600
Date: Thu, 30 Jan 2003 12:23:24 -0600
From: Bill Wendling <wendling@ncsa.uiuc.edu>
To: autoconf@gnu.org
Message-ID: <20030130182324.GA17858@ncsa.uiuc.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-PGP-Key: http://www.ncsa.uiuc.edu/~wendling/public_key.asc
X-PGP-Fingerprint: C169 5EB2 2F92 9C34 C9FA  E976 3C24 E3D3 EBE7 C80B
Subject: C to Fortran90 Type Detection?
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Post: <mailto:autoconf@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/autoconf>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 30 Jan 2003 18:23:28 -0000

Hi all,

Does anyone have a macro which will detect C to Fortran 90 type
conversions? We're looking for a way to automate how to determine what
Fortran 90 type is the best analogue for a C type.

Maybe even a program that could be run at compile time? :-)

Thanks!

-- 
|| Bill Wendling            "Real Programmers have a Snoopy Calendar
|| wendling@ncsa.uiuc.edu    of '69 hanging on their wall"
|| Coding Simian                       -- Toon Moene



