https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #37 from joseph at codesourcery dot com ---
On Wed, 9 Oct 2019, stsp at users dot sourceforge.net wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
>
> --- Comment #36 from Stas Sergeev ---
> (In reply to jos...@codesourc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #36 from Stas Sergeev ---
(In reply to jos...@codesourcery.com from comment #35)
> what you want. I'm familiar with many of the details through having
> written multiple such build systems myself.
But even you do make the wrong exp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #35 from joseph at codesourcery dot com ---
On Tue, 8 Oct 2019, stsp at users dot sourceforge.net wrote:
> As well as AS, LD and all the rest?
> But that defeats the entire purpose of configure.
> I need it to work on my PC, on launc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #34 from Stas Sergeev ---
(In reply to jos...@codesourcery.com from comment #33)
> to, you can also make your build system set all the variables such as CC
> and CXX that are needed for the host).
As well as AS, LD and all the rest?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #33 from joseph at codesourcery dot com ---
It can be useful to have the fully-prefixed host tools (but you don't need
to, you can also make your build system set all the variables such as CC
and CXX that are needed for the host).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #32 from Stas Sergeev ---
(In reply to jos...@codesourcery.com from comment #29)
> A common way of doing that is to make $host and $build textually different
> (after passing through config.sub) while still logically the same. E.g.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #31 from Stas Sergeev ---
(In reply to jos...@codesourcery.com from comment #29)
> A common way of doing that is to make $host and $build textually different
> (after passing through config.sub) while still logically the same. E.g.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #30 from Stas Sergeev ---
(In reply to jos...@codesourcery.com from comment #29)
> A common way of doing that is to make $host and $build textually different
> (after passing through config.sub) while still logically the same. E.g.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #29 from joseph at codesourcery dot com ---
On Mon, 7 Oct 2019, stsp at users dot sourceforge.net wrote:
> Is there any way to convince the build system that the
> resulting compiler is alien and cannot be used? I think
A common way
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #28 from Stas Sergeev ---
(In reply to jos...@codesourcery.com from comment #22)
> The build system design is that where A and B are both built at the same
> time, and the build of B uses A, it should use the *newly built* copy of A
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #27 from Stas Sergeev ---
(In reply to jos...@codesourcery.com from comment #26)
> On Thu, 3 Oct 2019, stsp at users dot sourceforge.net wrote:
>
> > Ah, I am starting to understand.
> > So basically you mean something like this:
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #26 from joseph at codesourcery dot com ---
On Thu, 3 Oct 2019, stsp at users dot sourceforge.net wrote:
> Ah, I am starting to understand.
> So basically you mean something like this:
> --with-sysroot=$prefix/$target --with-build-sy
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #25 from Stas Sergeev ---
(In reply to jos...@codesourcery.com from comment #24)
> > But isn't there always a possibility to add
> > one more stage? Say, in the example above where
> > at stage1 we only have a static-only compiler,
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #24 from joseph at codesourcery dot com ---
On Thu, 3 Oct 2019, stsp at users dot sourceforge.net wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
>
> --- Comment #23 from Stas Sergeev ---
> (In reply to jos...@codesourc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #23 from Stas Sergeev ---
(In reply to jos...@codesourcery.com from comment #22)
> On Thu, 3 Oct 2019, stsp at users dot sourceforge.net wrote:
> And overriding like that is fundamentally unsafe, because in general in a
> multi-stage
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #22 from joseph at codesourcery dot com ---
On Thu, 3 Oct 2019, stsp at users dot sourceforge.net wrote:
> - The stage2 compiler is built with --prefix=/usr and
> installed with the DESTDIR set to the build dir. As the
> result, this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #21 from Stas Sergeev ---
Hi Joseph, thanks for your assistance!
(In reply to jos...@codesourcery.com from comment #20)
> The only case where the newly built GCC should be overridden is the
> Canadian cross case,
Since today, this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #20 from joseph at codesourcery dot com ---
The only case where the newly built GCC should be overridden is the
Canadian cross case, and while that does use a pre-installed tool from the
PATH, it's best to use "make all-host" in tha
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #19 from Stas Sergeev ---
OK, but the setup when you want to override
the newly-built gcc, is also needed. Like, when
you want to build the "destdir" gcc with the one
installed directly into prefix (and therefore
working fine on host)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #18 from joseph at codesourcery dot com ---
No, --with-build-time-tools definitely should not override newly built
tools.
For example, in some bootstrap configurations you have to build GCC more
than once. If you're also installin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #17 from Stas Sergeev ---
Created attachment 46991
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46991&action=edit
the fix
Attached is the patch that I think is correct.
It also seems to work properly, i.e. the full
build proc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
Stas Sergeev changed:
What|Removed |Added
Status|RESOLVED|NEW
Resolution|INVALID
22 matches
Mail list logo
