Hi Daiki,
> > Whereas with
> >
> > gl_LIBUNISTRING_MODULE([0.9.10], [unicase/u8-prefix-context])
> >
> > the autoconfiguration will compile the module locally - thus filling
> > the "hole" in the installed libunistring.
>
> So, is my understanding correct that this only affects unreleased
> version of libunistring (0.9.10 is not released)?
No, I don't think it can be stated like this.
There are three kinds of packages that use GNU libunistring:
a) Those that use gnulib modules 'uni*/*', without module
'libunistring-optional'.
These packages don't link with libunistring, therefore they
have not experienced said bug, and they are not impacted by the changes
of this week.
b) Those that use gnulib modules 'uni*/*', with module
'libunistring-optional'.
These package got link errors when they attempted to use said *context
functions. These link errors will go away once
- the package updates its gnulib infrastructure (to get the modified
gl_LIBUNISTRING_MODULE invocations), or
- libunistring 0.9.10 or newer gets installed on the target system.
c) Those that use gnulib module 'libunistring', or don't use gnulib at all.
These package got link errors when they attempted to use said *context
functions. These link errors will go away once libunistring 0.9.10 or
newer gets installed on the target system.
Hope this clarifies.
Bruno
