Skip to content

m4/pcre2_visibility.m4: make sure PCRE2_EXPORT is always safe #413

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jun 7, 2024
Merged

m4/pcre2_visibility.m4: make sure PCRE2_EXPORT is always safe #413

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions ChangeLog
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,8 @@ misunderstanding one of the grapheme sequence breaking rules in Unicode Annex
break property unless a zero-width joiner intervenes. PCRE2 was not insisting
on the ZWJ, causing \X to match more than it should. See GitHub issue #410.

8. Avoid compilation issues with propietary compilers in UNIX since 10.43.


Version 10.43 16-February-2024
------------------------------
Expand Down
2 changes: 2 additions & 0 deletions m4/pcre2_visibility.m4
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,8 @@ AC_DEFUN([PCRE2_VISIBILITY],
else
AC_DEFINE(PCRE2_EXPORT, [], [to make a symbol visible])
fi
else
AC_DEFINE(PCRE2_EXPORT, [], [to make a symbol visible])
fi
AC_SUBST([VISIBILITY_CFLAGS])
AC_SUBST([VISIBILITY_CXXFLAGS])
Expand Down
Loading