public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug bootstrap/36995] New: [4.3 Regression] cannot build combined tree from 4.3 branch + trunk binutils
@ 2008-08-01 9:23 bonzini at gnu dot org
2008-08-01 12:02 ` [Bug bootstrap/36995] " joseph at codesourcery dot com
2008-08-10 23:27 ` pinskia at gcc dot gnu dot org
0 siblings, 2 replies; 3+ messages in thread
From: bonzini at gnu dot org @ 2008-08-01 9:23 UTC (permalink / raw)
To: gcc-bugs
trunk binutils needs the sha1 implementation from libiberty, but it's not on
4.3 branch. does the rule that gcc files should override the corresponding src
files hold for release branches? if so, should i backport revision 133503 from
trunk to 4.3 branch? it is safe and only adds the relevant files to include/
and libiberty/.
--
Summary: [4.3 Regression] cannot build combined tree from 4.3
branch + trunk binutils
Product: gcc
Version: 4.3.2
Status: UNCONFIRMED
Keywords: build
Severity: normal
Priority: P3
Component: bootstrap
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: bonzini at gnu dot org
GCC host triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36995
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug bootstrap/36995] [4.3 Regression] cannot build combined tree from 4.3 branch + trunk binutils
2008-08-01 9:23 [Bug bootstrap/36995] New: [4.3 Regression] cannot build combined tree from 4.3 branch + trunk binutils bonzini at gnu dot org
@ 2008-08-01 12:02 ` joseph at codesourcery dot com
2008-08-10 23:27 ` pinskia at gcc dot gnu dot org
1 sibling, 0 replies; 3+ messages in thread
From: joseph at codesourcery dot com @ 2008-08-01 12:02 UTC (permalink / raw)
To: gcc-bugs
------- Comment #1 from joseph at codesourcery dot com 2008-08-01 12:01 -------
Subject: Re: New: [4.3 Regression] cannot build combined
tree from 4.3 branch + trunk binutils
On Fri, 1 Aug 2008, bonzini at gnu dot org wrote:
> trunk binutils needs the sha1 implementation from libiberty, but it's not on
> 4.3 branch. does the rule that gcc files should override the corresponding src
> files hold for release branches? if so, should i backport revision 133503 from
> trunk to 4.3 branch? it is safe and only adds the relevant files to include/
> and libiberty/.
This is not a regression. If using combined trees you always need to take
the *most recent* version of libiberty and reconcile any API changes
manually.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36995
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug bootstrap/36995] [4.3 Regression] cannot build combined tree from 4.3 branch + trunk binutils
2008-08-01 9:23 [Bug bootstrap/36995] New: [4.3 Regression] cannot build combined tree from 4.3 branch + trunk binutils bonzini at gnu dot org
2008-08-01 12:02 ` [Bug bootstrap/36995] " joseph at codesourcery dot com
@ 2008-08-10 23:27 ` pinskia at gcc dot gnu dot org
1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2008-08-10 23:27 UTC (permalink / raw)
To: gcc-bugs
------- Comment #2 from pinskia at gcc dot gnu dot org 2008-08-10 23:26 -------
As mentioned this is not a bug as you have to make sure that the dependent
libraries are compatible.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |WONTFIX
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36995
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-08-10 23:27 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-08-01 9:23 [Bug bootstrap/36995] New: [4.3 Regression] cannot build combined tree from 4.3 branch + trunk binutils bonzini at gnu dot org
2008-08-01 12:02 ` [Bug bootstrap/36995] " joseph at codesourcery dot com
2008-08-10 23:27 ` pinskia at gcc dot gnu dot org
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).