Bug 14024 - No localtime_r and gcc instead of g++ (again)
Summary: No localtime_r and gcc instead of g++ (again)
Status: RESOLVED FIXED
Alias: None
Product: poppler
Classification: Unclassified
Component: glib frontend (show other bugs)
Version: unspecified
Hardware: Other Cygwin
: medium minor
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 12493
Blocks:
  Show dependency treegraph
 
Reported: 2008-01-11 08:30 UTC by Émilien Tlapale
Modified: 2008-01-11 11:27 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Émilien Tlapale 2008-01-11 08:30:01 UTC
Hi!
There is still the same problem within the same function, but in another file: glib/demo/info.c
So the same solution from Albert Astals Cid should do it (renaming to info.cc and copy/pasting the function from glib/test-poppler-glib.cc).
--
Émilien Tlapale

+++ This bug was initially created as a clone of Bug #12493 +++

Hi!
I am still using poppler in cross-compiling for windows so there are two minor bugs in 0.6. Or maybe it is just a misconfiguration on my laptop. Anyway.

There seem to be no localtime_r on my i686-mingw32 toolchain. I suppose a check might be needed and a HAVE_LOCALTIME_R added. In glib/test-poppler-glib.c the function is used into poppler_format_date(GTime), so maybe just some #if/#else would be nice. I replaced the `struct tm t;`  with `struct tm *t;` and `!localtime (&time, &t)` with `!(t = localtime (&time))` but i have absolutely no idea of the meaning.

Yet another problem while compiling is a `/bin/sh ../libtool --tag=CC --mode=link i686-mingw32-gcc ... -o test-poppler-glib.exe  test-poppler-glib.o ...` which gives many unresolved symbols. I replaced it with a `... --tag=CC --mode=link i686-mingw32-g++ ...` to compile.

Seems nothing at all and thanks a lot for this useful library :)
Comment 1 Albert Astals Cid 2008-01-11 11:27:06 UTC
should be fixed now, thanks for reporting


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.