On Tue, Jan 14, 2003 at 11:34:30PM +, Bro1 wrote:
> > Those libs are binary-only run-time libs if I understand correctly.
> > Did you evaluate the impact of those C++ libs in respect with gcc 3.2
> > migration path in sid? They are compiled against old ABI, I think. And the
> > same for all Kyl
On Tue, Jan 14, 2003 at 11:34:30PM +, Bro1 wrote:
> > Those libs are binary-only run-time libs if I understand correctly.
> > Did you evaluate the impact of those C++ libs in respect with gcc 3.2
> > migration path in sid? They are compiled against old ABI, I think. And the
> > same for all Kyl
> Those libs are binary-only run-time libs if I understand correctly.
> Did you evaluate the impact of those C++ libs in respect with gcc 3.2
> migration path in sid? They are compiled against old ABI, I think. And the
> same for all Kylix stuff.
Hi,
you understand this correctly, these package
> Those libs are binary-only run-time libs if I understand correctly.
> Did you evaluate the impact of those C++ libs in respect with gcc 3.2
> migration path in sid? They are compiled against old ABI, I think. And the
> same for all Kylix stuff.
Hi,
you understand this correctly, these package
On Mon, Jan 13, 2003 at 11:43:40AM -, Linas Jakucionis wrote:
> Hi,
>
> I am a developer of Kylix Libs Packaging Project
> http://kylixlibs.sourceforge.net/
>
> This project tries to package the required Kylix programming language
> libraries for the most popular Linux distributions so that
On Mon, Jan 13, 2003 at 11:43:40AM -, Linas Jakucionis wrote:
> Hi,
>
> I am a developer of Kylix Libs Packaging Project
> http://kylixlibs.sourceforge.net/
>
> This project tries to package the required Kylix programming language
> libraries for the most popular Linux distributions so that
6 matches
Mail list logo