public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: Jim Wilson <wilson@cygnus.com>, Geoff Keating <geoffk@cygnus.com>,
	hjl@lucon.org, gcc-patches@gcc.gnu.org,
	binutils@sourceware.cygnus.com
Subject: Re: $(build_tooldir)/lib (was Re: http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html)
Date: Fri, 21 Jul 2000 20:08:00 -0000	[thread overview]
Message-ID: <org0p2eu9u.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <u9lmyuvrb2.fsf@yorick.soma.redhat.com>

On Jul 21, 2000, Jason Merrill <jason@redhat.com> wrote:

> Do any other projects use unlibsubdir?

I don't think so.  It's GCC that does.  GCC creates the directory so
that other projects don't have to care about it: a yet-to-be-installed
GCC will just find libraries that have already been installed.  If GCC
refrains from creating the directory so that it can find pre-installed
libraries and headers, other projects that depend on it finding them
will have to be taught to tell GCC to look for them there.


H.J., I'm willing to play a bit with cross-building GCC, glibc and
maybe even the kernel itself.  Would you be willing to hand-hold me a
little bit, so that I could understand better the issues you're
talking about, then we'll come back to the list with a joint proposal?

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

  reply	other threads:[~2000-07-21 20:08 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20000520093135A.mitchell@codesourcery.com>
     [not found] ` <orhfbt9nwh.fsf@tamanduatei.dcc.unicamp.br>
     [not found]   ` <20000520095133R.mitchell@codesourcery.com>
2000-05-20 22:10     ` http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html H . J . Lu
2000-05-21 16:44       ` http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html Alexandre Oliva
2000-05-21 16:51         ` http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html H . J . Lu
2000-05-22 15:54         ` http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html Jim Wilson
2000-05-22 17:54           ` http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html H . J . Lu
2000-05-22 18:47             ` http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html Jim Wilson
2000-05-22 20:06               ` http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html H . J . Lu
2000-07-21  1:17           ` $(build_tooldir)/lib (was Re: http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html) Jason Merrill
2000-07-21  7:49             ` H . J . Lu
2000-07-21 10:38               ` Geoff Keating
2000-07-21 10:54                 ` H . J . Lu
2000-07-21 11:54                 ` Jim Wilson
2000-07-21 12:12                   ` H . J . Lu
2000-07-21 14:19                   ` Jason Merrill
2000-07-21 14:48                     ` Geoff Keating
2000-07-21 14:53                       ` H . J . Lu
2000-07-21 15:05                       ` Jim Wilson
2000-07-21 15:12                         ` Geoff Keating
2000-07-21 15:49                           ` H . J . Lu
2000-07-21 15:12                         ` H . J . Lu
2000-07-21 15:33                         ` Angela Marie Thomas
2000-07-21 15:28                     ` Jim Wilson
2000-07-21 17:15                       ` Jason Merrill
2000-07-21 17:41                         ` Jim Wilson
2000-07-21 18:01                           ` Jason Merrill
2000-07-21 19:15                             ` Alexandre Oliva
2000-07-21 19:20                               ` Jason Merrill
2000-07-21 20:08                                 ` Alexandre Oliva [this message]
2000-07-21 20:26                                   ` H . J . Lu
2000-07-21 21:53                                   ` Jason Merrill
2000-07-21 22:29                                     ` Alexandre Oliva
2000-07-22  0:58                                       ` Jason Merrill

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=org0p2eu9u.fsf@guarana.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=geoffk@cygnus.com \
    --cc=hjl@lucon.org \
    --cc=jason@redhat.com \
    --cc=wilson@cygnus.com \
    /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).