search for: modigied

I would like to test but the I modigied the configure to make unknown = OpenBSD and Unix and go pretty far but it died right after 'supports mkdir' yes... then the next line was 'your system is unsupported'' I have gcc 3.3 on OpenBSD 3.3 pro-police stack compiler... I am only really interested in testing the C/...

Hi Josephm > I would like to test but the I modigied the configure to make unknown > = OpenBSD and Unix and go pretty far but it died right after 'supports > mkdir' yes... Could that have been `checking for mkdir...'? > then the next line was 'your system is unsupported'' Have you looked at ./config.log. ./configu...

Hi again, I wrote: > > I would like to test but the I modigied the configure to make > > unknown = OpenBSD and Unix > > Have you looked at ./config.log. ./configure creates this as it runs > as a trace of the path it took through ./configure. Work backwards > from the end to find out what it didn't like. I remember SourceForge's c...

...out a dozen places). I suspect we'll have to add one for NetBSD also one day (even DragonflyBSD?). INT8_MAX and friends ought to be declared by <stdint.h>. It is on FreeBSD. Ralph Corderoy wrote: >Hi again, > >I wrote: > > >>>I would like to test but the I modigied the configure to make >>>unknown = OpenBSD and Unix >>> >>> >>Have you looked at ./config.log. ./configure creates this as it runs >>as a trace of the path it took through ./configure. Work backwards >>from the end to find out what it didn't...

...(there were about a dozen places). I suspect we'll have to add one for NetBSD also one day (even DragonflyBSD?). INT8_MAX and friends ought to be declared by . It is on FreeBSD. Ralph Corderoy wrote: >Hi again, > >I wrote: > > >>>I would like to test but the I modigied the configure to make >>>unknown = OpenBSD and Unix >>> >>> >>Have you looked at ./config.log. ./configure creates this as it runs >>as a trace of the path it took through ./configure. Work backwards >>from the end to find out what it didn't...

On Sun, 16 Apr 2006, Tanya Lattner wrote: > For testing, we would like a mix of people to do x86 and ppc. Please send > email to the list if you plan to test, what architecture, and if you will use > the llvm-gcc binary or compile it yourself. That way, I know who to expect > results from. I will test on Darwin/PPC, I'll try the precompiled llvmgcc, objdir != srcdir. -Chris

I've put the pre-release tar balls here: http://llvm.org/prereleases/1.7/ I'm asking for help to test this release and to review documentation. If anyone can spare some time to help out, I would really appreciate it. The more people that test, the better this release will be. Secondly, now that the tarballs have been created, everyone is free to check in documentation changes into the