I'd like to ping for this patch: https://gcc.gnu.org/ml/gcc-patches/2019-01/msg01779.html
Thanks Bernd. On 1/31/19 12:38 PM, Bernd Edlinger wrote: > Hi, > > I have an issue with the installation of gcc when configured with > --enable-languages=all > on an arm-target where install-sh is used, and make install fails at > libphobos as follows: > > if test -f $file; then \ > /home/ed/gnu/gcc-9-20190127-0/install-sh -c -m 644 -D $file > /home/ed/gnu/arm-linux-gnueabihf/lib/gcc/armv7l-unknown-linux-gnueabihf/9.0.1/include/d/$file > ; \ > else \ > /home/ed/gnu/gcc-9-20190127-0/install-sh -c -m 644 -D > ../../../../gcc-9-20190127-0/libphobos/libdruntime/$file \ > > /home/ed/gnu/arm-linux-gnueabihf/lib/gcc/armv7l-unknown-linux-gnueabihf/9.0.1/include/d/$file > ; \ > fi ; \ > done > /home/ed/gnu/gcc-9-20190127-0/install-sh: invalid option: -D > /home/ed/gnu/gcc-9-20190127-0/install-sh: invalid option: -D > /home/ed/gnu/gcc-9-20190127-0/install-sh: invalid option: -D > ... > > I have fixed the installation with the attached patch, but when I regenerate > the automake > files using automake-1.15.1 and autoconf-2.69, I have an issue that apparently > the configure.ac must be out of sync, and the the generated files are missing > the option --runstatedir no matter what I do. At least on the source > > RFC, because I am not sure what the --runstatedir option is, and if it is > intentional to remove, > and forgotten to re-generate, or if was intended to add, and forgotten to > check in the > configure.ac. > > Attached patch which fixes the install issue, and removes the --runstatedir > configure option. > Is OK as is, or has anybody an idea how to fix this mess? > > > Thanks > Bernd. >
