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

build: don't directly use the .libs directory #3097

Closed
wants to merge 1 commit into from

Conversation

orbea
Copy link

@orbea orbea commented Feb 27, 2024

This is a duplicate of PR #2980 to try to trigger the CI regression tests.

The build system should not directly use the .libs directory which is intended for internal use by the libtool implementation. Additionally when linking with internal a library the .la file should be used as this provides all the information required by the libtool implementation.

When using Slibtool instead of GNU Libtool the build fails because Slibtool is more strict about this and fails to find the required files to link with.

Gentoo Bug: https://bugs.gentoo.org/913484

The build system should not directly use the .libs directory which is
intended for internal use by the libtool implementation. Additionally
when linking with internal a library the .la file should be used as this
provides all the information required by the libtool implementation.

When using Slibtool instead of GNU Libtool the build fails because
Slibtool is more strict about this and fails to find the required files
to link with.
Copy link

sonarcloud bot commented Feb 27, 2024

Quality Gate Failed Quality Gate failed

Failed conditions
3.2% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud

@orbea
Copy link
Author

orbea commented Feb 27, 2024

Trying to split the changes in half didn't seem to make a difference for Quality Gate....

@orbea orbea closed this Feb 27, 2024
@airween
Copy link
Member

airween commented Feb 27, 2024

Trying to split the changes in half didn't seem to make a difference for Quality Gate....

Yeah, QG check is very weird - I'm sure that's a false positive hit (the code is definitely not NEW).

I have to find a solution - sorry, and thanks for your patience.

@orbea
Copy link
Author

orbea commented Feb 27, 2024

I have to find a solution - sorry, and thanks for your patience.

No worries and thanks for your time!

@airween
Copy link
Member

airween commented Feb 27, 2024

It sounds like a stupid question, but could you make a fresh clone and apply your modification in a separated new commit?

Here I see this:

modsec_duplicate

and may be Sonarcloud thinks that you added the mentioned lines through the pull. (Because 4d7d1fa was made in Sept, 2023)

@hydrapolic
Copy link

ping @orbea

@airween
Copy link
Member

airween commented Sep 26, 2024

May be we will copy this PR and send it again.

Meanwhile the CI workflow had changed a lot (eg. see the Windows support), so we insist to run the whole test.

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.

3 participants