similar to: [LLVMdev] LLVM Release 2.7 Download Links Broken

These are all fixed. Sorry for the mistake.. I blame lack of sleep ;) -Tanya On Apr 27, 2010, at 8:58 AM, Pitr wrote: > Trying to download Release 2.7 i get the response: > > The requested URL /releases/2.7/clang-2.7.tar.gz was not found on this server. > The requested URL /releases/2.7/clang-2.7-amd64-freebsd8.tar.gz was > not found on this server. > The requested URL

also get error with http://llvm.org/releases/2.7/clang-2.7-amd64-freebsd8.tar.gz 2010/4/27 Lucas Silva <landir at gmail.com>: > Hi for those who maintain the website: > The link to download Clang source code is broken in > http://llvm.org/releases/download.html#2.7 > It opens http://llvm.org/releases/2.7/clang-2.7.tar.gz with a 404 not found > page > > -- > Lucas da

Hi for those who maintain the website: The link to download Clang source code is broken in http://llvm.org/releases/download.html#2.7 It opens http://llvm.org/releases/2.7/clang-2.7.tar.gz with a 404 not found page -- Lucas da Costa Silva @landir -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I have a couple of FreeBSD-servers that I try to manage using puppet. I''m just trying it out at the moment and have just deployed 5 new boxes (from PXE and scripted installation so supposedly they are all identical except for the name and ip-addresses). On two of the servers I get the error-messages at the bottom of the post. The first error- message I get every time I run puppet on

Hey List- running samba 3.0.23b I have an issue with a single member of a group not being able to get write access to a share that all the other members have access to. I have checked the file permissions and they look good to me. Any thoughts on where to look or solve this? Below is some info. share portion of smb.cnf: [ecwtest] path = /data/www/webroot writeable = yes create mode = 6775

I am definitely in favor of this if it is ok with Tanya. I hope to spend some time in the next few weeks on tracking down miscompiles, and it would be great to get Clang to the "early-but-usable-beta" stage so it makes sense to roll binaries for 2.7. Tanya, I can also do the x86-32-pc-linux release testing if no one else steps up. - Daniel On Fri, Feb 12, 2010 at 3:02 PM, Douglas

On Feb 12, 2010, at 8:25 AM, David Greene wrote: > On Thursday 11 February 2010 18:17:33 Tanya Lattner wrote: >> Just a reminder that the 2.7 code freeze is on Feb 21st. >> >> All major changes should be committed approximately 1 week before the code >> freeze to ensure adequate testing. Please do your part to keep the tree >> stable in the days leading up to the

The 2.7 binaries are available for testing: http://llvm.org/pre-releases/2.7/pre-release1/ You will also find the source tarballs there as well. We rely on the community to help make our releases great, so please help test 2.7 if you can. Please follow these instructions to test 2.7: To test llvm-gcc: 1) Compile llvm from source and untar the llvm-test in the projects directory (name it

On Fri, Jul 22, 2016 at 2:37 PM, Tanya Lattner <tanyalattner at llvm.org> wrote: > > On Jul 21, 2016, at 11:59 PM, Sean Silva <chisophugis at gmail.com> wrote: > > Hi Tanya, > > I was spelunking through bugzilla and ran into an old mailing list link > http://lists.cs.uiuc.edu/pipermail/llvmdev/2006-January/005137.html > (found in PR36). > > I expect this

Hi Tanya, I was spelunking through bugzilla and ran into an old mailing list link http://lists.cs.uiuc.edu/pipermail/llvmdev/2006-January/005137.html (found in PR36). I expect this link to be broken since our servers are not on that domain. No big deal, just change it to lists.llvm.org: http://lists.llvm.org/pipermail/llvmdev/2006-January/005137.html Looks like that doesn't exist, as the

On Fri, Feb 12, 2010 at 5:48 PM, Daniel Dunbar <daniel at zuster.org> wrote: > I am definitely in favor of this if it is ok with Tanya. > > I hope to spend some time in the next few weeks on tracking down > miscompiles, and it would be great to get Clang to the > "early-but-usable-beta" stage so it makes sense to roll binaries for > 2.7. > > Tanya, I can

On 03/17/2010 10:12 PM, Tanya Lattner wrote: > The 2.7 binaries are available for testing: > http://llvm.org/pre-releases/2.7/pre-release1/ > > You will also find the source tarballs there as well. > > We rely on the community to help make our releases great, so please help > test 2.7 if you can. Please follow these instructions to test 2.7: > > /To test llvm-gcc:/

On 03/30/2010 09:15 PM, Tanya Lattner wrote: > > Thanks for testing the release! > >> Tests were run on x86-64, Debian unstable, Linux 2.6.33, gcc 4.4.3, >> 64-bit. I built srcdir == objdir, I have built llvm and clang myself, >> and used the binaries for llvm-gcc. >> >> 1. llvm-gcc 2.7 vs 2.6 >> compared to my results from Aug 31 2009, ignoring CBE

Hm, I also note that: $ file /opt/clang+llvm-2.7-i386-darwin10/bin/llvm-as /opt/clang+llvm-2.7-i386-darwin10/bin/llvm-as: Mach-O 64-bit executable x86_64 Why's the i386 package have an x86_64 binary in it? That could explain why it doesn't work on darwin9. On Fri, Mar 19, 2010 at 9:49 AM, Jeffrey Yasskin <jyasskin at google.com> wrote: > Hi Tanya, > > On darwin9, the

On Feb 12, 2010, at 3:02 PM, Douglas Gregor wrote: > > On Feb 12, 2010, at 8:25 AM, David Greene wrote: > >> On Thursday 11 February 2010 18:17:33 Tanya Lattner wrote: >>> Just a reminder that the 2.7 code freeze is on Feb 21st. >>> >>> All major changes should be committed approximately 1 week before the code >>> freeze to ensure adequate

All, There has been a huge lack of response to the release. We need people to help fix regressions and to participate in testing the release. Without this support, I see no reason that the release team should spend their time qualifying a release. We need to get all regressions fixed before 2.7 can continue onto pre-release2. Please take a look at all release blockers:

On 03/30/2010 09:21 PM, Török Edwin wrote: > On 03/30/2010 09:15 PM, Tanya Lattner wrote: >> Thanks for testing the release! >> >>> Tests were run on x86-64, Debian unstable, Linux 2.6.33, gcc 4.4.3, >>> 64-bit. I built srcdir == objdir, I have built llvm and clang myself, >>> and used the binaries for llvm-gcc. >>> >>> 1. llvm-gcc 2.7 vs

Just a reminder that the 2.7 code freeze is on Feb 21st. All major changes should be committed approximately 1 week before the code freeze to ensure adequate testing. Please do your part to keep the tree stable in the days leading up to the code freeze. Thanks! -Tanya 2/21 - Code Freeze (9PM PST) 2/27 - Pre-release1 released & community testing begins 3/6 - Pre-release1 testing ends 3/13

Hello, I am trying to build llvm-gcc 4.2 w/ llvm 2.2 on FreeBSD/amd64 and have found that it doesn't seem to want to build shared libraries. I've found numerous notes that I should try --disable-shared, because the linker ends up erroring out with a linker error when building libgcc_s.so. Subsequently, the same error is produced when it attempts to build libstdc++.so. If you do happen to

On Sep 24, 2011, at 3:54 PM, clepple+buildbot at ghz.cc wrote: > The Buildbot has detected a new failure of FreeBSD-x86 on Network > UPS Tools. > Full details are available at: > http://buildbot.networkupstools.org/public/nut/builders/FreeBSD-x86/builds/266 http://buildbot.ghz.cc/public/nut/builders/FreeBSD-x86/builds/266/steps/compile/logs/stdio : libtool: compile: gcc