Differences in building with gcc 3.4.6 versus gcc 4.4.0 ? - page 3 - General Discussion and Assistance - CHDK Forum

Differences in building with gcc 3.4.6 versus gcc 4.4.0 ?

  • 33 Replies
  • 26838 Views
Re: Differences in building with gcc 3.4.6 versus gcc 4.4.0 ?
« Reply #20 on: 23 / April / 2011, 23:16:50 »
Advertisements
http://chdk.setepontos.com/index.php?topic=2509.msg65366#msg65366
This was definitely not what I planned to spend 14 hours of my Saturday chasing but thank you so much reyalp for getting us all to a conclusion.   I built the latest and it all seems to work.  Now the patch file I had finished and submitted 12 hours ago is usable.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 14125
Re: Differences in building with gcc 3.4.6 versus gcc 4.4.0 ?
« Reply #21 on: 23 / April / 2011, 23:23:25 »
This was definitely not what I planned to spend 14 hours of my Saturday chasing but thank you so much reyalp for getting us all to a conclusion.
Hah, me neither, but that's how it goes. If we actually squished this one it's a good thing. Also made me look at the other readdir issues, which is good.

Quote
I built the latest and it all seems to work.
Did you confirm it works with both compilers ?
Don't forget what the H stands for.

Re: Differences in building with gcc 3.4.6 versus gcc 4.4.0 ?
« Reply #22 on: 23 / April / 2011, 23:32:24 »
Did you confirm it works with both compilers ?
Just gcc3.   I'll rebuild with gcc4 once I disconnect that from what I think is a RAW/DNG issue -- silly me making two changes at once.

Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 14125
Re: Differences in building with gcc 3.4.6 versus gcc 4.4.0 ?
« Reply #23 on: 23 / April / 2011, 23:36:37 »
Did you confirm it works with both compilers ?
Just gcc3.   I'll rebuild with gcc4 once I disconnect that from what I think is a RAW/DNG issue -- silly me making two changes at once.
You can also try the autobuild, which is gcc4.
Don't forget what the H stands for.

Re: Differences in building with gcc 3.4.6 versus gcc 4.4.0 ?
« Reply #24 on: 23 / April / 2011, 23:46:56 »
You can also try the autobuild, which is gcc4.
File browser issue gone when I compile with gcc3 or gcc4.   

No idea why I can't see previews in Play mode if I have RAW enabled.   Something new I hope but its late and my brain is fried.

Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 14125
Re: Differences in building with gcc 3.4.6 versus gcc 4.4.0 ?
« Reply #25 on: 24 / April / 2011, 00:03:52 »
No idea why I can't see previews in Play mode if I have RAW enabled.   Something new I hope but its late and my brain is fried.
The camera may get confused by files with the same number sharing certain combinations of extension and prefix. On both my cameras, a jpeg IMG_NNNN.JPG with a corresponding CRW_NNNN.CRW shows an extra icon.
Don't forget what the H stands for.

Re: Differences in building with gcc 3.4.6 versus gcc 4.4.0 ?
« Reply #26 on: 24 / April / 2011, 14:42:01 »
No idea why I can't see previews in Play mode if I have RAW enabled.   Something new I hope but its late and my brain is fried.
The camera may get confused by files with the same number sharing certain combinations of extension and prefix. On both my cameras, a jpeg IMG_NNNN.JPG with a corresponding CRW_NNNN.CRW shows an extra icon.

Okay - with a little sleep I've narrowed this down.  Using release 1154,  if I set things up to store my DNG files in their own folder, everything is fine.  However, if I select to have my DNG files stored in the same folder as their corresponding JPG files, then I get "no image" when I go to playback mode.  The files are on the card - the camera will just not display them.

If I patch 1154 with the CAM_DATE_FOLDER_NAMING patch that I posted yesterday,  this problem does not occur - everything seems to work fine.  DNG's are stored in the same folders as the JPG and I can scroll through the JPG in playback mode (i.e. no more "no image" problem).

http://chdk.setepontos.com/index.php?topic=650.msg65355#msg65355


Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Differences in building with gcc 3.4.6 versus gcc 4.4.0 ?
« Reply #27 on: 24 / April / 2011, 16:38:42 »
Perfectly illustrates why CHDK-Shell defaults to keeping dowloaded archives ... ;)
Okay - rub it in.  I was cursing the day I asked you to put in the function to delete old versions.  As one of my mentors once told me "Be careful what you ask for,  you might just get it.".
<snip>
Sorry, that was kind of insensitive. But I was not referring to the 'Remove old builds ...' function,
but to 'Archive Processing Mode' (also in SVN Options). If you still had that in the default mode,
i.e. 'Download/Unzip/Keep', you could have easily restored your original trunks by repeated
use of 'Unzip Archive ..' , because 'Remove old builds ...' only removes the trunkXXXX folders,
not the original zips (then again, one would probably set 'Archive Processing Mode' to
'Download/Unzip/Delete' when trying to minimise disk space consumption ....)

wim




Re: Differences in building with gcc 3.4.6 versus gcc 4.4.0 ?
« Reply #28 on: 25 / April / 2011, 12:16:37 »
that the structure is too small, is report earlier, use other compiler, only change the order of teh structure.it depend if after the struct is important data or not if it crash.

that the struct is too small is in IXus 1000 HS and S95.

http://chdk.setepontos.com/index.php?topic=5980.msg60700#msg60700

My guess is now, if a file have set some favourte or rating then dirent structure get larger.so Problem can happen on all Camera
« Last Edit: 25 / April / 2011, 12:19:06 by Bernd R »
Ixus 1000 HS

*

Offline reyalp

  • ******
  • 14125
Re: Differences in building with gcc 3.4.6 versus gcc 4.4.0 ?
« Reply #29 on: 25 / April / 2011, 12:26:33 »
that the structure is too small, is report earlier, use other compiler, only change the order of teh structure.it depend if after the struct is important data or not if it crash.
Did you *read* the thread ? changeset 1151
Don't forget what the H stands for.

 

Related Topics


SimplePortal © 2008-2014, SimplePortal