* Gene Spafford wrote on Mon, Mar 01, 2010 at 03:45:11AM CET:
Actually, I had something like that in place, but found an old (very
old) debugging statement that was putting out a single space. Once
fixed, those problems went away.
Good.
I have built or tried to build the following 4
ntp won't even build because of something in the configuration files.
The thing that I don't understand is: why do you even need any of
Autoconf or Automake installed for building an ntp release tarball?
It should contain all autotool-generated files, leaving you only to
run ./configure
Actually, I had something like that in place, but found an old (very old)
debugging statement that was putting out a single space. Once fixed, those
problems went away.
I have built or tried to build the following 4 packages on my system:
m4-1.4.14
automake-1.11
autoconf-2.65
ntp-4.2.6p1-RC5
* Gene Spafford wrote on Sat, Feb 27, 2010 at 03:37:42AM CET:
I use ksh
As part of the .profile, it runs the terminal reset sequence each login
I don't see this as bad behavior
The ,kshrc file sets the prompt and does no other output.
I don't see either of these as setting up a bad
I use ksh
As part of the .profile, it runs the terminal reset sequence each login
I don't see this as bad behavior
The ,kshrc file sets the prompt and does no other output.
I don't see either of these as setting up a bad environment
I don't see why either should break the test scripts.
On
Hello Gene,
let's keep the mailing list in CC:, thanks.
* Gene Spafford wrote on Thu, Feb 25, 2010 at 10:15:07PM CET:
On Feb 25, 2010, at 3:40 PM, Ralf Wildenhues wrote:
* Gene Spafford wrote on Thu, Feb 25, 2010 at 03:56:24PM CET:
[...]
229. torture.at:1549: testing ...
Thanks for the reply, Ralf.
I am enclosing the output of the make check on the m4 build so you can see
the failures.
The build of ntp also failed because of some confusion about types being
defined or not. I have no idea what is going on, but it sure makes it
difficult to build and install
