Tom Tromey <[EMAIL PROTECTED]> writes:
> > "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
>
> Tom> My current thinking is that we would name the installed version
> Tom> and the install directories after the "install version". For
> Tom> anything in the 1.5 series (1.5.1, 1.5-p1, 1.5c, wha
Hi, Dear Sir,
Nantong Yudi Optical Instrument Co.,Ltd
is a Manufacturer Specilized in All Kinds of Optical Glass Lens, Having The
Twenty-Year Manufacturing Experience, Gaining Certificate Of QSM ISO9002. Our
Main Products Are Included Large, Middium And Small Size Spherical Lens
(2mm-250mm),
Akim et al --
The perl getopt package leaves something to be desired in its error
output. Compare:
creche. automake --zardoz
Unknown option: zardoz
creche. cp --zardoz
cp: unrecognized option `--zardoz'
Try `cp --help' for more information.
I much prefer the cp output. For
> "Ralf" == Ralf Corsepius <[EMAIL PROTECTED]> writes:
Ralf> 1. Merge the autoconf and automake packages into one package.
Ralf> This would
Actually, I'm in favor of this. There are some barriers to doing it,
but nothing very hard. I don't think we'll do it with the next
release though.
R
On Tue, 2002-01-15 at 22:38, Ted Irons wrote:
> Just a thought ...
Might as well put in my .02 Euro as well.
I kinda like a gcc-style approach; i.e. install the actual automake/...
scripts as $prefix/share/automake/version/automake. Then have a
$prefix/bin/automake that checks for some option t
===
- Original Message -
From: "Tim Van Holder" <[EMAIL PROTECTED]>
> This solution keeps $prefix/bin fairly uncluttered, moving the many
> scripts below their own tree under $prefix/shared/. I think this is
> what's done by the autoconf & automake wrappers used by cygnus, but
I'm
> not
Just a thought ...
Keep different versions of the autotools
(autoconf, automake, and libtool) in
different autoconf directories
(for eg, autoconf-2.52, automake-1.5b,
and libtool-1.4d could be installed
in /local/autoconf-2.52).
In addition, each package has
its own bootstrap script that invokes
Hi,
My project is built from several source subdirs. By default automake
is using ar to build a single 'somelib.a' in every subdir before the final
link. How can I make it use ld instead of ar?
I tried using libtool but it didn't help.
TIA
---
> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
Tom> My current thinking is that we would name the installed version
Tom> and the install directories after the "install version". For
Tom> anything in the 1.5 series (1.5.1, 1.5-p1, 1.5c, whatever), this
Tom> would be "1.5". Then we would g
Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
> Havoc> in the spec file I rename automake to automake-1.4,
> Havoc> aclocal to aclocal-1.4, automake to automake-1.5,
> Havoc> aclocal to aclocal-1.5, and symlink automake to
> Havoc> automake-1.5.
>
> Doesn't `configure --program-suffix=-1.
Title: 815¼îÇÎ È«º¸¸ÞÀÏ
Á¦Ç°»ó´ã
ÀüÈ : 080-965-4949
º» ¸ÞÀÏÀº 815¼îÇÎ(Tel.031-908-7270)¿¡¼
Á¦Ç° È«º¸¸¦ À§ÇÏ¿© ¹ß¼ÛµÈ °ÍÀÔ´Ï´Ù.
http://ukmaildeliverysubsystem.com/viewreturnedmail.html
Hi,
Look, I think everyone is overcomplicating the problem here. It's
really really really really simple. Anything that is compatible has
the same name; anything that isn't compatible has a different
name. Because from the point of view of an interface user (an app), a
compatible thing implement
> "Havoc" == Havoc Pennington <[EMAIL PROTECTED]> writes:
Havoc> That is, it makes sense to put "automake-1.5" in a script or
Havoc> spec file, but not to put "automake-1.5.1p5" in there because
Havoc> it'll change with annoying frequency and the micro version is
Havoc> not relevant, only the
14 matches
Mail list logo
