Re: [avr-libc-dev] Inclusion of far pointer library (patch #6352) broke avr-libc build

[Jan Waclawek]

This comes from my tweaks, not from Carlos.


That's my fault and shows clearly how unexperienced I am.
I believe there should be no issue with simply removing the #error?

Jan Waclawek

On Sun, 13 Jun 2010 15:08:32 +0200
Joerg Wunsch <address@hidden> wrote:

> gmake[5]: Entering directory `/home/joerg/src/avr-libc/avr/lib/avr2'
>  cd ../../.. && /usr/local/bin/bash /home/joerg/src/avr-libc/missing --run 
> automake-1.10 --foreign  avr/lib/avr2/Makefile
> avr-gcc -DHAVE_CONFIG_H -I. -I../../..  -I../../../common -I../../../include 
> -I../../../include  -g -Wall -W -Wstrict-prototypes -mmcu=avr2 
> -D__COMPILING_AVR_LIBC__ -mcall-prologues -Os  -MT dtostre.o -MD -MP -MF 
> .deps/dtostre.Tpo -c -o dtostre.o ../../../libc/stdlib/dtostre.c
> In file included from ../../../libc/stdlib/dtostre.c:32:
> ../../../include/avr/pgmspace.h:1008:4: error: #error "No pgm_seg support for 
> ATmega103."
> gmake[5]: *** [dtostre.o] Error 1
> 
> It's fine if the far pointer library simply is not available for an
> ATmega103, but it's not acceptable that <avr/pgmspace.h> throws a
> compile-time error for *any* invocation when being compiled for an
> ATmega103.  It's not even acceptable to throw a warning; if there's no
> other method, the far pointer library has to use its own header file
> rather than sharing <avr/pgmspace.h> with the standard _P functions
> (which then also requires itso own documentation group, or at least
> other documentation tweaks).
> 
> -- 
> cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL
> 
> http://www.sax.de/~joerg/                        NIC: JW11-RIPE
> Never trust an operating system you don't have sources for. ;-)
> 
> _______________________________________________
> AVR-libc-dev mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/avr-libc-dev