From: DJ Delorie <dj@redhat.com>
To: hjl@lucon.org
Cc: ac131313@cygnus.com, gdb@sources.redhat.com, gcc@gcc.gnu.org
Subject: Re: The canadian cross build is broken
Date: Mon, 25 Mar 2002 09:50:00 -0000 [thread overview]
Message-ID: <200203251750.g2PHoKS25089@greed.delorie.com> (raw)
In-Reply-To: <20020323101441.A799@lucon.org> (hjl@lucon.org)
> I did. You can follow
>
> http://sources.redhat.com/ml/binutils/2002-02/msg00120.html
>
> to see it. DJ believed my patch was wrong, but didn't provide a working
> solution.
The problem is that --with-target-subdir invokes some behaviors that
aren't appropriate for a build-libiberty, mostly pertaining to
multilibs. You yourself weren't sure of your patch:
"The following hack seems to work, but I'm not convinced it's the
right fix."
> So far, only 2 people complained.
The number of people complaining usually has nothing to do with the
severity of a bug or the correctness of its solution. Plus, we do
canadians inside Red Hat all the time and nobody's complained to me
internally. This doesn't mean it's not a problem, it just means it's
not an "obviously broken" type of problem. There is a trivial
workaround (which is why RH doesn't see it): don't build in the source
directory.
Perhaps we should disable building in the source directory if it's not
a simple native? It would simplify some things and make maintaining
it easier. But that depends on how much more effort is needed to get
the current solution working right.
> We need more people to tell DJ to get it fixed.
Sorry, this won't work. I'm a volunteer, just like you. Maybe we
need more people to tell *you* to submit a correct solution? However,
I appreciate the reminder (even a mildly insulting one) as I do have
this on my todo list, and might have time to actually *look at* my
todo list this week ;)
> Maybe I should give up since my gcc, gdb and binutils don't have
> this problem.
You may do whatever you wish in your own sources, and we certainly
can't force you to contribute back to the official sources.
next prev parent reply other threads:[~2002-03-25 17:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-22 22:52 H . J . Lu
2002-03-23 7:29 ` Andrew Cagney
2002-03-23 10:14 ` H . J . Lu
2002-03-25 9:50 ` DJ Delorie [this message]
2002-03-25 14:15 ` DJ Delorie
2002-03-26 13:24 ` H . J . Lu
2002-03-26 13:35 ` DJ Delorie
2002-03-26 13:42 ` H . J . Lu
2002-03-26 13:49 ` DJ Delorie
2002-03-26 13:53 ` H . J . Lu
2002-03-26 14:00 ` DJ Delorie
2002-03-26 14:36 ` H . J . Lu
2002-03-26 14:49 ` DJ Delorie
2002-03-26 14:59 ` H . J . Lu
2002-03-26 15:30 ` 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=200203251750.g2PHoKS25089@greed.delorie.com \
--to=dj@redhat.com \
--cc=ac131313@cygnus.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--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