Issue 491893002: Handle bionic in safe_strerror_posix as well as glibc.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 491893002: Handle bionic in safe_strerror_posix as well as glibc. (Closed)

Created:
6 years, 4 months ago by Torne

Modified:
6 years, 4 months ago

Reviewers:
brettw

CC:
chromium-reviews, erikwright+watch_chromium.org, enh

Base URL:
svn://svn.chromium.org/chrome/trunk/src

Project:
chromium

Visibility:
Public.

More Reviews

Description

Handle bionic in safe_strerror_posix as well as glibc. Android's bionic C library is intending to adopt the same semantics as glibc for strerror_r: define the version that returns char* if the source is compiled with _GNU_SOURCE instead of the POSIX version which returns int. Add __BIONIC__ to the condition for USE_HISTORICAL_STRERRO_R so that Chromium will still work. BUG= Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=291050