team will be writing test cases for ctype(3), to make sure it
handles these things properly.
Oh, many years' ago I filed a bug report with gcc to get them to emit a
warning when somebody was using a signed char as an array offset. It
took a little back-and-forth to make it happen, but the warning w
Bruce,
I've got guile 2.0.9 on the ntp.org machines that used to cause problems
with that upgrade.
OK, on 1 of 2 Solaris machines. I can beat on the second machine if you
want to upgrade minimum guile requirement to 2.0.
And I just found an old debian machine that's running 1.8.8, but I'm
};
---
FAIL: str2m.test
1 of 42 tests failed
Please report to autogen-users@lists.sourceforge.net
--
Harlan Stenn st...@ntp.org
http://networktimefoundation.org - be a member
There's also a problem if gperf isn't installed.
Bruce, I have a bunch of upgraded documentation script/template files
too - what's a good way to get those to you?
H
--
Master Visual Studio, SharePoint, SQL, ASP.NET, C#
) $* $@ $ $% $? ; \
shell vars: $${MAKE} $$# $$F $${?} $${*}
FAIL: make.test
...
--
Harlan Stenn st...@ntp.org
http://networktimefoundation.org - be a member!
--
Live Security Virtual Conference
Exclusive live event will cover all
Bruce wrote:
I've found the problem: It exists in an atrophied section of code
for Guile 1.6 only code. I've fixed it in my source now.
Since I don't have access to any platform with 6 year old Guile,
I have to depend on others to alert me during the pre release phase.
Guile 1.8 was
Bruce wrote:
It seems I had considered a -I pointing at one tree and -L to another:
Use --with-libguile-cflags=xxx --with-libguile-ldflags=yyy
But why would you do that? --with-libguile is used to provide both
with one option.
This is clearly more flexible (and clearly a PITA), and I had
supported in existing
.tpl files.
I'm suggesting this because I do not want to have to maintain multiple
instances of a given stanza (for different output formats) unless I
absolutely have to.
--
Harlan Stenn st...@ntp.org
http://ntpforum.isc.org - be a member
Geof wrote:
If I run 'autogen' (no parameters) from anywhere on my system I get:
autogen: symbol lookup error: autogen: undefined symbol: snv_vasprintf
This is after removing and reinstalling autogen with Debian apt-get.
Anyone know how to track this one down?
It comes from autogen's
, uint32_t,
intptr_t, uintptr_t, uint_t])
+ AC_CHECK_TYPES([wchar_t, mode_t, pid_t, uid_t, gid_t])
# =
# sizes
--
Harlan Stenn [EMAIL PROTECTED]
http://ntpforum.isc.org - be a member!
-
Check out
10 matches
Mail list logo