From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/cvs: fix mktime related compile failure
Date: Sat, 30 May 2020 00:21:10 +0200 [thread overview]
Message-ID: <20200530002110.4e6fb1ee@gmx.net> (raw)
In-Reply-To: <20200529210705.0f1f9efe@windsurf.home>
Hello Thomas,
On Fri, 29 May 2020 21:07:05 +0200, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> On Fri, 29 May 2020 20:43:43 +0200
> Peter Seiderer <ps.report@gmx.net> wrote:
>
> > > With the time_t conversion to 64bit, time_t *is* larger than an
> > > unsigned int.
> > >
> > > So aren't you papering over the problem, and in fact potentially
> > > causing some issues in CVS, which seems to assume the time_t fits in
> > > 32-bit ?
> >
> > ....it is only the internal assumption of the local mktime implementation,
> > as far as I see all cvs callers of mktime use time_t to store the return
> > value....
>
> Hm, ok. But does it make sense to use the AlpineLinux patch instead ?
Did a short test (as the alpine linux patch patches configure directly):
$ wget https://git.alpinelinux.org/aports/plain/main/cvs/mktime-configure.patch
$ make cvs-patch
$ cd build/cvs-1.12.13/
$ patch -p 1 < mktime-configure.patch
$ cd ../..
$ make cvs
...still fails (as expected as the mktime check is a runtime check (?) which
is unfixable for cross-compile)...
Regards,
Peter
>
> Thomas
next prev parent reply other threads:[~2020-05-29 22:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 21:59 [Buildroot] [PATCH v2] package/cvs: fix mktime related compile failure Peter Seiderer
2020-05-29 6:09 ` Thomas Petazzoni
2020-05-29 18:43 ` Peter Seiderer
2020-05-29 19:07 ` Thomas Petazzoni
2020-05-29 22:21 ` Peter Seiderer [this message]
2020-08-13 21:36 ` Thomas Petazzoni
2020-08-28 16:31 ` Peter Korsgaard
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=20200530002110.4e6fb1ee@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.