On Friday, 7 October 2022 10:35:55 BST G. Branden Robinson wrote:
> One thing I don't understand is why "(gs)" (which, IIRC, means,
> "whatever Ghostscript's font search path reported in 'gs -h' is) comes
> right after the URW fonts directory when searching for Adobe or generic
> fonts but all the
Hi Deri,
At 2022-10-07T13:23:06+0100, Deri wrote:
> On Friday, 7 October 2022 10:35:55 BST G. Branden Robinson wrote:
> > One thing I don't understand is why "(gs)" (which, IIRC, means,
> > "whatever Ghostscript's font search path reported in 'gs -h' is)
> > comes right after the URW fonts directo
At 2022-10-07T03:25:05-0500, G. Branden Robinson wrote:
> I don't have enough information to solve this, but I do have two ideas
> that I think may help flush it out.
>
> 1. Add the purportedly successful URW font location path to the
> configuration report.
> 2. Have gropdf report more cont
At 2022-10-07T07:14:35+, Werner LEMBERG wrote:
>
> >> This inconsistency of gs on my GNU/Linux is of no importance, but
> >> it clearly shows that there is a bug while compiling groff: It uses
> >> `gropdf` from my system instead of using the just compiled
> >> `gropdf`!
> >
> > Are you sure?
>> This inconsistency of gs on my GNU/Linux is of no importance, but
>> it clearly shows that there is a bug while compiling groff: It uses
>> `gropdf` from my system instead of using the just compiled
>> `gropdf`!
>
> Are you sure? I cannot verify this hypothesis; whether I build
> inside the
Hi Werner,
At 2022-07-26T20:21:48+, Werner LEMBERG wrote:
> I got the following error messages:
[...]
> gropdf:contrib/mom/examples/typesetting.mom: fatal error:
> failed to open '/usr/share/ghostscript/9.52/Resource/Font/C059-Roman'
> gropdf:src/utils/addftinfo/addftinfo.1: fatal error:
>
Hi Branden,
> Werner wrote:
> > strace -f make &> strace.log
>
> There are going to be a _lot_ of system calls.
Since only ones which use a path are of interest, restrict the trace to
just those.
strace -fe %file make
--
Cheers, Ralph.
>> Perhaps it makes sense to execute
>>
>> ```
>> strace -f make &> strace.log
>> ```
>>
>> and check the resulting logfile for all file accesses outside of the
>> source and build directory, and whether they are expected.
>
> That's a good idea, if somewhat monstrous in its implications.
> Ther
At 2022-07-26T23:18:26+, Werner LEMBERG wrote:
> Perhaps it makes sense to execute
>
> ```
> strace -f make &> strace.log
> ```
>
> and check the resulting logfile for all file accesses outside of the
> source and build directory, and whether they are expected.
That's a good idea, if somewha
> I think the correct fix for this is to update the Automake files to
> set $GROFF_BIN_PATH to the build directory before running groff to
> generate our own artifacts. There are only a few directories that
> require this, all of which I think Ingo and/or I touched recently.
>
> Does that sound
[looping in groff@gnu]
Hi Werner,
At 2022-07-26T20:21:48+, Werner LEMBERG wrote:
> While building current git from groff (2f4432718c) with
>
> ```
> ./bootstrap --gnulib-srcdir=~/git/gnulib
> ./configure
> make -j12
> ```
>
> I got the following error messages:
>
> ```
> gropdf:contrib/mom
11 matches
Mail list logo
