Follow-up Comment #3, bug #30026 (project gnustep): Well .. looked like 'date' returned the correct time, and you have no environment variable set to specify the zone .. so unless you have the zone set in your user defaults or have set the localtime file in the GNUstep zones directory (which seems unlikely) that just leaves two possibilities: 1. your system has an incorrect timezone filename 2. your system has not timezone filename, and is returning the incorrect timezone in tzname.
My guess is that the problem is (1) ... so I've changed the order of precedence so we call the tzset() function and look at tzname (if available) before we resort to looking at the timezone filename. This seems reasonable to me as it's probably relatively easy for someone to link '/etc/localtime' (or whatever is the local timezone file) to a file with the wrong name. I didn't write the original code ... and Im not even sure that looking at the localtime file is supposed to be a reliable way of determining the timezone. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?30026> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/ _______________________________________________ Bug-gnustep mailing list Bug-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnustep