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

Silence “make: --libs: No such file or directory” warnings #3475

Closed
wants to merge 54 commits into from

Conversation

dilyanpalauzov
Copy link
Contributor

With GNU make 4.4 building Kamailio prints many “make: --libs: No such file or directory” and similar warnings. This changeset utilizes immediate variables and silences the warnings on my systems.

@miconda
Copy link
Member

miconda commented Jun 12, 2023

Afaik := evaluates the variable expression only once, does it evaluate it for each module Makefile, or only for the first time that variable is assigned? I mean, if module a and b have something like BUILDER=... in their Makefile, a make all is going to evaluate BUILDER variable each time, or the one from module a propagate to b compilation?

On the other hand = evaluates every time the variable is used.

Edit: I just noticed it is about make 4.4, not gcc 4.4 -- anyhow, I would avoid fixing the warnings in this way if it can create side effects by propagating values when not expecting.

@dilyanpalauzov
Copy link
Contributor Author

When the file a contains BUILDER:=a, the file b contains BUILDER:=b, and Makefile contains

include a
include b

all:
        @echo $(BUILDER)

(there is a TAB before @), then typing make prints b.

I do not understand the question and I do not understand the build system of Kamailio.

Copy link

github-actions bot commented Nov 8, 2023

This PR is stale because it has been open 6 weeks with no activity. Remove stale label or comment or this will be closed in 2 weeks.

@dilyanpalauzov
Copy link
Contributor Author

The proposed here change does fix problems (warnings). I object that this PR is closed, instead of fixing the underlying warnings by the suggested or other ways.

@miconda
Copy link
Member

miconda commented Nov 26, 2023

The automatic actions have the purpose to keep the reporter, and devs when it is the case, engaged. An issue or PR marked stale can have the label removed by reporter if it is still interested in it. Also, a closed issue or PR can be reopened. Note also that the stale label is added based on inactivity period, comments are considered activity, so the inactivity is reset with each of them..

Have in mind that this is a collaborative project, so everyone have to stay engaged, nobody pays for time spent by developers on reviewing commits. From that point of view, I think it is fair that the reporter reacts on a stale or close notification and indicate that the issue is still there or the PR is still relevant. Just coming to blame, it is by far not a nice approach. Some of developers here spent significant resources and time without any direct benefits over the past 20 years to make this application available, that should be appreciated. This kind of automatisation tries to make the life easier for everyone, feel free to propose tools or processes that can help improving and moving forward.

@dilyanpalauzov
Copy link
Contributor Author

From that point of view, I think it is fair that the reporter reacts on a stale or close notification and indicate that the issue is still there or the PR is still relevant.

Writing repeatedly any text just for the sake of keeping a ticket open does not help anyhow.

@miconda
Copy link
Member

miconda commented Nov 26, 2023

Probably you missed the note that you can simply remove the label stale. It was a message on sr-dev a few weeks ago as well.

The remark about comments was to clarify that they count as activity, so it is not about time since open, but time since no interest.

@dilyanpalauzov
Copy link
Contributor Author

An issue or PR marked stale can have the label removed by reporter…

This is not correct.

@miconda
Copy link
Member

miconda commented Nov 26, 2023

I was not aware of the triage role. Anyhow, making a small comment from time to time is a fair effort to keep the interest open and notify/remind the others about.

@miconda
Copy link
Member

miconda commented Nov 26, 2023

And, furthermore, I guess the option of the reporter to reopen the issue/pr is still available.

@dilyanpalauzov
Copy link
Contributor Author

I guess the option of the reporter to reopen the issue/pr is still available.

I do not see such option.

Currently the only way to prevent automatic closing is to write (probably periodically) any text.

@linuxmaniac
Copy link
Member

I've implemented a way to manage stale and re-open expired issues and pull requests.
So, if the comment as /notexpired it will be re-opened and labels expired and stale will be removed.

Hope this helps

Copy link

github-actions bot commented Jan 9, 2024

This PR is stale because it has been open 6 weeks with no activity. Remove stale label or comment or this will be closed in 2 weeks.

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

Successfully merging this pull request may close these issues.

None yet

3 participants