Re: libgl1 vs C++ transition, round 2
- To: Debian Developers <firstname.lastname@example.org>
- Subject: Re: libgl1 vs C++ transition, round 2
- From: Jamie Wilkinson <email@example.com>
- Date: Mon, 3 Feb 2003 19:05:47 +1100
- Message-id: <[🔎] 20030203080547.GB531@spacepants.org>
- Mail-followup-to: Debian Developers <firstname.lastname@example.org>
- In-reply-to: <20030131180603.GA6931@localhost>
- References: <20030127155257.GA1858@informatik.uni-stuttgart.de> <20030127233146.GC523@spacepants.org> <20030128114456.GA6182@informatik.uni-stuttgart.de> <20030129104704.GA4788@spacepants.org> <20030131180603.GA6931@localhost>
This one time, at band camp, Jochen Voss wrote:
>On Wed, Jan 29, 2003 at 09:47:04PM +1100, Jamie Wilkinson wrote:
>> a) GLU is broken and needs to have its ABI fixed so that programs don't
>> need to link against libstdc++ when they themselves are not written in C++.
>I think it is not the interface of GLU, that forces libstdc++ in.
>But libGLU uses functions from libstdc++ internally.
That is the expected behavior. According to #134262 that's not what's