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

fix linkage on Xenial (16.04) #627

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

fix linkage on Xenial (16.04) #627

wants to merge 1 commit into from

Conversation

DeckerSU
Copy link

@DeckerSU DeckerSU commented Sep 9, 2024

This PR fixes linkage error below on Xenial:

/usr/bin/ld: libcc.a(libcc_a-cclib.o): relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a shared object; recompile with -fPIC
libcc.a: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
Makefile:2305: recipe for target 'komodod' failed
make[2]: *** [komodod] Error 1

```
/usr/bin/ld: libcc.a(libcc_a-cclib.o): relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a shared object; recompile with -fPIC
libcc.a: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
Makefile:2305: recipe for target 'komodod' failed
make[2]: *** [komodod] Error 1
```
@TheComputerGenie
Copy link

While I think a PIC flag is a good idea, I cannot help but ask: "Why does anyone care about Xenial?". Xenial support for non-Pro subscribers ended its life some 3 years ago.
Why are we so determined to "lead" the future from as far back as possible?

@DeckerSU
Copy link
Author

Why does anyone care about Xenial?

Hmm... the answer is probably "because it costs zero effort," right? If we can support Xenial without any additional resources spent, why not?

@TheComputerGenie
Copy link

without any additional resources spent

Given that everything automated is running 20/22, some additional resources are clearly spent going back 2 releases further. At that point, might as well also set it up for Trusty Tahr (since "technically" its full EoL isn't until April 2026), no?

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.

2 participants