| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
These are now called by `uv_library_shutdown` in `src/uv-common.c` but
on UNIX we do not compile those features during CMake bootstrap.
|
|
|
|
|
| |
* upstream-libuv:
libuv 2020-04-29 (e7ebae26)
|
|
|
|
|
|
|
| |
libuv upstream commit `2475296c` (build: make code compilable for iOS on
Xcode, 2020-01-18, v1.35.0~47) added a `defined(TARGET_OS_IPHONE)`
preprocessor condition, but `TARGET_OS_IPHONE` is always defined on
Apple to either 0 or 1.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
libuv upstream commit `4a972bf0` (aix: Fix broken cmpxchgi() XL C++
specialization., 2019-09-06, v1.32.0~5) broke compilation with this
compiler. According to
https://www.ibm.com/support/knowledgecenter/SSGH3R_16.1.0/com.ibm.xlcpp161.aix.doc/migrate/migrate_to_xlclang.html
XLClang 16.1 for AIX does not support `__sync_val_compare_and_swap`.
The documentation suggests using C++11 atomic operations instead, but
this is C code. For now fall back to the non-atomic equivalent used
before so we can at least compile. Add a FIXME comment for this.
|
|
|
|
|
| |
* upstream-libuv:
libuv 2020-04-06 (d21f5aea)
|
|
|
|
|
| |
Port enough of libuv to HP-UX 11.31 ia64 with GCC 4.9.3 to work for
CMake.
|
|
|
|
|
|
| |
The `F_BARRIERFSYNC` constant was not added until the macOS 10.11 SDK.
Hard-code its value instead. This approach is backported from upstream
libuv PR 2334.
|
| |
|
|
|
|
|
| |
* upstream-libuv:
libuv 2019-06-10 (ee24ce90)
|
| |
|
| |
|
|
|
|
|
| |
* upstream-libuv:
libuv 2019-01-15 (f84c5e69)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some platforms (e.g. GNU/Hurd) do not define PATH_MAX. Add a few other
variants and a fallback constant. Also use alternatives where possible:
* For readlink(), use lstat() to read the length of the link first.
If it is not a symlink, report EINVAL before trying to allocate.
If the size reports as zero, fall back one of the PATH_MAX variants.
* For realpath(), POSIX 2008 allows us to pass a NULL buffer
to tell it to malloc() internally.
This patch was inspired by downstream patches in Debian packaging
for issues 897061 and 909011.
Issue: #18337
|
| |
|
|
|
|
|
| |
* upstream-libuv:
libuv 2018-05-06 (bf605bd7)
|
|\
| |
| |
| |
| |
| |
| | |
1c22fdf360 libuv: linux/sparc64: use fcntl to set and clear O_NONBLOCK
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2029
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Upstream libuv commits:
* node-v0.6.0~28 (linux: use ioctl(FIONBIO) to set O_NONBLOCK, saves a syscall, 2011-10-29)
* v1.11.0~11 (unix: use async-signal safe functions between fork and exec, 2016-12-12)
left an asymmetry in the way O_NONBLOCK is set and cleared. Normally
ioctl/FIONBIO is used for both. However, uv_spawn uses fcntl/O_NONBLOCK
to clear O_NONBLOCK between fork and exec. This fails on Linux/sparc64
where setting via ioctl/FIONBIO actually sets two bits (in O_NDELAY)
that cause clearing via fcntl/O_NONBLOCK to be silently ignored (though
clearing via ioctl/FIONBIO or fcntl/O_NDELAY works).
Since CMake commit v3.11.0-rc1~117^2 (CTest: Re-implement test process
handling using libuv, 2017-12-10), CTest uses libuv. On Linux/sparc64
child processes have been started with non-blocking output pipes. This
can lead to write errors or lost output from children not prepared to
deal with `EAGAIN` on stdout or stderr.
Fix this for now by switching libuv back to fcntl/O_NONBLOCK to set and
clear O_NONBLOCK when compiled on Linux/sparc64.
LibUV-Issue: 1830
Fixes: #17941
|
| |
| |
| |
| | |
Avoid depending on platform-specific pthread features during bootstrap.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Implement it on Linux, FreeBSD, and Windows for now, and fail with
UV_ENOTSUP on other platforms.
Backported from upstream libuv PR 1527, scheduled for inclusion
in libuv 2.0.
|
|/
|
|
|
|
|
|
| |
Implement it on Linux, FreeBSD, and Windows for now, and return
UV_ENOTSUP on other platforms.
Backported from upstream libuv PR 1527, scheduled for inclusion
in libuv 2.0.
|
|
|
|
|
| |
* upstream-libuv:
libuv 2018-01-19 (63de1eca)
|
|
|
|
|
|
|
|
|
|
| |
BSD `signal(2)` semantics make some system calls (e.g. for `write`)
restartable when interrupted by a signal handler. Use `SA_RESTART` to
enable these semantics everywhere that supports them.
This is required by C++ stream libraries that interpret `EINTR` as any
other error, set `badbit`, and stop writing. I've observed this with
`libstdc++` during a `std::cout.flush()` call interrupted by `SIGCHLD`.
|
|
|
|
|
|
|
| |
On UNIX, build only the parts of libuv we need for the filesystem,
process, and poll abstractions using the POSIX poll() backend. This
avoids many platform-specific conditions. On Windows, build all of
libuv; there are no conditional alternatives anyway.
|
|
|
|
|
| |
* upstream-libuv:
libuv 2017-05-25 (dc596109)
|
|
|
|
|
|
|
| |
* upstream-libuv:
libuv 2017-05-09 (e11dcd43)
Fixes: #16878
|
| |
|
| |
|
|
|
|
|
| |
* upstream-libuv:
libuv 2017-02-21 (52ae8264)
|
|
|
|
|
| |
* upstream-libuv:
libuv 2016-09-27 (8221f9b3)
|
|
|
|
|
| |
The Clang scan-build tool warns about assignments whose values are never
used, so initialize local variables at declaration instead.
|
| |
|
|
|
|
|
| |
We only need the availability macros in `unix/internal.h`. We already
include CoreServices where needed in implementation files.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Add '-w' or equivalent flag on compilers supporting it.
Tell MSVC to use its lowest warning level inside libuv sources.
|
|
* upstream-libuv:
libuv 2016-08-30 (897738b1)
|