Brian Nelson <[EMAIL PROTECTED]> writes:
>> sed -e 's/CC="gcc"/CC="g++"/g' libtool > lt.tmp && mv -f lt.tmp libtool
>>
>> to force it. What's the right way to get libstdc++ linked in to shared
>> libraries of C++ code? The package uses autoconf, automake, libtool, etc.
>
> Use -lstdc++ [...]?
N
On Sat, 2003-05-17 at 06:17, Matthew Palmer wrote:
> On 16 May 2003, Fabian Fagerholm wrote:
>
> > I've packaged the Albatross Web Toolkit. I've filed an ITP: Bug #193574.
>
> Once you've got it to the quality of wanting it in Debian, contact me and
> we'll work something out. It certainly looks
Neil Roeth <[EMAIL PROTECTED]> writes:
> I recently had a bug (193950) filed against one of my packages because the
> shared libraries had "undefined non-weak symbols" - libstdc++ was not being
> linked in. I resolved it with what I consider a gruesome hack. I discovered
> that forcing libtool t
Mike Schacht wrote:
> This list of debian machines: http://db.debian.org/machines.cgi, shows
> that some of the machines allow access by "all". There is no further
> explanation of who qualifies as "all", or how someone who is "all" can
> get access.
>
> The debian-admin list is given at the Ad
On May 30, Joey Hess ([EMAIL PROTECTED]) wrote:
> Neil Roeth wrote:
> > Thanks for the hints. I should have been more clear - I have no problem
> > getting the main page, i.e., [EMAIL PROTECTED] There are
> > links in that page to bugs.debian.org/cgi-bin/bugreport.cgi?bug= for each
> > bug,
Neil Roeth wrote:
> Thanks for the hints. I should have been more clear - I have no problem
> getting the main page, i.e., [EMAIL PROTECTED] There are
> links in that page to bugs.debian.org/cgi-bin/bugreport.cgi?bug= for each
> bug, and I want to get each of those as a local web page, too. That
I really think this should go to the debian-perl list so I'm sending it
there. The libc-include-perl example below is one of the best arguments
I've seen for changing the perl module naming scheme. It's a pity that
we didn't think it through more before deciding on it. IIRC we just took
the example
I recently had a bug (193950) filed against one of my packages because the
shared libraries had "undefined non-weak symbols" - libstdc++ was not being
linked in. I resolved it with what I consider a gruesome hack. I discovered
that forcing libtool to use g++ while linking would automatically link
Brian Nelson <[EMAIL PROTECTED]> writes:
>> sed -e 's/CC="gcc"/CC="g++"/g' libtool > lt.tmp && mv -f lt.tmp libtool
>>
>> to force it. What's the right way to get libstdc++ linked in to shared
>> libraries of C++ code? The package uses autoconf, automake, libtool, etc.
>
> Use -lstdc++ [...]?
N
On Sat, 2003-05-17 at 06:17, Matthew Palmer wrote:
> On 16 May 2003, Fabian Fagerholm wrote:
>
> > I've packaged the Albatross Web Toolkit. I've filed an ITP: Bug #193574.
>
> Once you've got it to the quality of wanting it in Debian, contact me and
> we'll work something out. It certainly looks
Neil Roeth <[EMAIL PROTECTED]> writes:
> I recently had a bug (193950) filed against one of my packages because the
> shared libraries had "undefined non-weak symbols" - libstdc++ was not being
> linked in. I resolved it with what I consider a gruesome hack. I discovered
> that forcing libtool t
Mike Schacht wrote:
> This list of debian machines: http://db.debian.org/machines.cgi, shows
> that some of the machines allow access by "all". There is no further
> explanation of who qualifies as "all", or how someone who is "all" can
> get access.
>
> The debian-admin list is given at the Ad
12 matches
Mail list logo
