This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: m68k: conflicting types for 'read'
- From: Anders Montonen <Anders dot Montonen at iki dot fi>
- To: Joel Sherrill <joel dot sherrill at oarcorp dot com>, newlib at sourceware dot org
- Date: Sun, 3 Aug 2014 18:22:48 +0300
- Subject: Re: m68k: conflicting types for 'read'
- Authentication-results: sourceware.org; auth=none
- References: <13F98E57-4B6C-46F1-8EB5-6B393E5915AF at iki dot fi> <0c6d1b53-2db9-421c-b24c-05ae021b490d at email dot android dot com>
On Aug 3, 2014, at 17:08, Joel Sherrill wrote:
> On August 3, 2014 5:48:24 AM CDT, Anders Montonen <Anders.Montonen@iki.fi> wrote:
>> Hi,
>>
>> When trying to compile newlib 2.1.0 for a m68k-unknown-elf target using
>> GCC 4.9.1 (same behaviour with GCC 4.8.3), the build fails with an
>> error about conflicting types for the read function. Newlib 2.0.0
>> compiles without errors.
>>
>> /Users/anders/work/toolchain/gcc/4.9.1/m68k-elf/./gcc/xgcc
>> -B/Users/anders/work/toolchain/gcc/4.9.1/m68k-elf/./gcc/ -nostdinc
>> -B/Users/anders/work/toolchain/gcc/4.9.1/m68k-elf/m68k-elf/newlib/
>> -isystem
>> /Users/anders/work/toolchain/gcc/4.9.1/m68k-elf/m68k-elf/newlib/targ-include
>> -isystem
>> /Users/anders/work/toolchain/gcc/4.9.1/gcc-4.9.1/newlib/libc/include
>> -B/Users/anders/work/toolchain/gcc/4.9.1/m68k-elf/m68k-elf/libgloss/m68k
>> -L/Users/anders/work/toolchain/gcc/4.9.1/m68k-elf/m68k-elf/libgloss/libnosys
>> -L/Users/anders/work/toolchain/gcc/4.9.1/gcc-4.9.1/libgloss/m68k
>> -B/Users/anders/local/m68k-elf/bin/ -B/Users/anders/local/m68k-elf/lib/
>> -isystem /Users/anders/local/m68k-elf/include -isystem
>> /Users/anders/local/m68k-elf/sys-include -g -O2 -g -O2 -mcpu=51qe
>> -DHOSTED=1 -I. -I../../../../../gcc-4.9.1/libgloss/m68k/.. -c
>> ../../../../../gcc-4.9.1/libgloss/m68k/io-read.c -o hosted-read.o
>> ../../../../../gcc-4.9.1/libgloss/m68k/io-read.c:33:9: error:
>> conflicting types for 'read'
>> ssize_t read (int fd, void *buf, size_t count)
>> ^
>> In file included from
>> /Users/anders/work/toolchain/gcc/4.9.1/gcc-4.9.1/newlib/libc/include/sys/unistd.h:8:0,
>> from
>> /Users/anders/work/toolchain/gcc/4.9.1/gcc-4.9.1/newlib/libc/include/unistd.h:4,
>> from ../../../../../gcc-4.9.1/libgloss/m68k/io-read.c:17:
>> /Users/anders/work/toolchain/gcc/4.9.1/gcc-4.9.1/newlib/libc/include/sys/unistd.h:144:25:
>> note: previous declaration of 'read' was here
>> _READ_WRITE_RETURN_TYPE _EXFUN(read, (int __fd, void *__buf, size_t
>> __nbyte ));
>
> What is _READ_WRITE_RETURN_TYPE defined to for this target? I recall that ssize_t is correct because -1 can be returned.
If I'm reading the sources right, it falls under the default 'int' case in sys/config.h. This has not changed between 2.0.0 and 2.1.0. However, I suspect that in sys/_types.h, _ssize_t is now typedef'd from GCC's __SIZE_TYPE__ instead of int as before.
Regards,
Anders Montonen