llvm dev - Mar 2005 - [LLVMdev] GCC 3.4.1 and conflicting types for 'malloc' (2)

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:
> > http://llvm.cs.uiuc.edu/testresults/SparcV9/2004-12-07.html
> 
> Yup, this patch should fix it:
>
http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041213/022366.html
> 
> -Chris
> 
> 
> > --- 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 'malloc'
> >>> /homes/myuser/LLVM/llvmobj/../llvmsrc/utils/Burg/zalloc.c:9:
error: conflictin
> >>> g types for 'malloc'
> >>> gmake[2]: ***
[/homes/myuser/LLVM/llvmobj/utils/Burg/Release/zalloc.o] Error 1
> >>> gmake[2]: Leaving directory
`/homes/myuser/LLVM/llvmobj/utils/Burg'
> >>> gmake[1]: *** [all] Error 1
> >>> gmake[1]: Leaving directory
`/homes/myuser/LLVM/llvmobj/utils'
> >>> =======================> >>>
> >>> Any help on this will be greatly appreciated
> >>
> >> Ok, that is very wierd: line 9 is: fatal(const char *name, int
line)
> >>
> >> Are you using an up-to-date check out from CVS or LLVM 1.4?  Can
you send
> >> the output of "make VERBOSE=1" in that directory?
> >>
> >> -Chris
> >>
> >> --
> >> http://nondot.org/sabre/
> >> http://llvm.cs.uiuc.edu/
> >>
> >> _______________________________________________
> >> LLVM Developers mailing list
> >> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> >> http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev
> >>
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam protection around
> > http://mail.yahoo.com
> >
> > _______________________________________________
> > LLVM Developers mailing list
> > LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> > http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev
> >
> 
> -Chris
> 
> -- 
> http://nondot.org/sabre/
> http://llvm.cs.uiuc.edu/
> 
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev
> 

		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/

On Sat, 12 Mar 2005, xavier wrote:
> 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?
zalloc is part of Burg, which is used by the Sparc backend.  I strongly 
suggest adding '#include <stdlib.h>' to that file as well.

-Chris
> --- 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:
>>> http://llvm.cs.uiuc.edu/testresults/SparcV9/2004-12-07.html
>>
>> Yup, this patch should fix it:
>>
http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041213/022366.html
>>
>> -Chris
>>
>>
>>> --- 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 'malloc'
>>>>>
/homes/myuser/LLVM/llvmobj/../llvmsrc/utils/Burg/zalloc.c:9: error: conflictin
>>>>> g types for 'malloc'
>>>>> gmake[2]: ***
[/homes/myuser/LLVM/llvmobj/utils/Burg/Release/zalloc.o] Error 1
>>>>> gmake[2]: Leaving directory
`/homes/myuser/LLVM/llvmobj/utils/Burg'
>>>>> gmake[1]: *** [all] Error 1
>>>>> gmake[1]: Leaving directory
`/homes/myuser/LLVM/llvmobj/utils'
>>>>> =======================>>>>>
>>>>> Any help on this will be greatly appreciated
>>>>
>>>> Ok, that is very wierd: line 9 is: fatal(const char *name, int
line)
>>>>
>>>> Are you using an up-to-date check out from CVS or LLVM 1.4? 
Can you send
>>>> the output of "make VERBOSE=1" in that directory?
>>>>
>>>> -Chris
>>>>
>>>> --
>>>> http://nondot.org/sabre/
>>>> http://llvm.cs.uiuc.edu/
>>>>
>>>> _______________________________________________
>>>> LLVM Developers mailing list
>>>> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>>>> http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev
>>>>
>>>
>>> __________________________________________________
>>> Do You Yahoo!?
>>> Tired of spam?  Yahoo! Mail has the best spam protection around
>>> http://mail.yahoo.com
>>>
>>> _______________________________________________
>>> LLVM Developers mailing list
>>> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>>> http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev
>>>
>>
>> -Chris
>>
>> --
>> http://nondot.org/sabre/
>> http://llvm.cs.uiuc.edu/
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>> http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev
>>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Small Business - Try our new resources site!
> http://smallbusiness.yahoo.com/resources/
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev
>
-Chris

-- 
http://nondot.org/sabre/
http://llvm.cs.uiuc.edu/