similar to: [LLVMdev] GCC 3.4.1 and conflicting types for 'malloc' (2)

Hi These are: ======================== llvm[2]: Linking Release Object Library LLVMbzip2.o gmake[2]: Leaving directory `/homes/myuser/LLVM/llvmobj/lib/Support/bzip2' gmake[1]: Leaving directory `/homes/myuser/LLVM/llvmobj/lib/Support' gmake[1]: Entering directory `/homes/myuser/LLVM/llvmobj/utils' gmake[2]: Entering directory `/homes/myuser/LLVM/llvmobj/utils/Burg' llvm[2]:

It seems that this happened before but I do not know the details: http://llvm.cs.uiuc.edu/testresults/SparcV9/2004-12-07.html Thanks --- Chris Lattner <sabre at nondot.org> wrote: > On Sat, 12 Mar 2005, xavier wrote: > > llvm[2]: Compiling zalloc.c for Release build > > /homes/myuser/LLVM/llvmobj/../llvmsrc/utils/Burg/zalloc.c:9: error: conflictin > > g types for

I commented this line and it is compiling now: extern void *malloc ARGS((unsigned)); I hope that will not cause a different kind of problem. What it is zalloc used for? Thanks --- Chris Lattner <sabre at nondot.org> wrote: > On Sat, 12 Mar 2005, xavier wrote: > > > It seems that this happened before but I do not know the details: > >

Chris, Thanks for your answer Here is the verbose output: =========================== gmake tools-only VERBOSE=1 TOOL_VERBOSE=1 for dir in lib/System lib/Support utils lib tools ; do \ if [ ! -f $dir/Makefile ]; then \ /home/myuser/LLVM/objdir/../srcdir/autoconf/mkinstalldirs $dir; \ cp /home/myuser/LLVM/objdir/../srcdir//$dir/Makefile $dir/Makefile; \ fi; \ (gmake -C $dir all )

> > Are you able to run nightly test ? > Yes, I can run nightly test. > Here is what I see... > > $ make TEST=dbgopt > /Developer/usr/bin//llvm-gcc sse.expandfft.c -g --emit-llvm -c -o > Output/sse.expandfft.bc > /Volumes/Nanpura/mainline/llvm/Debug/bin/opt Output/sse.expandfft.bc - > strip-nondebug -strip-debug -std-compile-opts -strip -f -o Output/ >

Hi I am trying to build the llvm tools following the instructions here: http://llvm.cs.uiuc.edu/docs/CFEBuildInstrs.html But I get this error: /zalloc.c:9: error: conflicting types for 'malloc' I am using gcc 3.4.1 What can be the problem? __________________________________ Do you Yahoo!? Yahoo! Sports - Sign up for Fantasy Baseball. http://baseball.fantasysports.yahoo.com/

I found 179 more *.{c,cpp,h} files with tabs. Unfortunately, the tabs stops used vary so blindly expanding them messes up alignment in many cases :( Index: examples/BFtoLLVM/BFtoLLVM.cpp Index: include/llvm/AbstractTypeUser.h Index: include/llvm/GlobalVariable.h Index: include/llvm/InstrTypes.h Index: include/llvm/IntrinsicInst.h Index: include/llvm/ADT/PostOrderIterator.h Index:

Another error: ======================= gmake[2]: Entering directory `/home/myuser/LLVM/objdir/gcc' for d in libgcc; do \ if [ -d $d ]; then true; else /bin/sh ../../srcdir/llvm-gcc/gcc/mkinstalldirs $d; fi; \ done mkdir -p -- libgcc if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi /home/myuser/LLVM/objdir/gcc/xgcc -B/home/myuser/LLVM/objdir/gcc/

Hello, In preparation for the LLVM public release, I've moved the reoptimizer out of the main cvs module "llvm" and into the cvs module "reopt". You can go ahead and delete the lib/Reoptimizer directory from your tree, about which cvs will undoubtedly be complaining to you. If you want to build the reoptimizer, cd into your SPARC tree's "projects"

On Thu, 16 Dec 2004, Markus F.X.J. Oberhumer wrote: > Hello Chris, > > many thanks for your quick fix. No problem. > I'm currently trying to compile llvm under AMD64 - after applying the trivial > fix for Burg/zalloc.c attached below I do get pretty far - compilation stops > somewhere in gcc when compiling libgcc, probably related to a varargs problem. > I still have to

The following patches shave some rough edges off the tools build system to allow cross compiling for at least arm32 and arm64 based on the Debian/Ubuntu multiarch infrastructure. They also add the necessary fixes to build for arm64 (which I have only tried cross, not native). I have posted some instructions on how to compile with these patches on the wiki:

Morten Ofstad wrote: >> Hi, >> >> There's no HAVE_RAND48 symbol provided by autoconf. You'll have to >> add the appropriate check to autoconf/configure.ac before we can take >> this patch. I installed autoconf with cygwin now and I think I've managed to do this right now -- there are some strange problems with running the AutoRegen.sh script, so I

> Hi, > > There's no HAVE_RAND48 symbol provided by autoconf. You'll have to add > the appropriate check to autoconf/configure.ac before we can take this > patch. Sorry I forgot to mention I didn't make any changes to the configure script. The problem is that I can't test these things since I'm not on a Unix platform, and I'm not even using the

If you're on the new Makefile system, you will want to update your Makefile.rules. The patch below provides some important fixes for parallel builds and dependencies. It also adds some new features like the -local targets. For example, you can now build "all-local" to build the local directory without recursing into subdirectories. See the comments below for details of the change.

On Apr 4, 8:06 pm, heisenbug <ggr... at gmail.com> wrote: > On Apr 4, 7:51 pm, Török Edwin <edwinto... at gmail.com> wrote: > > > > > heisenbug wrote: > > > On Apr 3, 10:53 pm, Gabor Greif <ga... at mac.com> wrote: > > > ... > > > >>> 3) Make sure that make check and some reasonable subset of llvm-test > > >>>

Hello, I ran into a few problems when trying to build openssh 5.2p1 on IRIX 5.3. First one is new to 5.2p1: cc -I. -I. -I/usr/tgcware/include/openssl -I/usr/tgcware/include -DSSHDIR=\"/usr/tgcware/etc/ssh\" -D_PATH_SSH_PROGRAM=\"/usr/tgcware/bin/ssh\" -D_PATH_SSH_ASKPASS_DEFAULT=\"/usr/tgcware/libexec/ssh-askpass\"

On 11/24/2013 03:29 AM, Gene Cumm wrote: >> >> (Sorry for the top posting.) > > I just started examining this and find it odd that the core_udp_recv() > doesn't zalloc() its token while core_udp_send()/core_udp_sendto() do. > All three are a part of commit fe283b78 by Matt Fleming. Should this > be made into a zalloc() rather than pushing it into the stack?

On Apr 4, 7:51 pm, Török Edwin <edwinto... at gmail.com> wrote: > heisenbug wrote: > > On Apr 3, 10:53 pm, Gabor Greif <ga... at mac.com> wrote: > > ... > > >>> 3) Make sure that make check and some reasonable subset of llvm-test > >>> passes with this patch :) > > >> I have never run llvm-test in the past. Is it just checking it

heisenbug wrote: > On Apr 3, 10:53 pm, Gabor Greif <ga... at mac.com> wrote: > ... > > >>> 3) Make sure that make check and some reasonable subset of llvm-test >>> passes with this patch :) >>> >> I have never run llvm-test in the past. Is it just checking it out and >> following a readme? >> > > > After

On Tue, Nov 26, 2013 at 2:02 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 11/24/2013 03:29 AM, Gene Cumm wrote: >>> >>> (Sorry for the top posting.) >> >> I just started examining this and find it odd that the core_udp_recv() >> doesn't zalloc() its token while core_udp_send()/core_udp_sendto() do. >> All three are a part of commit