fla LINT breakage.
Alfred Perlstein <bright <at> mu.org>
2002-03-19 20:19:01 GMT
Fixes format warnings. Since there was so much... bitching about my
last commit to something contrib/* I'm posting the fix here.
Index: fla.c
===================================================================
RCS file: /home/ncvs/src/sys/contrib/dev/fla/fla.c,v
retrieving revision 1.29
diff -u -r1.29 fla.c
--- fla.c 12 Sep 2001 08:36:59 -0000 1.29
+++ fla.c 19 Mar 2002 20:22:51 -0000
<at> <at> -181,8 +181,9 <at> <at>
enum doc2k_work what;
if (fla_debug > 1)
- printf("flastrategy(%p) %s %x, %d, %ld, %p)\n",
- bp, devtoname(bp->bio_dev), bp->bio_flags, bp->bio_blkno,
+ printf("flastrategy(%p) %s %x, %lld, %ld, %p)\n",
+ bp, devtoname(bp->bio_dev), bp->bio_flags,
+ (long long)bp->bio_blkno,
bp->bio_bcount / DEV_BSIZE, bp->bio_data);
sc = bp->bio_dev->si_drv1;
<at> <at> -225,8 +226,9 <at> <at>
ENTER();
if (fla_debug > 1 || error) {
- printf("fla%d: %d = rwe(%p, %d, %d, %d, %ld, %p)\n",
- unit, error, bp, unit, what, bp->bio_pblkno,
+ printf("fla%d: %d = rwe(%p, %d, %d, %lld, %ld, %p)\n",
+ unit, error, bp, unit, what,
(Continue reading)
However, the symbol in question does not appear to exist in the version of libc.so.4 in -CURRENT's /usr/lib/compat -- and that can cause programs which had been compiled under -STABLE and which might well otherwise work Just Fine under -CURRENT to fail, thus: freebeast(5.0-C)[8] screen /usr/libexec/ld-elf.so.1: screen: Undefined symbol "nl_langinfo" freebeast(5.0-C)[9] In this particular case, I've been working around the nuisance by merely recompiling a "-CURRENT-private" version of screen (on each of my build machine & laptop). I'm rather less eager to do this for, say, mozilla (for example).... What is the procedure for getting /usr/lib/compat/libc.so.4 updated to include nl_langinfo (and, perhaps, other symbols that might be in -STABLE's /usr/lib/libc.so.4)? [Were this strictly a -STABLE issue, I'd file a PR. But for -CURRENT, things seem to be sufficiently fluid that the additional overhead of dealing with a PR appears (to me) to be just that -- additional overhead. And it's not a problem that manifests itself as a "problem with/running -STABLE" -- it bites someone running -CURRENT, who is supposed to have some minimal level of clue....]
poke me. 
RSS Feed