timezone: long vs char*

[Joseph S. Atkinson]

Hello. I was working on bringing audio/liboggz up to date in ports, but hit a 
snag. liboggz expects timezone information to be long, which is (I am told) in 
accordance with SUSv3. FreeBSD is appears to be returning char*.

I asked about this in #bsdports and was told that it appears that FreeBSD is 
wrong in this case and should be fixed. I saw no mention of this as a known 
issue on the standards webpage.