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

PackageTests/ForeignLibs/setup.test.hs fails on MacOS on GHC 8.0.2 #7989

Closed
andreabedini opened this issue Feb 17, 2022 · 4 comments
Closed

Comments

@andreabedini
Copy link
Collaborator

PackageTests/ForeignLibs/setup.test.hs fails on MacOS on GHC 8.0.2, discovered while working on #7952

creating /Users/runner/work/cabal/cabal/cabal-testsuite/PackageTests/ForeignLibs/setup.dist/usr/lib
Installing executable setup.dist/work/dist/build/myforeignlib/libmyforeignlib.dylib to /Users/runner/work/cabal/cabal/cabal-testsuite/PackageTests/ForeignLibs/setup.dist/usr/lib/libmyforeignlib.dylib
+ /usr/bin/gcc '-std=c11' -Wall -o uselib UseLib.c -l myforeignlib -L /Users/runner/work/cabal/cabal/cabal-testsuite/PackageTests/ForeignLibs/setup.dist/usr/lib
+ /Users/runner/work/cabal/cabal/cabal-testsuite/PackageTests/ForeignLibs/./uselib
dyld: REBASE_OPCODE_SET_SEGMENT_AND_OFFSET_ULEB has segment 2 which is not a writable segment (__LINKEDIT) in /Users/runner/work/cabal/cabal/cabal-testsuite/PackageTests/ForeignLibs/setup.dist/usr/lib/x86_64-osx-ghc-8.0.2/libHSmy-foreign-lib-0.1.0.0-ghc8.0.2.dylib

stderr:
*** Exception: Command /Users/runner/work/cabal/cabal/cabal-testsuite/PackageTests/ForeignLibs/./uselib failed.
Output:
dyld: REBASE_OPCODE_SET_SEGMENT_AND_OFFSET_ULEB has segment 2 which is not a writable segment (__LINKEDIT) in /Users/runner/work/cabal/cabal/cabal-testsuite/PackageTests/ForeignLibs/setup.dist/usr/lib/x86_64-osx-ghc-8.0.2/libHSmy-foreign-lib-0.1.0.0-ghc8.0.2.dylib



*** unexpected failure for PackageTests/ForeignLibs/setup.test.hs

See full log here

@Mikolaj
Copy link
Member

Mikolaj commented Feb 17, 2022

That's most likely a GHC 8.0 bug and we will drop GHC 8.0 in a year or two. However, there is low probability that it's actually a cabal bug, so worth making sure that it isn't.

robx added a commit to robx/cabal that referenced this issue Feb 28, 2022
robx added a commit to robx/cabal that referenced this issue Feb 28, 2022
robx added a commit to robx/cabal that referenced this issue Feb 28, 2022
robx added a commit to robx/cabal that referenced this issue Mar 3, 2022
@jneira jneira added the type: testing Issues about project test suites label Mar 3, 2022
robx added a commit to robx/cabal that referenced this issue Mar 3, 2022
robx added a commit to robx/cabal that referenced this issue Mar 4, 2022
jneira added a commit to jneira/cabal that referenced this issue Mar 6, 2022
jneira added a commit to jneira/cabal that referenced this issue Mar 12, 2022
jneira added a commit to jneira/cabal that referenced this issue Mar 14, 2022
jneira added a commit to jneira/cabal that referenced this issue Mar 14, 2022
jneira added a commit to jneira/cabal that referenced this issue Mar 15, 2022
jneira added a commit to jneira/cabal that referenced this issue Mar 15, 2022
Kleidukos pushed a commit to Kleidukos/cabal that referenced this issue Mar 30, 2022
@jneira
Copy link
Member

jneira commented Apr 25, 2022

Hi, the test was marked as broken for ghc >= 9.0 and windows with #8045. I forgot to comment here the new case (but this issue was linked in several commits, including the merge in master).

Later the case was fixed by #7764 and the test was unmarked as broken for windows and those ghc versions by #8111.

So the issue state is the initial one: it is reproduced in macos and ghc 8.0.2

andreabedini pushed a commit to andreabedini/cabal that referenced this issue May 5, 2022
@ulysses4ever
Copy link
Collaborator

ulysses4ever commented Aug 18, 2022

As of bd998ce, 8.0 is no longer used on CI. Should this be closed?

@Mikolaj
Copy link
Member

Mikolaj commented Aug 19, 2022

Yes, let me close. Thank you.

@Mikolaj Mikolaj closed this as completed Aug 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants