https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116730
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2024-09-16 00:00:00 |2024-09-17
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Keywords| |documentation
Summary|`make install` fails when |build is broken when
|processing libbacktrace |building in subdirectory of
|while installing libstdc++ |a subdirectory of the src
|due invoking configure with |directory
|a relative path other than |
|../ |
Component|libstdc++ |bootstrap
--- Comment #11 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Oh yes. This was never really supported.
We had wording in install.texi warning about this case but it was changed with
r14-6041-g875c7771097d12 because it looks like it was misunderstood what was
supported on this or not.
so in summary:
```
cd gcc
mkdir -p objdir/objdir
../../configure --prefix=${MYPREFIX}
make -jN && make install
```
fails and even using:
```
`pwd`/../../configure --prefix=${MYPREFIX}
```
fails.
The best thing is not to build two layers deap.
I am testing a full non relative path configure now; that is:
```
mkdir -p t1/t1
cd t1/t1
/home/apinski/src/tt1/worktrees/14.2.0/configure --prefix=${HOME}/gcc-14.2.0
make -j16 && make install
```
TO see if that fails.
