no, it only means that the C library is not built with this symbols, because
they are guarded by macros like:

#if HAVE_DAYLIGHT
int  daylight;
#endif

and HAVE_DAYLIGHT is not defined when building the C library. Solving the
issue requires changing the build
script for the C library.

However, you can get the same information with a call to gmtime() or
localtime()
since the struct tm structure has fields named "tm_isdst" and "tm_gmtoff"
that serve similar purposes

On Thu, Mar 26, 2009 at 5:51 AM, Yogi <[email protected]> wrote:

>
> Thanks for reply..
> You mention that  'standard build does not define the preprocessor
> symbols so as to include those declarations'.
> Can i include that preprocessor symbol in my library?
> Can i know what is that preprocessor symbol?
>
> Thanks,
> Yogi
>
> Huaka‘i Po wrote:
> > daylight and timezone aren't missing in time.h.  The entries are
> > extern declarations meant to indicate that those variables are defined
> > somewhere else.  That somewhere else is normally localtime.c, except
> > Android has some guards around the definitions.  It appears the
> > standard build does not define the preprocessor symbols so as to
> > include those declarations.  Hence, there are no definitions to
> > resolve against, which is why you're getting the link errors.
> >
> > > When i have checked the daylight & timezone variable in time.h
> > > (android bionic folder) definition of both the variable is different.
> >
> > Different from what?  daylight is declared/defined as int in the
> > relevant places.  It's slightly disturbing that timezone is declared
> > as long int in time.h and time_t in localtime.c,  but time_t is just
> > long int (at least on ARM and x86).
> >
> > What's puzzling is the only references to daylight and timezone come
> > from code also guarded by the same preprocessor symbol.  Do you know
> > what in your code is referencing those variables?
> >
>

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to