| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
[Bug #16497]
https://github.com/ruby/stringio/commit/4958a5ccab
(cherry picked from commit e257c08f2ec27e2d66cdfa7e2415deb492522e22)
|
|
|
|
|
|
| |
Because the package provided by GitHub releases is different from sourceware.
(cherry picked from commit 47a1872cd8b901b8aab6dedce7fa3807c97d290d)
|
|
|
|
|
| |
[Bug #16681]
(cherry picked from commit 86022167461dc90b70164e2bb23316959bbfd6ba)
|
|
|
|
|
|
|
|
|
|
| |
To enable implementation-defined output processing, for the
compatibility with readline. [Bug #16509]
https://bugs.ruby-lang.org/issues/16509
https://github.com/ruby/io-console/commit/8c8b0b6757
(cherry picked from commit 4e56ec4ef74cf77dbcb4ce7c669e0595cd0d12fa)
|
|
|
|
|
| |
Block for `create_makefile` is expected to return the content of
the makefile.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BSD make can run parallel more aggressively than GNU make. It communicate
with other make process through -J option in MAKEFLAGS environment variable
to notify a build failure happend in an other pararell make process.
https://www.freebsd.org/cgi/man.cgi?make
It usually works well but ext/-test-/cxxanyargs/Makefile has two targets
which are expected to fail (failure.o and failurem1.o).
Additional note:
To test and debug this issue, following command will speed up it.
`make -f exts.mk -j8 clean all`
|
| |
|
|
|
|
| |
https://github.com/ruby/readline-ext/commit/f5abaf5be1
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* Default VMIN and VTIME to minimum input.
* Disable parity check bits explicitly.
* Disable all bits for flow control on input.
Co-Authored-By: NARUSE, Yui <naruse@airemix.jp>
https://github.com/ruby/io-console/commit/5ce201a686
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
TCSAFLUSH discards the buffer read before the mode change, which makes
IRB ignore the buffer input immediately after invoked. TCSANOW
preserves the buffer.
https://github.com/ruby/io-console/commit/b362920182
|
|
|
|
|
|
| |
In raw mode with interrupt enabled.
https://github.com/ruby/io-console/commit/e9e8e3ff17
|
|
|
|
| |
https://github.com/ruby/io-console/commit/a49462ed97
|
| |
|
| |
|
| |
|
|
|
|
| |
https://github.com/ruby/io-console/commit/ae5c72e481
|
|
|
|
|
|
| |
function
https://github.com/ruby/io-console/commit/21338ab287
|
|
|
|
| |
https://github.com/ruby/io-console/commit/499ff3de48
|
| |
|
|
|
|
|
|
| |
This reverts commit 0d7d8b2989e1738dd902d354cc41186899e6b71e,
but restore `$warnflags` without the flag, to get rid of using
deprecated functions.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It fails to build on Solaris:
```
ossl_cipher.c: 関数 ‘ossl_cipher_init’ 内:
ossl_cipher.c:228:2: エラー: ‘EVP_md5’ is deprecated [-Werror=deprecated-declarations]
228 | EVP_BytesToKey(EVP_CIPHER_CTX_cipher(ctx), EVP_md5(), iv,
| ^~~~~~~~~~~~~~
In file included from /usr/include/openssl/x509.h:73,
from /usr/include/openssl/x509v3.h:63,
from ossl.h:23,
from ossl_cipher.c:10:
/usr/include/openssl/evp.h:732:26: 備考: ここで宣言されています
732 | DEPRECATED const EVP_MD *EVP_md5(void);
| ^~~~~~~
```
I agree that `-Werror=` is a good habit, but adding it by default is too
aggressive.
|
|
|
|
|
|
|
| |
MonitorMixin#new_cond can be called before mon_initialize, so we
need to initialize `@monitor` before it.
https://bugs.ruby-lang.org/issues/16255#note-4
|
|
|
|
| |
https://github.com/ruby/io-console/commit/4c172c01aa
|
|
|
|
| |
https://github.com/ruby/zlib/commit/5af77c1ee8
|
|
|
|
| |
https://github.com/ruby/gdbm/commit/ffb2b063a3
|
|
|
|
| |
https://github.com/ruby/etc/commit/78987ce56a
|
|
|
|
| |
https://github.com/ruby/dbm/commit/163078359d
|
|
|
|
| |
https://github.com/ruby/readline-ext/commit/e5b969215a
|
|
|
|
| |
https://github.com/ruby/stringio/commit/4c1e267e1a
|
|
|
|
| |
https://github.com/ruby/stringio/commit/1fed3aacd3
|
|
|
|
| |
https://github.com/ruby/date/commit/202b2dad93
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Asynchronous events such as signal trap, finalization timing,
thread switching and so on are managed by "interrupt_flag".
Ruby's threads check this flag periodically and if a thread
does not check this flag, above events doesn't happen.
This checking is CHECK_INTS() (related) macro and it is placed
at some places (laeve instruction and so on). However, at the end
of C methods, C blocks (IMEMO_IFUNC) etc there are no checking
and it can introduce uninterruptible thread.
To modify this situation, we decide to place CHECK_INTS() at
vm_pop_frame(). It increases interrupt checking points.
[Bug #16366]
This patch can introduce unexpected events...
|
| |
|
| |
|
|
|
|
| |
Since https://github.com/ruby/ruby/pull/2576,
`new_cond` uses the Monitor object, not the receiver.
|
| |
|
|
|
|
|
|
|
|
| |
This reverts commit e1b234148829f65bea9f5ecc7018beb782ea6023.
This allows to build Psych against system libyaml again on Fedora.
[Bug #16359]
|
| |
|
| |
|
|
|
|
|
| |
Get rid of races in parallel configuration when using the
ext/Setup file.
|
| |
|
|
|
|
|
|
| |
Ruby 2.7 deprecates taint and it no longer has an effect.
The lack of taint support should not cause a problem in
previous Ruby versions.
|
|
|
|
|
|
| |
Ruby 2.7 deprecates taint and it no longer has an effect.
The lack of taint support should not cause a problem in
previous Ruby versions.
|
|
|
|
|
|
| |
Ruby 2.7 deprecates taint and it no longer has an effect.
The lack of taint support should not cause a problem in
previous Ruby versions.
|