On Fri, Nov 21, 2025, 17:38 Mark Thomas <[email protected]> wrote: > On 21/11/2025 18:15, Gilles Sadowski wrote: > > Le ven. 21 nov. 2025 à 15:39, Mark Thomas <[email protected]> a écrit : > >> > >> On 21/11/2025 12:24, Gilles Sadowski wrote: > >>> Le ven. 21 nov. 2025 à 09:28, Mark Thomas <[email protected]> a écrit : > >>>> > >>>> On 21/11/2025 01:10, Gilles Sadowski wrote: > >>>>> Hi. > >>>>> > >>>>> Blocked at the second step of "src/native/unix/INSTALL.txt": > >>>>> > >>>>> $ cd src/native/unix > >>>>> $ sh support/buildconf.sh > >>>> > >>>> The above step is only necessary if building from a git checkout. > >>> > >>> Aren't we supposed to do that (i.e. build *everything*) as part > >>> of the review procedure? > >> > >> You built Windows from the src zip so I assumed you used the tarball for > >> Linux. I was just pointing out if you had, that step wasn't required. > > > > ? > > I don't build anything on "Windows". > > Sorry. Mis-read the thread. It was Gary that built on Windows. >
FYI I build on Windows 11 AND Ubuntu in WSL ;-) Gary > > Mark > > > > >> If you want to check the build directly from a checkout then you are of > >> course free to do so. > > > > I don't want to claim that I built that component if I didn't... > > I must be missing something (I never tried to review this > > component, nor any other that requires compiling C code). > > > >>>> If > >>>> using the native-src bundle it is not necessary. > >>>> > >>>>> support/buildconf.sh: configure script generated successfully > >>>>> $ ./configure --with-java=/usr/lib/jvm/java-17-openjdk-amd64/ > >>>>> configure: error: cannot find install-sh, install.sh, or shtool in > >>>>> ./support "."/./support > >>>> > >>>> That looks like an environmental issue. configure (and subsequent > build) > >>>> works as expected for me. > >>> > >>> OK. The message isn't necessarily clear for everyone (including > >>> people who did C programming a long time ago). > >>> Maybe the "INSTALL.txt" should list utilities that must be available > >>> so that we can tell apart issues? > >> > >> It does state Automake is required. Strictly it is Autotools (of which > >> automake is one). I can update that so it is clearer. > > > > $ dpkg -L autotools-dev > > /. > > /usr > > /usr/bin > > /usr/bin/dh_autotools-dev_restoreconfig > > /usr/bin/dh_autotools-dev_updateconfig > > /usr/share > > /usr/share/doc > > /usr/share/doc/autotools-dev > > /usr/share/doc/autotools-dev/NEWS.Debian.gz > > /usr/share/doc/autotools-dev/README.Debian.gz > > /usr/share/doc/autotools-dev/TODO > > /usr/share/doc/autotools-dev/changelog.Debian.gz > > /usr/share/doc/autotools-dev/changelog.gz > > /usr/share/doc/autotools-dev/copyright > > /usr/share/doc/autotools-dev/upstream.mail.template > > /usr/share/man > > /usr/share/man/man1 > > /usr/share/man/man1/dh_autotools-dev_restoreconfig.1.gz > > /usr/share/man/man1/dh_autotools-dev_updateconfig.1.gz > > /usr/share/misc > > /usr/share/misc/config.guess > > /usr/share/misc/config.sub > > /usr/share/perl5 > > /usr/share/perl5/Debian > > /usr/share/perl5/Debian/Debhelper > > /usr/share/perl5/Debian/Debhelper/Sequence > > /usr/share/perl5/Debian/Debhelper/Sequence/autotools_dev.pm > > > > So, package "autotools-dev" is installed. > > > > $ uname -a > > Linux eccen 5.10.0-32-amd64 #1 SMP Debian 5.10.223-1 (2024-08-10) > > x86_64 GNU/Linux > > $ ./configure > > configure: error: cannot find install-sh, install.sh, or shtool in > > ./support "."/./support > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
