Compile error with R69

[GoogleCodeExporter]

Please fill out the following information:

Problem Disc: na
--------------------------------------------------
Disc Region: na
Wii Region: E(urope)
cIOS Version: Wiigator r7

Which SoftChip revision are you using? r69
--------------------------------------------------

Please describe the issue you're having
Compile error:
> "make" 
main.cpp
SoftChip.cpp
DIP.cpp
cIOS.cpp
Logger.cpp
Input.cpp
Configuration.cpp
Console.cpp
Storage.cpp
/loader/source/Storage/Storage.cpp: In member function 'void
Storage::Release_FAT()':
/loader/source/Storage/Storage.cpp:73: error: cannot convert 'const char*'
to 'PARTITION_INTERFACE' for argument '1' to 'bool
fatUnmount(PARTITION_INTERFACE)'
make[1]: *** [Storage.o] Error 1
"make": *** [build] Error 2
--------------------------------------------------

Please provide any additional information below.
--------------------------------------------------

Before updating softchip source to R69 also libogc and libfat was updated
via script to latest version

Original issue reported on code.google.com by girottim...@googlemail.com on 11 Dec 2008 at 8:51

[GoogleCodeExporter]

Via script? Please use the devkitPro updater. You have a wrong libfat version.

Original comment by luccax@gmail.com on 11 Dec 2008 at 11:50

[GoogleCodeExporter]

For issue 23 (FAT problem) it was neccessary in the past to get the 
latest/actual
libogc and libfat version via GIT (as described here:
http://wiki.softchip-mod.com/index.php/Windows_Build_Guide). Therefore I 
created a
batch file which simply calls all commands that are mentioned in this guide and
builds softchip afterwards => that's what I meant with 'script'). If I update 
now
libogc and libfat as desribed in the guide I get the compile error). If I use 
the
latest devkitPro updater (1.4.8) to reinstall/update devkitPro then I can 
compile
softchip without problems as long as I not updated the libs via GIT again.
So I recommend to remove this instructions to update libogc and libfat from the 
guide
since these steps obviously causes the problem.

Original comment by girottim...@googlemail.com on 11 Dec 2008 at 1:52

[GoogleCodeExporter]

It's already changed in the Windows Build Guide (since r69)...

Original comment by luccax@gmail.com on 11 Dec 2008 at 4:05

• Changed state: NonIssue