aboutsummaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
* Kill `-fwarn-unused-imports`-induced sillinessGravatar Herbert Valerio Riedel2015-11-16
| | | | | | | | | This all started in e968172cb0c9f4fc653c775faf3ecb661f5b1948 which tried to get rid of redundant import warnings. But we should rather err on having to tolerate a few warnings on exotic configurations rather than breaking a build... This hopefully fixes #36
* Don't assume existence of termios constants beyond `B38400`Gravatar Herbert Valerio Riedel2015-11-16
| | | | | | | | | | This patch does not modify the `BaudRate` structure but rather causes some functions taking a `BaudRate` to throw exceptions on systems which don't provide `B57600` and/or `B115200`. I'm not totally happy with this patch yet, but this unbreaks compilation on platforms which don't define at least of these constants. This fixes #51
* Don't assume non-POSIX `WCOREDUMP(x)` macro existsGravatar Herbert Valerio Riedel2015-11-16
| | | | This fixes #50
* Relax upper bound on `base` for base-4.9Gravatar Herbert Valerio Riedel2015-10-28
|
* Merge pull request #42 from argiopetech/masterGravatar Elliot Robinson2015-03-09
|\ | | | | Adds a more comprehensive check for fdatasync
| * Adds a more comprehensive check for fdatasyncGravatar Elliot Robinson2015-03-08
|/ | | | | Some versions of OS X have fdatasync in the headers but don't include implementations in the standard library. This leads to a compile failure in configure.ac when using AC_CHECK_FUNCS. This change explicitly attempts to compile a file containing a call to fdatasync and properly sets the AC_CHECK_FUNCS flags depending on the result of compilation.
* Add GHC 7.8.4 to test-matrixGravatar Herbert Valerio Riedel2014-12-27
|
* Merge pull request #32 from redneb/getcwd-exn-safeGravatar Gregory Collins2014-12-23
|\ | | | | rewrite getWorkingDirectory to use allocaBytes for exception safety
* | Add GHC 7.10.1 to test-matrixGravatar Herbert Valerio Riedel2014-12-23
| |
| * rewrite getWorkingDirectory to use allocaBytes for exception safetyGravatar Marios Titas2014-12-23
|/
* Add /Since/ annotation to System.Posix.FcntlGravatar Herbert Valerio Riedel2014-12-19
|
* Prepare for 2.7.1.0 releaseGravatar Herbert Valerio Riedel2014-12-19
|
* Tweak markdown markup again [skip ci]Gravatar Herbert Valerio Riedel2014-12-19
|
* Fix markdown markup [skip ci]Gravatar Herbert Valerio Riedel2014-12-19
|
* Tighten SafeHaskellGravatar Herbert Valerio Riedel2014-12-19
| | | | This was forgotten in e14fbe2cb3bbd604dadcc3847882ca37edf548b3
* Fix SIGINFO and SIGWINCH.Gravatar Erik de Castro Lopo2014-12-19
| | | | | | | | | | | | It seems these two signals have not been working since at least 2009. Detection of these signals seems to have never been added to the configure.ac script and the code guarded by #ifdef then bit-rotted (the idiom used to handle these signals seems to have been abandoned for something simpler/better in 2009). This fix simply handles these signals the same way the other signals are handled in System/Posix/Signals.hsc. Closes #30 and #31
* Be more explicit in WARNING what will be thrownGravatar Herbert Valerio Riedel2014-12-15
|
* Add since-annotations to new fileSync opsGravatar Herbert Valerio Riedel2014-12-15
|
* Wrap posix_fadvise(2) and posix_fallocate(2)Gravatar Herbert Valerio Riedel2014-12-15
| | | | | | | | | | | | This adds two new functions in `System.Posix.Unistd` - `fileAdvise` (aka `posix_fadvise(2)`), and - `fileAllocate` (aka `posix_fallocate(2)`) This is based in part on #7 and has been heavily refactored from its original patch submission by Ricardo Catalinas Jiménez. Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>
* Merge pull request #29 from haskell/safefixes710againGravatar Herbert Valerio Riedel2014-12-09
|\ | | | | More fixes for Safe Haskell bounds under GHC 7.10
| * More fixes for Safe Haskell bounds under GHC 7.10Gravatar David Terei2014-12-08
|/
* Tweak execvpe.h hack (see 256b19184bcb) some moreGravatar Herbert Valerio Riedel2014-12-07
|
* Wrap fsync(2) and fdatasync(2)Gravatar Herbert Valerio Riedel2014-12-07
| | | | | | | | | | | | | | This adds two new functions in `System.Posix.Unistd` - `fileSynchronise` (aka `fsync(2)`), and - `fileSynchroniseDataOnly` (aka `fdatasync(2)`) This is based on part of #7 and has been heavily refactored from its original patch submission by Ricardo Catalinas Jiménez. This also bumps version to 2.7.1.0 as a minor version bump is now needed. Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>
* Repeat execvpe(3) prototype (fup to 7bad9d7d52d)Gravatar Herbert Valerio Riedel2014-12-06
| | | | | This is needed in case `<unistd.h>` was included before "execvpe.h" w/o `_GNU_SOURCE` set (on Glibc systems)
* Have "execvpe.h" provide execvpe() againGravatar Herbert Valerio Riedel2014-12-06
| | | | | | Turns out `process` reuses `unix`'s execvpe() implementation, and the refactoring in f24ba78f68b2cbc4f4afadc8dd60fc2935357255 broke process.
* `M-x untabify` && `M-x delete-trailing-whitespace`Gravatar Herbert Valerio Riedel2014-12-06
|
* Retry process execution in case of ENOTDIRGravatar Iku Iwasa2014-12-06
| | | | | | | If `PATH` environment variable contains non directory component, `__hsunix_execvpe()` failed by `ENOTDIR`. This fixes #11 for all platforms.
* Refactor local `execvpe(3)` implementationGravatar Herbert Valerio Riedel2014-12-06
| | | | | | | | | | | | | | | | | The previous code was prone to conflicts with when the platform happens to expose a `execvpe(3)` implementation in its libc. This commit renames the internal implementation to `__hsunix_execvpe` as well as adding an autoconf-detection for the presence of `execvpe(3)`, in which case `__hsunix_execvpe()` forwards the call to `execvpe(3)`. Moreover, the code has been cleaned up to remove likely bitrotted CPP conditionals. This should fix #22 (This also partially addresses #11 on platforms which have a libc-provided `execvpe(3)`)
* Do not blindly add libdl to extra librariesGravatar Igor Pashev2014-12-06
| | | | | | | | On some systems dlopen() is available without libdl (illumos, solaris). Sometimes libdl.so cannot be loaded by runtime linker, see https://ghc.haskell.org/trac/ghc/ticket/8713 Closes #8
* Tighten Safe Haskell bounds, fixes new warning in GHC 7.10.Gravatar David Terei2014-12-06
| | | | Closes #27
* Kill spurious line from changelogGravatar Herbert Valerio Riedel2014-12-06
| | | [skip ci]
* fixup Travis CI jobGravatar Herbert Valerio Riedel2014-12-06
|
* Update Travis CI JobGravatar Herbert Valerio Riedel2014-12-06
|
* Merge pull request #18 from neverpanic/masterGravatar Herbert Valerio Riedel2014-11-07
|\ | | | | `System.Posix.Files.fileAccess` fails inside OS X sandbox
* | Add hackage-shield to README.mdGravatar Herbert Valerio Riedel2014-10-23
| |
* | Merge pull request #5 from hvr/pr-LFSGravatar Herbert Valerio Riedel2014-10-18
|\ \ | | | | | | Fix potential LFS related issues
| * | fix _FILE_OFFSET_BITS redefined warning on Solaris/x86Gravatar Karel Gardas2014-10-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The issue is that sys/types.h header on Solaris includes somehow /usr/include/sys/feature_tests.h which tests if _FILE_OFFSET_BITS is defined and if not, then it defines it to 32 if we're compiling 32 bit code (x86). This is simply wrong since we'd like to have it defined to 64. The issue is solved by including HsUnixConfig.h first which defines _FILE_OFFSET_BITS to 64 and feature_tests.h is later OK with that.
| * | Use CAPI FFI imports for `truncate`Gravatar Herbert Valerio Riedel2014-10-18
| | | | | | | | | | | | | | | This makes sure we pick up the LFS version of `truncate` in case `off_t` is affected by CPP defines such as `_FILE_OFFSET_BITS`.
| * | Use correct POSIX offset-type for tell/seekdirGravatar Herbert Valerio Riedel2014-10-18
|/ / | | | | | | | | | | | | | | | | | | | | | | This fixes the FFI imports to use the proper `CLong` type over the previous incorrect `COff` type, as using the wrong argument type can cause problems when the `long` and `off_t` types have different size. Historic note from the manual page: In glibc up to version 2.1.1, the return type of telldir() was off_t. POSIX.1-2001 specifies long, and this is the type used since glibc 2.1.2 (released in 1999).
* | Replace obsolete `defaultUserHooks` by `autoconfUserHooks`Gravatar Herbert Valerio Riedel2014-09-27
| |
* | Merge pull request #19 from thomie/masterGravatar Herbert Valerio Riedel2014-09-26
|\ \ | | | | | | Disable getlogin tests for the moment (#1487)
| * | Disable getlogin tests for the moment (#1487)Gravatar Thomas Miedema2014-09-26
|/ /
| * Accept EPERM as valid error code for access(2)Gravatar Clemens Lang2014-09-21
| | | | | | | | | | | | | | This is useful on OS X when its sandboxing mechanism is used, because that will set errno = EPERM when a file can't be written due to sandboxing (as opposed to setting it to EACCES when file permissions deny writing).
| * Unify accepted errno flags for accessGravatar Clemens Lang2014-09-21
| | | | | | | | | | | | | | The ByteString variant of the access function didn't accept the same flags as the non-ByteString one, but it makes sense that the OS doesn't care about which one is being used and returns all error codes for both variants.
| * Unify whitespace in System/Posix/Files/ByteStringGravatar Clemens Lang2014-09-21
|/
* Update config.{guess,sub} to GNU automake 1.14.1Gravatar Herbert Valerio Riedel2014-09-16
|
* Relax upper bound to allow `time-1.5`Gravatar Herbert Valerio Riedel2014-09-10
|
* Use import list for `Data.Time.Clock.POSIX`Gravatar Herbert Valerio Riedel2014-09-10
| | | | | This makes it more obvious why `unix` depends on `time` in the first place, i.e. for the sole purpose of reusing the `POSIXTime` type.
* Merge branch 'sol-fix-getgrgid_r-v3' of https://github.com/kgardas/unix into ↵Gravatar Herbert Valerio Riedel2014-09-10
|\ | | | | | | | | | | | | kgardas-sol-fix-getgrgid_r-v3 Conflicts: changelog.md
| * fix getGroupEntryForID/Name on SolarisGravatar Karel Gardas2014-09-10
| | | | | | | | | | | | | | | | | | This patch fixes getGroupEntryForID and getGroupEntryForName on Solaris The issue on Solaris is that it defines both required getgrgid_r and getgrnam_r functions as CPP macros which depending on configuration are mapped to real function implementations with different names. The issue is solved by using C API calling convention instead of platform C ABI calling convention.
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-30 01:23:20 +0000