Thursday, June 3, 2004, 9:43:11 AM, you wrote:
>> > I just forced a build of the libraries. Approx 30 files failed with
>> > SIGSEGV errors and 15
>> > more would not assemble.
> [to Matthias] I would like to have an extract of the error
> messages, along with some of the sources that caused the errors if
That wasn't my post :) Actually, I for me the sdcc worked but not the
gpasm. There were hundreds of error like:
pic18f452.asm:112:Error Unknown opcode ".globl"
I think weather I have an old gpasm or there is an incompatibility.
>> I mananged to build the pic lib only under MS Windows with MPASM.
>> If you like I could send them to you. In the meantime I was looking in
>> the sources for this bug, but I cann't find one. I assume it is a
>> GPASM incompatibility.
> GPASM is made to be as compatible as possible with MPASM. To which
> bug are you refering? The one that has to do with PCLATU? If yes, this was
> not a bug but a warning of the pic16 port.
PS.: ... waiting for the new features ;)