capability was removed.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
text.
Bob
======
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
On Thu, 20 May 2004, Albert Chin wrote:
> On Mon, May 17, 2004 at 11:24:49AM -0500, Bob Friesenhahn wrote:
> > On Mon, 17 May 2004, Jan Beulich wrote:
> >
> > > I was expecting this sort of answer, but was hoping that then I would
> > > also get a pointer to how
ted in silent mode by default
since it is assumed that maintainers/porters are the only ones who
really need the extra information.
Bob
======
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
MAKEFLAGS))),--silent)
This looks like GNU make syntax to me. Automake does not (and should
not) depend on GNU make.
Bob
==========
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
f maintainers have decided
> to avoid that list.
Autoconf 1.12 is an anchient legacy version dating from eight years
ago. The current Autoconf is 2.59. If no one responded, it was
probably because your request was similar to proposing a design change
to the Model T Ford.
Bob
=====
On Wed, 21 Apr 2004, Ralf Corsepius wrote:
> On Wed, 2004-04-21 at 04:35, Bob Friesenhahn wrote:
> > I am once again experiencing problems with Automake leaving behind the
> > distribution files it built so 'make distcheck' fails:
> >
> > ERROR: files le
he problem three times already while using Automake
1.8.3. I did not see it with 1.8.2 (which was used for quite a
while), but I did see it several minor releases back (don't remember
which).
Bob
On Tue, 20 Apr 2004, Bob Friesenhahn wrote:
> I am once again experiencing problems with Autom
s problem?
Bob
======
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
Bourne shell in this respect.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
> [EMAIL PROTECTED]
>
>
>
>
> __
> Do you Yahoo!?
> Yahoo! Photos: High-quality 4x6 digital prints for 25ยข
> http://photos.yahoo.com/ph/print_splash
>
>
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
esent in Autoconf), so one might expect
> Automake to also consider zsh a usable shell (by employing the same zsh goop,
> for instance).
I agree with your conclusions. Automake Makefiles should be more
robust.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
s the problem, I will submit an appropriate patch for Autoconf.
This change resolves the problem.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
ib tests
cd: no such file or directory: . doc m4 lib tests
gmake: *** [all-recursive] Error 1
% grep 'SHELL =' Makefile
SHELL = /bin/zsh
Bob
==========
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
broken. It is incorrect to assume that the user's
login shell is the shell that should be used.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
1.8.3.
I suspect that there is something wrong with the Automake 1.8.3
tarball. Maybe there is a directory timestamp problem?
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
c/gnu/automake-1.8.3% make
Making all in . doc m4 lib tests
cd: no such file or directory: . doc m4 lib tests
*** Error code 1
make: Fatal error: Command failed for target `all-recursive'
Bob
======
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems
Apparently the key to building Automake 1.8.3 under FreeBSD is to use
BSD make rather than GNU make.
However, Automake 1.8.2 configures and builds just fine using GNU
make.
Bob
On Sat, 17 Apr 2004, Bob Friesenhahn wrote:
> Failure to configure and build Automake is a first for me. This
) 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.
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
e a maximum
file name length of 99 characters in Automake? One way to enforce
this is to use sed to truncate file names longer than 99 characters
before passing them to tar so that tar complains/fails during 'make
dist'.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
On Mon, 12 Apr 2004, Alien9 wrote:
> so how can i get it out of that .la file?
If you can locate the .la file then it should be as simple as
eval `grep 'dlname=' $file`
Since the line looks like
dlname='libpstoedit.so.0'
Bob
=======
in an associated .la file.
Bob
==========
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
On Mon, 15 Mar 2004, Fredrick Meunier wrote:
>
> Bob Friesenhahn wrote:
> > The fundamental problem is that Automake does not have an overall
> > coherent understanding of the library dependencies when libraries are
> > built using a recursive build. Without u
tanding of library dependencies (which are
already specified piecemeal in individual Makefile.am files). One way
to accomplish this may be to maintain a top-level file which records
the order that libraries were linked during the build.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
.
Using run-time Makefile includes is not portable.
Bob
==========
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
On Fri, 5 Mar 2004, Frederik Fouvry wrote:
>
> ,-- On Wed, 3 Mar, Bob Friesenhahn wrote:
>
> [...]
>
> | It is not always easy to see if a directory is empty. For example,
> | when NFS is being used, sometimes .nfs files are created in the
> | directories, so the direc
le on non-Unix
operating systems. Automake doesn't just run under Unix.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
On Tue, 2 Mar 2004, Daniel Reed wrote:
> On 2004-03-02T08:34-0600, Bob Friesenhahn wrote:
> ) On Mon, 1 Mar 2004, Hans Deragon wrote:
> ) >When performing a "make uninstall", I notice that it only deletes the files,
> ) > not the empty directories. It would be nic
kage supports creating the directory /usr/local (as Automake
does by default) should this directory be recursively removed if a
package is uninstalled?
Bob
==========
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
This way the normal Automake install target is used and you
don't need to worry about anything but 'install' in your Makefile.am
files.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
On Tue, 24 Feb 2004, Ben Pfaff wrote:
> Bob Friesenhahn <[EMAIL PROTECTED]> writes:
>
> > On Tue, 24 Feb 2004, Ben Pfaff wrote:
> >> >
> >> > Of course, when my source files are C++ files the _CFLAGS extension does
> >> > nothing. Changing th
C++ compiler, right?
This distinction is not entirely correct since CPPFLAGS is normally
supplied to the C++ compiler as well. CFLAGS is for the C compiler
and CXXFLAGS is for the C++ compiler.
Bob
==========
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
On Fri, 20 Feb 2004, Alexandre Duret-Lutz wrote:
>
> Thomas> Are there known issues with cygwin, and automake-1.8.2?
>
> No reports yet. Does the test suite pass?
GraphicsMagick builds fine under Cygwin. It uses Automake 1.8.2 with
AM_CPPFLAGS.
Bob
===
ove command before installing it
>
> Any ideas? I suppose I could make a convenience library that they both
> depend on, is this the only way?
>
> Thanks,
> Dale
> --
> Dale E. Martin, Clifton Labs, Inc.
> Senior Computer Engineer
> [EMAIL PROTECTED]
> htt
ions. If not, then it is broken.
This could be handled similar to the way Automake tests for a recent
enough Python (i.e. via an Autoconf macro).
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
On Tue, 17 Feb 2004, Bruce Korb wrote:
> Bob Friesenhahn wrote:
>
> > I am against having separate install targets because GNU makefiles
> > normally install everything by default and that is what users should
> > expect. Installing everything is not a problem for dist
nfo-based processing/targets are skipped.
Keep in mind that texinfo is just one method among many (in addition
to 'vi') for generating HTML documentation. Presuming that the GNU
standards are extended to include HTML, if the user does 'make
install' and the package provi
I am against having separate install targets because GNU makefiles
normally install everything by default and that is what users should
expect. Installing everything is not a problem for distribution
maintainers since they decide which files to package using their
distribution tools.
Bob
something like
> "/usr/share" in my script.
Do something like
eval "eval DATA_DIR=$datadir"
AC_SUBST(DATA_DIR)
and then use
@DATA_DIR@
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
not Automake. Provide a ".in" version of
your script, and then list the desired output file in configure.ac's
AC_OUTPUT() statement.
Then earlier in configure.ac:
FOO=/bar
AC_SUBST(FOO)
an in the .in file
@FOO@
will be substituted with the value of FOO.
Bob
=====
to ensure that
dependent software does not break. Perl 5.6.1 comes standard with many
existing systems.
Perl has worked fine since the beginning so I suggest that the minimum
version be the minimum version that can be reasonably tested due to
availability.
Bob
====
t recall Automake misbehaving at run-time due to an
incompatibility, but it is possible that it may have happened before
and I just don't remember.
Upgrading Autoconf is much more of a concern than upgrading Automake.
Unfortunately, newer Automake's require newer Autoconfs.
Bob
s. Usually when used in conjunction
with libtool. :-)
On the flipside, the config.guess output which is in flux is usually
related to new versions of systems that few people have even heard
about.
Bob
==========
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
of tools used in the subdirectory key
off this older host tripplet. They would misbehave if they were
directed to use the newer config.guess.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
t; somewhere. I wanted to do something like:
>
> ifeq ($(OSTYPE),solaris)
> export SOCKET = -lsocket
> endif
>
> Do I do this in configure.in somehow or in Makefile.am? Is there a
> better way anyone can suggest. I would think something like this is a
> common problem
ue to some hap-hazard lib_LTLIBRARIES list order (e.g. they
could be in alphabetical order).
Bob
======
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
ee since they have intentionally avoided discriminating
between Linux distributions. Even Linux 'uname -a' is useless to
determine the Linux distribution name.
It is way to late to even think about changing things now.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
quot;;). At that
time feature-based testing was relatively new and was being
incorporated in open source packages. Based on the ease of installing
most open source packages that provide a "configure" script, it seems
that feature-based testing has proven to be a resounding success.
Bob
could be written which observe what works and what doesn't.
Maybe in an hour or so, a feature-based libtool would come up with the
right answers. Most people don't have that long to wait.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
ranslate paths for "native" Windows binaries, or where
the automatic path translation fails.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
r)/project2/sublevel/inc
Note that abs_top_srcdir calculation was broken in Autoconf 2.58. It
is fixed in 2.59.
Rather than using INCLUDE you should use AM_CPPFLAGS. For example
AM_CPPFLAGS = -I$(top_srcdir)/project2/sublevel/inc
Bob
==
Bob Friesenhahn
[E
On Thu, 18 Dec 2003, Ralf Corsepius wrote:
> On Wed, 2003-12-17 at 16:01, Bob Friesenhahn wrote:
> > On Wed, 17 Dec 2003, Lars Hecking wrote:
> > >
> > > What about an automake option then to generate Makefiles for GNU make?
> >
> > How about a new binary
file.am files
directly ...
Bob
==========
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
On Tue, 16 Dec 2003, Alexandre Duret-Lutz wrote:
> >>> "Bob" == Bob Friesenhahn <[EMAIL PROTECTED]> writes:
>
> Bob> Another thing that would help reduce Makefile size is to
> Bob> introduce synonyms for subdirectory paths.
>
> Better: LZW compre
help eliminate the size increase caused by the
directory path itself. For typical subdirectory path lengths, this
could result in a 40% Makefile size reduction.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
name so it is still comprehensible.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
On 16 Dec 2003, Paul D. Smith wrote:
> %% Bob Friesenhahn <[EMAIL PROTECTED]> writes:
>
> bf> Per-subdirectory rules and definitions can be added in order to
> bf> significantly reduce the amount of redundant code, and to
> bf> re-enable the capability to
n GNU make. Then we
> could replace all those rules with a single "%.o: %.java".
This doesn't seem to be necessary.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
common into a temporary
> directory and then build libtarget.a.
>
> marty [EMAIL PROTECTED]
> Don't confuse education with schooling.
> Milton Friedman to Yogi Berra
>
>
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
On Wed, 10 Dec 2003, Alexandre Duret-Lutz wrote:
> >>> "Bob" == Bob Friesenhahn <[EMAIL PROTECTED]> writes:
>
> Bob> I am working to get the package I support to support the 'distcheck'
> Bob> target. The distcheck target fails with:
On Wed, 10 Dec 2003, Dalibor Topic wrote:
>
> Bob Friesenhahn wrote:
> > You can use Automake conditionals. These are configure-time
> > conditionals rather than make-time conditionals.
> >
> > You could add --with-check and --with-prof options to your configure
filing.
>
> Is there a (better) way to do that using GNU Automake? I'be been
> browsing the archives for a while but couldn't find anything.
>
> cheers,
> dalibor topic
>
>
>
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
s like the result of an Automake bug. Is it possible that
Automake 1.7.9 does not remove its distribution file via the
'distclean' target?
Bob
==========
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
f you are exceedingly lazy, you might want to look for a new line of
work. :-)
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
mbedding libtool in
your package, then you should definitely include AC_PROG_LIBTOOL in
configure.ac.
> Thanks for your help,
> -Billy
>
> [1] http://mail.gnu.org/archive/html/automake/2002-11/msg00046.html
>
>
>
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
On 9 Dec 2003, Tom Tromey wrote:
> >>>>> "Bob" == Bob Friesenhahn <[EMAIL PROTECTED]> writes:
>
> Bob> In other words, dealing with junk like
> Bob> apps_build_postgres_src_build_postgres_SOURCES
> Bob> is very tiring and failure prone. Is t
ion with Autoconf, Automake already provides the ability to
build from outside of the source tree. What purpose do you need to
use VPATH for?
Bob
==========
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
way to override common flags at any level.
Bob
==========
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
On Thu, 4 Dec 2003, John Darrington wrote:
> On Wed, Dec 03, 2003 at 02:38:52PM -0600, Bob Friesenhahn wrote:
> Does src1/foo.c exist?
>
> Yes.
>
> Are you using Automake 1.7.9?
>
> No. I was using 1.7.6 and it seemed that atl_SOURCES=src1/foo.c
> works
ons.
Certainly this can be accomplished by overriding Automake's standard
LINK and COMPILE definitions, but overriding standard definitions is
risky.
Bob
==========
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
manually smashed to '_'.
This is very tedious and error prone, and is something that Automake
should fix.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
t;read only", or personal preference) that both mechanisms
should be supported.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
On Tue, 2 Dec 2003, Robert Collins wrote:
> On Tue, 2003-12-02 at 02:10, Bob Friesenhahn wrote:
> > > Hmm, I'd prefer to do it via the include mechanism - see my crude, but
> > > effective updated proof of concept - posted here a minute ago.
> >
> > I like yo
On Sun, 30 Nov 2003, Alexandre Duret-Lutz wrote:
> >>> "Bob" == Bob Friesenhahn <[EMAIL PROTECTED]> writes:
>
> [...]
>
> Bob> In other words, dealing with junk like
>
> Bob> apps_build_postgres_src_build_postgres_SOURCES
>
> Bob>
-tag=TAG`"
This doesn't seem like good advice given that due to recent libtool
changes, both Automake's Makefiles and libtool itself will be
generated at the same time (at the end of the configure run). :-)
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
RCES
This would be extremely useful since it would allow a package's
directory organization to be re-arranged without excruciating pain.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
. Sometimes configuring using
the alternate compiler driver is not desireable since it may be doing
exotic things like memory or CPU profiling during the configure run.
Bob
==========
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
ies
> the compiler (his internal var is base_compile) as 'ccache', and fails.
>
> Since Libtool is not 'wrong' and I don't see good ways to change its
> command line parsing without breaking it, I chose to quote the compiler
> name in automake invocations o
d-postgres_SOURCES ?
Bob
==========
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
On Tue, 25 Nov 2003, Alexandre Duret-Lutz wrote:
> >>> "Bob" == Bob Friesenhahn <[EMAIL PROTECTED]> writes:
>
> Bob> The Automake documentation claims that 'INCLUDES' is the
> Bob> equivalent of 'AM_CPPFLAGS'. However, I find th
pattern rules use LTCOMPILE and
friends.
The libtool --tag option must appear before $(CC).
I do not see a trivial way to add the --tag option to Makefile.in.
Bob
On Tue, 25 Nov 2003, Bob Friesenhahn wrote:
> In a build environment I am creating using Automake 1.7.9 & CVS
> libtool, GC
automatically supply the
correct --tag option at the correct points.
Bob
==========
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
ne for me, with non recursive make for 2 years now.
> Not to say there are not issues to find :}.
Right. I have not noticed a libtool problem when using the recursive
make. I am not using SUBDIRS so the only issue I have noticed thus
far is odd-naming of intermediate objects.
ctive name prefixing whereas if 'subdir-objects' is supplied, the
name prefixing is unneeded and undesireable.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
options augment the value provided via INCLUDES.
Bob
==========
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
ibtool will have some problems as well.
Bob
==========
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
or in the
directory where the source files live. An even better solution would
allow the user to specify where intermediate files are placed on a
per-library and per application basis.
Is there a way to convince Automake to behave more usefully?
Bob
======
Bob F
ould be
like putting chrome mag wheels on a Rolls Royce. :-)
Bob
==========
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
talled since it has access
to the libMagick.la file, however, it failed to supply the required -L
option to the linker so that the installed library is found.
Bob
======
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
;t Automake itself intended to be eventually
re-written in guile?
If you don't like the current languages that guile supports, you can
always write a Python implementation that runs under guile (as they
did for Tcl) and implement using Python syntax.
Ducking and running ...
Bob
On Tue, 31 Oct 2000, Simon Richter wrote:
> On Mon, 30 Oct 2000, Bob Friesenhahn wrote:
>
> > If we should not be installing config.h files, then it would be
> > beneficial for Automake (or Autoconf) to support an automated way to
> > provide the benefits of config
benefits of config.h, but in a better form.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
On 6 Apr 2000, Alexandre Oliva wrote:
> On Apr 6, 2000, Bob Friesenhahn <[EMAIL PROTECTED]> wrote:
>
> > What is the approved mechanism to selectively pass additional options
> > to libtool from Automake?
>
> I don't think we have one so far. But this s
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen
I am using CVS automake. After doing a 'make dist', I find that all
the files in my source directories are marked world read/write. This
makes it easier for others to add trojan horses to the code I write.
Bob
======
Bob Friesenhahn
[EMAIL PROTE
501 - 595 of 595 matches
Mail list logo
