On Wed, Jan 04, 2023 at 08:02:12PM +, Gavin Smith wrote:
> I've committed the change to the master branch. I will add it to the
> release branch if there is no further feedback.
I've added the fixes for building on Solaris to the release/7.0 branch now.
On Wed, Jan 04, 2023 at 01:31:22PM +0100, Patrice Dumas wrote:
> On Tue, Jan 03, 2023 at 09:28:03PM +, Gavin Smith wrote:
> > On Mon, Jan 02, 2023 at 03:46:56PM +, Gavin Smith wrote:
> > > One way of fixing this might be to put the generated file in a
> > > subdirectory so that make can't
On Wed, Jan 04, 2023 at 12:44:45PM +, Gavin Smith wrote:
> On Wed, Jan 04, 2023 at 01:31:22PM +0100, Patrice Dumas wrote:
> > On Tue, Jan 03, 2023 at 09:28:03PM +, Gavin Smith wrote:
> > > On Mon, Jan 02, 2023 at 03:46:56PM +, Gavin Smith wrote:
> > > > One way of fixing this might be
On Wed, Jan 04, 2023 at 01:31:22PM +0100, Patrice Dumas wrote:
> On Tue, Jan 03, 2023 at 09:28:03PM +, Gavin Smith wrote:
> > On Mon, Jan 02, 2023 at 03:46:56PM +, Gavin Smith wrote:
> > > One way of fixing this might be to put the generated file in a
> > > subdirectory so that make can't
On Tue, Jan 03, 2023 at 09:28:03PM +, Gavin Smith wrote:
> On Mon, Jan 02, 2023 at 03:46:56PM +, Gavin Smith wrote:
> > One way of fixing this might be to put the generated file in a
> > subdirectory so that make can't see it. Or it might not be worth
> > bothering as this version of make
Gavin Smith wrote:
> somehow harder to get access to local files.
>
> The solution appears to be to install something called the Guest Additions.
Alternatively, one can use 'scp' between the guest and the host (at
IPv4 address 10.0.2.2).
Bruno
On Mon, Jan 02, 2023 at 03:46:56PM +, Gavin Smith wrote:
> One way of fixing this might be to put the generated file in a
> subdirectory so that make can't see it. Or it might not be worth
> bothering as this version of make and/or operating system isn't
> very important. Another alternative
On Mon, Jan 02, 2023 at 03:46:56PM +, Gavin Smith wrote:
> I'm yet to work out how to get logs out of the virtual machine
I found it easy to get Internet access on the virtual machine (I downloaded
Texinfo 7.0.1 from ftp.gnu.org using curl), but somehow harder to get
access to local files.
On Mon, Jan 02, 2023 at 09:01:23PM +0100, Bruno Haible wrote:
> By doing this, you improved things on Solaris OpenIndiana. But it
> got worse on FreeBSD, where the 'man' command has a '-w' option
> that displays the location but does not have a '--where' option [1].
> Likewise on macOS, where 'man
Gavin Smith wrote:
> I will be deleting the disk image as soon as this is finished due
> to the amount of space it takes up. I will not be testing routinely
> on OpenIndiana using VirtualBox.
That's OK, as I will be routinely testing on Solaris OpenIndiana
when you ask.
> > After the system it
On Sun, Jan 01, 2023 at 09:48:47PM +0100, Patrice Dumas wrote:
> This looks like a failure of formatting
> manual_include_accented_file_name_latin1 test, which could be checked
> separately with
>
> ./run_parser_all.sh -dir formatting manual_include_accented_file_name_latin1
>
> But it is a bit
On Sun, Jan 01, 2023 at 06:49:38PM +, Gavin Smith wrote:
> Making check in tests
> mksh: Fatal error: The string `included_lan1.texi' is not valid in
> current locale
> Current working directory: /export/home/g/texinfo-7.0.1/tp/tests
>
> ( is a single byte).
>
> This is in a UTF-8 locate.
>
On Tue, Dec 27, 2022 at 12:57:21PM +0100, Bruno Haible wrote:
> Building GNU texinfo 7.0.1 on OpenSolaris 2022.10, I get the same failure
> as reported in
> <https://lists.gnu.org/archive/html/bug-texinfo/2022-10/msg00187.html>:
>
> FAIL: t/dir-file-sloppily.sh
>
&g
Building GNU texinfo 7.0.1 on OpenSolaris 2022.10, I get the same failure
as reported in
<https://lists.gnu.org/archive/html/bug-texinfo/2022-10/msg00187.html>:
FAIL: t/dir-file-sloppily.sh
Gavin Smith wrote:
> I don't know what is causing this and would need access to a system with
14 matches
Mail list logo
