There is a ftbfs on armel bug for postler: https://bugs.launchpad.net/ubuntu/+source/postler/+bug/791319
Attached test compiles fine on amd64 but fails on armel:
20:16 hrw@malenstwo:postler-0.1.1$ gcc _build_/.conf_check_0/test.c _build_/.conf_check_0/test.c: In function ‘main’: _build_/.conf_check_0/test.c:5:1: error: incompatible type for argument 3 of ‘vasprintf’ /usr/include/stdio.h:396:12: note: expected ‘__gnuc_va_list’ but argument is of type ‘char *’
Can someone explain me why this happens?
Ubuntu armel and armhf cross compilers, CSL 2011.03-42 have same problem.
On czw, 2011-06-16 at 20:31 +0200, Marcin Juszkiewicz wrote:
There is a ftbfs on armel bug for postler: https://bugs.launchpad.net/ubuntu/+source/postler/+bug/791319
Attached test compiles fine on amd64 but fails on armel:
20:16 hrw@malenstwo:postler-0.1.1$ gcc _build_/.conf_check_0/test.c _build_/.conf_check_0/test.c: In function ‘main’: _build_/.conf_check_0/test.c:5:1: error: incompatible type for argument 3 of ‘vasprintf’ /usr/include/stdio.h:396:12: note: expected ‘__gnuc_va_list’ but argument is of type ‘char *’
Can someone explain me why this happens?
Ubuntu armel and armhf cross compilers, CSL 2011.03-42 have same problem.
Compiled fine with gcc 4.3 from Poky toolchain. Same with Emdebian gcc-4.3 cross compiler.
On 16 June 2011 19:37, Marcin Juszkiewicz marcin.juszkiewicz@linaro.org wrote:
On czw, 2011-06-16 at 20:31 +0200, Marcin Juszkiewicz wrote:
There is a ftbfs on armel bug for postler: https://bugs.launchpad.net/ubuntu/+source/postler/+bug/791319
Attached test compiles fine on amd64 but fails on armel:
20:16 hrw@malenstwo:postler-0.1.1$ gcc _build_/.conf_check_0/test.c _build_/.conf_check_0/test.c: In function ‘main’: _build_/.conf_check_0/test.c:5:1: error: incompatible type for argument 3 of ‘vasprintf’ /usr/include/stdio.h:396:12: note: expected ‘__gnuc_va_list’ but argument is of type ‘char *’
Can someone explain me why this happens?
Ubuntu armel and armhf cross compilers, CSL 2011.03-42 have same problem.
Compiled fine with gcc 4.3 from Poky toolchain. Same with Emdebian gcc-4.3 cross compiler.
Looks more to me like the old compilers are the ones with the problems and the new one is correctly throwing an error - it's supposed to have a va_list there - why would it take a string?
Dave
On czw, 2011-06-16 at 19:48 +0100, David Gilbert wrote:
Ubuntu armel and armhf cross compilers, CSL 2011.03-42 have same problem.
Compiled fine with gcc 4.3 from Poky toolchain. Same with Emdebian gcc-4.3 cross compiler.
Looks more to me like the old compilers are the ones with the problems and the new one is correctly throwing an error - it's supposed to have a va_list there - why would it take a string?
OK, but why it compiles fine on amd64/i386/powerpc?
On Fri, Jun 17, 2011 at 7:11 AM, Marcin Juszkiewicz marcin.juszkiewicz@linaro.org wrote:
On czw, 2011-06-16 at 19:48 +0100, David Gilbert wrote:
Ubuntu armel and armhf cross compilers, CSL 2011.03-42 have same problem.
Compiled fine with gcc 4.3 from Poky toolchain. Same with Emdebian gcc-4.3 cross compiler.
Looks more to me like the old compilers are the ones with the problems and the new one is correctly throwing an error - it's supposed to have a va_list there - why would it take a string?
OK, but why it compiles fine on amd64/i386/powerpc?
(begin randon statement without investigation)
On many architectures such as i386 va_list is a void * but on some it's a struct. Perhaps ARM uses a struct?
-- Michael
On 17 June 2011 00:30, Michael Hope michael.hope@linaro.org wrote:
On Fri, Jun 17, 2011 at 7:11 AM, Marcin Juszkiewicz marcin.juszkiewicz@linaro.org wrote:
On czw, 2011-06-16 at 19:48 +0100, David Gilbert wrote:
Ubuntu armel and armhf cross compilers, CSL 2011.03-42 have same problem.
Compiled fine with gcc 4.3 from Poky toolchain. Same with Emdebian gcc-4.3 cross compiler.
Looks more to me like the old compilers are the ones with the problems and the new one is correctly throwing an error - it's supposed to have a va_list there - why would it take a string?
OK, but why it compiles fine on amd64/i386/powerpc?
(begin randon statement without investigation)
On many architectures such as i386 va_list is a void * but on some it's a struct. Perhaps ARM uses a struct?
According to the AAPCS va_list is defined to be a struct .
struct __va_list { void *ap; }
There is no option but to fix the offending code here.
cheers Ramana
-- Michael
linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
linaro-toolchain@lists.linaro.org
-
David Gilbert -
Marcin Juszkiewicz -
Michael Hope -
Ramana Radhakrishnan