> Can you please be a little more specific as to what kind of breakage you
> see and/or specific configuration options and steps required to reproduce
> it?
/usr/bin/install: missing destination file operand after 'rts/libgnat-21.so'
Try '/usr/bin/install --help' for more information.
ln: failed
Eric,
On Wed, 18 Dec 2019, Maciej W. Rozycki wrote:
> On Wed, 18 Dec 2019, Eric Botcazou wrote:
>
> > > gcc/ada/
> > > * gcc-interface/Makefile.in (ADA_RTL_DSO_DIR): New variable.
> > > (install-gnatlib): Use it in place of ADA_RTL_OBJ_DIR for shared
> > > library installation.
> > >
>
On Wed, 18 Dec 2019, Eric Botcazou wrote:
> > gcc/ada/
> > * gcc-interface/Makefile.in (ADA_RTL_DSO_DIR): New variable.
> > (install-gnatlib): Use it in place of ADA_RTL_OBJ_DIR for shared
> > library installation.
> >
> > libada/
> > * Makefile.in (toolexecdir, toolexecli
> gcc/ada/
> * gcc-interface/Makefile.in (ADA_RTL_DSO_DIR): New variable.
> (install-gnatlib): Use it in place of ADA_RTL_OBJ_DIR for shared
> library installation.
>
> libada/
> * Makefile.in (toolexecdir, toolexeclibdir): New variables.
> (LIBADA_FLAGS_T
On Fri, 27 Sep 2019, Arnaud Charlet wrote:
> > Shall I amend the change description anyhow then? I know it has not (as
> > yet, as discussed at the GNU Tools Cauldron recently) been enforced for
> > the GCC project (unlike with e.g. glibc), however I mean to use it whole
> > as the commit mes
> Shall I amend the change description anyhow then? I know it has not (as
> yet, as discussed at the GNU Tools Cauldron recently) been enforced for
> the GCC project (unlike with e.g. glibc), however I mean to use it whole
> as the commit message, which is what I have been doing for quite a wh
On Thu, 26 Sep 2019, Arnaud Charlet wrote:
> > Notice that ADA_RTL_OBJ_DIR never changes with/without the use of this
> > configuration option (as expected).
> >
> > Does it answer your question?
>
> Yes, that's now very clear, thanks!
Sorry not to make the original change description clear
> Notice that ADA_RTL_OBJ_DIR never changes with/without the use of this
> configuration option (as expected).
>
> Does it answer your question?
Yes, that's now very clear, thanks!
The change is OK for me, thanks.
Arno
On Thu, 26 Sep 2019, Arnaud Charlet wrote:
> > Respect the `--enable-version-specific-runtime-libs' configuration
> > option in libada/, so that shared gnatlib libraries will be installed
> > in non-version-specific $(toolexeclibdir) if requested. In a
> > cross-compilation environment this he
> Respect the `--enable-version-specific-runtime-libs' configuration
> option in libada/, so that shared gnatlib libraries will be installed
> in non-version-specific $(toolexeclibdir) if requested. In a
> cross-compilation environment this helps setting up a consistent
> sysroot, which can th
Respect the `--enable-version-specific-runtime-libs' configuration
option in libada/, so that shared gnatlib libraries will be installed
in non-version-specific $(toolexeclibdir) if requested. In a
cross-compilation environment this helps setting up a consistent
sysroot, which can then be shar
11 matches
Mail list logo
