Search Criteria
Package Details: mingw-w64-fribidi 1.0.13-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/mingw-w64-fribidi.git (read-only, click to copy) |
---|---|
Package Base: | mingw-w64-fribidi |
Description: | A Free Implementation of the Unicode Bidirectional Algorithm (mingw-w64) |
Upstream URL: | http://fribidi.org |
Licenses: | LGPL |
Submitter: | kfg |
Maintainer: | kfg |
Last Packager: | kfg |
Votes: | 8 |
Popularity: | 0.000000 |
First Submitted: | 2013-06-16 15:46 (UTC) |
Last Updated: | 2023-06-02 14:06 (UTC) |
Dependencies (5)
- mingw-w64-crt
- git (git-vfs, git-run-command-patch-git, git-git, git-fc) (make)
- mingw-w64-gcc (make)
- mingw-w64-meson (make)
- mingw-w64-wine (make)
Latest Comments
1 2 Next › Last »
Martchus commented on 2020-05-19 11:03 (UTC)
Btw, I've just figured the problem out. (Starting the systemd-nspawn container with
--console=interactive
is not enough. One needs to set theTERM
variable via--setenv=TERM=xterm
as well.)Martchus commented on 2020-05-19 10:49 (UTC)
@kfg Thanks for trying to help. In the meantime I've noticed that other packages trying to use wine fail in the same way. So this has nothing to do with this particular package after all and is just my setup. Apparently WINE needs a terminal but there is none in my systemd-nspawn container which leads to the odd message.
kfg commented on 2020-05-19 10:40 (UTC)
@Martchus Can't really see from the build log what the exact problem is.
The "'unknown': I need something more specific." message looks odd but I have no idea where that is coming from. Can I see the meson.log.txt somewhere?
Martchus commented on 2020-05-17 11:51 (UTC)
When rebuilding against the new GCC I've run into the following error: https://martchus.no-ip.biz/build-data/rebuild-dw2/mingw-w64-fribidi/pkg/build.log
VJSchneid commented on 2019-12-23 00:11 (UTC) (edited on 2019-12-23 00:12 (UTC) by VJSchneid)
The last two tests failed due to a missing shared library. I was able to fix this by copying the library into the corresponding test directory as seen below.
tuxsavvy commented on 2018-09-01 07:43 (UTC)
@kfg I ran the test three times due to seeing timeouts in at least first two tests (of eight in total). The final time I ran the test it ended up with a failure for the last test but the former tests resulted in passing for some reason.
Here is the meson test log:
In addition, I believe these syslogs may be useful (they were outputted during compiling):
Thanks in advance
kfg commented on 2018-08-31 13:51 (UTC)
@tuxsavvy
The tests now run with WINEDEBUG=-all does that fix i686 for you?
If not please post the meson test log.
tuxsavvy commented on 2018-08-31 10:28 (UTC)
I am unsure why I fail only the last test for i686,
BidiCharacterTest
however it passes tests on x86-64 instead. Here are the logs:Building normally as is:
Disabled i686 and updated
_commit
to latest (b534ab2642f694c3106d5bc8d0a8beae60bf60d3):doragasu commented on 2018-08-03 08:14 (UTC)
I have the same problem. I have tried removing the dos2unix command, and the problem is even worse (more tests fail).
kfg commented on 2018-08-02 18:49 (UTC)
Do they work for you if you remove the unix2dos conversion in line 30?
For me wine added windows line endings in the output so i thought converting the reference file to have them as well would make the test work correctly under wine.
The tests weren't run at all previously since meson test was run in the wrong directory.
1 2 Next › Last »