On 2019-10-30 12:49 , Thomas R. Murphy wrote:
> Is there a reason poppler is setup to disallow in-place updating? This
> essentially makes port upgrade outdatedrequire manual intervention when
> a rev-bump of poppler comes by. The end of the build log indicates that
> this is an intentional
Is there a reason poppler is setup to disallow in-place updating? This
essentially makes port upgrade outdatedrequire manual intervention when
a rev-bump of poppler comes by. The end of the build log indicates that
this is an intentional prebuild check:
:debug:configure Executing
> On 29 Oct 2019, at 3:57 pm, René J.V. Bertin wrote:
>
> Hi,
>
> After upgrading my ICU ports on Mac OS X 10.9 I'm getting the above error
> when trying to load libicu-le-hb.dylib .
>
> {{{
>> demangle _ZTIN6icu_657UObjectE
> _ZTIN6icu_657UObjectE -> "typeinfo for icu_65::UObject"
> }}}
Hi,
After upgrading my ICU ports on Mac OS X 10.9 I'm getting the above error when
trying to load libicu-le-hb.dylib .
{{{
> demangle _ZTIN6icu_657UObjectE
_ZTIN6icu_657UObjectE -> "typeinfo for icu_65::UObject"
}}}
As far as I can tell the 3 ports involved were all build using C++11 (and
Can anyone help me getting this PR through? :)
https://github.com/macports/macports-ports/pull/5016
_
-. .´ |
', ;|∞∞
˜˜ |∞ RdB
,.,|∞∞
.' '. |
-' `’
https://rdb.is
signature.asc
Description: Message signed with
