GNU bug report logs - #22463
c++ linker instead of c linker

Previous Next

To reply to this bug, email your comments to 22463 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Sylvain BERTRAND <sylvain.bertrand <at> gmail.com>
To: bug-automake <at> gnu.org
Subject: c++ linker instead of c linker
Date: Mon, 25 Jan 2016 22:08:48 +1100

Hi,

(debian jessie automake 1.14.1)

In git efl (enlightenment), the libtool library libevas.la has always a c++
linker rule generated, even though, with some disabled options, only a c linker
is required: Some AM_CONDITIONAL can remove all c++ source/object files from
libevas.la,

Is this a bug, or this is not the "right way"?

cheers,

-- 
Sylvain

Message #8 received at 22463 <at> debbugs.gnu.org (full text, mbox):

From: Mike Frysinger <vapier <at> gentoo.org>
To: Sylvain BERTRAND <sylvain.bertrand <at> gmail.com>
Cc: 22463 <at> debbugs.gnu.org
Subject: Re: c++ linker instead of c linker
Date: Sun,  2 Jan 2022 09:48:11 +0000 (UTC)

On Mon, 25 Jan 2016 22:08:48 +1100, Sylvain BERTRAND wrote:
> In git efl (enlightenment), the libtool library libevas.la has always a c++
> linker rule generated, even though, with some disabled options, only a c linker
> is required: Some AM_CONDITIONAL can remove all c++ source/object files from
> libevas.la,

can you link to a specific example file ?  i looked through efl.git a bit
at commit 6e2497bc014397c4ec9fe78cf06b1f9412cabb68 (which is Jan 2016) and
i couldn't find what you're referring to.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.