On Mon, May 11, 2020 at 1:00 PM Thomas Wagner <[email protected]> wrote:
> Hi, > > what if as a temorary fix, the g++-X-runtime is getting a new dependency > on corresponding gcc-X-runtime? > Then every older user package requiring g++-X-runtime would get libssp > in package gcc-X-runtime through that dependency. > I tried it but unfortunately it does not seem to make a difference, the dependency already exists but is not followed. Too bad this was a good idea :S Given the rather low number of packages to fix, I'll probably just add GCC_RUNTIME_PKG to make the transition. Thank you! > > Over the time, old user packages all move to gcc-X-runtime > automatically. > > Thomas > > On Mon, May 11, 2020 at 12:03:27PM +0200, Aurélien Larcher wrote: > > Hi, > > while packaging gcc-9 I noticed that libssp had been misplaced in > > g++-X-runtime since gcc-49. > > I checked solaris-userland and moved libssp to gcc-X-runtime for > > consistency. > > Unfortunately this means that we have a bogus dependency on > GXX_RUNTIME_PKG > > in ~80 components, which should be GCC_RUNTIME_PKG. > > For the gcc-10 build zone I need to fix these dependencies: currently > about > > 1000 components republished, 130 failures. > > Putting libssp back in g++-runtime would be convenient but incorrect. > > Any idea? > > > > Kind regards, > > > > Aurélien > > > > -- > > --- > > Praise the Caffeine embeddings > > > _______________________________________________ > > oi-dev mailing list > > [email protected] > > https://openindiana.org/mailman/listinfo/oi-dev > > > -- > -- --- Praise the Caffeine embeddings
_______________________________________________ oi-dev mailing list [email protected] https://openindiana.org/mailman/listinfo/oi-dev
