Package Details: ted 2.23-11

Git Clone URL: https://aur.archlinux.org/ted.git (read-only, click to copy)
Package Base: ted
Description: Lightweight RTF text processor
Upstream URL: https://www.nllgg.nl/Ted/
Licenses: GPL
Submitter: sergej
Maintainer: willemw
Last Packager: willemw
Votes: 17
Popularity: 0.000000
First Submitted: 2012-12-04 12:18 (UTC)
Last Updated: 2022-01-02 09:04 (UTC)

Required by (0)

Sources (25)

Latest Comments

1 2 Next › Last »

willemw commented on 2022-03-14 06:42 (UTC)

"Configure" is normally run before "make", in a single thread, to setup makefiles. The reason of the build errors was that "configure" here runs inside "make", which runs multiple threads, causing build race-conditions.

frankspace commented on 2022-03-13 23:52 (UTC)

Apologies for how long it took, but the current PKGBUILD does now work for me without any pesky tampering or re-running makepkg or anything like that. Thank you!

willemw commented on 2021-12-25 18:11 (UTC)

@frankspace: for me it is very difficult to reproduce any build error.

You could try adding/replacing options=(!buildflags !makeflags) in PKGBUILD, which probably will also make no difference. See https://wiki.archlinux.org/title/Makepkg#Makepkg_fails,_but_make_succeeds

Adding this gets very close to running make manually. With echo $VARIABLE in PKGBUILD and on the command line you can print the build and make values listed in /etc/makepkg.conf and check the difference.

frankspace commented on 2021-12-25 17:37 (UTC)

Thank you! So, that's wild. Turns out, on my box, options=(!buildflags) doesn't make any noticable difference (I tested this outside a chroot, so YMMV) -- but I have to run makepkg three times in a row (without tampering with the src and pkg folders) before compilation succeeds all the way through. I once again am not clever enough to have any idea why, but I suspect the build flags are not actually the issue one way or the other.

willemw commented on 2021-12-25 09:13 (UTC)

@frankspace:

That with-GTK warning is always there.

Remove the options=(!buildflags) line from PKGBUILD and try again (without any old build files). This will build with the build flags from /etc/makepkg.conf. When running make manually, it won't build with those flags.

The build only sometimes fails. Adding options=(!buildflags) seemed to fix it. But could eventually, after trying several times, produce a build error in an up-to-date clean chroot build environment. Will remove options=(!buildflags) again.

frankspace commented on 2021-12-24 18:19 (UTC)

Compilation fails for me, repeatedly telling me configure: WARNING: unrecognized options: --with-GTK. I've tried this both in a clean chroot and not. Blindly removing "CONFIGURE_OPTIONS=--with-GTK" from the Makefile seemingly solves that issue, but compilation nevertheless terminates, just saying ERROR: A failure occurred in build().. The only hint I can find in the output thereafter is that midway there, I get make: *** [Makefile:170: lib/docEdit.a] Error 2 and make: *** [Makefile:198: lib/utilPs.a] Error 2. I am not clever enough to have any idea where to start looking for the source of the problem. Inexplicably, when I just uncompress the source and run make manually, compilation succeeds just fine.

willemw commented on 2021-10-29 11:09 (UTC)

Build succeeds when adding options=(!buildflags) to PGKBUILD.

sez11a commented on 2021-10-27 22:36 (UTC)

This package doesn't build. Fails here: 

Choosing GTK ...
configure: creating ./config.status
config.status: creating makefile
config.status: creating tedConfig.h
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: ted

willemw commented on 2018-06-15 07:15 (UTC)

@es_18: Updated to use https, in addition to some fixes/cleanups.

es_18 commented on 2018-06-14 21:43 (UTC)

Wouldn't it be more secure to use http rather than https for the sources? The server accepts https as well.

1 2 Next › Last »