Skip to content

Conversation

@trofi
Copy link

@trofi trofi commented Jun 4, 2022

gcc-10 changed the default from -fcommon to fno-common:
https://gcc.gnu.org/PR85678

As a result build of lvmrun fails as:

...
gcc -o lvmrun ... -lm -ldl
ld: core/module.o:(.bss+0x0): multiple definition of `bytes_ops'; core/loader.o:(.bss+0x0): first defined here
ld: core/fail.o:(.bss+0x0): multiple definition of `global_exn_frame'; core/evaluator.o:(.bss+0x10): first defined here
ld: core/signals.o:(.bss+0x8): multiple definition of `global_exn_frame'; core/evaluator.o:(.bss+0x10): first defined here
ld: heap/bytes.o:(.data.rel.local+0x0): multiple definition of `bytes_ops'; core/loader.o:(.bss+0x0): first defined here

The change drops excessive variable definitions from headers.

gcc-10 changed the default from -fcommon to fno-common:
  https://gcc.gnu.org/PR85678

As a result build of lvmrun fails as:

    ...
    gcc -o lvmrun ... -lm -ldl
    ld: core/module.o:(.bss+0x0): multiple definition of `bytes_ops'; core/loader.o:(.bss+0x0): first defined here
    ld: core/fail.o:(.bss+0x0): multiple definition of `global_exn_frame'; core/evaluator.o:(.bss+0x10): first defined here
    ld: core/signals.o:(.bss+0x8): multiple definition of `global_exn_frame'; core/evaluator.o:(.bss+0x10): first defined here
    ld: heap/bytes.o:(.data.rel.local+0x0): multiple definition of `bytes_ops'; core/loader.o:(.bss+0x0): first defined here

The change drops excessive variable definitions from headers.
trofi added a commit to trofi/nixpkgs that referenced this pull request Jun 11, 2022
The package fails to build with upstream gcc-10 as:

    ld: heap/bytes.o:(.data.rel.local+0x0): multiple definition of `bytes_ops';
      core/loader.o:(.bss+0x0): first defined here

Upstream report: Helium4Haskell/lvm#4
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.

1 participant