public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Bernd Jendrissek <berndfoobar@users.sourceforge.net>,
	Nathanael Nerode <neroden@twcny.rr.com>,
	gcc@gcc.gnu.org, gdb@sources.redhat.com,
	binutils@sources.redhat.com
Subject: Re: Partial autoconf transition thoughts
Date: Fri, 13 Jun 2003 14:02:00 -0000	[thread overview]
Message-ID: <orisraulcr.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <Pine.GSO.3.96.1030613115951.13762A-100000@delta.ds2.pg.gda.pl>

On Jun 13, 2003, "Maciej W. Rozycki" <macro@ds2.pg.gda.pl> wrote:

>  OK, then what about the following example: on an i386-linux system I have
> three shared binaries of libbfd, one is for i386-linux host and i386-linux
> target, another one is for i386-linux host and mipsel-linux target and the
> last one is for mipsel-linux host and mipsel-linux target.

$(exec_prefix)/$(target_alias) should place them in different
directories.

>  Anyway see 'http://sources.redhat.com/ml/binutils/2002-05/msg00184.html'
> and its follow ups for the origin of the choice -- as you took part in the
> discussion, I'm actually surprised you are not aware of the current setup.

/me claims faulty memory, in self defense :-)

/me notes that the original thread subject was bfd.h, and
$(includedir) is part of $(prefix), not $(exec_prefix) like $(libdir).

Anyway, after re-reading the thread, I remember why we chose to do it
the way we did it.  It does make sense, even thought I still find it
not ideal.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer

  reply	other threads:[~2003-06-13 14:02 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-10  0:40 Nathanael Nerode
2003-06-10  0:59 ` Alexandre Oliva
2003-06-10 10:59   ` Maciej W. Rozycki
2003-06-10 11:38     ` Andreas Schwab
2003-06-10 12:45       ` Maciej W. Rozycki
2003-06-10 22:06     ` Alexandre Oliva
2003-06-11 11:32       ` Maciej W. Rozycki
2003-06-11 18:04         ` Alexandre Oliva
2003-06-11 19:39           ` Maciej W. Rozycki
2003-06-11 20:39             ` Alexandre Oliva
2003-06-12 11:21               ` Maciej W. Rozycki
2003-06-12 12:10                 ` Bernd Jendrissek
2003-06-12 12:26                   ` Maciej W. Rozycki
2003-06-12 21:42                     ` Alexandre Oliva
2003-06-13 10:35                       ` Maciej W. Rozycki
2003-06-13 14:02                         ` Alexandre Oliva [this message]
2003-06-13 18:32                           ` Maciej W. Rozycki
2003-06-13 19:25                             ` Alexandre Oliva
2003-06-13 20:15                               ` Maciej W. Rozycki
2003-06-13 20:54                                 ` Alexandre Oliva
2003-06-14 14:33                                   ` Maciej W. Rozycki
2003-06-14 15:43                                     ` Alexandre Oliva
2003-06-14 18:27                                       ` Maciej W. Rozycki
2003-06-26  7:24                                         ` Alexandre Oliva
2003-06-28  0:35                                           ` Maciej W. Rozycki
  -- strict thread matches above, loose matches on Subject: below --
2003-06-10  1:40 Nathanael Nerode
2003-06-10  1:46 ` DJ Delorie
2003-06-09 22:02 Daniel Jacobowitz
2003-06-09 22:17 ` Andrew Cagney
2003-06-09 22:34 ` Alexandre Oliva
2003-06-09 23:14   ` Daniel Jacobowitz
2003-06-10  0:44     ` Alexandre Oliva

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=orisraulcr.fsf@free.redhat.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=berndfoobar@users.sourceforge.net \
    --cc=binutils@sources.redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=macro@ds2.pg.gda.pl \
    --cc=neroden@twcny.rr.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).