Dear Coreboot Folks I see that this issues is still not resolved, can you guys give me some steps so that I can do those changes in my local copy And build libpayload.
Regards Pradish -----Original Message----- From: Pradish M P, ERS, HCLTech Sent: Monday, April 01, 2013 1:22 PM To: Paul Menzel; [email protected] Subject: RE: [coreboot] coreboot-libpayload 'size_t' conflicting type error Dear Paul and Coreboot Folks i have followed all the steps you have mention in this mail and still i am getting the same error. bpci/libpci.libpci.o In file included from include/libpayload.h:54:0, from libpci/libpci.c:30: include/x86/arch/types.h:56:23: error: conflicting types for 'size_t' /usr/lib/gcc/i686-linux-gnu/4.6.1/include/stddef.h:212:23: note: previous declaration of 'size_t' was here make: *** [build/libpci/libpci.libpci.o] Error 1 regards pradish _______________________________________ From: [email protected] [[email protected]] On Behalf Of Paul Menzel [[email protected]] Sent: Wednesday, March 27, 2013 3:02 PM To: [email protected] Subject: Re: [coreboot] coreboot-libpayload 'size_t' conflicting type error Dear Pradish, in my last message I asked you *not* to send any HTML messages! Additionally you did not reply to the list. Please use a decent mail client which has the option to reply to the list. (As a workaround you might use the reply to all feature. Am Mittwoch, den 27.03.2013, 13:08 +0530 schrieb Pradish MP: [...] > but i get new errors > > pradish@pradish-VirtualBox:~/coreboot/payloads/libpayload$ make > install build/libpayload-config.h build/config.h differ: byte 93, line 4 > CC libpci/libpci.libpci.o > AR build/libpci.a > CC arch/x86/main.libc.o > CC arch/x86/sysinfo.libc.o > CC arch/x86/timer.libc.o > CC arch/x86/coreboot.libc.o > CC arch/x86/util.libc.o > CC arch/x86/exec.libc.o > CC arch/x86/virtual.libc.o > CC arch/x86/string.libc.o > CC arch/x86/multiboot.libc.o > CC crypto/sha1.libc.o > CC libc/malloc.libc.o > CC libc/printf.libc.o > CC libc/console.libc.o > CC libc/string.libc.o > In file included from libc/string.c:35:0: > include/inttypes.h:250:2: error: unknown type name 'intmax_t' > include/inttypes.h:251:2: error: unknown type name 'intmax_t' > include/inttypes.h:255:1: error: unknown type name 'intmax_t' > include/inttypes.h:255:1: warning: parameter names (without types) in > function declaration [enabled by default] > include/inttypes.h:256:1: warning: parameter names (without types) in > function declaration [enabled by default] > include/inttypes.h:257:1: error: unknown type name 'intmax_t' > include/inttypes.h:258:1: error: unknown type name 'uintmax_t' > libc/string.c: In function 'strtoul': > libc/string.c:542:12: error: 'UINT32_MAX' undeclared (first use in > this function) > libc/string.c:542:12: note: each undeclared identifier is reported > only once for each function it appears in > make: *** [build/libc/string.libc.o] Error 1 > > how to resolve this one? Thanks to Stefan Reinauer these errors should be fixed with the following commit. commit c7b6d7db092cfd925f1fb6333e166a54663310e7 Author: Stefan Reinauer <[email protected]> Date: Mon Mar 25 15:03:41 2013 -0700 libpayload: Fix type issues There were a number of type issues in libpayload that sneaked in with 903f8e0. - size_t and ssize_t were conflicting with gcc builtins - some stdint types were used in libpayload but not defined in our stdint.h [...] Reviewed-on: http://review.coreboot.org/2903 Please do `git remote update` and `git rebase origin/master` to get the latest revision and everything should be fine. [...] Thanks, Paul ::DISCLAIMER:: ---------------------------------------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ---------------------------------------------------------------------------------------------------------------------------------------------------- -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
