Re: [sdcc-devel] make silence

[Raphael N. <rn...@we...>]

Hi,

> And then it actually happened: this was lost in the messy output:

I understand that this is frustrating for you, but it compiles without
errors on my box. See below: Your gputils are too old. May I kindly
suggest you update you gputils installation and try again?
Alternatively, remove your gputils. Then none of the PIC libraries
should build by default and none of my library bugs will ever concern
you again. Seriously.

> Making all in libm
> Making all in libsdcc/regular
> Making all in libsdcc/enhanced
> _gptrget2.S:61:Error [103] syntax error

This is from the pic14 libsdcc stuff. moviw is probably the culprit,
should be present in recent gputils versions. (Works for me.)

> I'm beginning to get the feeling that we should disable
> pic14 and pic16 by default, because there were so much
> more errors. Shouldn't the SDCC source distribution
> compile out-of-the box with regular packages installed?

Yes, it should. If the prerequisites are fulfilled, it even does.


While we are at bashing our build system: On my Ubuntu box I get

../../../src/ds390/main.c: In function ‘_tininative_do_assemble’:
../../../src/ds390/main.c:1199: warning: implicit declaration of
function ‘sdcc_system’
In file included from /usr/include/c++/4.4/backward/hash_set:60,
                 from /usr/include/boost/graph/adjacency_list.hpp:25,
                 from /usr/include/boost/graph/graphviz.hpp:24,
                 from ../../../src/z80/../SDCCralloc.hpp:45,
                 from ../../../src/z80/ralloc2.cc:24:
/usr/include/c++/4.4/backward/backward_warning.h:28:2: warning:
#warning This file includes at least one deprecated or antiquated
header which may be removed without further notice at a future date.
Please use a non-deprecated interface with equivalent functionality
instead. For a listing of replacement headers and interfaces, consult
the file backward_warning.h. To disable this warning use
-Wno-deprecated.


Nobody concerned about that? The first one (sdcc_system) is relatively
new, the other one is present since Philipp introduced the
STL/STX/boost graph stuff.


> Here's the rest:
>
> Making all in debug
> Making all in libc
> Making all in libio
> libio18f23k22_a-dummy.asm:8:Error [132] Unknown
> processor.
> libio18f23k22_a-dummy.asm:17:Error [131] Processor type
> is undefined.

Relatively new processors require relatively new gputils to assemble and link.

> cp: cannot stat `pic16/*/crt0*.o': No such file or
> directory

Due to the abort-on-error above.

> [  CC   ] ==> pic16f720.o
> pic16f720.asm:12:Error [179] Unable to open file
> "p16f720.inc" - No such file or directory
> error: "pic16f720.o" is not a valid object file

Same story: 16f720 is not available in your gputils, hence *they* do
not find the .inc file.

> [  CC   ] ==> pic16f721.o
> pic16f721.asm:12:Error [179] Unable to open file
> "p16f721.inc" - No such file or directory
> error: "pic16f721.o" is not a valid object file

And again ...

> [  CC   ] ==> pic12f1822.o
> pic12f1822.asm:12:Error [179] Unable to open file
> "p12f1822.inc" - No such file or directory
> error: "pic12f1822.o" is not a valid object file

Oh, surprise: another one!

> [  CC   ] ==> pic12f1840.o
> pic12f1840.asm:12:Error [179] Unable to open file
> "p12f1840.inc" - No such file or directory
> error: "pic12f1840.o" is not a valid object file

Yawn ...


Either your gputils are really old or incompletely installed. To my
knowledge, there is nothing wrong with the PIC libraries at the
moment.


Anyway, have a nice Sunday.

Raphael