This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: plugin directory

From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
To: Basile STARYNKEVITCH <basile at starynkevitch dot net>
Cc: Dave Korn <dave dot korn dot cygwin at googlemail dot com>, Rafael Espindola <espindola at google dot com>, gcc-patches <gcc-patches at gcc dot gnu dot org>
Date: Wed, 23 Dec 2009 10:51:59 +0000
Subject: Re: plugin directory
References: <4B153FB2.8050501@starynkevitch.net> <38a0d8450912221321p57afa875y1ee475bed1956912@mail.gmail.com> <4B31EAB9.3060408@gmail.com> <4B31EDEA.6000008@starynkevitch.net>

Basile STARYNKEVITCH wrote:

> 
> In principle, I perhaps could do that. In practice, autoconf is
> something that scares me a big lot. Could you help me (e.g. give me
> concrete insights) on how to autoconf that ".so" string?

  I think you could be able to use the SHLIB_EXT variable used in building
libgcc, which you'd need to pass in using a -D option from the makefile.  (I
spoke without thinking, libtool of course doesn't get a look in at the
$objdir/gcc/ level.)

> Regards.
> 
> PS. I might not answer before 2010. Happy Christmas to every one.

  Likewise :)

    cheers,
      DaveK

References:
- plugin directory
  - From: Basile STARYNKEVITCH
- Re: plugin directory
  - From: Rafael Espindola
- Re: plugin directory
  - From: Dave Korn
- Re: plugin directory
  - From: Basile STARYNKEVITCH

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]