From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: <nickc@redhat.com>, <binutils@sourceware.org>
Cc: <gdb@sourceware.org>
Subject: [Build failure] tm struct tm_gmtoff field build error
Date: Mon, 19 Jan 2009 12:40:00 -0000 [thread overview]
Message-ID: <004301c97a33$0fa174d0$2ee45e70$@u-strasbg.fr> (raw)
Trying to compile a "--enable-targets=all" GDB
on current cvs HEAD on cygwin,
I found a new error in src/bfd:
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../purecvs/bfd -I. -I.
-I../../p
urecvs/bfd -I../../purecvs/bfd/../include -W -Wall -Wstrict-prototypes
-Wmissing
-prototypes -Werror -g -O2 -c ../../purecvs/bfd/vmsutil.c -o vmsutil.o
../../purecvs/bfd/vmsutil.c: In function `vms_file_stats_name':
../../purecvs/bfd/vmsutil.c:249: error: structure has no member named
`tm_gmtoff
'
make[3]: *** [vmsutil.lo] Error 1
245-
246- if (cdt)
247- {
248- ts = localtime (&buff.st_mtime);
249: gmtoff = ts->tm_gmtoff;
250- *cdt = (long long) (((buff.st_mtim.tv_sec + gmtoff) *
VMS_GRANULARITY_FACTOR)
251- + (buff.st_mtim.tv_nsec / 100))
252- + VMS_EPOCH_OFFSET;
253- }
The failure is related to a commit by Nick Clifton dated January 15. 2009
adding vmsutils.c file.
tm_gmtoff seems to be an optional field according to:
http://www.delorie.com/gnu/docs/glibc/libc_435.html
and some configure script do check for its presence
before using it, for instance
src/config/tcl.m4
AC_CACHE_CHECK([tm_gmtoff in struct tm], tcl_cv_member_tm_gmtoff, [
AC_TRY_COMPILE([#include <time.h>], [struct tm tm; tm.tm_gmtoff;],
tcl_cv_member_tm_gmtoff=yes, tcl_cv_member_tm_gmtoff=no)])
if test $tcl_cv_member_tm_gmtoff = yes ; then
AC_DEFINE(HAVE_TM_GMTOFF)
fi
Could this test be added and vmsutils.c
be updated accordingly?
Thanks in advance,
Pierre Muller
Pascal language support maintainer for GDB
next reply other threads:[~2009-01-19 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 12:40 Pierre Muller [this message]
2009-02-17 21:48 ` Cary Coutant
2009-02-20 9:44 ` Nick Clifton
2009-02-20 19:05 ` Cary Coutant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='004301c97a33$0fa174d0$2ee45e70$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=nickc@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox