Michael Tautschnig writes:
> > Michael Tautschnig writes:
> > > > Assume we do build the default gcc depending on a libppl0, now the
> > > > libppl soname is changed to libppl1, a new ppl source is uploaded, and
> > > > suddendly libppl0 isn't available anymore. And we still need to
> > > > rebuild
> Michael Tautschnig writes:
> > > Assume we do build the default gcc depending on a libppl0, now the
> > > libppl soname is changed to libppl1, a new ppl source is uploaded, and
> > > suddendly libppl0 isn't available anymore. And we still need to
> > > rebuild gcc using gcc. Making the ppl source
Michael Tautschnig writes:
> > Assume we do build the default gcc depending on a libppl0, now the
> > libppl soname is changed to libppl1, a new ppl source is uploaded, and
> > suddendly libppl0 isn't available anymore. And we still need to
> > rebuild gcc using gcc. Making the ppl source versioned
> Assume we do build the default gcc depending on a libppl0, now the
> libppl soname is changed to libppl1, a new ppl source is uploaded, and
> suddendly libppl0 isn't available anymore. And we still need to
> rebuild gcc using gcc. Making the ppl source versioned (pplX), we
> still have the old li
Assume we do build the default gcc depending on a libppl0, now the
libppl soname is changed to libppl1, a new ppl source is uploaded, and
suddendly libppl0 isn't available anymore. And we still need to
rebuild gcc using gcc. Making the ppl source versioned (pplX), we
still have the old libppl0 in t
5 matches
Mail list logo
