search for: somchai

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

Has it been decided to skip 3.7.1 and just wait until 3.8.0? I keep checking but never see any update on the web site to allow downloading 3.7.1 tar files.

...ts.llvm.org> wrote: > Got to admit, I'm curious too. I have finished migrating to the v3.7.1-final tags, and I'm waiting for the green light :-) > > MartinO > > -----Original Message----- > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Somchai Smythe via llvm-dev > Sent: 28 December 2015 10:35 > To: llvm-dev at lists.llvm.org > Subject: [llvm-dev] 3.7.1 release cancelled? > > Has it been decided to skip 3.7.1 and just wait until 3.8.0? I keep checking but never see any update on the web site to allow downloading > 3.7....

Hello testers, 5.0.0-rc4 was just tagged. There were very few changes after rc3, and if nothing unexpected comes up, this is what the final release will look like. Please test and let me know if there are any issues. Cheers, Hans

Hello, The llvm.org web site says the release would be in mid-june. There was a message posted to the dev list that 3.8.1 was tagged. Then there was another message that said essentially "don't make your own tarballs - wait for release tarballs". I have two questions: 1. If the 3.8.1 tag does not represent what will be the tarball contents, will the tag be moved when the

...c package (https://git.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/glibc) and don't see any local patches. Therefore I assume it hasn't been patched. On Mon, Sep 12, 2016 at 1:38 AM, Renato Golin <renato.golin at linaro.org> wrote: > On 12 September 2016 at 07:11, Somchai Smythe > <buraphalinuxserver at gmail.com> wrote: >> If you are on glibc-2.24, did you patch it with the fix >> 24e2b1cede1952d7d4411a3cafd25dd8593dab9f that revert commits >> 80f87443eed17838fe453f1f5406ccf5d3698c25 and >> a824d609581d5ee7544aabcbbc70e8da44b2b5b6?...

Hello everyone, There's plenty of time before the release process starts, but I'd like to begin the schedule discussion. For the September release we usually branch mid-July. However, this year my vacation runs a little later, so a good branch date for me would be the 1st of August. Proposal: - 1 August 2018: Branch; RC1 soon after - 22 August 2018: RC2; all lose ends should be tied up

Hello everyone, The release branch for LLVM 9 and its sub-projects was just created from trunk at r366426, and the trunk version was subsequently bumped to 10.0.0. Release blockers are tracked by https://llvm.org/PR42474 Please mark any bugs, old or new, that need to be fixed before the release as blocking that. To get a change committed to the branch, first commit it to trunk as usual, and

Fine, I will do it all again and use some tool like 'script' to log every single byte, but it'll be a few days before I can email that to you since it takes overnight to zero out the drive to ensure no old data will interfere, and copying the data from the old drive to the new one is also rather slow. For the record, I did RTFM. It has no complete examples for _ANY_ use case, and you

Hello List Members, I have a machine that has used extlinux to boot for many years, but the hard disk needs to be replaced. I got a new hard disk and installed it in my system. The old disk is /dev/sda, and the new one is /dev/sdb. I'm using GPT partitioning, and I did (after a day) finally get the legacy bootable flag set on /dev/sdb for the boot partition /dev/sda1. I then formatted out

1. ext4 mke2fs -b 4096 -m 5 -t ext4 -O^uninit_bg -r 1 -v /dev/sdb1 sdparm --command=sync /dev/sdb 2. 150G 3. gdisk /dev/sdb x a 2 w y sdparm --command=sync /dev/sdb 4. mount /dev/sdb1 /mnt/sdb1 cd /mnt/sdb1 extlinux -i /mnt/sdb1/boot umount /mnt/sdb1 sync;sync;sync sdparm --command=sync /dev/sdb cat gptmbr.bin >/dev/sdb1 sync;sync;sync sdparm --command=sync /dev/sdb