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 After the change, m4 makes and passes the self-check. Thus, we can drop that address going forward. :-) Automake and autoconf both build, but neither passes all the self-tests. ntp won't even build because of something in the configuration files. It appears to be doubly defining some constants. As near as I can tell from trying to look at the autoconfig stuff, it thinks that some of the constants in <sys/int_types.h>, which are included as part of <inttypes.h> are not defined. So, it redefines them in a compat.h file, and the compiler gets very, very unhappy about that. Email to the ntp bugs list was rejected by the moderator who said I should post to the help list. I did, but no one has responded. So, in my quest to get a new ntp up, I find I have to install a bunch of packages I don't understand, and that I can't get to pass the checks! At least you have responded to some of my concerns, for that, thank you. Under separate cover, and not cc-d to the m4 list, I will send the autoconf error log. If you want to see the automake errors, or ntp errors, let me know. I have a bunch of em. :-) (What is somewhat depressing about this is that 15-25 years ago, I was writing stuff like this and posting it....and answering help questions. Now that I have become more of a an administrator, I'm finding it frustrating to realize I can't even remember some of the options to the command I need to track this stuff down!) --spaf On Feb 28, 2010, at 12:27 AM, Ralf Wildenhues wrote: > * 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 environment > > Both of these are useful when setting up an interactive shell, but for a > noninteractive shell, they make little sense. Shell setups that produce > output tend to bother other programs like ssh as well. > > One easy workaround is to wrap these commands in > > case $- in > *i*) > setup for interactive shell ... > ;; > esac > > Cheers, > Ralf
smime.p7s
Description: S/MIME cryptographic signature
