On Fri, 20 Jun 2025 06:01:00 +0200,
Brad Smith wrote:
>
> Here is a port for automake 1.18.
> [2 automake-1.18.tgz ]
Tested on -current/amd64.
Patches looks the same with 1.17;
It builds, installs.
`make test` had almost similar with 1.17 resul
Here is a port for automake 1.18.
automake-1.18.tgz
Description: application/tar-gz
automake has supported Python 3 since version 1.11. Our continued use of
Python 2 is unnecessary.
I sent this diff out about a year and Stuart okay'ed it back then but I
never committed it. (I only did the bits for earlier automake versions).
I'm aiming to commit this in the nex
On 2025/01/09 13:47, Kirill A. Korinsky wrote:
> On Tue, 31 Dec 2024 00:53:59 +0100,
> Kirill A. Korinsky wrote:
> >
> > ports@,
> >
> > I just noticed that automake-1.17 was released about 6 months ago.
> > I'd like to import it.
> >
> > An
On Tue, 31 Dec 2024 00:53:59 +0100,
Kirill A. Korinsky wrote:
>
> ports@,
>
> I just noticed that automake-1.17 was released about 6 months ago.
> I'd like to import it.
>
> Announce and changes:
> https://lists.gnu.org/archive/html/autotools-announce/2024-07/msg00
31.12.2024 15:42, Kirill A. Korinsky пишет:
> Yay, thanks for notice it! Replaced 1.16 to 1.17
OK kn
On Tue, 31 Dec 2024 13:28:06 +0100,
Stuart Henderson wrote:
>
> On 2024/12/31 00:53, Kirill A. Korinsky wrote:
> > ports@,
> >
> > I just noticed that automake-1.17 was released about 6 months ago.
> > I'd like to import it.
> >
> > Announce and
On 2024/12/31 00:53, Kirill A. Korinsky wrote:
> ports@,
>
> I just noticed that automake-1.17 was released about 6 months ago.
> I'd like to import it.
>
> Announce and changes:
> https://lists.gnu.org/archive/html/autotools-announce/2024-07/msg0.html
>
>
ports@,
I just noticed that automake-1.17 was released about 6 months ago.
I'd like to import it.
Announce and changes:
https://lists.gnu.org/archive/html/autotools-announce/2024-07/msg0.html
I had tested it with some random ports which uses automake, and haven't find
any
On 2024/12/08 15:33, Kirill A. Korinsky wrote:
> On Sun, 08 Dec 2024 09:43:02 +0100,
> Brad Smith wrote:
> >
> > Looking at newer automake I noticed the autoconf version should have
> > been bumped with the 1.16.4 release.
..
> > -AUTOCONF_VERSION= 2.6
On Sun, 08 Dec 2024 09:43:02 +0100,
Brad Smith wrote:
>
> Looking at newer automake I noticed the autoconf version should have
> been bumped with the 1.16.4 release.
>
>
> Index: Makefile
> ===
> RC
Looking at newer automake I noticed the autoconf version should have
been bumped with the 1.16.4 release.
Index: Makefile
===
RCS file: /cvs/ports/devel/automake/1.16/Makefile,v
retrieving revision 1.9
diff -u -p -u -p -r1.9
The automake NEWS file says that Python 3 has been supported since 1.11,
so switch the TDEPs in 1.11+ versions from Python2 to Python3.
For the 1.8, 1.9, and 1.10 releases, just switch the TDEPs too and let's
not worry about the Python test failures. These older automake versions
have a
The build logs show many instances of this warning:
Unescaped left brace in regex is deprecated here (and will be
fatal in Perl 5.30)
This fixes automake-1.1[0-4]. Newer versions already have the fix,
older ones don't have this code.
ok?
Index: 1.10/Mak
Oh yes yes yes please :-)
I will work on an autoreconf style at g2k19.
—
Antoine
> On 2 Apr 2019, at 15:33, Christian Weisgerber wrote:
>
> I would like to remove CONFIGURE_STYLE="automake". This is a very
> confusing setting. Crucially, it does not actually run a
OK
On 2019/04/02 15:33, Christian Weisgerber wrote:
> I would like to remove CONFIGURE_STYLE="automake". This is a very
> confusing setting. Crucially, it does not actually run automake.
> Nobody I've talked to understands it or what its point is. Today
> I have remove
I would like to remove CONFIGURE_STYLE="automake". This is a very
confusing setting. Crucially, it does not actually run automake.
Nobody I've talked to understands it or what its point is. Today
I have removed the few remaining uses in the tree.
There are two patches attache
OK
On Sun, January 13, 2019 15:57, Rafael Sadowski wrote:
> On Sat Jan 12, 2019 at 11:09:30PM +0300, Kirill Bychkov wrote:
>> Hi!
>> automake-1.16 fails to build with MAKE_JOBS set in mk.conf
>> with the following error:
>>
>> : && mkdir -p doc &
On Sat Jan 12, 2019 at 11:09:30PM +0300, Kirill Bychkov wrote:
> Hi!
> automake-1.16 fails to build with MAKE_JOBS set in mk.conf
> with the following error:
>
> : && mkdir -p doc && ./pre-inst-env /usr/bin/perl ./doc/help2man
> --output=doc/aclocal-1.16.1
Hi!
automake-1.16 fails to build with MAKE_JOBS set in mk.conf
with the following error:
: && mkdir -p doc && ./pre-inst-env /usr/bin/perl ./doc/help2man
--output=doc/aclocal-1.16.1 aclocal-1.16
: && mkdir -p doc && ./pre-inst-env /usr/bin/perl ./doc/help2
Here is a port for automake 1.14.
OK?
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
automake-1.14.tar.gz
Description: application/tar-gz
69: error: AC_CONFIG_HEADERS not found in configure.ac
> /usr/local/bin/automake[35]: /usr/local/bin/automake-1.12: not found
> I am going to run ./configure with no arguments - if you wish
> to pass any to it, please specify them on the ./autogen.sh command line.
> configure: error: canno
0: error: possibly undefined macro: AC_FIND_XFT
configure.ac:281: error: possibly undefined macro: AC_IMAGE_SUPPORT
autoheader-2.69: error: AC_CONFIG_HEADERS not found in configure.ac
/usr/local/bin/automake[35]: /usr/local/bin/automake-1.12: not found
I am going to run ./configure with no arguments
On Sun, Jun 24, 2012 at 06:06:30PM -0400, Brad Smith wrote:
> On Sun, Jun 24, 2012 at 05:27:18PM +0200, Matthieu Herrb wrote:
> > Hi,
> >
> > Automake 1.10 used to call various shell scripts (mostly the infamous
> > install-sh one) without an explicit /bin/sh in fron
On Sun, Jun 24, 2012 at 05:27:18PM +0200, Matthieu Herrb wrote:
> Hi,
>
> Automake 1.10 used to call various shell scripts (mostly the infamous
> install-sh one) without an explicit /bin/sh in front of them, which
> caused Xenocara builds to fail, since no shell script in /us
Hi,
Automake 1.10 used to call various shell scripts (mostly the infamous
install-sh one) without an explicit /bin/sh in front of them, which
caused Xenocara builds to fail, since no shell script in /usr/xenocara
is supposed to have the 'x' bit set (since OpenBSD doesn't want fi
On Fri, 23 Mar 2012, Jeremy C. Reed wrote:
> Can someone please explain how
> ports/devel/automake/1.11/patches/patch-lib_am_header-vars_am works with
> /usr/local/share/aclocal-1.11/install-sh.m4 (note that it results in
> ${SHELL} ${SHELL
Can someone please explain how
ports/devel/automake/1.11/patches/patch-lib_am_header-vars_am works with
/usr/local/share/aclocal-1.11/install-sh.m4 (note that it results in
${SHELL} ${SHELL} install-sh)?
revision 1.1
date: 2011/05/18 19:38:15; author: matthieu
Here is an update to automake 1.11.3.
Tested with everything in the tree using 1.11.
Index: Makefile
===
RCS file: /home/cvs/ports/devel/automake/1.11/Makefile,v
retrieving revision 1.5
diff -u -p -r1.5 Makefile
--- Makefile20
On Sat, Mar 12, 2011 at 01:40:16PM -0500, Brad wrote:
> On Sat, Mar 12, 2011 at 06:27:28PM +, Stuart Henderson wrote:
> > On 2011/03/12 12:45, Brad wrote:
> > > I noticed the automake python macro does not know how to find
> > > Python 2.6. Here is a patch to fi
Here is the same change Matthieu mentioned in this thread brought over
to automake 1.8..
http://marc.info/?l=openbsd-ports&m=130552728727077&w=2
Index: Makefile
===
RCS file: /home/cvs/ports/devel/automake/1.8/Makefile,v
re
On Mon, May 16, 2011 at 08:24:49AM +0200, Matthieu Herrb wrote:
> On Sun, May 15, 2011 at 06:55:34PM -0400, Brad wrote:
> > On 15/05/11 5:55 PM, Matthieu Herrb wrote:
> > >Similar patches should be added to automake 1.10 and 1.11
> > >
> > >ok?
> >
> &
On 16/05/11 2:24 AM, Matthieu Herrb wrote:
On Sun, May 15, 2011 at 06:55:34PM -0400, Brad wrote:
On 15/05/11 5:55 PM, Matthieu Herrb wrote:
Similar patches should be added to automake 1.10 and 1.11
ok?
No, do as you said above first.
What do you mean? submit the patches for automake 1.10
On Sun, May 15, 2011 at 06:55:34PM -0400, Brad wrote:
> On 15/05/11 5:55 PM, Matthieu Herrb wrote:
> >Similar patches should be added to automake 1.10 and 1.11
> >
> >ok?
>
> No, do as you said above first.
What do you mean? submit the patches for automake 1.10 and 1
On 15/05/11 5:55 PM, Matthieu Herrb wrote:
Similar patches should be added to automake 1.10 and 1.11
ok?
No, do as you said above first.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Hi,
since we avoid/ban executable files in CVS, the install-sh scripts in
/usr/xenocara are supposed not to be executable.
An upcoming update of libX11 to 1.4.2 uses automake features that makes it
use ${install_sh_DATA} to install stuff. This fails when install-sh is not
executable.
The
quot;Useless use of /d modifier in transliteration operator at
>>> /usr/local/share/automake-1.9/Automake/Wrap.pm line 60."
>>> that often appears during port builds.
>>
>> Groovy & ok ! Since you're there, can you also fix that :) ?
>> checking f
On Thu, May 5, 2011 at 1:17 PM, Landry Breuil wrote:
> On Thu, May 05, 2011 at 03:49:39AM -0600, David Coppa wrote:
>>
>> Hi,
>>
>> Fix the following warning caused by perl 5.11:
>> "Useless use of /d modifier in transliteration operator at
>> /usr/lo
On Thu, May 05, 2011 at 03:49:39AM -0600, David Coppa wrote:
>
> Hi,
>
> Fix the following warning caused by perl 5.11:
> "Useless use of /d modifier in transliteration operator at
> /usr/local/share/automake-1.9/Automake/Wrap.pm line 60."
> that often appears d
Hi,
Fix the following warning caused by perl 5.11:
"Useless use of /d modifier in transliteration operator at
/usr/local/share/automake-1.9/Automake/Wrap.pm line 60."
that often appears during port builds.
Also here, upstream git:
http://git.savannah.gnu.org/gitweb/?p=automake.git;
On Sat, Mar 12, 2011 at 06:27:28PM +, Stuart Henderson wrote:
> On 2011/03/12 12:45, Brad wrote:
> > I noticed the automake python macro does not know how to find
> > Python 2.6. Here is a patch to fix this.
>
> I think it would make sense to check for 2.7 as well..
I
On 2011/03/12 12:45, Brad wrote:
> I noticed the automake python macro does not know how to find
> Python 2.6. Here is a patch to fix this.
I think it would make sense to check for 2.7 as well..
I noticed the automake python macro does not know how to find
Python 2.6. Here is a patch to fix this.
Index: 1.10/Makefile
===
RCS file: /home/cvs/ports/devel/automake/1.10/Makefile,v
retrieving revision 1.7
diff -u -p -r1.7
Hello,
has anyone a port of automake 1.11?
Regards,
Markus
Hello all.
Does anyone have a port(-s) for autoconf 2.63+ and/or automake 1.10+? I
have a few ports here that want them, some work with autoconf 2.62 (with
many warnings in configure stage, of course), some require 2.65 and/or
automake 1.10+. Sometimes I have to patch Makefile.in instead of
hmm, on Mon, Feb 01, 2010 at 03:29:47PM +0100, frantisek holop said that
> is someone working on automake 1.10+?
> some newer ports seem to require it.
hi there,
here is a work in progress for automake 1.11 against autoconf 2.62.
the next step could be upgrading autoconf to 2.65 but
i go
hi there,
is someone working on automake 1.10+?
some newer ports seem to require it.
-f
--
and god said, e = 1/2mv^2 - ze^2/r, and there was light.
Hi,
My favourite project (X.Org) is going to require automake 1.11 at some
point in the near future. We'll need a port for it. So I'm calling for
help here.
As a start, could the one who already looked at that speak up and list
the issues?
--
Matthieu Herrb
On Thu, Jul 23, 2009 at 02:52:29PM -0400, Frederick C Druseikis wrote:
> Hi,
>
> By chance does anyone have a working port of automake 1.10.2 (which would be
> the last version before 1.11.x series) ? I need this for a port of cacao
> jvm.
>
> Doing something easy and
Hi,
By chance does anyone have a working port of automake 1.10.2 (which would be
the last version before 1.11.x series) ? I need this for a port of cacao
jvm.
Doing something easy and obvious based on the existing port of automake 1.9
yields the dreaded "unrequested stack trace".
Regards,
Fred
This allows working on newer Automake ports, e.g. 1.10.2.
- Patch automake-1.9.info to be in line with other versions, and
do not conflict with Automake 1.10 and newer.
- Bump PKGNAME.
Index: Makefile
===
RCS file: /cvs/ports/devel
Tim van der Molen [Sun, Mar 30, 2008 at 06:10:29PM +0200] wrote:
>Hello,
>
>It seems the recent update to metaauto-0.8 breaks
>automake-1.9.6p2:
>
>[EMAIL PROTECTED]:/usr/ports/devel/automake/1.9 $ make configure
>[...]
>checking whether autoconf is installed... no
>conf
Hello,
It seems the recent update to metaauto-0.8 breaks
automake-1.9.6p2:
[EMAIL PROTECTED]:/usr/ports/devel/automake/1.9 $ make configure
[...]
checking whether autoconf is installed... no
configure: error: Autoconf 2.58 or better is required.
Please make sure it is installed and in your
that
directory. On OpenBSD, this variable ends up being install_sh -d, which does
not copy at all with race conditions.
The sad part is the automake test. If you look closely at the generated
configure, you'll see it goes to great length to try to ensure that
mkdir -p -- directory does the
On Tue, Mar 27, 2007 at 08:51:52AM -0500, Todd T. Fries wrote:
> I've already had one person verify it works (the one that requested I do this,
> future upgrade to ggi) .. anybody else care to comment?
Without even compiling it, I can see at least three minor issues in the
Makefile (Missing #GPL m
250797 (FWD)
| \
\\
37E7 D3EB 74D0 8D66 A68D B866 0326 204E 3F42 004A
http://todd.fries.net/pgp.txt
automake-1.10.tgz
Description: application/tar-gz
hi,
the attached patch is enough to have automake generate makefiles that
works with no executable files in the checked out version of xenocara,
since on OpenBSD systems, install-sh is only used to create directories.
This matches what automake already does when 'mkinstalldirs'
On Sun, Mar 18, 2007 at 08:06:01PM +0100, Matthieu Herrb wrote:
> hi,
>
> the attached patch is enough to have automake generate makefiles that
> works with no executable files in the checked out version of xenocara,
> since on OpenBSD systems, install-sh is only used to cre
* Matthieu Herrb wrote:
> the attached patch, shuts up many automake warnings on tcl.m4 (warning:
> underquoted definition of SC_BLAH).
>
> It helps shortening my xenocara build logs.
>
> (There are a few more ports that need the same kind of patches, but Tcl
> is by far
Hi,
the attached patch, shuts up many automake warnings on tcl.m4 (warning:
underquoted definition of SC_BLAH).
It helps shortening my xenocara build logs.
(There are a few more ports that need the same kind of patches, but Tcl
is by far the most annoying one).
--
Matthieu Herrb
Index
[EMAIL PROTECTED] dixit:
You do not provide much detail on what you're doing so I can only
guess and try to give generic help.
>automake-1.9: ####
>automake-1.9: ## Internal Error ##
>automake-1.9:
>automake-1.9: unrequested trace `'
I
Greetings,
I'm looking for advice as to possible work-arounds or insight into
potential causes for the following error from automake 1.9.
Google shows some similar but not identical messages, and most of
the discussion makes it appear to be a settled issue -- either
automake 1.8 and earli
according to bsd.port.mk(5), 'automake' should be added to
CONFIGURE_STYLE if automake may need to be rerun.
however, there is no explicit support for running automake.
below is a patch to gnu.port.mk to actually run automake
if automake is in CONFIGURE_STYLE.
comments?
I haven'
Andreas Vögele dixit:
> automake-1.9:
> automake-1.9: ## Internal Error ##
> automake-1.9: ####
> automake-1.9: unrequested trace `include'
Ah, I fixed that long ago.
>From the MirPorts patch-automake_in:
@@ -4651,6 +4653,7 @@ sub
What you've done here is send people on a red herring's chase. I
spent some
time looking at that automake port, and figuring out why tests were
wrong.
Luckily, I noticed the gnumake checks, instead of embarking on
autoconf
tests.
Well, Guile's autogen.sh still fails with the sam
On Sun, Jul 24, 2005 at 11:28:23PM +0200, Andreas Vögele wrote:
> Marc Espie writes:
> >What did you use to conduct your tests and assert that automake 1.9
> >does not work with /usr/bin/m4 ?
> A couple of months ago I tried to built the CVS version of Guile, the
>
Marc Espie writes:
What did you use to conduct your tests and assert that automake 1.9
does not work with /usr/bin/m4 ?
A couple of months ago I tried to built the CVS version of Guile, the
GNU project's Scheme interpreter. Since Guile CVS requires automake
1.9 I created my own aut
On Sun, Jul 24, 2005 at 03:28:17PM +0200, Marc Espie wrote:
> What did you use to conduct your tests and assert that automake 1.9
> does not work with /usr/bin/m4 ?
>
By the way, it works better without patches/patch-doc_automake_texi.
Sorry.
What did you use to conduct your tests and assert that automake 1.9
does not work with /usr/bin/m4 ?
In particular, what version of OpenBSD ?
Am 23.07.2005 um 16:36 schrieb Alexandre Anriot:
On Fri, Jul 22, 2005 at 11:51:52PM +0200, Alexandre Anriot wrote:
Here is automake 1.9 port, based on 1.8 one from Jacob Meuser. It
becomes more and more needed by recent Software.
Don't waste you time with this port for now.
It works
On Fri, Jul 22, 2005 at 11:51:52PM +0200, Alexandre Anriot wrote:
> Here is automake 1.9 port, based on 1.8 one from Jacob Meuser. It
> becomes more and more needed by recent Software.
Don't waste you time with this port for now.
It works with some softs but doesn't pass regress
Here is automake 1.9 port, based on 1.8 one from Jacob Meuser. It
becomes more and more needed by recent Software.
automake-1.9.tar.gz
Description: application/tar-gz
74 matches
Mail list logo
