Should -i mkdir?

2003-09-25 Thread Akim Demaille

Several projects used config/ without any hand written file in it,
thanks to Automake's wonderful ability to ship the files all by
itself.  But then, often, such projects, when just checked out, or
de-tar'ed by hand, don't have a config/.  Et soudain, c'est
l'accident :

~/src/vampire % autoreconf -fvi   nostromo 9:55
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/local/bin/autoconf --force
autoreconf: configure.ac: not using Autoheader
autoreconf: running: automake --add-missing --copy --force-missing
cp: cannot create regular file `config/install-sh': No such file or directory
configure.ac: installing `config/install-sh'
configure.ac: error while copying
cp: cannot create regular file `config/mkinstalldirs': No such file or directory
configure.ac: installing `config/mkinstalldirs'
configure.ac: error while copying
cp: cannot create regular file `config/missing': No such file or directory
configure.ac: installing `config/missing'
configure.ac: error while copying
cp: cannot create regular file `config/mdate-sh': No such file or directory
doc/texinfo/Makefile.am:20: installing `config/mdate-sh'
doc/texinfo/Makefile.am:20: error while copying
cp: cannot create regular file `config/texinfo.tex': No such file or directory
doc/texinfo/Makefile.am:20: installing `config/texinfo.tex'
doc/texinfo/Makefile.am:20: error while copying
autoreconf: automake failed with exit status: 1



So, should automake -i make sure the directory exists and create it if
needed?  Or that would be considered unsafe (a typo in the name, et
voilà, a nasty dir pollutes your codeshore).




URGENT REQUEST

2003-09-25 Thread Kumalo Diawara
DEAR SIR,
I HAVE RECEIVED YOUR NAME AND CONTACT INFORMATION FROM
A SEARCH AT THE INTERNET.
I AM BARRISTER OSCAR KUMALLO, AN ATTORNEY AT LAW
AND THE PERSONAL LAWYER TO ENGINEER YOSHIDA HIROSHI.
PLEASE
TAKE NOTE THAT THE ABOVE ENGINEER  IS A CITIZEN OF
YOUR
COUNTRY WHO VISITED NIGERIA FOR OIL EXPLORATIONS.
ON THE 21st APRIL 2001, MY CLIENT,THE  ENGINEER 
AND HIS FAMILY WERE INVOLVED IN A MOTOR ACCIDENT.
UNFORTUNATELY, 
ALL THE OCCUPANTS OF THE VEHICLE LOST THEIR LIVES.
SINCE THEN, 
I HAVE MADE SEVERAL INQUIRIES TO YOUR EMBASSY IN
NIGERIA TO HELP
ME TO LOCATE ANY OF THE RELATIVES OF MY LATE CLIENT IN
YOUR COUNTRY BUT SO FAR, NONE WAS FOUND.

I AM CONTACTING YOU TO ASSIST ME TO CLAIM THE AMOUNT
OF US$30MILLION IN CASH WHICH THE DECEASED DEPOSITED
IN A VAULT WITH A SECURITY COMPANY IN
NIGERIA/HOLLAND FOR SAFE-KEEPINGS. 

THE SECURITY COMPANY IN AMSTERDAM HAS CONTACTED ME
MOST RECENTLY WITH THE INFORMATION THAT I SHOULD
NOMINATE THE NEXT OF KIN/RELATIVES OF MY LATE CLIENT 
OR THEY WILL DECLARE THE DEPOSIT AS AN 'ABANDONED
PROPERTY'.

SINCE I HAVE BEEN VERY UNSUCCESFULL IN LOCATING THE
NEXT OF KIN/RELATIVE OF MY LATE CLIENT SINCE YOU HAVE
THE SAME SURNAME, I WILL LIKE TO NOMINATE YOU TO THE
SECURITY COMPANY IN NIGERIA/AMSTERDAM AS THE ONLY
RELATIVE OF MY LATE CLIENT, SO THAT THE DEPOSIT OF
US$30MLLION AT VAULT OF THE SECURITY COMPANY IN
NIGERIA/AMSTERDAM WILL BE RELEASED TO YOU.
IF YOU AGREE TO THIS PROPOSAL, AS THE ATTORNEY TO
THE DECEASED AND BECAUSE THE SECURITY COMPANY HERE IN
NIGERIA AND 
AMSTERDAM TRUST ME AS THE PERSONAL LAWYER TO THE
DECEASED, I SHALL PREPARE DOCUMENTS TO SHOW THAT YOU
ARE THE NEXT OF KIN, A COUSIN OR A RELATIVE OF MY LATE
CLIENT.
ADDITIONALLY, I WILL ALSO OBTAIN COURT AFFIDAVIT IN
NIGERIA TO SHOW THAT YOU ARE THE NEXT OF KIN AND
RELATIVE OF THE DECEASED. ONCE THIS IS DONE, THE TRUNK
BOXES CONTAINING THE CASH WILL BE RELEASED TO YOU
BY THE SECURITY COMPANY IN AMSTERDAM.
THE SECURITY COMPANY IS MOST WILLING TO RETURN THE
DEPOSIT TO THE NEXT OF KIN OR A RELATIVE OF MY LATE
CLIENT. ONCE I PRODUCE THIS DOCUMENTS WITH YOUR NAME
AS THE NEXT OF KIN TO MY LATE CLIENT, THEY CANNOT
HESITATE TO RELEASE THE BOX CONTAINING THE CASH TO
YOU.
IF YOU ARE INTERESTED IN THIS PROPOSAL,YOU WILL SEND
TO ME BY EMAIL ATTACHMENT THE RELEVANT PAGES OF YOUR
INTERNATIONAL PASSPORT TO ENABLE ME PREPARE THE NEXT
OF KIN NOMINATION CERTIFICATES IN YOUR FAVOUR AND
FORWARD TO THE SECURITY COMPANY IN HOLLAND SO THAT THE
DEPOSIT WILL BE RELEASED TO YOU. ADDITIONALLY, I WILL
ALSO OBTAIN AFFIDAVIT IN YOUR NAME FROM OUR HIGH COURT
STATING THAT YOU ARE THE NEXT OF KIN OF MY LATE
CLIENT.
AFTER THIS, ALL YOU WILL BE REQUIRED TO DO IS TO
TRAVEL TO HOLLAND/AMSTERDAM WITH YOUR INTERNATIONAL
PASSPORT AND VISIT THE SECURITY COMPANY TO SECURE THE
RELEASE OF THE BOXES CONTAINING THE CASH. 

WHEN YOU GO TO AMSTERDAM, YOU WILL ALSO OPEN A
NON-RESIDENTIAL BANK ACCOUNT IN AMSTERDAM WHERE YOU
WILL PAY IN THE MONEY WHEN IT IS RELEASED TO YOU.

OF-COURSE THE SECURITY COMPANY WILL GIVE YOU ALL THE
ASSISTANCE TO HELP YOU OPEN A NON RESIDENTIAL
ACCOUNT IN HOLLAND WHERE YOU CAN PAY IN THE MONEY
WHEN IT IS RELEASED TO YOU. 
BEFORE YOU TRAVEL TO HOLLAND, I WILL ALSO GIVE YOU THE
PHONE NUMBERS OF THE SECURITY SO THAT YOU WILL CALL
THEM AND NOTIFY THEM OF YOUR VISIT TO ENABLE THEM PICK
YOU UP AT THE AIRPORT.
ALSO, BEFORE YOU TRAVEL, I WILL GIVE YOU THE CODE
NUMBERS WHICH YOU WILL USE TO UNLOCK THE BOXES WHEN IT
IS RELEASED TO YOU JUST TO MAKE SURE THAT THE CASH IS
INTACT. 


WHEN YOU HAVE CLAIMED THE MONEY, WE SHALL SHARE
BETWEEN OURSELVES. 50% TO YOU AND 50% TO MYSELF .
AFTER PAYING THE MONEY INTO YOUR ACCOUNT IN HOLLAND,
YOU WILL SEND USD5000 TO ME TO ENABLE ME PURCHASE
TICKETS AND JOIN YOU IN HOLLAND TO COLLECT MY SHARE.

PLEASE CONTACT ME URGENTLY BY ONLY WITH THE BELOW
ALTERNATIVE E-MAIL FOR
MORE:CLARIFICATIONS: [EMAIL PROTECTED]

WAITING TO HEAR FROM YOU AND PLEASE KEEP TOP-SECRET.

BARRISTER OSCAR KUMALLO
SENIOR ADVOCATE OF NIGERIA





Charle con sus amigos online usando CHAT 123 
http://www.123.com/sp/chat/section.php?id_section=329





How many packages use autotools?

2003-09-25 Thread Bernd Jendrissek
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello all

I am wondering how widespread the use of the autotools is - particularly
among projects that are *not* GNU or other Free Software, or even Open
Source but not-quite Free.  IOW how many in-house completely locked-up
proprietary packages use them?

It's probably a bit hard to tell, these packages being uber-secret and
all.  Any (gu)estimates?

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

iD8DBQE/cvBN/FmLrNfLpjMRArGZAJ96Dha4MLCDIg14EInt6U8AeF0nNQCfQZ73
DIh59vdwn21jlWujB7ribwY=
=Me6j
-END PGP SIGNATURE-




Re: Should -i mkdir?

2003-09-25 Thread Thien-Thi Nguyen
Akim Demaille [EMAIL PROTECTED] writes:

   So, should automake -i make sure the directory exists and create it if
   needed?  Or that would be considered unsafe (a typo in the name, et
   voil=E0, a nasty dir pollutes your codeshore).

perhaps only if --force is also specified, else signal error.

thi




dist target and bin_SCRIPTS

2003-09-25 Thread Magnus Therning
Sorry if this has been brought up before.

This behaviour is a bit odd to me:

bin_SCRIPTS = my_script

will not get 'my_script' included in the dist-tarball. I needed to add a

EXTRA_DIST = my_script

as well. I couldn't find this behaviour documented anywhere, and a quick
search on Google didn't turn up anything either (might be due to my
search skills).

automake version:
automake (GNU automake) 1.7.7
Written by Tom Tromey [EMAIL PROTECTED].

Copyright 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

autoconf version:
autoconf (GNU Autoconf) 2.57
Written by David J. MacKenzie and Akim Demaille.

Copyright 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

A simple example that shows the behaviour:

autoconf.ac:
AC_INIT(test, 0)
AC_CONFIG_SRCDIR(my_script)
AM_INIT_AUTOMAKE
 
dnl Create the files
AC_CONFIG_FILES([Makefile])
AC_OUTPUT

Makefile.am:
bin_SCRIPTS = my_script

$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c

config.status: creating Makefile
$ make distcheck

configure: error: cannot find sources (my_script) in ..
make: *** [distcheck] Error 1

/M

-- 
Magnus Therning  mailto:[EMAIL PROTECTED]
+31-40-2745179  http://pww.innersource.philips.com/magnus/
OpenPGP:0x4FBB2C40

I'd doubt that it represents a threat to anything but the notion that you can
sell bad code by refusing to let anyone see what's in the box.
 -- Amy Wohl on Linux and Open Source


signature.asc
Description: Digital signature


Agenda Juridica 2004

2003-09-25 Thread Editora
Title: Untitled Document





  
 
  

   
AGENDA 
  JURDICA 2004 - 
  Encadernao de luxo
  LEVE, PRTICA E FUNCIONAL
  Um produto com
a garantia 
  do EMENTRIO 
  FORENSE
  Desde 1948 servindo aos
Profissionais 
  de Direito


  
  
 
   
   Agenda 
Jurdica 2004
Dados Pessoais
Calendrios
Prazos CPC
Seccionais da OAB
Justia Federal
Tribunais de Justia
Tribunais Regionais do Trabalho
Calendrio Mensal
Audincias
Agenda Telefnica
  

  
  
 
   
 
  Preo
unitrio: 
R$ 20,00
ESCOLHA A 
OPO DE COMPRA
Preencha, 
imprima o
formulrio 
abaixo e devolva por FAX ou postal,
juntando o comprovante de depsito ou cheque
nominal.



  
  
 
  1 
OPO: Depsito em conta corrente desta
Editora. 
Escolha o banco:

 
   

BANCO DO BRASIL
S/A 
- Agncia 0087-6 - Conta corrente n
9003-4

 
   

BANCO REAL S/A
- Agncia 
0453 - Conta corrente n 5718604-3

 
   

BRADESCO S/A -
Agncia 
2509 - Conta Corrente n 40923-5

 
   
2 
  OPO: Cheque nominal a EDITORA MUNDO FORENSE
LTDA.
  Envie por carta para nosso endereo
abaixo:
  

 
   
 
  Agenda
2004
Editora Mundo Forense Ltda.
Rua da Lapa, 180 s/809
20021-180 - RIO DE JANEIRO - RJ

  


  3 
OPO: Receba gratuitamente esta agenda
adquirindo o 

CD-ROM EMFOR - Tradicional Banco de Dados 
EMENTRIO FORENSE - Ano LV
Faa o pedido pelo nosso site - www.emfor.com.br


  
  
 
   
PEDIDO 
  A EDITORA MUNDO FORENSE LTDA
   CNPJ 03.305.769/0001-06
  Solicito 
  a remessa de 
  
  (mencionar a
quantidade) AGENDA(S) 
  EMFOR para
o endereo 
  abaixo.
  

 
   
Nome:
  
   

  

 
   
Empresa:
  
   

  

 
   
Endereo 
  de Entrega:
  
   

  

 
   
Cidade:
  
   
  
  
  Estado: 
  

  

 
   
CEP:
  
   

  

 
   
CIC/CNPJ:
  
   

Inscr. Est:



 
   
Tel:
  
   

E-mail:



  
  
 
   
Remessa 
  via postal com Registro para seu endereo. 
  Prazo de entrega:15 dias teis aps o
recebimento 
  do pedido
  


   
Pedidos 
   Informaes
  Tel.: 21.2556-9879 FAX: 21.2285-7864
  E-mail: [EMAIL PROTECTED]

  

  
  
 
 
  
CASO NÃO 
  O QUEIRA RECEBER NOVAMENTE, Clique
Aqui
  


  

  







Re: How many packages use autotools?

2003-09-25 Thread Roger Leigh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Bernd Jendrissek [EMAIL PROTECTED] writes:

 I am wondering how widespread the use of the autotools is - particularly
 among projects that are *not* GNU or other Free Software, or even Open
 Source but not-quite Free.  IOW how many in-house completely locked-up
 proprietary packages use them?

 It's probably a bit hard to tell, these packages being uber-secret and
 all.  Any (gu)estimates?

I use it in all my Free software packages.  I also use it at work, for
non-free commercial stuff.

TBH, a lot of commercial software has archaic build processes, since
there's not the same requirement for repeated building of source on
multiple platforms--there's one build and the binaries are
distributed.  Therefore, on DOS many projects are built by hand or
with batch files and on UNIX, a plain Makefile or shell script will
often do.  I'd guess it's used, but far, far less than for Free
software.

Free software, being distributed primarily as source, must build
conveniently and quickly on any user's system.  That's the main reason
for using autoconf (and automake etc.).  Personally, I've spent
several hundred hours working on the gimp-print build infrastructure
alone.  For the stuff I do for work, the company doesn't care how it
builds as long as they can supply a set of binaries to customers.  In
addition, commercial pressures mean that there simply isn't time to
devote to such things--which is just one reason why Free software is
so oftern of much better quality.


Regards,
Roger

- -- 
Roger Leigh

Printing on GNU/Linux?  http://gimp-print.sourceforge.net/
GPG Public Key: 0x25BFB848.  Please sign and encrypt your mail.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 http://mailcrypt.sourceforge.net/

iD8DBQE/c1vYVcFcaSW/uEgRAlkqAJ9r1SEjfl/D1OFh41IXITnmDXzEEQCg02Ri
AGGzMvx9mzd5BsnHoUQTsxY=
=syRd
-END PGP SIGNATURE-




Autoconf 2.57d released

2003-09-25 Thread Akim Demaille

#secure method=pgpmime mode=sign

This is our candidate release for Autoconf 2.58.  We plan to release
it soon, so that Automake 1.8 can be released, hence Libtool 1.6, so
that GNU M4 2.0 can be shipped, enabling Autoconf 2.60 ;)

Please, test it thoroughly.

Akim, Alexandre, Jim, Paul, and Tom.

Here are the compressed sources:
  http://www.lrde.epita.fr/~akim/download/autoconf-2.57d.tar.gz   (1.2MB)
  http://www.lrde.epita.fr/~akim/download/autoconf-2.57d.tar.bz2  (837KB)

And here are xdelta-style diffs:
  http://www.lrde.epita.fr/~akim/download/autoconf-2.57b-2.57d.xdelta   (26KB)

Here are GPG detached signatures:
  http://www.lrde.epita.fr/~akim/download/autoconf-2.57d.tar.gz.asc
  http://www.lrde.epita.fr/~akim/download/autoconf-2.57d.tar.bz2.asc

Here are the MD5 and SHA1 signatures:

2fd6b2ce93c20272114580696b873b13  autoconf-2.57d.tar.gz
11283066884ee9dac83b9e6d9a7870f4  autoconf-2.57d.tar.bz2
f1bf3224ee351de53229c8e3957ac888  autoconf-2.57b-2.57d.xdelta
810ea71de4c866970f76079036847c63ad605d77  autoconf-2.57d.tar.gz
be65e491f94df9e1fa0aa272df78848d0ef2ac84  autoconf-2.57d.tar.bz2
92306a504a352c140c7795839cfe374f7e931046  autoconf-2.57b-2.57d.xdelta

NEWS

* Major changes in Autoconf 2.57d

* Major changes in Autoconf 2.57b

  Released 2003-08-24, by Akim Demaille.

** Autotest and local.at
  The optional file local.at is always included in Autotest test suites.

** Warnings
  The warnings are always issued, including with cached runs.
  This became a significant problem since aclocal and automake can
  run autoconf behind the scene.

** autoheader warnings
  The warnings of autoheader can be turned off, using --warning.
  For instance, -Wno-obsolete disables the complaints about acconfig.h
  and other deprecated constructs.

* Major changes in Autoconf 2.57a

** New macros
  AC_C_RESTRICT, AC_INCLUDES_DEFAULT.

** AC_DECL_SYS_SIGLIST
  Works again.

** AC_FUNC_MKTIME
  Now checks that mktime is the inverse of localtime.

** Improve DJGPP portability
  The Autoconf tools and configure behave better under DJGPP.

** Present But Cannot Be Compiled
  New FAQ section dedicated to the mystic

configure: WARNING: pi.h: present but cannot be compiled
configure: WARNING: pi.h: check for missing prerequisite headers?
configure: WARNING: pi.h: proceeding with the preprocessor's result
  messages.

** Concurrent executions of autom4te
  autom4te now locks its internal files, which enables concurrent
  executions of autom4te, likely to happen if automake, autoconf,
  autoheader etc. are run simultaneously.

** Libtool
  Use of Libtool 1.5 and higher is encouraged.  Compatibility with
  Libtool pre-1.4 is not checked.

** Autotest
  Testsuites no longer rerun failed tests in verbose mode; instead,
  failures are logged while the test is run.

  In addition, expected failures can be marked as such.



ChangeLog entries:

**
ChangeLog
**
2003-09-25  Akim Demaille  [EMAIL PROTECTED]

Version 2.57d.

* bin/Makefile.am (edit): Handle '@configure_input@'.
(autoconf, autoheader, autom4te, autoreconf, autoscan, autoupdate)
(ifnames): chmod -w.
* tests/wrapper.as (AUTOCONF, AUTOM4TE, ): Point to tests/
executables, not bin/ executables!  Otherwise all the magic needed
to find non installed files is turned off.  This caused a failure
of test 40 and 41 that ran aclocal 1.8 which in turn ran autom4te
as found in its environment (sent by tests/autoreconf): pointing
to bin/autom4te that could not find its files.
* tests/mktests.sh: Force the replacement of generated files, for
the sake of mv program that are interactive when overwriting a
-w file.
* config/install-sh: Upgrade from CVS Automake.

2003-09-23  Paul Eggert  [EMAIL PROTECTED]

* doc/autoconf.texi (Limitations of Builtins): Document test -h
versus test -L issues.

2003-09-23  Daniel Jacobowitz  [EMAIL PROTECTED] and
Paul Eggert [EMAIL PROTECTED]

Trivial change to support GCC's configuration procedure.
* lib/autoconf/c.m4 (AC_PROG_CPP_WERROR): New macro.
* lib/autoconf/headers.m4 (_AC_CHECK_HEADER_MONGREL): Don't warn
about inconsistency if the preprocessor is set to give errors for
any warning.
* doc/autoconf.texi (C Compiler Characteristics): Document this.

2003-09-13  Alexandre Duret-Lutz  [EMAIL PROTECTED]

* Makefile.am (autom4te-update, autom4te_files): Fetch Struct.pm
and XFile.pm from Automake.
* lib/Autom4te/XFile.pm: Update from Automake.

2003-09-12  Akim Demaille  [EMAIL PROTECTED]

Version 2.57c.

2003-09-12  Akim Demaille  [EMAIL PROTECTED]

* config/config.guess, config/config.sub, config/missing,
* lib/Autom4te/Channels.pm, lib/Autom4te/Configure_ac.pm: