Re: Krusader for OS X Intel
Catalin Hritcu
> I tried using Fink (per http://hritcu.wordpress.com/2006/08/10/krusader-on-intel-mac/), but the
> build of 'bundle-kde-ssl' failed.
>
This is definitely not a Krusader problem per-se and the instructions
I gave there worked for me as well as others. Can you give more
details about the error you get, maybe some log etc.
Catalin
PS. I was getting "An error was encountered while trying to post,
please try again later." for some minutes before I gave up and posted
this from gmail.
Frank Schoolmeesters
Hi Catalin,
Can i use the instructions of your website
http://hritcu.wordpress.com/2006/08/10/krusader-on-intel-mac/
to update the Krusader handbook?
http://krusader.sourceforge.net/handbook/mac-port.html
The reason that the mac-port info is not up to date is that i don't
have a mac ... , so i can't test it. The other thing is that the
feedback about the mac port of Krusader is very low.
If your updated krusader.info and krusader.patch are needed, than it
would be nice to include this information into the Krusader source.
btw. Does krusader-1.80.0-beta2 compile on (intel)-mac?
It would be nice to send us a info file for 1.80.0 so that it will be
available in the stable release.
btw. i have sended this mail in CC to Bodo Tasche, he maintains the
Krusader mac port and i suppose he still does.
thanks and bye,
Frank
Catalin Hritcu
> Can i use the instructions of your website
> http://hritcu.wordpress.com/2006/08/10/krusader-on-intel-mac/
> to update the Krusader handbook?
> http://krusader.sourceforge.net/handbook/mac-port.html
>
As long as someone can test that they still work, sure. I will also
test again now (still updating fink will take a while for me ... 232
updates for packages), but it would be better if we can try it on more
than one machine.
>
> The reason that the mac-port info is not up to date is that i don't
> have a mac ... , so i can't test it. The other thing is that the
> feedback about the mac port of Krusader is very low.
>
I was also put of my this (actually now i'm using muCommander because
it's better supported on the mac). Still, I would really love to see
Krusader being easy to install on a mac.
> If your updated krusader.info and krusader.patch are needed, than it
> would be nice to include this information into the Krusader source.
>
I looked at the patch now. I don't really remember what it was
supposed to do. I don't even remember if it's made by me. Anyway, I
will try to remember :)
> btw. Does krusader-1.80.0-beta2 compile on (intel)-mac?
>
Don't know. I will also give this a try then.
> It would be nice to send us a info file for 1.80.0 so that it will be
> available in the stable release.
>
Sure, this would be great. I will try.
Regards,
Catalin
Catalin Hritcu
On 5/2/07, Catalin Hritcu <catalin...@gmail.com> wrote:
> Hi Frank,
>
> > Can i use the instructions of your website
> > http://hritcu.wordpress.com/2006/08/10/krusader-on-intel-mac/
> > to update the Krusader handbook?
> > http://krusader.sourceforge.net/handbook/mac-port.html
> >
> As long as someone can test that they still work, sure. I will also
> test again now (still updating fink will take a while for me ... 232
> updates for packages), but it would be better if we can try it on more
> than one machine.
>
> >
> > The reason that the mac-port info is not up to date is that i don't
> > have a mac ... , so i can't test it. The other thing is that the
> > feedback about the mac port of Krusader is very low.
> >
> I was also put of my this (actually now i'm using muCommander because
> it's better supported on the mac). Still, I would really love to see
> Krusader being easy to install on a mac.
>
> > If your updated krusader.info and krusader.patch are needed, than it
> > would be nice to include this information into the Krusader source.
> >
> I looked at the patch now. I don't really remember what it was
> supposed to do. I don't even remember if it's made by me. Anyway, I
> will try to remember :)
>
OK. Now I know. Without it I was getting the following error on make
(the error still persists on krusader-1.80.0-beta2 and my patch still
seems to fix it):
Making all in radialMap
/sw/lib/qt3/bin/moc ./widget.h -o widget.moc
if g++ -DHAVE_CONFIG_H -I. -I. -I../../..
-I../../../krusader/DiskUsage/filelightParts -I/sw/include
-I/sw/lib/qt3/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT
-D_LARGEFILE64_SOURCE -DKDE_NO_COMPAT -DQT_NO_ASCII_CAST
-Wno-long-long -Wundef -Wall -W -Wpointer-arith -O2
-Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -MT
widget.o -MD -MP -MF ".deps/widget.Tpo" -c -o widget.o widget.cpp; \
then mv -f ".deps/widget.Tpo" ".deps/widget.Po"; else rm -f
".deps/widget.Tpo"; exit 1; fi
widget.cpp: In member function 'void RadialMap::Widget::zoomIn()':
widget.cpp:175: error: 'Config' has not been declared
widget.cpp:175: error: 'defaultRingDepth' was not declared in this scope
widget.cpp: In member function 'void RadialMap::Widget::zoomOut()':
widget.cpp:187: error: 'Config' has not been declared
widget.cpp:187: error: 'defaultRingDepth' was not declared in this scope
widget.cpp:188: error: 'Config' has not been declared
make[4]: *** [widget.o] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
> > btw. Does krusader-1.80.0-beta2 compile on (intel)-mac?
> >
> Don't know. I will also give this a try then.
>
After patching I still get this error:
/sw/lib/qt3/bin/moc ./normal_vfs.h -o normal_vfs.moc
if g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I/sw/include
-I/sw/lib/qt3/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT
-D_LARGEFILE64_SOURCE -DKDE_NO_COMPAT -DQT_NO_ASCII_CAST
-Wno-long-long -Wundef -Wall -W -Wpointer-arith -O2
-Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -MT
normal_vfs.o -MD -MP -MF ".deps/normal_vfs.Tpo" -c -o normal_vfs.o
normal_vfs.cpp; \
then mv -f ".deps/normal_vfs.Tpo" ".deps/normal_vfs.Po"; else rm -f
".deps/normal_vfs.Tpo"; exit 1; fi
normal_vfs.cpp:286:5: warning: "HAVE_NON_POSIX_ACL_EXTENSIONS" is not defined
normal_vfs.cpp:293:5: warning: "HAVE_NON_POSIX_ACL_EXTENSIONS" is not defined
normal_vfs.cpp:308:5: warning: "HAVE_NON_POSIX_ACL_EXTENSIONS" is not defined
normal_vfs.cpp: In static member function 'static QString
normal_vfs::getACL(const QString&, int)':
normal_vfs.cpp:304: error: invalid conversion from 'int' to 'acl_type_t'
normal_vfs.cpp:304: error: initializing argument 2 of '_acl*
acl_get_file(const char*, acl_type_t)'
normal_vfs.cpp:316: error: 'ACL_USER_OBJ' was not declared in this scope
normal_vfs.cpp:317: error: 'ACL_GROUP_OBJ' was not declared in this scope
normal_vfs.cpp:318: error: 'ACL_OTHER' was not declared in this scope
make[3]: *** [normal_vfs.o] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Does any of you have a clue about what could cause this ?
Catalin Hritcu
Probably this causes it
http://groups.google.com/group/krusader-devel/browse_frm/thread/c26f98eb0dfc62bb/0d4e147acf8a3a2f?#0d4e147acf8a3a2f
Anyway, adding the "--without-acl" configure flag fixed it for now.
Krusader 1.80.0-beta2 compiled, installed and works fine on my machine
(screenshot attached)
Catalin Hritcu
http://www.ps.uni-sb.de/~hritcu/download/krusader-1.80.0-beta2.info
and the instructions here:
http://hritcu.wordpress.com/2006/08/10/krusader-on-intel-mac/
Is there anyone reading who can test this ?
Thanks,
Catalin
Frank Schoolmeesters
Thanks for the testing!
I you lanch this message on a fink/mac website/forum/mailinglist/...
, you will probably get more responce and users who will test this i
guess.
Thanks and bye,
Frank
Frank Schoolmeesters
>
> > Can i use the instructions of your website
> > http://hritcu.wordpress.com/2006/08/10/krusader-on-intel-mac/
> > to update the Krusader handbook?
> > http://krusader.sourceforge.net/handbook/mac-port.html
> >
> As long as someone can test that they still work, sure. I will also
> test again now (still updating fink will take a while for me ... 232
> updates for packages), but it would be better if we can try it on more
> than one machine.
Just wondering, do you need to compile KDE 3.5 ?
and if yes, why there are no fresh KDE binaries provided by fink?
So it's more easy to install.
I hope that KDE4 will open new doors (more easy to use and install)
for the Krusader Mac port btw.
thanks and bye,
Frank
Catalin Hritcu
On 5/3/07, Frank Schoolmeesters <frank.scho...@gmail.com> wrote:
> On 5/2/07, Catalin Hritcu <catalin...@gmail.com> wrote:
> > Hi Frank,
> >
> > > Can i use the instructions of your website
> > > http://hritcu.wordpress.com/2006/08/10/krusader-on-intel-mac/
> > > to update the Krusader handbook?
> > > http://krusader.sourceforge.net/handbook/mac-port.html
> > >
> > As long as someone can test that they still work, sure. I will also
> > test again now (still updating fink will take a while for me ... 232
> > updates for packages), but it would be better if we can try it on more
> > than one machine.
> ....
>
> Just wondering, do you need to compile KDE 3.5 ?
Yes.
> and if yes, why there are no fresh KDE binaries provided by fink?
> So it's more easy to install.
Because the fink packages for KDE 3.5 are considered unstable:
http://pdb.finkproject.org/pdb/package.php/bundle-kde
(don't even know if there ever was a stable version, I think not)
> I hope that KDE4 will open new doors (more easy to use and install)
> for the Krusader Mac port btw.
>
I also hope so, but I'm afraid it might take a while until that happens.
Regards,
Catalin
Frank Schoolmeesters
Hi,
It's a pitty that fink doesn't provide kde beta binaries, compiling
kde(libs) takes a while.
It would be nice if Krusader is added to the KDE fink packages list
(more exposure, users, feedback, ...)
http://pdb.finkproject.org/pdb/section.php/kde
Can this be done?
btw. good luck with the help call on the fink-users mailing-list
http://www.finkproject.org/lists/index.php?phpLang=en
http://thread.gmane.org/gmane.os.macosx.fink.user/23587
thanks a lot and bye,
Frank