Bug Reports against Recent Builds -- Report bugs here - page 9 - CHDK Releases - CHDK Forum supplierdeeply

Bug Reports against Recent Builds -- Report bugs here

  • 281 Replies
  • 134120 Views
*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #80 on: 20 / December / 2008, 14:23:26 »
Advertisements
are you sure you updated to the latest revision?

*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #81 on: 20 / December / 2008, 14:30:53 »
Quote
are you sure you updated to the latest revision?

...and used the full version ?

wim

*

Offline hotvedt

  • ***
  • 106
  • A540/SX110IS/350D
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #82 on: 20 / December / 2008, 14:36:03 »
Yes, i just updated, and even deleted the config-file.

Edit: wait a minute, i may have done something stupid

-
Edit #2:
Yes, i must have done something really stupid. It turned out that i still had #648.
I think that the autobuild-server may have served me "a540-100b-0.8.10-648-full.zip" even when the link said a540-100b-0.8.10-649-full.zip".
Now the game shows in menu, and is working. Sorry for the trouble  :'(
« Last Edit: 20 / December / 2008, 14:51:32 by hotvedt »

*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #83 on: 20 / December / 2008, 15:57:29 »
no, the link is always telling you the version of the autobuild. but when you click on the link, you will get to the assembla trac version history, which sometimes is newer than the autobuild. autobuild is roughly 30 minutes behind svn.


*

Offline hotvedt

  • ***
  • 106
  • A540/SX110IS/350D
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #84 on: 20 / December / 2008, 16:12:42 »
Then, it's only the stupid-part left to blame  ;)

*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #85 on: 21 / December / 2008, 07:10:36 »
While compiling trunk #649 for A590, A620, A630 and ixus70
----------------------------------------------------------------------
Quote
(from gcc 4.3.2 error log)
gui.c: In function 'gui_redraw':
gui.c:2138: warning: suggest parentheses around comparison in operand of !=
Quote
gui.c:2138
        if (gui_mode != GUI_MODE_REVERSI && gui_mode != GUI_MODE_SOKOBAN && gui_mode != GUI_MODE_4WINS != GUI_MODE_MASTERMIND)

i suppose there's a '&& gui_mode' missing before the last '!=', no ?

--------------------------------------------------------------------------------------------------------------------------------------------

Also, with both GCC 3.4.6 & 4.3.2 i get:
Quote
(from either gcc error log, only on compiles for A620 & 630)
/bin/sh: line 5: stubs_auto.S: Permission denied
... so #649 does not build for A620 and 630


wim

edit: in my last compile before this, #645, these warnings/errors were not present.
« Last Edit: 21 / December / 2008, 07:18:16 by whim »

*

Offline fudgey

  • *****
  • 1705
  • a570is
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #86 on: 21 / December / 2008, 09:39:59 »
Quote
/bin/sh: line 5: stubs_auto.S: Permission denied
... so #649 does not build for A620 and 630

I had no problems with make batch-zip-complete from a clean complete copy of trunk 649 on gcc 3.4.6 (on Ubuntu), no firmware dumps in place. I have rw perms on all files.

*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #87 on: 21 / December / 2008, 10:13:42 »
@fudgey

i'm on WinXP, but i found the difference with my #645 source: somehow the entire #649 source gets unzipped
as read-only files - even though my CHDK Shell always uses the same command to unpack the DL'ed source.
This is on a FAT partition (so no chance for Winblows to mess with my access rights via ADS). Sigh.
Guess i'll have to add an attrib pass over unzipped source if this turns out to be caused by changed svn settings ...
(edit: done for next version)
Thanks again for the zebra stuff, BTW - great improvement (even before your latest mods, which i haven't tried yet)

wim 
« Last Edit: 21 / December / 2008, 10:40:34 by whim »


*

Offline fudgey

  • *****
  • 1705
  • a570is
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #88 on: 21 / December / 2008, 11:32:54 »
i'm on WinXP, but i found the difference with my #645 source: somehow the entire #649 source gets unzipped
as read-only files - even though my CHDK Shell always uses the same command to unpack the DL'ed source.
This is on a FAT partition (so no chance for Winblows to mess with my access rights via ADS). Sigh.
Guess i'll have to add an attrib pass over unzipped source if this turns out to be caused by changed svn settings ...
(edit: done for next version)
Thanks again for the zebra stuff, BTW - great improvement (even before your latest mods, which i haven't tried yet)

Maybe default setup changed in assembla's zipper? I get my trunk copies with "svn co 404 Not Found, not from a zip. I now tried assembla's zip too and indeed all files lack read and write permissions in there, that's not good at all!

As for zebra stuff, we have Ljl to thank for really, he did the original brainy hard work. My latest modification you'll want to disable if your camera has enough RAM for the one in trunk 649.

*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #89 on: 22 / December / 2008, 16:39:54 »
Quote
/bin/sh: line 5: stubs_auto.S: Permission denied
... so #649 does not build for A620 and 630

I had no problems with make batch-zip-complete from a clean complete copy of trunk 649 on gcc 3.4.6 (on Ubuntu), no firmware dumps in place. I have rw perms on all files.

i sometimes have this on windows, (in svn working copy). not on the exact same file, but definitly a "permission" denied message. usually a "gmake clean" fixes it, though most times this error is created after a "gmake clean && gmake fir". strange.

 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal