Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not always link to /usr/lib/wine #1

Merged
merged 1 commit into from
Feb 13, 2020
Merged

Conversation

terencode
Copy link
Contributor

Doing that makes linking stage fail when compiling for 32bit because it
will link against both /usr/lib/wine and /usr/lib32/wine

Doing that makes linking stage fail when compiling for 32bit because it
will link against both /usr/lib/wine and /usr/lib32/wine
@falkTX
Copy link
Member

falkTX commented Feb 13, 2020

I find it weird that this is an issue, since usually having multiple link locations is fine (compiler will skip to the next path if the libs on the current one are not usable)
But compilers/linkers can misbehave too.

Will apply, thanks.

@falkTX falkTX merged commit 60e6b47 into wineasio:master Feb 13, 2020
@terencode
Copy link
Contributor Author

Ah, thanks for clarifying.
I am on gcc 9.2.1 and I get the following:

/usr/bin/ld: i386:x86-64 architecture of input file `/usr/lib/wine/libuuid.a(uuid.o)' is incompatible with i386 output
/usr/bin/ld: relocatable linking with relocations from format elf64-x86-64 (/usr/lib/wine/libwinecrt0.a(dll_entry.o)) to format elf32-i386 (wineasio.eFtMgN.o) is not supported
winebuild: /usr/bin/ld failed with status 1
winegcc: /usr/bin/winebuild failed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants