At 2022-07-08T14:27:31+0100, Deri wrote:
> On Friday, 8 July 2022 05:54:11 BST G. Branden Robinson wrote:
> > There is another issue I've been hitting. My builds still work fine
> > in my general-purpose development environment, but fail in my Debian
> > bullseye chroot with no optional
[dropped CCs to Robert and bug-groff]
At 2022-07-08T14:18:38-0500, G. Branden Robinson wrote:
> I now see diagnostics from afmtodit that I've never observed before,
> though I think other people have reported them. I suspect they are
> freshly exposed bugs in our "font/devps/generate/textmap"
Hi Deri,
At 2022-07-08T14:27:31+0100, Deri wrote:
> On Friday, 8 July 2022 05:54:11 BST G. Branden Robinson wrote:
> > There is another issue I've been hitting. My builds still work fine in
> > my general-purpose development environment, but fail in my Debian
> > bullseye chroot with no optional
Hi Deri,
At 2022-07-08T14:27:31+0100, Deri wrote:
> On Friday, 8 July 2022 05:54:11 BST G. Branden Robinson wrote:
> > There is another issue I've been hitting. My builds still work fine in
> > my general-purpose development environment, but fail in my Debian
> > bullseye chroot with no optional
On Friday, 8 July 2022 05:54:11 BST G. Branden Robinson wrote:
> There is another issue I've been hitting. My builds still work fine in
> my general-purpose development environment, but fail in my Debian
> bullseye chroot with no optional dependencies _except_ the URW fonts.
Hi Branden,
Yes,
On Friday, 8 July 2022 05:54:11 BST G. Branden Robinson wrote:
> There is another issue I've been hitting. My builds still work fine in
> my general-purpose development environment, but fail in my Debian
> bullseye chroot with no optional dependencies _except_ the URW fonts.
Hi Branden,
Yes,
[content warning: this message is a bug hunt]
Hi Deri,
At 2022-07-07T16:30:43+0100, Deri wrote:
> On Thursday, 7 July 2022 05:48:33 BST G. Branden Robinson wrote:
> > Deri, can you throw any light on this stuff?
>
> One possibility is that somehow it is running the currently installed
> groff,
[content warning: this message is a bug hunt]
Hi Deri,
At 2022-07-07T16:30:43+0100, Deri wrote:
> On Thursday, 7 July 2022 05:48:33 BST G. Branden Robinson wrote:
> > Deri, can you throw any light on this stuff?
>
> One possibility is that somehow it is running the currently installed
> groff,
I restarted my computer, and now groff is building dvi's and pdf's without
complaining that it can't find DESC files (sorry, I didn't note exactly
which error message came up before).
Robert.
On Thu, Jul 7, 2022 at 1:13 PM Deri wrote:
> On Thursday, 7 July 2022 17:03:50 BST Robert Goulding
I restarted my computer, and now groff is building dvi's and pdf's without
complaining that it can't find DESC files (sorry, I didn't note exactly
which error message came up before).
Robert.
On Thu, Jul 7, 2022 at 1:13 PM Deri wrote:
> On Thursday, 7 July 2022 17:03:50 BST Robert Goulding
On Thursday, 7 July 2022 17:03:50 BST Robert Goulding wrote:
> Sorry to keep up the stream of emails. My newly installed groff 1.23 cannot
> find DESC files for pdf and dvi (but handles ps OK) -- even though those
> files are in fact there in the right place. It seems to be looking for font
>
On Thursday, 7 July 2022 17:03:50 BST Robert Goulding wrote:
> Sorry to keep up the stream of emails. My newly installed groff 1.23 cannot
> find DESC files for pdf and dvi (but handles ps OK) -- even though those
> files are in fact there in the right place. It seems to be looking for font
>
On Thursday, 7 July 2022 16:47:08 BST Robert Goulding wrote:
> (What I don't understand is how I've been compiling pdfs
> from troff documents with no difficulties using my installed groff, even
> though the download file was pointing at non-existent fonts?)
>
If your troff documents are only
Sorry to keep up the stream of emails. My newly installed groff 1.23 cannot
find DESC files for pdf and dvi (but handles ps OK) -- even though those
files are in fact there in the right place. It seems to be looking for font
files in the wrong place (perhaps in my stock groff installation?);
Sorry to keep up the stream of emails. My newly installed groff 1.23 cannot
find DESC files for pdf and dvi (but handles ps OK) -- even though those
files are in fact there in the right place. It seems to be looking for font
files in the wrong place (perhaps in my stock groff installation?);
I completely uninstalled my 1.23 installation, and then the whole make/make
install went through without error.
On Thu, Jul 7, 2022 at 11:47 AM Robert Goulding
wrote:
> The download file in the build font/devpdf directory correctly points to
> the 9.53.3 installation of the Ghostscript fonts.
I completely uninstalled my 1.23 installation, and then the whole make/make
install went through without error.
On Thu, Jul 7, 2022 at 11:47 AM Robert Goulding
wrote:
> The download file in the build font/devpdf directory correctly points to
> the 9.53.3 installation of the Ghostscript fonts.
The download file in the build font/devpdf directory correctly points to
the 9.53.3 installation of the Ghostscript fonts. The stock groff that I
have from Debian is 1.22.4, which does not have a devpdf directory. I have
1.23.0 installed myself, and the download file in
On Thursday, 7 July 2022 05:48:33 BST G. Branden Robinson wrote:
> Hi Robert,
>
> At 2022-07-06T17:34:49-0400, Robert Goulding wrote:
> > I checked out the latest source and tried building it on my Chromebook
> > (i.e., Debian 11 (bullseye)). The compile stopped when it tried to
> > build the pdf
On Thursday, 7 July 2022 05:48:33 BST G. Branden Robinson wrote:
> Hi Robert,
>
> At 2022-07-06T17:34:49-0400, Robert Goulding wrote:
> > I checked out the latest source and tried building it on my Chromebook
> > (i.e., Debian 11 (bullseye)). The compile stopped when it tried to
> > build the pdf
And I checked out a brand new clone of the repository, and build failed
with the same error about Ghostscript 9.27.
On Thu, Jul 7, 2022 at 7:20 AM Robert Goulding
wrote:
> I can't understand it myself, but I did "make distclean" and
> re-configured, and got precisely the same error about 9.27.
And I checked out a brand new clone of the repository, and build failed
with the same error about Ghostscript 9.27.
On Thu, Jul 7, 2022 at 7:20 AM Robert Goulding
wrote:
> I can't understand it myself, but I did "make distclean" and
> re-configured, and got precisely the same error about 9.27.
I can't understand it myself, but I did "make distclean" and re-configured,
and got precisely the same error about 9.27. Twice Even though my
configure output matches yours, and identified my Ghostscript as 9.53, and
said that URW fonts were found. I'll try deleting and redownloading and
I can't understand it myself, but I did "make distclean" and re-configured,
and got precisely the same error about 9.27. Twice Even though my
configure output matches yours, and identified my Ghostscript as 9.53, and
said that URW fonts were found. I'll try deleting and redownloading and
[looping in groff@gnu]
Hi Robert,
At 2022-07-06T17:34:49-0400, Robert Goulding wrote:
> I checked out the latest source and tried building it on my Chromebook
> (i.e., Debian 11 (bullseye)). The compile stopped when it tried to
> build the pdf of all the man pages:
>
> make[1]: Entering
[looping in groff@gnu]
Hi Robert,
At 2022-07-06T17:34:49-0400, Robert Goulding wrote:
> I checked out the latest source and tried building it on my Chromebook
> (i.e., Debian 11 (bullseye)). The compile stopped when it tried to
> build the pdf of all the man pages:
>
> make[1]: Entering
I checked out the latest source and tried building it on my Chromebook
(i.e., Debian 11 (bullseye)). The compile stopped when it tried to build
the pdf of all the man pages:
make[1]: Entering directory '/home/rdgoulding/groff-git'
GROFFdoc/groff-man-pages.pdf
27 matches
Mail list logo
