similar to: bind-9.3.3-9.0.1 RPM BUILD error

CentOS Errata and Security Advisory 2007:0740 https://rhn.redhat.com/errata/RHSA-2007-0740.html The following updated files have been uploaded and are currently syncing to the mirrors: x86_64: bind-9.3.3-9.0.1.el5.x86_64.rpm bind-chroot-9.3.3-9.0.1.el5.x86_64.rpm bind-devel-9.3.3-9.0.1.el5.i386.rpm bind-devel-9.3.3-9.0.1.el5.x86_64.rpm bind-libbind-devel-9.3.3-9.0.1.el5.i386.rpm

LLVM 9.0.1 is now available! Download it now, or read the release notes. This release contains bug-fixes for the LLVM 9.0.0 release. This release is API and ABI compatible with 9.0.0. Binaries and sources for 9.0.1 can be found on GitHub: https://github.com/llvm/llvm-project/releases/tag/llvmorg-9.0.1 LLVM 9.0.1 would not be possible without the help of our volunteer release team! Thanks to all

GCC 9.0.1 isn't smart enough to work out that buf is initialized on all the relevant paths that lead to backend->pwrite being called. By initializing it we can avoid the warning. protocol.c: In function ‘protocol_recv_request_send_reply’: protocol.c:241:9: error: ‘buf’ may be used uninitialized in this function [-Werror=maybe-uninitialized] 241 | if (backend->pwrite (backend,

On 01/08/2020 09:24 AM, Brian Cain wrote: > Tom, the 9.0.1 final binaries didn't (yet?) make it to the github release page https://github.com/llvm/llvm-project/releases/tag/llvmorg-9.0.1 > The binaries have been posted now. > I also checked https://releases.llvm.org/ because I recall some debate or back-and-forth about where the releases should go and/or redirects or links from

CentOS Errata and Security Advisory 2007:0740 https://rhn.redhat.com/errata/RHSA-2007-0740.html The following updated files have been uploaded and are currently syncing to the mirrors: i386: bind-9.3.3-9.0.1.el5.i386.rpm bind-chroot-9.3.3-9.0.1.el5.i386.rpm bind-devel-9.3.3-9.0.1.el5.i386.rpm bind-libbind-devel-9.3.3-9.0.1.el5.i386.rpm bind-libs-9.3.3-9.0.1.el5.i386.rpm

Hello all, We just encountered several serious Out of Memory Problems caused by the file 4.17-9.0.1.EL5 utility on our mail Gateway. CentOS 5.1 kept it self alive by killing it parent process Amavisd-new. Manually restarting Amavisd-new and flushing the mail queue caused same problem. Disabling file for the moment, caused Amavisd-new to fail, and also defer all mail. My quick and dirty

On 01/09/2020 09:11 AM, Brian Cain wrote: > > > On Thu, Jan 9, 2020 at 12:29 AM Tom Stellard <tstellar at redhat.com <mailto:tstellar at redhat.com>> wrote: > > On 01/08/2020 09:24 AM, Brian Cain wrote: > > Tom, the 9.0.1 final binaries didn't (yet?) make it to the github release page https://github.com/llvm/llvm-project/releases/tag/llvmorg-9.0.1

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

On 01/14/2020 08:59 AM, Russell Gallop wrote: > Hi Tom, Hans, > > I can't see LLVM-9.0.1-win*.exe from Hans on the GitHub release page (https://github.com/llvm/llvm-project/releases/tag/llvmorg-9.0.1). Is this still in progress? > Hans did you upload these? I don't see them on the server. -Tom > Thanks > Russ > > On Thu, 9 Jan 2020 at 20:05, Tom Stellard via

I've done something a while back that has messed with my named.conf and prevents me from restarting named service normally... My problem... # service named restart Stopping named: [FAILED] Starting named: named: already running [FAILED] nothing gets logged in /var/log/messages obviously, I can do this to restart it... [root at

On 12/10/2019 12:06 AM, Tobias Hieta wrote: > Hello, > > I finally figured out that I still need Python 2.7 in order to get > tests running correctly on macOS. But this lead to a bunch of test > fails when using the script: > > FAIL: LLVM :: Bindings/Go/go.test (23671 of 61786) I've seen this go failure before on macOS, so it is somewhat expected. Do the rest of these

hi, i want to setup DNS server on centos 5.0, and find the preinstalled version is bind.x86_64 30:9.3.3-7.el5 , and bind.x86_64 30:9.3.3-9.0.1.el5 in the updates repository. but i need to upgrade bind to version 9.3.4-P1 to prevent from any known security bugs is there any way i can do ? thanks, Bell

Hi, I've just tagged the 9.0.1-final release. Testers can begin uploading binaries. -Tom

I just want to confirm that this is a "bug" before reporting it to Bugzilla. I started with the sample named.conf included in the distribution and found that I couldn't query my server from outside my LAN. I finally traced it down to the match expressions in the sample's external view. bind-9.3.3-9.0.1.el5 /usr/share/doc/bind-9.3.3/sample/etc/named.conf The view has these

Hi, I've tagged the LLVM 9.0.1-rc1 release. Testers can begin testing and upload binaries. I've also updated the test-release.sh script to pull from GitHub instead of SVN, if you run into any issues with the new script, let me know. -Tom

Hi, I've tagged LLVM 9.0.1-rc2. Testers can begin testing and uploading binaries. If all goes well, this will be the last -rc. -Tom

Hi, I've just tagged LLVM 9.0.1-rc3. Testers can begin testing and uploading binaries. This will be the last release candidate unless there is a major problem. I'm planning to tag the final release on Dec 19. -Tom

Hi, I have updated the kernel to 2.4.21-27.0.2 on Centos 3.4 (was 3.3 when I did the kernel update) and have modified grub.conf to use the single CPU kernel: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. #

hi guys i have: CentOS_5.1 Linux 2.6.24 #2 SMP Fri Feb 15 20:03:34 AST 2008 i686 i686 i386 GNU/Linux with: bind-utils-9.3.3-10.el5ypbind-1.19-8.el5bind-9.3.3-10.el5bind-chroot-9.3.3-10.el5bind-libs-9.3.3-10.el5 when i try to start named i get this : Locating /var/named/chroot/etc/named.conf//etc/named.conf failed: [FAILED]i allready

Hello all, I?ve installed a proxy Squid in my gateway and a Cache DNS Server with bind. The problem is the server is only resolving is own querys but not the client queries from my company. When I do: $service named start I see in /var/log/messages: starting BIND 9.3.4-P1 -u named -t /var/named/chroot found 1 CPU, using 1 worker thread loading configuration from '/etc/named.conf'