On 06/11/2010 16:49, Raphael Neider wrote:
>>
>> +++
>> checking for rmdir... rmdir
>> configure: error: gputils (gpasm, gplink, and gplib) are required but
>> not found.
>> Either install gputils or reconfigure with --disable-pic14-port and
>> --disable-pi
>> c
> +++
> checking for rmdir... rmdir
> configure: error: gputils (gpasm, gplink, and gplib) are required but
> not found.
> Either install gputils or reconfigure with --disable-pic14-port and
> --disable-pi
> c16-port.
> configure: error: ./configure failed fo
On 06/11/2010 10:46, Philipp Klaus Krause wrote:
>
> Am 06.11.2010 15:17, schrieb Claude Sylvain:
>> - It looks like something goes wrong with the z80 library files.
>> That problem was not there until SDCC V3.0.0 (was only appearing
>> on the following snapshots).
>> "crt0.s" an
Dear all,
After tuning some generic pointers to __data pointers the generated
program was broken in v3.0(win32). The same code compiled flawlessly
with v2.9(linux amd64).
Kind regards,
Alain Péteut
--
The Next 800 C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 06.11.2010 15:17, schrieb Claude Sylvain:
> - It looks like something goes wrong with the z80 library files.
>That problem was not there until SDCC V3.0.0 (was only appearing
>on the following snapshots).
>"crt0.s" and other files seems
On 06/11/2010 04:42, Philipp Klaus Krause wrote:
> Am 06.11.2010 03:55, schrieb Claude Sylvain:
>>
>> - When taking a look in the following source directory:
>> sdcc\device\lib\z80
>>
>> It seems that there is a lot of missing files !?
>>
>
> I've just build current svn. In svn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 06.11.2010 03:55, schrieb Claude Sylvain:
> - When taking a look in the following source directory:
> sdcc\device\lib\z80
>
>It seems that there is a lot of missing files !?
I've just build current svn. In svn there are the following fil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 06.11.2010 08:13, schrieb Lin Rongrong:
> This may not be a new problem. I have been using my own crt0.s/crt0.o since
> 2.6.0 five years ago.
> What worrys me about 3.0.0 are those new warnings.
Don't worry about the "z80instructionSize() failed
This may not be a new problem. I have been using my own crt0.s/crt0.o since
2.6.0 five years ago.
What worrys me about 3.0.0 are those new warnings.
Woody
http://palmmicro.com/woody/
- Original Message -
From: "Claude Sylvain"
To:
Sent: Saturday, November 06, 2010 10:55 AM
Subject: [
