On Fri, Sep 11, 2020 at 10:57:54PM +0200, Christian Weisgerber wrote:
> Otto Moerbeek:
>
> > > Is it possible that char* (env_vers_cstr) points to null or garbage
> > > because env changed? Or is this nonsense and this cannot happen and
> > > env_vers_cstr is always valid with the first match?
>
Otto Moerbeek:
> > Is it possible that char* (env_vers_cstr) points to null or garbage
> > because env changed? Or is this nonsense and this cannot happen and
> > env_vers_cstr is always valid with the first match?
>
> No, Posix allows previous values of getenv() to be invalidated by
>
On Fri, Sep 11, 2020 at 08:11:09PM +0200, Rafael Sadowski wrote:
> On Thu Aug 13, 2020 at 04:47:47PM +0200, Christian Weisgerber wrote:
> > Occasionally, print/poppler fails to build with a curious error:
> >
> > A shared library has been built with the version number from
> > SHARED_LIBS, but
On Thu Aug 13, 2020 at 04:47:47PM +0200, Christian Weisgerber wrote:
> Occasionally, print/poppler fails to build with a curious error:
>
> A shared library has been built with the version number from
> SHARED_LIBS, but during the fake stage this is forgotten and the
> upstream version number
On 2020-08-13, Christian Weisgerber wrote:
> A shared library has been built with the version number from
> SHARED_LIBS, but during the fake stage this is forgotten and the
> upstream version number used. This produces an error, because the
> file doesn't exist.
>
> It only happens _sometimes_
Occasionally, print/poppler fails to build with a curious error:
A shared library has been built with the version number from
SHARED_LIBS, but during the fake stage this is forgotten and the
upstream version number used. This produces an error, because the
file doesn't exist.
It only happens
