Fix disabling of year 2038 support on 32-bit hosts by default
Commite5f2f7d901
("Disable year 2038 support on 32-bit hosts by default") fixed a mismatch between 64-bit time_t in GDB and system headers and 32-bit time_t in BFD. However, since commit862776f26a
("Finalized intl-update patches") gnulib's year 2038 support has been accidentally re-enabled — causing problems for 32-bit hosts again. The commit split baseargs into {h,b}baseargs, but this hasn't been done for the code that handles --disable-year2038. This patch restores the intended behaviour. With this change, the number of unexpected core files goes from 18 to 4. Tested on armv8l-linux-gnueabihf. Approved-By: Luis Machado <luis.machado@arm.com>
This commit is contained in:
parent
a8b1650962
commit
9c0aa4c531
2 changed files with 4 additions and 2 deletions
3
configure
vendored
3
configure
vendored
|
@ -10313,7 +10313,8 @@ hbaseargs="$hbaseargs --disable-option-checking"
|
|||
tbaseargs="$tbaseargs --disable-option-checking"
|
||||
|
||||
if test "$enable_year2038" = no; then
|
||||
baseargs="$baseargs --disable-year2038"
|
||||
bbaseargs="$bbaseargs --disable-year2038"
|
||||
hbaseargs="$hbaseargs --disable-year2038"
|
||||
tbaseargs="$tbaseargs --disable-year2038"
|
||||
fi
|
||||
|
||||
|
|
|
@ -3432,7 +3432,8 @@ hbaseargs="$hbaseargs --disable-option-checking"
|
|||
tbaseargs="$tbaseargs --disable-option-checking"
|
||||
|
||||
if test "$enable_year2038" = no; then
|
||||
baseargs="$baseargs --disable-year2038"
|
||||
bbaseargs="$bbaseargs --disable-year2038"
|
||||
hbaseargs="$hbaseargs --disable-year2038"
|
||||
tbaseargs="$tbaseargs --disable-year2038"
|
||||
fi
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue