From: Zack Weinberg <zack@codesourcery.com>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: DJ Delorie <dj@redhat.com>,
hjl@lucon.org, binutils@sources.redhat.com,
gcc-patches@gcc.gnu.org
Subject: Re: PATCH: Fix shared library build for libiberty
Date: Fri, 17 Dec 2004 06:03:00 -0000 [thread overview]
Message-ID: <877jnh8nrf.fsf@codesourcery.com> (raw)
In-Reply-To: <m3wtvh4l41.fsf@uniton.integrable-solutions.net> (Gabriel Dos Reis's message of "17 Dec 2004 05:14:22 +0100")
Gabriel Dos Reis <gdr@integrable-solutions.net> writes:
D> Zack Weinberg <zack@codesourcery.com> writes:
>
> | DJ Delorie <dj@redhat.com> writes:
> |
> | >> I believe libiberty is the only library which uses config/mh-CPUpic
> | >> for building shared library. Other libraries use libtool for that,
> | >> which doesn't use config/mh-CPUpic.
> | >
> | > I'd rather libiberty use libtool, then. Any reason not to? Would you
> | > like to try changing it?
> |
> | libtool is evil and must be destroyed,
>
> Maybe we should avoid describing software (mis)features in [...]
I was being tongue-in-cheek, as the rest of the sentence should have
made clear.
zw
next prev parent reply other threads:[~2004-12-17 6:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 23:01 H. J. Lu
2004-12-17 2:01 ` DJ Delorie
2004-12-17 2:08 ` H. J. Lu
2004-12-17 2:10 ` DJ Delorie
2004-12-17 2:56 ` Zack Weinberg
2004-12-17 4:16 ` Gabriel Dos Reis
2004-12-17 6:03 ` Zack Weinberg [this message]
2004-12-17 5:21 ` H. J. Lu
2004-12-17 15:41 ` H. J. Lu
2004-12-17 17:48 ` DJ Delorie
2004-12-17 19:01 ` H. J. Lu
2004-12-17 19:11 ` DJ Delorie
2004-12-18 0:22 ` H. J. Lu
2004-12-18 0:49 ` DJ Delorie
2004-12-18 1:44 ` H. J. Lu
2004-12-18 1:51 ` DJ Delorie
2004-12-18 21:38 ` Andrew Pinski
2004-12-24 14:10 ` Andreas Jaeger
2004-12-24 15:23 ` DJ Delorie
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=877jnh8nrf.fsf@codesourcery.com \
--to=zack@codesourcery.com \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=hjl@lucon.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).