Package Details: abiword-git 1:3.1.0.20780.2a06be6a1-1

Git Clone URL: https://aur.archlinux.org/abiword-git.git (read-only, click to copy)
Package Base: abiword-git
Description: Fully-featured word processor from official GNOME GitLab instance
Upstream URL: http://www.nl.abisource.com/
Licenses: GPL-2.0-or-later
Conflicts: abiword, abiword-plugins
Provides: abiword, abiword-plugins
Submitter: haawda
Maintainer: None
Last Packager: micwoj92
Votes: 1
Popularity: 0.000000
First Submitted: 2018-08-25 20:24 (UTC)
Last Updated: 2024-08-20 17:57 (UTC)

Latest Comments

1 2 Next › Last »

haawda commented on 2021-06-01 16:18 (UTC)

You are wrong. The PKGBUILD already pulls from the gnome gitlab repo.

c4pote commented on 2021-05-31 19:23 (UTC)

This seems to be not the AbiWord which is on the Gnome Gitlab? https://gitlab.gnome.org/World/AbiWord

Gnome Gitlab AbiWord has been last updated on Apr 20, 2021. Is there any way we can point this package to the GNOME repo?

andreas_baumann commented on 2018-06-28 09:20 (UTC) (edited on 2018-06-28 09:25 (UTC) by andreas_baumann)

The following snippet in PKGBUILD made the AC_MSG_ERROR error go away (but it's most likely not the proper fix):

prepare() {
...
export CXXFLAGS+=" -O3"
sed -i '/AC_INIT/ a m4_pattern_allow([AC_MSG_ERROR])' configure.ac
NOCONFIGURE=1 ./autogen.sh
...
}

Now the next error popping up is:

./configure: line 18458: syntax error near unexpected token `-fsanitize=$withval,'
./configure: line 18458: `      AX_CHECK_COMPILE_FLAG(-fsanitize=$withval,'

I commented out the whole sanitizer section as this AS_IF is apparently not expanded correctly and written directly into the generated configure script:

dnl ***********************************************************************
dnl GCC/Clang sanitizer support
dnl ***********************************************************************
dnl AC_ARG_WITH([sanitizer],
dnl            [AS_HELP_STRING([--with-sanitizer=@<:@address/undefined/no@:>@],
dnl                            [Use specific GCC/Clang analyzer])],
dnl            [with_sanitizer=$withval],
dnl            [with_sanitizer=no])
dnl AS_IF([test "x$with_sanitizer" != "xno"],[
dnl     AX_CHECK_COMPILE_FLAG([-fsanitize=$withval],
dnl                           [CFLAGS="$CFLAGS -fsanitize=$withval"
dnl                            CXXFLAGS="$CXXFLAGS -fsanitize=$withval"],
dnl                           [AC_MSG_ERROR([-fsanitize=$withval is not supported])])
dnl        AX_APPEND_COMPILE_FLAGS([-fno-omit-frame-pointer])
dnl        AC_LANG_PUSH(C++)
dnl        AX_APPEND_COMPILE_FLAGS([-fno-omit-frame-pointer])
dnl        AC_LANG_POP
dnl])

and the next section:

dnl ***************************************************************
dnl Excessive warnings
dnl ***************************************************************
dnl AC_LANG_PUSH(C++)
dnl AX_CHECK_COMPILE_FLAG([-Werror=unknown-warning-option], [
dnl     ax_compiler_flags_test="-Werror=unknown-warning-option"
dnl], [
dnl     ax_compiler_flags_test=""
dnl])
dnl XXX enable these
dnl -Wformat-nonliteral
...
dnl ], [], [$ax_compiler_flags_test])

(sanitizers and warnings are useful for developers and maintainers, not when building the software, so I don't think I broke something..)

Maybe a incompatible or old version of https://www.gnu.org/software/autoconf-archive/ax_check_compile_flag.html is causing the problem.

haawda commented on 2017-06-26 22:33 (UTC)

Confirmed, but I do not have a fix for this. And it is not the same issue as in march, that one was fixed.

colinkeenan commented on 2017-06-26 05:57 (UTC)

I'm trying to build this in a clean chroot using makechrootpkg -c -r $CHROOT but I'm getting the same error @Rhinoceros told you about in March 2017: ==> Starting build()... libtoolize: putting auxiliary files in '.'. libtoolize: copying file './ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. libtoolize: copying file 'm4/libtool.m4' libtoolize: copying file 'm4/ltoptions.m4' libtoolize: copying file 'm4/ltsugar.m4' libtoolize: copying file 'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' configure.ac:58: error: possibly undefined macro: AC_MSG_ERROR If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf: /usr/bin/autoconf failed with exit status: 1 Skipping configure process. configure: error: cannot find install-sh, install.sh, or shtool in "." "./.." "./../.." ==> ERROR: A failure occurred in build(). Aborting...

haawda commented on 2017-05-29 14:11 (UTC)

Yes it is fixed. The repos' update to gcc 7 needs another fix. Please re-checkout.

jtojnar commented on 2017-05-28 03:21 (UTC)

@haawda It should be fixed in 35439.

haawda commented on 2017-04-20 22:24 (UTC)

This package currently does not build. I opened a bug report upstream. https://bugzilla.abisource.com/show_bug.cgi?id=13858

Rhinoceros commented on 2017-03-12 06:15 (UTC)

Also, for the record, IMO you shouldn't be bumping VCS packages with every update either.

Rhinoceros commented on 2017-03-12 00:00 (UTC)

This fails to build, with the following error. I've built it fine previously (35397-1). configure.ac:58: error: possibly undefined macro: AC_MSG_ERROR If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf: /usr/bin/autoconf failed with exit status: 1 Skipping configure process. configure: error: cannot find install-sh, install.sh, or shtool in "." "./.." "./../.."

1 2 Next › Last »