It took some time to figure out, but it wasn't a configuration issue.
At least, not on my part - it turns out that the j printf/etc length
is used in 40 places in the code. This is a fairly recent introduction
to the c library, and is not supported under Solaris 8 (it is under
Solaris 10). gcc
On Thu, Dec 3, 2009 at 12:07 PM, flow...@hagsc.org wrote:
This is likely an issue for any machine whose libc does not support the
j length.
We use the formatting functionality provided by glib, which promises
to support 'j'. It does this by testing the implementation in the C
library, and
Ah, I'd wondered if glib did that (it looked like it passed through to
libc for all the printf functions when I checked the code). I'm using
2.8.1, and config.h in the source directory has
/* #undef HAVE_GOOD_PRINTF */
which would seem to imply it's using the system printf, as you'd
suggested.
On Thu, Dec 3, 2009 at 1:01 PM, flow...@hagsc.org wrote:
/* #undef HAVE_GOOD_PRINTF */
which would seem to imply it's using the system printf, as you'd
suggested. I suppose I could toggle that and recompile glib to fix the
problem as well.
No, that means it's using the bundled printf.
No, HAVE_INTMAX_T is defined, and caused no issues while building amanda.
Ah, mistake on my part - this is indeed an old library, and was compiled
on an earlier machine running Solaris 7, which I no longer have access to.
It's quite possible the config.h created at that point was different
from what I'm seeing now.
Is there any way to pry configuration information out
On Thu, Dec 3, 2009 at 2:29 PM, flow...@hagsc.org wrote:
Ah, mistake on my part - this is indeed an old library, and was compiled
on an earlier machine running Solaris 7, which I no longer have access to.
It's quite possible the config.h created at that point was different
from what I'm
And, having tested with a recompiled 2.8.1, and with 2.22.3, this was
exactly the problem. Thanks for the help in tracking it down!
Do the backup succeeded? It looks it failed.
flow...@hagsc.org wrote:
I'm running a fresh install of amanda 2.6.1pl1 (I recently upgraded to
p2 and experienced the same problem). When performing full dumps, the
curinfo/machine/disk/info files are getting updated (they have proper
ownership),
I'm running a fresh install of amanda 2.6.1pl1 (I recently upgraded to
p2 and experienced the same problem). When performing full dumps, the
curinfo/machine/disk/info files are getting updated (they have proper
ownership), but the stats: line for level 0 is mostly filled with 0's.
version: 0
11 matches
Mail list logo
