[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #64155] specifying -fZD on command line generates warnings
From: |
G. Branden Robinson |
Subject: |
[bug #64155] specifying -fZD on command line generates warnings |
Date: |
Mon, 5 Feb 2024 20:30:25 -0500 (EST) |
Update of bug#64155 (group groff):
Assigned to: gbranden => deri
_______________________________________________________
Follow-up Comment #20:
Hi Deri,
[comment #19 comment #19:]
> [derij@pip build (master)]$ ll ~/groff-git/groff/build/font/devpdf/U-T*
> -rw-r--r-- 1 derij derij 26563 Feb 5 23:40
/home/derij/groff-git/groff/build/font/devpdf/U-TB
> -rw-r--r-- 1 derij derij 30421 Feb 5 23:40
/home/derij/groff-git/groff/build/font/devpdf/U-TBI
> -rw-r--r-- 1 derij derij 30662 Feb 5 23:40
/home/derij/groff-git/groff/build/font/devpdf/U-TI
> -rw-r--r-- 1 derij derij 26596 Feb 5 23:40
/home/derij/groff-git/groff/build/font/devpdf/U-TR
> [derij@pip build (master)]$ ll /usr/share/groff/1.23.0/font/devpdf/U-T*
> -rw-r--r-- 1 root root 26563 Feb 5 23:44
/usr/share/groff/1.23.0/font/devpdf/U-TB
> -rw-r--r-- 1 root root 30421 Feb 5 23:44
/usr/share/groff/1.23.0/font/devpdf/U-TBI
> -rw-r--r-- 1 root root 30662 Feb 5 23:44
/usr/share/groff/1.23.0/font/devpdf/U-TI
> -rw-r--r-- 1 root root 17000 Feb 5 23:44
/usr/share/groff/1.23.0/font/devpdf/U-TR
Before we go down a rabbit hole of instrumentation and/or GDB backtracing, I
noticed something there.
These file sizes are the same except for U-TR. What's going on there? Is the
U-TR in _/usr/share/groff/1.23.0/font/devpdf/_ a valid font file? If so, how
does it differ from the one in
_/home/derij/groff-git/groff/build/font/devpdf/_?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64155>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- [bug #64155] specifying -fZD on command line generates warnings,
G. Branden Robinson <=
Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- [bug #64155] specifying -fZD on command line generates warnings, Deri James, 2024/02/06
Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- [bug #64155] specifying -fZD on command line generates warnings, G. Branden Robinson, 2024/02/06