Borut,
>Sorry for a lost day
No, that's a misunderstanding. All I wanted to say was that the testing cycle
consisted of going to the place with XP machine in the morning, spending maybe
10 minutes with compiling the patched version, then in the evening test it on
the W9x machine which I use for
Borut Razem wrote:
> Jan,
>
> thank you very much to track down the problem.
> I didn't remember that the path in argv[0] on Windows 9x is always upper
> case :-(
>
> I introduced a diagnostic message if SDAS_DIAG and / or SDLD_DIAG
> environment variables are set.
>
> Sorry for a lost day, but y
Jan,
thank you very much to track down the problem.
I didn't remember that the path in argv[0] on Windows 9x is always upper
case :-(
I introduced a diagnostic message if SDAS_DIAG and / or SDLD_DIAG
environment variables are set.
Sorry for a lost day, but you at least succeeded. I lost few se
Borut,
On a WXP machine, I've patched sdld.c to printf path and progname, compiled
with gcc under cygwin, and run it on the W98 (the two machines are physically
remote and this cycle takes me a whole day :-( ).
The result is:
C:\WEK\51\sbc\sdcc\snake>sdcc test.c -o test.ihx -V --verbose
sdcc:
Maarten,
I tried to install Win98 in a VirtualBox on Linux, but I had a lot of
troubles, so I gave up. (It worked well in VMware on WinXP. Maybe I
should install VMware on Linux...).
Can you please try to find out what is going wrong so that the following
errors are shown?
Unkown option -y ign
Interestingly enough, sdcc test.c -o test.ihx compiles OK.
JW
- Original Message ---
>... but fails to build test.c (the minimal program) - you apparently have
>built in a catch to the linker, haven't you ;-)
>
>C:\>sdcc --verbose test.c
>sdcc: Calling preprocessor...
>sdcc: Gen
... but fails to build test.c (the minimal program) - you apparently have built
in a catch to the linker, haven't you ;-)
C:\>sdcc --verbose test.c
sdcc: Calling preprocessor...
sdcc: Generating code...
sdcc: Calling assembler...
sdcc: Calling linker...
Assertion failed: str != NULL, file /home/
Installed flawlessly.
Thanks
Jan
- Original Message ---
>Can you try to install sdcc-20100207-5677-setup.exe and see if it
>uncompress correctly?
>On my machine is OK.
--
The Planet: dedicated and mana
C:\>sdcc -V test.c
+ C:\PROGRA~1\SDCC\BIN\SDCPP.EXE -nostdinc -Wall -obj-ext=.rel -DSDCC_MODEL_SMAL
L -DSDCC_FLOAT_REENT -DSDCC=297 -DSDCC_REVISION=5664 -DSDCC_mcs51 -D__mcs51 -isy
stem "C:\PROGRA~1\SDCC\BIN\..\include\mcs51" -isystem "C:\PROGRA~1\SDCC\BIN\..\i
nclude" "test.c"
+ C:\PROGRA~1\SDCC\
I updated the nsis installer to the latest version 2.46 and made an
other build.
Can you try to install sdcc-20100207-5677-setup.exe and see if it
uncompress correctly?
On my machine is OK.
Borut
Borut Razem wrote:
> Some strange things are happening: the installer was not changed for
> alon
Jan, can you please send me the result of sdcc -V?
From there we will see what is the command line for sdas and sdld.
Borut
Jan Waclawek wrote:
> OK, I think I spotted the problem.
>
> In sdld.c/sdld_init(), a target autodetection is performed, relying on
> argv[0] (passed from the caller, ma
Yes, I successfully installed sdcc-20100205-5672-setup.exe downloaded
from the snapshot builds web page.
In the meantime I also restarted the today's snapshot build: for some
reason the original build was not uploaded. So I propose to wait and
retry with the today's build.
Borut
Jan Waclawek
OK, I think I spotted the problem.
In sdld.c/sdld_init(), a target autodetection is performed, relying on argv[0]
(passed from the caller, main()). Internet said, that COMMAND.COM mangles
argv[0] - I don't know the exact details but I'd say it encloses it into
double-quotes) (this might be also
Some strange things are happening: the installer was not changed for
along time: the last update was 14.10.2009.
But I also noticed that the pictures on the installer pages are missing.
The today's build is done, but it also doesn't uncompress on my XP
running in VirtualBox.
I'll try to update
So, is this (the unexpected warnings) a Win98-specific problem?
Are there any substantial system calls involved in deciphering the capabilities
of the linker (which would lead to rejection of them)? That sounds strange.
And, also, is the installer problem Win98-specific?
So far, I had no proble
Jan and Borut,
I just tried on my old Win98 laptop and cannot complete
the installer either. I get the same error as Jan.
And if I instead use the zip-file which can be read ok
by 7-zip, I get the same warnings about -y, -Y, PSEG and
l_IRAM.
I don't have Visual C installed on it or any other
Borut,
In my previous post,
https://sourceforge.net/mailarchive/forum.php?thread_name=000f01caa77a%2455202860%240401a8c0%40pc&forum_name=sdcc-user
, I reported that I cannot *install* from sdcc-20100205-5672-setup.exe (I just
retried with a freshly downloaded
http://sdcc.sourceforge.net/snapsh
I tried it with the snapshot build sdcc-20100205-5672-setup.exe:
SDCC : mcs51/gbz80/z80/ds390/pic16/pic14/TININative/ds400/hc08 2.9.7
#5672 (Feb 5 2010) (MINGW32)
and it works. The .mem file is generated too.
Can you please confirm it?
Borut
Jan Waclawek wrote:
> (the subject slightly lies -
This one has consequences:
> Unkown option -y ignored
And, indeed, the .mem file is missing.
JW
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the
(the subject slightly lies - as I explained in my previous post, the latest
snapshot couldn't be installed)
Trying to run sdcc gives a couple of confusing warnings:
---
C:\>sdcc --version
SDCC : mcs51/gbz80/z80/ds390/pic16/pic14/TININative/ds400/hc08 2.9.7 #5664 (Jan
31 2010) (MINGW32)
C:\>sdc
20 matches
Mail list logo
