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 static uClibc-ng support #2501

Merged
merged 1 commit into from Jan 22, 2019
Merged

fix static uClibc-ng support #2501

merged 1 commit into from Jan 22, 2019

Conversation

Kokan
Copy link
Collaborator

@Kokan Kokan commented Jan 18, 2019

In case of static uClibc-ng lib, the <dlfcn.h> does not exists.

The signal-handler.c solves an issue in case of program src/dst
and Java destination. That combination is really rare if not impossible.

This patch simply disables own sigaction if <dlfcn.h> is not present.

Fixes #2491

@cpackham could you test with this patch, if any other issue is present ?

In case of static uClibc-ng lib, the <dlfcn.h> does not exists.

The signal-handler.c solves an issue in case of program src/dst
and Java destination. That combination is really rare if not impossible.

This patch simply disables own sigaction if <dlfcn.h> is not present.

Signed-off-by: Kokan <kokaipeter@gmail.com>
@kira-syslogng
Copy link
Contributor

Build SUCCESS

@cpackham
Copy link
Contributor

@Kokan this fixes the build failure. Thanks.

@furiel
Copy link
Collaborator

furiel commented Jan 21, 2019

@Kokan the changeset itself looks good to me.

About java+program destination: do you think it would be useful to add a configure/cmake time check, so that when dlfcn.h is not available, java and program destination should be disabled?

@Kokan
Copy link
Collaborator Author

Kokan commented Jan 21, 2019

@furiel I was thinking about it, but compiling those modules are fine, even using them in a different syslog-ng instance are ok; using only a warning could be a way, but imho won't be noticed.
As I wrote above this is probably not a use case anybody has, I tend to not to handle at all.

If you or anybody still think a warning would be nice, I can update the patch accordingly.

@furiel
Copy link
Collaborator

furiel commented Jan 21, 2019

@Kokan I agree warning is not necessary here.

@lbudai lbudai merged commit a51d1c8 into syslog-ng:master Jan 22, 2019
@Kokan Kokan deleted the optional_dlsym branch January 22, 2019 08:51
@lbudai lbudai added this to the OSE 3.20 milestone Jan 22, 2019
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.

None yet

5 participants