public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Basile STARYNKEVITCH <basile@starynkevitch.net>
To: GCC Mailing List <gcc@gcc.gnu.org>
Subject: adding extra libraries in branches...
Date: Wed, 02 Sep 2009 20:36:00 -0000	[thread overview]
Message-ID: <4A9ED747.5040107@starynkevitch.net> (raw)

Hello All

I am trying to clean up the configure.ac & Makefile.in inside the MELT 
branch. [Several people rightly complained about that].

But I am not an autoconf expert. I welcome a big lot the recent update 
to autoconf 2.64

I have no clear understanding of:

how to add an extra libary (free software) into the middle end [that is 
is, into cc1 binary) Apparently there are several cases:

* the extra library is [L]GPL-ed & FSF-owned & blessed somehow by I 
don't know who, eg GDBM or readline, so could be handled as MPFR.

* the extra library is LGPL-ed but not FSF-owned, but is required by the 
branch

* the extra library is optional to the branch


Any practical hints are very welcome. If someone have time to explain it 
on the wiki or the mailing list, I would be delighted.

BTW, I am trying to
   make PPL & plugin machinery mandatory in the MELT branch
   adding GDBM inside [1].

Regards.

NB: the motivation for GDBM is to perhaps be able to persistently store 
data. http://gcc.gnu.org/ml/gcc/2009-09/msg00053.html

-- 
Basile STARYNKEVITCH         http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***

                 reply	other threads:[~2009-09-02 20:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A9ED747.5040107@starynkevitch.net \
    --to=basile@starynkevitch.net \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).