Displaying 6 results from an estimated 6 matches for "forkpty".
Did you mean:
forkit
2016 Feb 25
0
[Release-testers] [3.8 Release] RC3 has been tagged
...uild, test, and
> upload to the sftp.
Uploaded:
clang+llvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-16.04.tar.xz
clang+llvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-15.10.tar.xz
clang+llvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-14.04.tar.xz
On Ubuntu 16.04 x86_64:
Failing Tests (7):
MemorySanitizer :: Linux/forkpty.cc
MemorySanitizer :: Linux/tcgetattr.cc
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent_r
MemorySanitizer-Unit ::
Msan-x86_64-with-call-Test/MemorySanitizer.getmntent
MemorySanitizer-Uni...
2016 Feb 23
10
[3.8 Release] RC3 has been tagged
Dear testers,
Release Candidate 3 has just been tagged [1]. Please build, test, and
upload to the sftp.
If there are no regressions from previous release candidates, this
will be the last release candidate before the final release.
Release notes can still go into the branch.
Thanks again for all your work!
Hans
[1] http://lists.llvm.org/pipermail/llvm-branch-commits/2016-February/009866.html
2012 Dec 21
1
Problem compiling Samba4, Python installed in nonstandard location
...3/./Modules/signalmodule.c:113: undefined reference to `fmod'/opt/python2/lib/libpython2.7.a(posixmodule.o): In function `posix_openpty':/usr/src/Python-2.7.3/./Modules/posixmodule.c:3756: undefined reference to `openpty'/opt/python2/lib/libpython2.7.a(posixmodule.o): In function `posix_forkpty':/usr/src/Python-2.7.3/./Modules/posixmodule.c:3816: undefined reference to `forkpty'/opt/python2/lib/libpython2.7.a(complexobject.o): In function `_Py_c_pow':/usr/src/Python-2.7.3/Objects/complexobject.c:139: undefined reference to `hypot'/usr/src/Python-2.7.3/Objects/complexobject...
2016 Sep 12
3
-fsanitize=memory failing on 3.9.0
If you are on glibc-2.24, did you patch it with the fix
24e2b1cede1952d7d4411a3cafd25dd8593dab9f that revert commits
80f87443eed17838fe453f1f5406ccf5d3698c25 and
a824d609581d5ee7544aabcbbc70e8da44b2b5b6? I had to do that since it
broke go, gcc, and clang address sanitizers without the patch.
On 9/12/16, Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> On 11 September
2017 Mar 02
12
[4.0.0 Release] Release Candidate 3 has been tagged
Hello testers,
4.0.0-rc3 was just tagged from the branch at r296762.
This is a release candidate in the real sense: if no major issues show
up with this one, it is the version that will be released.
Please let me know if you find any issues, including in release notes
or documentation, which will be on the pre-release web site later
today.
Please build, test, and upload binaries to the sftp
2016 Feb 02
7
[3.8 Release] RC2 has been tagged
Dear testers,
Release Candidate 2 has just been tagged [1]. Please build, test, and
upload to the sftp.
I know there are still outstanding issues from RC1, but there have
been a lot of merges going into the branch and I think it's time for
another round of RC testing.
This RC comes a little behind schedule, sorry about that, but I'm
still optimistic about hitting the target of releasing