From: Manuel Lauss <manuel.lauss@gmail.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: libc-help@sourceware.org,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Alistair Francis <alistair23@gmail.com>
Subject: Re: 32bit builds broken by gettime64 vDSO patches
Date: Fri, 13 Dec 2019 16:58:00 -0000 [thread overview]
Message-ID: <CAOLZvyGW_6DiDE6vXJ1RPLJG4rGkx6jbq-7eNfhh5vaDUbkxPA@mail.gmail.com> (raw)
In-Reply-To: <20191213150511.2ebeb898@jawa>
Hi Lukasz,
I tried --enable-kernel=3.2.0 (Gentoo default), 5.3.0 and 5.4.0, none
work. Your patch however does fix the build!
Manuel
On Fri, Dec 13, 2019 at 3:05 PM Lukasz Majewski <lukma@denx.de> wrote:
>
> Hi Manuel,
>
> > Hello,
> >
> > 32bit builds of latest git head (tested x86, MIPS o32, ARM, SH4)
> > break on my system; 64 bit (arm64, x86_64) builds are fine.
> > Reverting Alistair Francis' 2 clock_gettime64 patches fixes that.
> >
> > In file included from ../sysdeps/unix/sysv/linux/clock_gettime.c:28:
> > ../sysdeps/unix/sysv/linux/clock_gettime.c: In function
> > ‘__clock_gettime64’: ../sysdeps/unix/sysv/linux/sysdep-vdso.h:40:15:
> > error: ‘__vdso_clock_gettime64’ undeclared (first use in this
> > function); did you mean ‘__vdso_clock_gettime’?
> > 40 | __typeof (__vdso_##name) vdsop = __vdso_##name; \
> > | ^~~~~~~
> > ../sysdeps/unix/sysv/linux/clock_gettime.c:41:11: note: in expansion
> > of macro ‘INLINE_VSYSCALL’
> > 41 | return INLINE_VSYSCALL (clock_gettime64, 2, clock_id, tp);
> > | ^~~~~~~~~~~~~~~
> > ../sysdeps/unix/sysv/linux/sysdep-vdso.h:40:15: note: each undeclared
> > identifier is reported only once for each function it appears in
> > 40 | __typeof (__vdso_##name) vdsop = __vdso_##name; \
> > | ^~~~~~~
> > ../sysdeps/unix/sysv/linux/clock_gettime.c:41:11: note: in expansion
> > of macro ‘INLINE_VSYSCALL’
> > 41 | return INLINE_VSYSCALL (clock_gettime64, 2, clock_id, tp);
> > | ^~~~~~~~~~~~~~~
> > ../sysdeps/unix/sysv/linux/sysdep-vdso.h:42:15: warning: comparison
> > between pointer and integer
> > 42 | if (vdsop != NULL) \
> > | ^~
> > ../sysdeps/unix/sysv/linux/clock_gettime.c:41:11: note: in expansion
> > of macro ‘INLINE_VSYSCALL’
> > 41 | return INLINE_VSYSCALL (clock_gettime64, 2, clock_id, tp);
> > | ^~~~~~~~~~~~~~~
> > In file included from ../sysdeps/unix/sysv/linux/clock_gettime.c:28:
> > ../sysdeps/unix/sysv/linux/sysdep-vdso.h:44:35: error: called object
> > ‘vdsop’ is not a function or function pointer
> > 44 | sc_ret = INTERNAL_VSYSCALL_CALL (vdsop, sc_err, nr, ##args);
> > \ | ^~~~~
> > ../sysdeps/unix/sysv/linux/sysdep-vdso.h:26:6: note: in definition of
> > macro ‘INTERNAL_VSYSCALL_CALL’
> > 26 | funcptr (args)
> > | ^~~~~~~
> > ../sysdeps/unix/sysv/linux/clock_gettime.c:41:11: note: in expansion
> > of macro ‘INLINE_VSYSCALL’
> > 41 | return INLINE_VSYSCALL (clock_gettime64, 2, clock_id, tp);
> > | ^~~~~~~~~~~~~~~
> > In file included from ../sysdeps/unix/sysv/linux/clock_gettime.c:28:
> > ../sysdeps/unix/sysv/linux/sysdep-vdso.h:40:30: note: declared here
> > 40 | __typeof (__vdso_##name) vdsop = __vdso_##name; \
> > | ^~~~~
> > ../sysdeps/unix/sysv/linux/clock_gettime.c:41:11: note: in expansion
> > of macro ‘INLINE_VSYSCALL’
> > 41 | return INLINE_VSYSCALL (clock_gettime64, 2, clock_id, tp);
> > | ^~~~~~~~~~~~~~~
> > make[2]: ***
> > [/tmp-ram/portage/sys-libs/glibc-2.30-r3/work/build-x86-x86_64-pc-linux-gnu-nptl/sysd-rules:213:
> > /tmp-ram/portage/sys-libs/glibc-2.30-r3/work/build-x86-x86_64-pc-linux-gnu-nptl/time/clock_gettime.o]
> > Error 1 make[2]: Leaving directory
> > '/tmp-ram/portage/sys-libs/glibc-2.30-r3/work/glibc-2.30/time'
> >
> > glibc is configured thusly:
> > configure --enable-stack-protector=no
> > --enable-stackguard-randomization --disable-cet --enable-kernel=5.2.0
> > --without-selinux --without-cvs --disable-werror --enable-bind-now
> > --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --disable-profile
> > --without-gd --with-headers=/usr/include --prefix=/usr
> > --sysconfdir=/etc --localstatedir=/var --libdir=$(prefix)/lib
> > --mandir=$(prefix)/share/man --infodir=$(prefix)/share/info
> > --libexecdir=$(libdir)/misc/glibc
> > --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion=Gentoo
> > 2.30-r3 p4 --enable-crypt --disable-systemtap --disable-nscd
> > --disable-timezone-tools
> >
>
> Do you use kernel headers > 5.1 but < 5.4 (32 bit) ?
>
> For 32 bit devices there is a fix available:
> https://github.com/lmajewski/y2038_glibc/commit/93a26fc4b3c4c3f57dec539d1f3244f7ae417be3
>
>
> >
> > Thanks!
> > Manuel
>
>
>
>
> Best regards,
>
> Lukasz Majewski
>
> --
>
> DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
prev parent reply other threads:[~2019-12-13 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 12:17 Manuel Lauss
2019-12-10 21:56 ` Adhemerval Zanella
2019-12-13 14:05 ` Lukasz Majewski
2019-12-13 16:58 ` Manuel Lauss [this message]
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=CAOLZvyGW_6DiDE6vXJ1RPLJG4rGkx6jbq-7eNfhh5vaDUbkxPA@mail.gmail.com \
--to=manuel.lauss@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--cc=alistair23@gmail.com \
--cc=libc-help@sourceware.org \
--cc=lukma@denx.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).