On 06 Apr 2023 02:34, Wu Zhenyu wrote:
> https://www.gnu.org/software/automake/manual/html_node/Python.html
> describe how to package python by automake. I have
>
> $ tree src/foobar
> src/foobar
> ├── __init__.py
> ├── __main__.py
> └── utils
>├── a.py
>
Excuse me:
https://www.gnu.org/software/automake/manual/html_node/Python.html
describe how to package python by automake. I have
$ tree src/foobar
src/foobar
├── __init__.py
├── __main__.py
└── utils
├── a.py
├── b.py
└── c.py
And my Makefil
On Thu, Dec 8, 2022, at 5:18 AM, aotto wrote:> Hi,
> I use "automake" to setup a "gnu make" build-environment and I have the
> following rule to create a special file:
> Problem: the "$(c_Meta)" failed with error but MAKE continue… why??
...
> $(csmkkernel_meta) $(csmqmsgque_meta) $(cslcconfig_met
Hi,
I use "automake" to setup a "gnu make" build-environment and I have the
following rule to create a special file:
Problem: the "$(c_Meta)" failed with error but MAKE continue… why??
=
csmkkernel_meta := $(srcdir)/.LibMkKernel_cs.meta
cs
And of course there's always meson + ninja, which are together rapidly
becoming the clear choice for new projects...
Assuming you're talking about interacting with the GNU make jobserver, I
suggest asking this question on the GNU make list[1], after reading the
relevant documentation on the jobserver[2].
There are other make implemetations (e.g. NetBSD make) which support
parallelism but probably use a
On Sep 21, 2019, at 9:55 PM, Nicholas Krause wrote:
>
> what is the easiest way to get this info into
> the gcc frontend.
I’m not seeing that this is an Automake topic. The output of Automake is a GNU
make file, which doesn’t control how you call “make”. Automake is on the other
side of that
Greetings,
I'm currently looking on and continuing the palleraling of gcc. There was
a discussion about if its possible to link to make -j to split the tasks if
possible. If so how and what is the easiest way to get this info into
the gcc frontend.
Thanks,
Nick
I have an existing project that appeared to work in the past on slackware.
I am trying to compile it on a modern Ubuntu system:
egoff@ubuntu:~/Perforce/bpsmain/main/tests/libdnet$ uname -a
Linux ubuntu 3.19.0-64-generic #72~14.04.1-Ubuntu SMP Fri Jun 24 17:59:48 UTC
2016 x86_64 x86_64 x86_64 GNU/
15.3.3.2 Log files generation and test results recording
:test-global-result:
This is used to declare the "global result" of the script. Currently,
the value of this field is needed only to be reported (more or less
verbatim) in the generated global log file $(TEST_SUITE_LOG), so it's quite
fre
with TESTS = perl_program and TESTS = perl_program
bash_script with the same result.
The basic question is how is the association between the compiler in
TESTS_ENVIRONMENT and the test program in TESTS made. In parallel processing
this association is made explicit using TEST_EXTENSIONS and t
I just constructed a test case to checkout how automake works and got the
errors below. The tests worked correctly in that and fail is a FAIL, a skip
a SKIP etc., so superficially there doesn't seem to be anything wrong.
As another (2) issues:
1: There seems be a lot of chatter when "make check" i
On 30 April 2015 at 23:01, Arthur Schwarz wrote:
>
> I'm trying figure out how the serial testing environment works and:
>
> If TESTS is defined in Makefile.am as
> TESTS = a.sh
>
> And the user changes it to:
>
>env TESTS="b.sh c.exe d.py e.pl" make -e check
>
> What happens?
>
Why not tr
I'm trying figure out how the serial testing environment works and:
If TESTS is defined in Makefile.am as
TESTS = a.sh
And the user changes it to:
env TESTS="b.sh c.exe d.py e.pl" make -e check
What happens?
Does this behavior change for the parallel interface?
Software Entropy: Main
> -Original Message-
> From: Gavin Smith [mailto:gavinsmith0...@gmail.com]
> Sent: Sunday, April 26, 2015 1:42 PM
> To: Arthur Schwarz
> Cc: Automake Mailing List
> Subject: Re: Question on --test-name=NAME
>
> > As a point, 15.3.3.1 Command-line arguments
> As a point, 15.3.3.1 Command-line arguments for test drivers shows all
> options as having the syntax "--option=value". Your example does not have
> this syntax. Will your example work? Should this be in the manual, as in
> "--option[=| ]value?"
I am sure that both should be supported although I
(thanks by the way)
> On 26 April 2015 at 18:39, Arthur Schwarz wrote:
> > Now for the case you mentioned in identifying a program, which is
> > really a test case renamed in the manual for mystifying and unknowable
> > reasons. Well, there is no mechanism for "The first non-option
> > argume
escribe how or what
> to do I guess we get to make it all up.
As I said before, they are not options typed in by a user invoking "make".
>
> In http://lists.gnu.org/archive/html/automake/2015-04/msg00022.html the
> question was asked as to how a program (test script) is to b
>
>
> -Original Message-
> From: Gavin Smith [mailto:gavinsmith0...@gmail.com]
> Sent: Sunday, April 26, 2015 9:03 AM
> To: Arthur Schwarz
> Cc: Automake Mailing List
> Subject: Re: Question on --test-name=NAME
>
> On 26 April 2015 at 16:30, Arthur Schwar
On 26 April 2015 at 16:30, Arthur Schwarz wrote:
>
>
> 15.3.3.1 Command-line arguments for test drivers
>
>--test-name=NAME
>
>The name of the test, with VPATH prefix (if any) removed. This can
> have a suffix and a directory component (as in e.g., sub/foo.test), and is
> mostly meant
15.3.3.1 Command-line arguments for test drivers
--test-name=NAME
The name of the test, with VPATH prefix (if any) removed. This can
have a suffix and a directory component (as in e.g., sub/foo.test), and is
mostly meant to be used in console reports about testsuite advancements and
On 25 April 2015 at 00:13, Arthur Schwarz wrote:
>
> 15.3.3.1 Command-line arguments for test drivers
>
> --color-tests={yes|no}
>
> Is 'always' an option? See 15.2.1 Scripts-based Testsuites
> "AM_COLOR_TESTS=always"
>From my reading, if AM_COLOR_TESTS=always, then --color-tests=yes will
be pas
15.3.3.1 Command-line arguments for test drivers
--color-tests={yes|no}
Is 'always' an option? See 15.2.1 Scripts-based Testsuites
"AM_COLOR_TESTS=always"
The failure of the past is the challenge of the present and the success of
the future.
cription.
> I'm also a bit confused about the use of env. Does this use mean that
> Makefile evaluates TEST_LOG_DRIVER by escaping to a shell? Otherwise,
> does Makefile do it's own interpretation of 'env'? the reason that I'm
> asking this question is that on
t in non-print formats, and
(b) change over time.
Section headings suffer from (b) too but to a much lesser degree.
This is important not only so that we can figure out what part of the
manual is being discussed today, but also so that 10+ years from now,
someone searching can find this ques
t in non-print formats, and
(b) change over time.
Section headings suffer from (b) too but to a much lesser degree.
This is important not only so that we can figure out what part of the
manual is being discussed today, but also so that 10+ years from now,
someone searching can find this ques
Automake manual pg. 120
Does anyone know where AM_TAP_AWK is defined and what it does?
Software Entropy: Maintenance
Hello,
I am quite new to the autotools and need help, not sure if this is an
autoconf or automake or something else question.
How does one handle application data with the autotools system?
More specifically, I have a test project with the following structure
test4
| - configure.ac
On Wed, Aug 13, 2014 at 04:17:51PM -0700, Arthur Schwarz wrote:
> I ran automake --add-missing then autoreconf and automake failed to find
> Changelog.
No, it failed to find ChangeLog.
> Makefile.am: error: required file './ChangeLog' not found
> autoreconf-2.69: automake failed with
Win 7
Cygwin
automake-1.14
I ran automake --add-missing then autoreconf and automake failed to find
Changelog.
Makefile.am: error: required file './ChangeLog' not found
autoreconf-2.69: automake failed with exit status: 1
Changelog (AUTHORS, NEWS ..) all exist in the directory th
Hi Thomas.
thanks for your reply.
On Thu, Jan 16, 2014 at 03:56:04PM +0100, Thomas Jahns wrote:
> ./libtool --mode=execute main/program
digging deeper, it looks like libtool cannot resolve this. it would have
to guess the location from where files in ${pkglibdir} have come. or
take some extra hi
Hello Felix,
not an automake issue, but...
On 01/16/14 13:02, Felix Salfelder wrote:
[rpath in uninstalled binary]
The normal mode of using libtool to run the binary with adjusted paths in
circumstances like yours is
./libtool --mode=execute main/program
Regards, Thomas
--
Thomas Jahns
DKRZ G
Hi there.
i have a problem with LTLIBRARY modules and the executables wrapper.
consider the following setup.
project/lib/Makefile.am
lib_LTLIBRARIES = library.la
project/plugins/Makefile.am
programdir = $(pkglibdir)
program_LTLIBRARIES = plugin.la
plugin_la_LDFLAGS = -module
project/main/Makef
Miles Bader wrote:
>songbird writes:
>>> That "extra stuff" is what will allow your package to work on the
>>> machines of your users without requiring them to have all the
>>> developer's tools you're using (autoconf, automake, aclocal, bison,
>>> flex).
>>
>> ok. i'm one of those people who ha
songbird writes:
>> That "extra stuff" is what will allow your package to work on the
>> machines of your users without requiring them to have all the
>> developer's tools you're using (autoconf, automake, aclocal, bison,
>> flex).
>
> ok. i'm one of those people who hates extra
> files being l
sence of developer-specific tools. This is not the case with your
> distribution tarball.
ok, i will leave it alone then. out comes the
dist-hook.
>> except now distcheck doesn't work.
>>
> And rightly so -- it is basically informing you that your 'dist-hook'
es
> nothing at all, that's not the important part
> at the moment in this trail of learning, i'm
> just examining the build environment and making
> sure it configures, compiles, dists, etc. correctly.
>
>
> my question? it's at the end, but to be compl
rning, i'm
just examining the build environment and making
sure it configures, compiles, dists, etc. correctly.
my question? it's at the end, but to be complete
i include background and development.
i've used a small tutorial that is part of an
online book at:
http://so
Dave Hart wrote on 2011/12/05 19:17:26:
> On Mon, Dec 5, 2011 at 17:33, Joakim Tjernlund
> wrote:
> > One thing that would go a long way is if one could do something like this:
> > make install eq_ss
> > and have make just install what is in the eq_ss directory
>
> As long as subdirectories of e
On Mon, Dec 5, 2011 at 17:33, Joakim Tjernlund
wrote:
> One thing that would go a long way is if one could do something like this:
> make install eq_ss
> and have make just install what is in the eq_ss directory
As long as subdirectories of eq_ss are intended to be installed as well:
cd eq_ss
m
"Ralf Wildenhues" wrote on 2011/12/05 17:27:35:
>
> Hello Joakim,
>
> * Joakim Tjernlund wrote on Wed, Nov 30, 2011 at 08:11:31AM PST:
> > Question: "make install" always install all targets, even if some of then
> > haven't been rebuilt
&g
Hello Joakim,
* Joakim Tjernlund wrote on Wed, Nov 30, 2011 at 08:11:31AM PST:
> Question: "make install" always install all targets, even if some of then
> haven't been rebuilt
> since last install. Is it possible to have some dependency sensitive install
> so
s not installed if
$(bindir) expands to the empty string. This should not depend on wheteher
we are doing a "normal" install or a "DESTDIR" install.
> Question: "make install" always install all targets, even if some of
> then haven't been rebuilt since last i
On 11/30/11 11:11 AM, Joakim Tjernlund wrote:
Question: "make install" always install all targets, even if some of then
haven't been rebuilt
since last install. Is it possible to have some dependency sensitive install so
only rebuilt
targets are reinstalled?
Hi Jocke,
In one o
Noticed this in my automake(1.10.3) generated Makefile:
install-binPROGRAMS: $(bin_PROGRAMS)
@$(NORMAL_INSTALL)
test -z "$(bindir)" || $(MKDIR_P) "$(DESTDIR)$(bindir)"
Should not that be: test -z "$(DESTDIR)$(bindir)" || $(MKDIR_P)
"$(DE
Ralf,
I'm running into the same issue reported:
http://lists.gnu.org/archive/html/automake/2010-10/msg00063.html
I was wondering if automake could do things a little differently to deal with
this issue more graceful:
Today we have something like the following in configure:
pax)
am__tar=
On 11/08/2010 03:03 PM, Dave Hart wrote:
On Mon, Nov 8, 2010 at 6:56 AM, xufeng zhang wrote:
On 10/30/2010 03:37 PM, Ralf Wildenhues wrote:
I don't think there is much that can be done about this in Automake, as
[...]
If you still think that Automake is in the position
On Mon, Nov 8, 2010 at 6:56 AM, xufeng zhang wrote:
> On 10/30/2010 03:37 PM, Ralf Wildenhues wrote:
>> I don't think there is much that can be done about this in Automake, as
[...]
>> If you still think that Automake is in the position to do something
>> about this, then please provide more detai
On 10/30/2010 03:37 PM, Ralf Wildenhues wrote:
Hello Xufeng Zhang,
thanks for the report.
* xufeng zhang wrote on Wed, Oct 27, 2010 at 05:24:18AM CEST:
I'm a developer from WindRiver, and I have a question about automake.
When I using a large UID/GID(>2097151) to configure and
Hello Xufeng Zhang,
thanks for the report.
* xufeng zhang wrote on Wed, Oct 27, 2010 at 05:24:18AM CEST:
> I'm a developer from WindRiver, and I have a question about automake.
> When I using a large UID/GID(>2097151) to configure and build a
> linux project,
> gnu tar fails
Hi,
I'm a developer from WindRiver, and I have a question about automake.
When I using a large UID/GID(>2097151) to configure and build a linux
project,
gnu tar fails and automake select pax as a replacement. However,
automake seems
fail to pass the correct parameters to pax(we are usi
Hello Chase,
* Maupin, Chase wrote on Fri, Sep 24, 2010 at 03:25:21PM CEST:
> Hopefully someone here can clarify the automake licensing for me. I
> am looking at the sources for automake version 1.11.1 and I noticed
> that there appears to be two licenses in the sources.
>
> At the top-level dir
All,
Hopefully someone here can clarify the automake licensing for me. I am looking
at the sources for automake version 1.11.1 and I noticed that there appears to
be two licenses in the sources.
At the top-level directory the COPYING file says that the license is GPLv2 and
I do not see the "o
y but the .directive.asc with my old key?
>
> I don't know the answer to this. But I think this is a policy question
> that FTP masters and/or GNU should address, and if the additional
> freedom is ok then gnupload can add the functionality.
I tried. It doesn't. My up
ctive.asc be created with the same key, or does it only validate
> the directive, in which case I could manually create a .sig with my new
> key but the .directive.asc with my old key?
I don't know the answer to this. But I think this is a policy question
that FTP masters and/or GNU shoul
I'm in the interesting situation of trying to upload autoconf 2.67
signed by my new key, but while still waiting for my new key to be
installed by the ftp-upload folks to run the upload process (see
http://lists.gnu.org/archive/html/autoconf/2010-07/msg00016.html).
Right now, gnupload assumes that
Hello David,
* David Bond wrote on Tue, Apr 27, 2010 at 07:54:02PM CEST:
> I'm working on a project that we are converting to autotools and I
> had a question. If this is the wrong place to ask these please
> direct me to the right location.
This is the right place to ask, but
Hello,
I'm working on a project that we are converting to autotools and I had
a question. If this is the wrong place to ask these please direct me
to the right location.
Our project has a particle feature with three posible states:
STATIC, DYNAMIC, or NONE
Ideally we would like the bui
Hello Ed,
* Ed Hartnett wrote on Fri, Apr 02, 2010 at 07:15:34PM CEST:
> We don't want all this to happen when the user builds netcdf, so I have
> a line in the Makefile.am:
>
> # These files will be included with the dist.
> EXTRA_DIST = netcdf.m4 $(pdf_docs) $(html_mans) $(txt_docs) $(dvi_docs)
Howdy all!
I am maintaining a free software package called netCDF, which provided
array-oriented data access for Earth scientists. I use automake to build
netcdf.
But one little problem is in the documentation directory. Most of our
documentation come from .texi files, but we all have some man pa
Hello Andreas,
* Andreas Otto wrote on Wed, Nov 25, 2009 at 10:39:54AM CET:
> I have integrated an subpackage into an already existing package
> everything works well but one problem still exists
>
> the debugging feature is turned on in the toplevel package with
> --enable-symbols and in t
Hi,
I have integrated an subpackage into an already existing package
everything works well but one problem still exists
the debugging feature is turned on in the toplevel package with
--enable-symbols and in the subpackage with --enable-debug
some kind of translation is necessary
Andreas Otto wrote:
is a "builddir" other than "." possible ?
No
http://www.gnu.org/software/autoconf/manual/autoconf.html#Preset-Output-Variables
--
Peter Johansson
svndigest maintainer, http://dev.thep.lu.se/svndigest
yat maintainer, http://dev.thep.lu.se/yat
Hi,
is a "builddir" other than "." possible ?
mfg
aotto1968
On Mon, 2009-10-05 at 21:53 +0200, Ralf Wildenhues wrote:
> Hello Gaetan,
>
> * Gaetan Nadon wrote on Fri, Oct 02, 2009 at 08:30:51PM CEST:
> >
> > Our components use "foreign" and "dist-bzip2" options. We distribute the
> > tarballs. When running distclean, the tarballs are not removed from the
Hello Gaetan,
* Gaetan Nadon wrote on Fri, Oct 02, 2009 at 08:30:51PM CEST:
>
> Our components use "foreign" and "dist-bzip2" options. We distribute the
> tarballs. When running distclean, the tarballs are not removed from the
> build tree. This is not a problem for us. I was wondering if this is
Our components use "foreign" and "dist-bzip2" options. We distribute the
tarballs. When running distclean, the tarballs are not removed from the
build tree. This is not a problem for us. I was wondering if this is a
conscious design decision or an omission.
The reason for asking is the behaviour
Sorry - I forgot to give the relative path in the pic_DATA variable
below - here's the corrected version:
picdir = $(datadir)/pics # assuming you want png's installed in
/usr/local/share/pics
pic_DATA = pics/mypicture.png
Hi David,
On 8/11/2009 7:28 AM, David Liebman wrote:
Hello,
This is a newbie question.
I have a simple project that I'm using automake and autoconf on. It
involves a simple c program, but uses a png image. The png image is in a
directory called 'pics' and I want it copi
Hello,
This is a newbie question.
I have a simple project that I'm using automake and autoconf on. It
involves a simple c program, but uses a png image. The png image is in a
directory called 'pics' and I want it copied to a certain directory on
the system when the user cal
Hello Jerry,
* Jerry Wang wrote on Wed, Jul 01, 2009 at 06:00:24PM CEST:
> Has the if/else statement always been supported by automake?
Conditionals first appeared in version 1.2 from 1997, and else/endif
in 1.5 from 2001. However, several features need special handling for
being able to appear
Hi,
Has the if/else statement always been supported by automake? - I have 2
machines with the same source code, 1 has an older version of automake, and
it's failing to build at the if/else statement.
Thanks,
Jerry
Jan Engelhardt writes:
> I reckon that %-style suffix rules (e.g. "%.o: %.c") are rather
> unportable, but I wonder how the old-fashioned suffix rule for
>
> %.1: %.1.php
>
> would look like.
There is none. A suffix rule can contain at most two periods, so the
closest you can get is this:
.ph
Hi,
I reckon that %-style suffix rules (e.g. "%.o: %.c") are rather
unportable, but I wonder how the old-fashioned suffix rule for
%.1: %.1.php
would look like.
Hello,
guys, let's please cut this off at this point. I don't like
top-posting, I don't like it if people don't trim their replies to
only quote what they address. I spend very little time reading most
messages, and am very likely to just drop those that are sloppily
written, unreadable, un-unde
I'll enforce top-posting from this side of Atlantic ;)
Don't worry.
Bob Friesenhahn <[EMAIL PROTECTED]> - Wed, 8 Oct 2008
14:56:39 -0500 (CDT)
>It seems that some folks on this list just can't help but retain all
>previous content from the discussion thread and put their few lines at
>the bott
It seems that some folks on this list just can't help but retain all
previous content from the discussion thread and put their few lines at
the bottom of the new email. This requires paging down five or six
screens of text just to find the tiny tidbit which was added.
There is only so much ti
Michel Briand wrote:
Sorry for the confusion ! Its my fault
I would not have chosen "VERSION" for my variable in Makefile.am since
it duplicates one predefined variable (configure).
I should have named it "MY_VERSION", or better
"TRAINING_PROGRAM_VERSION"
The variable is dynamic. Make w
;>>
>>>> c) Integration step finishes well and we are ok to release. But we'll
>>>> keep the generated files (object, executable) in configuration. So we
>>>> don't want to rebuild the tree after all tests have passed. So we do
>>>> not w
sion since it's
embedded. So I've a dependency to relink it.
Is my explanation enough clear/detailed ?
Ok. Got your point. One question though. Where do you read the file
PROGRAM_VERSION?
Is the info in PROGRAM_VERSION somehow propagated through variable
$(VERSION)? But I t
ep the generated files (object, executable) in configuration. So we
>> don't want to rebuild the tree after all tests have passed. So we do
>> not want to change the PROGRAM_VERSION if we know that it'll change
>> config.h => rebuilt the tree...
>>
>> The
27;s
embedded. So I've a dependency to relink it.
Is my explanation enough clear/detailed ?
Ok. Got your point. One question though. Where do you read the file
PROGRAM_VERSION?
Is the info in PROGRAM_VERSION somehow propagated through variable
$(VERSION)? But I thought $(VERSION) always was set in AC_INIT?
Cheers,
Peter
Peter Johansson <[EMAIL PROTECTED]> - Tue, 07 Oct 2008 11:21:26 -0400
>Hello Michel,
>
>Michel Briand wrote:
>> Hi all,
>>
>> I implemented a new idea for program's version.
>>
>> In src/bin/Makefile.am:
>>
>> internal_version.c: ${top_srcdir}/PROGRAM_VERSION
>> ${top_srcdir}/vtempl.pl $(com
Hello Michel,
Michel Briand wrote:
Hi all,
I implemented a new idea for program's version.
In src/bin/Makefile.am:
internal_version.c: ${top_srcdir}/PROGRAM_VERSION
${top_srcdir}/vtempl.pl $(component) $(VERSION) < $(templ) > $@
training_SOURCES = training.c internal_version.c
The v
Hi all,
I implemented a new idea for program's version.
In src/bin/Makefile.am:
internal_version.c: ${top_srcdir}/PROGRAM_VERSION
${top_srcdir}/vtempl.pl $(component) $(VERSION) < $(templ) > $@
training_SOURCES = training.c internal_version.c
The vtempl.pl Perl program takes a template
Ralf Wildenhues <[EMAIL PROTECTED]> - Mon, 29 Sep 2008 13:19:32
+0200
...
>* Michel Briand wrote on Mon, Sep 29, 2008 at 10:34:20AM CEST:
>> Ralf Wildenhues <[EMAIL PROTECTED]> - Mon, 29 Sep 2008 08:34:09 +0200
>> >* Michel Briand wrote on Sun, Sep 28, 2008 at 11:04:36AM CEST:
>> >> $ make
>> >>
Hello Michel,
* Michel Briand wrote on Sun, Sep 28, 2008 at 11:04:36AM CEST:
> an error that's wonder me :
>
> $ make
> cd . && /bin/bash /home/michel/svn/exc/autotraining/config/missing --run
> aclocal-1.10 -I m4
> aclocal-1.10: couldn't open directory `m4': Aucun fichier ou répertoire de ce
>
ig'.
>> > >
>> > > I do not use the macro you mention.
>> >
>> > Please do, though. When you do, please also add
>> > ACLOCAL_AMFLAGS = -I m4
>> >
>> > to the toplevel Makefile.am.
>>
>> ... which brings up a que
Hello Michael,
Michel Briand wrote:
Peter Johansson <[EMAIL PROTECTED]> - Wed, 27 Aug 2008 10:50:48 -0400
Michel Briand wrote:
::
src/lib/Makefile.am
::
# Library: libtraining
# Generates its own pkg-config definition file
AM_CPPFLAGS = -DLIBRARY_VERSION=\"$(L
Peter Johansson <[EMAIL PROTECTED]> - Wed, 27 Aug 2008 10:50:48 -0400
>Michel Briand wrote:
>>
::
src/lib/Makefile.am
::
# Library: libtraining
# Generates its own pkg-config definition file
AM_CPPFLAGS = -DLIBRARY_VERSION=\"$(LIBRARY_VER
I will discuss the issue with the Automake maintainer. I have never
used Automake myself, so I don't know the issues.
One fact I can see is that this is just a matter of defaults, and
doesn't stop users from doing whatever they want. Please don't
exaggerate.
Making Automake have different defau
is good to discuss and consider how automake
should best work.
The question is: do we need to cater for people who both don't read the
documentation and don't take care of writing a COPYING file themselves?
(Yes, this is a bit pointed.)
Basically, I agree that is the question. However I
ee
>>> software community.
>>
>> That to me really sounds a bit over the top. Given there are very easy
>> ways to avoid this, and given that the current mode of operation is
>> documented very clearly,
>
> While I do agree that it is documented reasonably, man
-editor is GPLv3 or the actual
license as specified in the source files? This seems confusing.
This is a question for a lawyer, not for this list. I agree that it's
confusing, but note that there should be both: the license file, and the
copyright notices at the top of each source file.
fusing.
This is a question for a lawyer, not for this list. I agree that it's
confusing, but note that there should be both: the license file, and the
copyright notices at the top of each source file. It is not uncommon
that source trees have files with differing (compatible) licenses, and
carr
Ralf,
Thanks. I have removed my own htmldir definition, and it works now.
Thanks,
> Date: Wed, 3 Sep 2008 22:53:49 +0200
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> CC: automake@gnu.org
> Subject: Re: question about htmldir
>
> Hello Susan,
>
> * sus
Hi, Ralf,
When I use automake command, I got the following error message:
automake
doc/Makefile.am:12: htmldir was already defined in condition TRUE, which
includes condition DOXYGEN ...
configure.ac:5: ... `htmldir' previously defined here
But in configure.ac:5 (line): A C_INIT(SOFT, 1.0, [E
Hello Susan,
* susan xie wrote on Wed, Sep 03, 2008 at 10:05:59PM CEST:
> When I use automake command, I got the following error message:
>
> automake
> doc/Makefile.am:12: htmldir was already defined in condition TRUE, which
> includes condition DOXYGEN ...
> configure.ac:5: ... `htmldir' prev
* Braden McDaniel wrote on Wed, Aug 27, 2008 at 08:45:56PM CEST:
> Ralf Wildenhues wrote:
>> * Braden McDaniel wrote on Wed, Aug 27, 2008 at 08:48:45AM CEST:
>>> ... which brings up a question I have: Why doesn't AC_CONFIG_MACRO_DIR
>>> eliminate the need for
+0200
Why '-I config -I m4'? AFAICS you do not use AC_CONFIG_MACRO_DIR([m4])
in configure.ac. I'd use that, and drop '-I config'.
I do not use the macro you mention.
Please do, though. When you do, please also add
ACLOCAL_AMFLAGS = -I m4
to the toplevel Makefile.am.
1 - 100 of 378 matches
Mail list logo
