This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[PATCH] Change build g++ to xg++ like gcc is done (PR 54279)

  If the PATH contains the current working directory (yes a bad idea
but it could happen with our users), the build fails because it finds
the newly created g++ which might not find the correct cc1plus.  See
the thread starting at .

This fixes the problem by changing the name of the built g++ to xg++
just like how gcc is handled with xgcc.  I had to change the few
places where g++ is used.

OK?  Bootstrapped and tested on x86_64-linux-gnu with no regressions
and made sure the installed binary was called g++.

Andrew Pinski

* (CXX_FOR_TARGET): Change over to use xg++.
* configure: Regenerate.
* Makefile.tpl (POSTSTAGE1_CXX_EXPORT): Change over to use xg++.
* Regenerate.

* lib/g++.exp (g++_init): Search for xg++ instead of g++ in the build
* lib/obj-c++.exp (obj-c++_init): Likewise.

* (g++$(exeext)): Rename to
(xg++$(exeext)): This.
(g++-cross$(exeext)): Use xg++$(exeext) instead of g++$(exeext).
(c++.start.encap): Likewise.
(c++.install-common): Likewise.

* (${QMTEST_DIR}/context): Use xg++ instead of g++.

* scripts/ (--build-cxx): Use xg++ instead of g++.
* testsuite/lib/libstdc++.exp (libstdc++_init): Likewise.

Attachment: fix54279.diff.txt
Description: Text document

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]