Opened 3 years ago
Closed 3 years ago
#13026 closed defect (fixed)
ScummVM: Compiling error with fribidi v1.0.10 and fribidi v1.0.11
Reported by: | ctoroman | Owned by: | ctoroman |
---|---|---|---|
Priority: | normal | Component: | Common |
Version: | Keywords: | ||
Cc: | Game: |
Description
Link error when using fribidi v1.0.10 and fribidi v1.0.11
E:/msys64/mingw32/bin/../lib/gcc/i686-w64-mingw32/10.3.0/../../../../i686-w64-mingw32/bin/ld.exe: common/libcommon.a(unicode-bidi.o):unicode-bidi.c:(.text+0x156): undefined reference to `_impfribidi_log2vis'
collect2.exe: error: ld returned 1 exit status
make: * [Makefile.common:127: scummvm.exe] Error 1
I'm sorry if off topic
Change History (4)
comment:1 by , 3 years ago
comment:2 by , 3 years ago
Just from those paths in the error messages (mingw components rooted in the windows drive and not /) it doesn't look like you're running from within a msys2 terminal, or at least not the way the wiki describes: https://wiki.scummvm.org/index.php?title=Compiling_ScummVM/MinGW-w64
Are you following the wiki instructions for your environment or doing something different?
I'm also not having any problems, and I'm building on Windows with msys2/i686-w64-mingw32. I just upgraded msys2 packages and there was a slightly newer fribidi and that also worked.
comment:3 by , 3 years ago
sluicebox, yes, i'm following the wiki instructions. But i'm using static libs (not *.dll.a), and I get scummvm.exe without any other files. When using fribidi v1.0.9, the linking is ok.
When using fribidi v1.0.10 and fribidi v1.0.11, i get the error reported above.
I'm using msys and msys2, the error is the same
Libs I build from source. I don’t understand what I’m doing wrong.
comment:4 by , 3 years ago
Owner: | set to |
---|---|
Resolution: | → fixed |
Status: | new → closed |
I am using fribidi 1.0.10 myself (and have been for a while) and I don't have that error. There is also no
_impfribidi_log2vis
symbol in mylibcommon.a
; there is only one to _fribidi_log2vis`This is maybe Windows specific? Or maybe a build issue? Did you try to do a
make clean clean
and full build again?