Hi,
First, thanks a lot to all the people who reported problems, fixed bugs
and made various enhancements in the last few months.
There were non-trivial changes since 1.22.4.rc3 but the build looks
stable and everyone seems to agree that there are no more commits needed
for 1.22.4 and that we can
On Fri, Nov 30, 2018, Bertrand Garrigues wrote:
> To all the developers: please hold on your commits now, this release is
> for final sanity checks, only critical fixes should be commited from
> now. If you really want to publish something that you are working on,
> feel free to push a development
Hi Bertrand,
Bertrand Garrigues wrote on Fri, Nov 30, 2018 at 01:00:59AM +0100:
> There were non-trivial changes since 1.22.4.rc3 but the build looks
> stable and everyone seems to agree that there are no more commits needed
> for 1.22.4 and that we can finalize the release. So I've just made a
Hi Ingo,
On Fri, Nov 30 2018 at 05:33:11 PM, Ingo Schwarze wrote:
[...]
> However, there are problems on Oracle Solaris 11:
>
> schwarze@unstable11s [unstable11s]:~/groff-1.22.4.rc4/build > uname -a
> SunOS unstable11s 5.11 11.3 sun4u sparc SUNW,SPARC-Enterprise
>
> This is from ../configure
Hi,
so here is my final test report.
On Solaris 11, with the following workaround, it built, it installed,
and it runs.
export groff_cv_decl_needed_hypot=no
../configure
I'm not planning to do more testing on Solaris 11 unless somebody asks
for additional information.
Also, i briefly test
On Fri, Nov 30, 2018 at 01:00:59AM +0100, Bertrand Garrigues wrote:
> To all the developers: please hold on your commits now, this release is
> for final sanity checks, only critical fixes should be commited from
> now.
I pushed a couple of corrections to error paths in the new
contrib/mom/example
> Anything in particular you want me to have a closer look at on
> OpenBSD, Debian Jessie, or Solaris 9, 10, or 11?
Thanks for checking the issues! As soon as they are fixed I suggest
we contact Nelson Beebe[*] to build and install the next RC on his
(really impressive) zoo of operating systems
Hi Bertrand,
Bertrand Garrigues wrote on Fri, Nov 30, 2018 at 01:00:59AM +0100:
> A few checks can be done with:
>
> make check
Oops, i overlooked this part earlier.
OpenBSD-current:
schwarze@isnote $ make check
make check-am
make
make all-am
make check-TESTS
PASS: contrib/gdiffmk/tes
Hi Ingo,
Thanks for all your tests !
On Fri, Nov 30 2018 at 05:33:11 PM, Ingo Schwarze wrote:
[...]
> However, there are problems on Oracle Solaris 11:
[...]
> checking whether URW fonts in pfb format are available...
> grep: illegal option -- A
> Usage: grep [-c|-l|-q] -bhinsvw pattern file
Ingo,
On Sat, Dec 01 2018 at 01:20:30 AM, Ingo Schwarze wrote:
> On Solaris 11, with the following workaround, it built, it installed,
> and it runs.
>
> export groff_cv_decl_needed_hypot=no
> ../configure
I'll check what you've described on this issue on your other mail next
week. Should I
Hi Ingo,
On Sat, Dec 01 2018 at 04:44:45 PM, Ingo Schwarze wrote:
> OpenBSD-current:
>
> schwarze@isnote $ make check
> make check-am
> make
> make all-am
> make check-TESTS
> PASS: contrib/gdiffmk/tests/gdiffmk_tests.sh
> sed -e
> "s|[@]abs_top_builddir[@]|/usr/ports/pobj/groff-1.22.4/gro
Hi Colin,
On Sat, Dec 01 2018 at 01:13:54 AM, Colin Watson wrote:
> I pushed a couple of corrections to error paths in the new
> contrib/mom/examples/test-mom.sh.in script. Not perhaps quite critical,
> but since it was only added a week ago and the changes can only possibly
> affect "make check
Hi Werner,
On Sat, Dec 01 2018 at 07:09:44 AM, Werner LEMBERG wrote:
>> Anything in particular you want me to have a closer look at on
>> OpenBSD, Debian Jessie, or Solaris 9, 10, or 11?
>
> Thanks for checking the issues! As soon as they are fixed I suggest
> we contact Nelson Beebe[*] to build
Hi Bertrand,
Bertrand Garrigues wrote on Mon, Dec 03, 2018 at 01:29:38AM +0100:
> I'm not very familiar with Solaris, so first a general question:
> what is the most 'important' Solaris-like distribution?
There are no such things as Solaris-like distributions.
> I've understood that Solaris 11
>> As soon as they are fixed I suggest we contact Nelson Beebe[*] to
>> build and install the next RC on his (really impressive) zoo of
>> operating systems.
>
> Sounds interesting, but what is it exactly? I've skimmed through
> his home page (https://www.math.utah.edu/~beebe/) but haven't seen
Hi Ingo and Colin,
On Mon, Dec 03 2018 at 01:48:19 AM, Bertrand Garrigues
wrote:
> On Sat, Dec 01 2018 at 04:44:45 PM, Ingo Schwarze wrote:
>> So it appears you are unconditionally testing for optional features
>> in the test suite.
>
> Yes, I will work on Colin's suggestion wo exit with 77 in
Since a new rc will have to be built anyway, any chance this patch
could be included? It's not critical by any means, but it's very
low-risk (correcting only documentation) and fixes a factual error
that makes following the logic of the example confusing until you go
look up what the nl register a
Hi Dave,
On Wed, Dec 05 2018 at 09:11:45 AM, Dave Kemper wrote:
> Since a new rc will have to be built anyway,
Yes, unfortunately the "Final RC" in my mail subject was too optimistic.
> any chance this patch could be included? It's not critical by any
> means, but it's very low-risk (correcting
Salut Bertrand,
i just finished redoing the tests. I'm not sure how much they tell
us about the upcoming release: i built the release tarballs that i
now tested myself, starting with the process described in INSTALL.REPO.
I also had a look at the changes you committed and didn't spot anything
th
Hi Bertrand,
i finally figured out the hdtbl failure on Solaris.
The mom test is still failing, though.
OK to push the patch below, before release?
I see no regression on OpenBSD, and no regression on Debian.
Yours,
Ingo
commit 9cb6801d5f90a221be6f22df975ef54a00751fef
Author: Ingo Schwarze
Hi Deri, hi Bertrand,
i found out more about why the mom test is failing on Solaris 11.
It turns out not just the test is broken, but there is likely a
portability issue in gropdf(1).
I see this in the build log:
GROFFcontrib/mom/examples/typesetting.pdf
Negative length at /home/schwar
Hi Ingo,
On Thu, Dec 06 2018 at 06:44:18 PM, Ingo Schwarze wrote:
> Hi Bertrand,
>
> i finally figured out the hdtbl failure on Solaris.
> The mom test is still failing, though.
>
> OK to push the patch below, before release?
> I see no regression on OpenBSD, and no regression on Debian.
No regr
Hi Ingo,
On Thu, Dec 06 2018 at 09:45:31 PM, Ingo Schwarze wrote:
> i found out more about why the mom test is failing on Solaris 11.
> It turns out not just the test is broken, but there is likely a
> portability issue in gropdf(1).
>
> I see this in the build log:
>
> GROFFcontrib/mom/e
Hi Bertrand,
Bertrand Garrigues wrote on Thu, Dec 06, 2018 at 11:47:46PM +0100:
> On Thu, Dec 06 2018 at 09:45:31 PM, Ingo Schwarze wrote:
>> i found out more about why the mom test is failing on Solaris 11.
>> It turns out not just the test is broken, but there is likely a
>> portability issue
On Thursday, 6 December 2018 20:45:31 GMT Ingo Schwarze wrote:
> Hi Deri, hi Bertrand,
>
> i found out more about why the mom test is failing on Solaris 11.
> It turns out not just the test is broken, but there is likely a
> portability issue in gropdf(1).
>
> I see this in the build log:
>
>
Hi Deri,
Deri wrote on Fri, Dec 07, 2018 at 12:09:20AM +:
> I only have access to intel or arm. Please can you test changing
> line 2428 to:-
>
> my $sl=unpack('L>',$hdr);
>
> I.E. Adding the ">" symbol.
With 'L>', the problem remains unchanged. I guess that is due to the
fa
At 2018-12-06T18:44:18+0100, Ingo Schwarze wrote:
> Improve shell script portability in the hdtbl fonts examples.
Thanks for catching and fixing this!
> 1. POSIX requires "echo -n" to print "-n" followed by
>a newline character, so use printf(1) instead.
> 2. According to POSI
Hi,
> > +| tr '[:cntrl:]' '[ *32]'"
>
> This might not be portable _enough_.
I wasn't going to bother Ingo, given all the ports-testing he's doing,
but since popped up...
The time-honoured way to get modern-day `printf foo' is
echo foo | tr -d \\012
If groff's still hoping to build
On Friday, 7 December 2018 01:41:54 GMT Ingo Schwarze wrote:
> Thanks a lot for looking into the matter!
Hi Ingo
Thanks for all your help.
> I think you should commit and push the change to add the '<' before
> Bertrand releases. You already tested on little endian, i tested
> on big endian,
Hi Ralph,
Ralph Corderoy wrote on Fri, Dec 07, 2018 at 11:06:53AM +:
> I wasn't going to bother Ingo, given all the ports-testing he's doing,
> but since popped up...
>
> The time-honoured way to get modern-day `printf foo' is
>
> echo foo | tr -d \\012
>
> If groff's still hoping to b
Hi Ingo,
> > The time-honoured way to get modern-day `printf foo' is
> >
> > echo foo | tr -d \\012
>
> Thanks for looking at it, but unfortunately, that does not work at all.
> I just tested the version you suggest, and even on OpenBSD, it does not
> work:
>
> . pso sh -c \
>"printf
Hi Ralph,
Ralph Corderoy wrote on Fri, Dec 07, 2018 at 05:05:21PM +:
> Ingo:
>> Ralph:
>>> The time-honoured way to get modern-day `printf foo' is
>>>
>>> echo foo | tr -d \\012
>> Thanks for looking at it, but unfortunately, that does not work at all.
>> I just tested the version you s
Hi Branden,
G. Branden Robinson wrote on Thu, Dec 06, 2018 at 11:17:11PM -0500:
> At 2018-12-06T18:44:18+0100, Ingo Schwarze wrote:
>> -| tr '[:cntrl:]' ' '"
>> +| tr '[:cntrl:]' '[ *32]'"
> This might not be portable _enough_.
>
> The number of characters in the class :cntrl: i
Hi Ingo,
On Fri, Nov 30 2018 at 05:33:11 PM, Ingo Schwarze wrote:
> What is potentially more serious is that "make" dies like this:
>
> CXX src/libs/libgroff/libgroff_a-hypot.o
> ../src/libs/libgroff/hypot.cpp:24:30: error: ‘double hypot(double, double)’
> conflicts with a previous declar
Hi Ingo,
> > > > The time-honoured way to get modern-day `printf foo' is
> > > >
> > > > echo foo | tr -d \\012
>
> Why would you want to return to echo(1)?
Because I was giving the `time-honoured way' and I thought I saw a
recent mention on this that if something still works on older system
Hi Ralph,
Ralph Corderoy wrote on Sat, Dec 08, 2018 at 11:28:40AM +:
> Ingo:
>> Ralph:
>>> Ingo:
Ralph:
> The time-honoured way to get modern-day `printf foo' is
> echo foo | tr -d \\012
>> Why would you want to return to echo(1)?
> Because I was giving the `time-honoured
Hi Bertrand,
incidentally, i did an update of my OpenBSD-current base system
since building the last groff release tarball three days ago.
The system now uses the LLVM linker by default instead of the GNU
binutils linker:
$ which ld
/usr/bin/ld
$ ld --version
LLD 6.0.0 (compatible with
> On Solaris 9, installation still fails because of the "for f in ;
> do" we discussed earlier, and the test suite still fails as shown at
> the end (no change in that respect), but i see no regressions from
> your patch.
I really see no reason to not fix this single spot that prevents
installat
Hi Ingo,
> On Solaris 10, Perl 5.8.4 is in use. On that ancient version of Perl,
> Deri's latest gropdf(1) endianness fix is ineffective because support
> for "L<" appears to be broken in unpack(3p).
Are you aware of `N' and `V'? I wonder if they work.
Cheers, Ralph.
On Saturday, 8 December 2018 23:52:04 GMT Bertrand Garrigues wrote:
> > On Solaris 10, Perl 5.8.4 is in use. On that ancient version of Perl,
> > Deri's latest gropdf(1) endianness fix is ineffective because support
> > for "L<" appears to be broken in unpack(3p).
>
> [...]
>
> > I don't think w
Hi Deri,
Deri wrote on Sun, Dec 09, 2018 at 12:30:14AM +:
> On Saturday, 8 December 2018 23:52:04 GMT Bertrand Garrigues wrote:
>> I can't judge if it would be easy or not to work around this problem (I
>> let Deri comment on that), but I agree that it's probably not worth
>> spending too muc
Hi Bertrand,
Bertrand Garrigues wrote on Sun, Dec 09, 2018 at 12:52:04AM +0100:
> On Sat, Dec 08 2018 at 08:06:11 PM, Ingo Schwarze wrote:
>> On Solaris 10, Perl 5.8.4 is in use. On that ancient version of Perl,
>> Deri's latest gropdf(1) endianness fix is ineffective because support
>> for "L<
Hi,
Bertrand Garrigues wrote on Sun, Dec 09, 2018 at 01:09:28AM +0100:
> On Sat, Dec 08 2018 at 09:56:07 PM, Werner LEMBERG wrote:
>> Ingo Schwarze wrote:
>>> On Solaris 9, installation still fails because of the "for f in ;
>>> do" we discussed earlier, and the test suite still fails as shown a
At 2018-12-09T05:12:25+0100, Ingo Schwarze wrote:
> Here is a better idea, which is also simpler.
> The problem is that the variables PREFIXMAN5 and PREFIXMAN7 are empty.
>
> Carefully inspecting the groff source tree with grep(1), i convinced
> myself that they are *always* empty, no matter the c
Hi Ingo,
> Ouch. My first attempt to fix this with "test -n" failed miserably:
>
> [...]
> if test -n ""; then \
> for f in ; do \
> cp -f $f /home/schwarze/Local9/share/man/man5/g`basename $f`; \
> done; \
> fi
> bash: -c: line 2: syntax error near unexpected token `;'
The
Hi Ingo,
> To confirm this, i just commented out the line
>
> double hypot(double, double);
>
> in /usr/include/math.h
...
> CXX src/libs/libgroff/libgroff_a-hypot.o
> ../src/libs/libgroff/hypot.cpp:
> In function 'double groff_hypot(double, double)':
> ../src/libs/libgroff/hypo
On Sunday, 9 December 2018 00:53:48 GMT Ingo Schwarze wrote:
> Ralph Corderoy suggested using
>
> unpack('V'
>
> instead of
>
> unpack('L<'
>
> and that works for me on OpenBSD, Debian Jessie, Solaris 11, 10, and 9.
Hi Ingo, Ralph,
Suggested change has been committed, mary thanks for your
Hi Ralph,
Ralph Corderoy wrote on Sun, Dec 09, 2018 at 11:09:51AM +:
> Ingo Schwarze wrote:
>> To confirm this, i just commented out the line
>>
>> double hypot(double, double);
>>
>> in /usr/include/math.h
> ...
>> CXX src/libs/libgroff/libgroff_a-hypot.o
>> ../src/libs/libgroff
Hi Deri,
Deri wrote on Sun, Dec 09, 2018 at 12:50:48PM +:
> On Sunday, 9 December 2018 00:53:48 GMT Ingo Schwarze wrote:
>> Ralph Corderoy suggested using
>>
>> unpack('V'
>>
>> instead of
>>
>> unpack('L<'
>>
>> and that works for me on OpenBSD, Debian Jessie, Solaris 11, 10, and 9.
Hi Bertrand, hi Ralph,
Ralph Corderoy wrote on Sun, Dec 09, 2018 at 10:36:25AM +:
> Ingo Schwarze wrote:
>> Ouch. My first attempt to fix this with "test -n" failed miserably:
>>
>> [...]
>> if test -n ""; then \
>> for f in ; do \
>> cp -f $f /home/schwarze/Local9/share/man/ma
Hi Ingo,
> > > To confirm this, i just commented out the line
> > >
> > > double hypot(double, double);
> > >
> > > in /usr/include/math.h
...
> > > The lack of hypot() in libm is *not* detected
>
> > Did you remove hypot() from libm.a too?
>
> No i didn't.
...
> Then, the test that the gnulib h
Hi Ingo,
On Sunday, 9 December 2018 13:14:58 GMT Ingo Schwarze wrote:
> Did you intentionally not credit Ralph with the idea?
No. but my thanks was directed to both of you. :-)
> Whoever commits next can remove the stray blank line that was
> accidentally introduced into the ChangeLog; i don't t
Hi Ingo,
On Sat, Dec 08 2018 at 08:06:11 PM, Ingo Schwarze wrote:
> incidentally, i did an update of my OpenBSD-current base system
> since building the last groff release tarball three days ago.
> The system now uses the LLVM linker by default instead of the GNU
> binutils linker:
[...]
> I do n
Hi Werner,
On Sat, Dec 08 2018 at 09:56:07 PM, Werner LEMBERG wrote:
>> On Solaris 9, installation still fails because of the "for f in ;
>> do" we discussed earlier, and the test suite still fails as shown at
>> the end (no change in that respect), but i see no regressions from
>> your patch.
>
Hi Ingo,
On Sun, Dec 09 2018 at 01:59:11 PM, Ingo Schwarze wrote:
> Then, the test that the gnulib hypot module is supposed to replace
> intends to test whether the function needs to be *declared*. In
> the past, our build system did not provide any replacement code for
> a missing hypot() objec
Hi Bertrand,
Bertrand Garrigues wrote on Mon, Dec 10, 2018 at 12:59:24AM +0100:
> On Sun, Dec 09 2018 at 01:59:11 PM, Ingo Schwarze wrote:
>> Then, the test that the gnulib hypot module is supposed to replace
>> intends to test whether the function needs to be *declared*. In
>> the past, our bu
On Sat, Dec 08, 2018 at 07:17:59PM +0100, Ingo Schwarze wrote:
> Hi Ralph,
>
> Ralph Corderoy wrote on Sat, Dec 08, 2018 at 11:28:40AM +:
> > Ingo:
> >> Ralph:
> >>> Ingo:
> Ralph:
>
[...]
> The printf(1) utility is already used in
>
> * Makefile.in (5 places)
> * bootstrap (8 places
Hi Bjarni,
> > > > . pso sh -c \
> > > > "printf '%s' '.ds *f ' ; \
> > > > ls \\*[fontpath]/dev\*[.T] \
> > > > -| tr '[:cntrl:]' '[ *32]'"
> > > > +| tr 'n' ' '"
> > > > . \" This dummy line is necessary; the preceding line eats it.
...
> cd \\*[fontpa
Ingo Schwarze wrote in <20181209133200.gc7...@athene.usta.de>:
..
|Ralph Corderoy wrote on Sun, Dec 09, 2018 at 10:36:25AM +:
..
|> The time-honoured way to achieve this is using the built-in `set'.
|>
|> $ l='foo bar xyzzy'
|> $ set -- $l; for f; do echo f=$f; done | fmt
|>
Hi Ingo,
On Sun, Dec 09 2018 at 02:32:00 PM, Ingo Schwarze wrote:
> Ralph Corderoy wrote on Sun, Dec 09, 2018 at 10:36:25AM +:
>> The time-honoured way to achieve this is using the built-in `set'.
>>
>> $ l='foo bar xyzzy'
>> $ set -- $l; for f; do echo f=$f; done | fmt
>> f=foo
Hi Ingo,
On Mon, Dec 10 2018 at 01:58:56 AM, Ingo Schwarze wrote:
[...]
> My first impulse was to say "presumably, at some time in the (possibly
> remote) past, systems existed where libm provided a viable implementation
> of hypot(), but failed to declare it. Your propsed direction
> might bre
At 2018-12-03T06:27:35+0100, Werner LEMBERG wrote:
> > Sounds interesting, but what is it exactly? I've skimmed through
> > his home page (https://www.math.utah.edu/~beebe/) but haven't seen
> > any mention of that.
>
> Cf. this message on the TeXLive mailing list.
>
> https://tug.org/pipermai
>> Cf. this message on the TeXLive mailing list.
>>
>> https://tug.org/pipermail/tex-live/2018-November/042697.html
>
> I only mention this because it's an error that has crept into our
> documentation before (and which I've fixed).
>
> "Cf." means "compare" (Latin: "confere"). People seem t
At 2018-12-11T15:20:45+0100, Werner LEMBERG wrote:
> > I only mention this because it's an error that has crept into our
> > documentation before (and which I've fixed).
> >
> > "Cf." means "compare" (Latin: "confere"). People seem to use it as if
> > it were a synonym of "q.v." ("quod vide" -> *
64 matches
Mail list logo
