You are not logged in.

KPilot & AvantGo

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

shock_ez

Beginner

  • "shock_ez" started this thread

Posts: 37

  • Send private message

1

Friday, February 6th 2004, 6:39pm

KPilot & AvantGo

Does anyone have suggestions for how to get KPilot working with an easy Conduit for AvantGo? I found this page http://reinhold.kainhofer.com/Linux/KPilot/ for Reinhold Kainhofer's conduit but following his instructions I can't seem to get it to work...is it because I updated using a SuSE rpm for kdepim instead of building from source? I did install the libmal as suggested.

TIA

tom

Beginner

Posts: 26

Location: Darmstadt, Germany

  • Send private message

2

Saturday, February 7th 2004, 12:29am

Hi,
did you install Malsync (http://www.tomw.org/malsync/)?
I think malsync is required when syncing with AvantGo when using pilot-link. But I'm not sure if it is required when uning KPilot.

Tom
---
There are only 10 types of people in the world:
Those who understand binary and those who don't.
---

shock_ez

Beginner

  • "shock_ez" started this thread

Posts: 37

  • Send private message

3

Saturday, February 7th 2004, 9:46pm

I figured out that I just needed to compile the kdepim package from source for it to pick up that I have libmal installed. However, I get this error when performing make (see below).

Note that during configure I set the prefix=/opt/kde3 because that's where SuSE installs KDE packages...

Any ideas? Thanks!

/opt/kde3/bin/dcopidlng ./kmailIface.h > kmailIface.kidl || ( rm -f kmailIface.kidl ; false )
/opt/kde3/bin/dcopidlng: line 1: kde-config: command not found
Can't open perl script "/dcopidlng/kalyptus": No such file or directory
make[3]: *** [kmailIface.kidl] Error 1
make[3]: Leaving directory `/home/Justin/Storage/Downloads/kdepim-3.2.0/kmail'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/Justin/Storage/Downloads/kdepim-3.2.0/kmail'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/Justin/Storage/Downloads/kdepim-3.2.0'
make: *** [all] Error 2

tom

Beginner

Posts: 26

Location: Darmstadt, Germany

  • Send private message

4

Sunday, February 8th 2004, 8:49am

Which KDE version are you using?

[code:1]
$ which kde-config
/opt/kde3/bin/kde-config
$ rpm -qf /opt/kde3/bin/kde-config
kdelibs3-3.2.0-2
[/code:1]
---
There are only 10 types of people in the world:
Those who understand binary and those who don't.
---

shock_ez

Beginner

  • "shock_ez" started this thread

Posts: 37

  • Send private message

5

Sunday, February 8th 2004, 10:44pm

Quoted

Original von tom

Which KDE version are you using?

[code:1]
$ which kde-config
/opt/kde3/bin/kde-config
$ rpm -qf /opt/kde3/bin/kde-config
kdelibs3-3.2.0-2
[/code:1]


I get the same output, but ONLY if I'm not in root or SU. In other words, if I run which kde-config I'll only get /opt/kde3/bin/kde-config if I'm in a terminal as my regular user. If I'm SU'd or using a root terminal, I get no output. Does that matter?

:(

I have the feeling that this may have to do with the fact that I installed all of the kde 3.2 packages from SuSE RPM's...maybe things weren't updated right or something?

tom

Beginner

Posts: 26

Location: Darmstadt, Germany

  • Send private message

6

Sunday, February 8th 2004, 11:08pm

Please have at your $PATH variable as root
PATH=$PATH:/opt/kde3/bin ./configure --prefix=/opt/kde3
should do it.

BTW: Why do you compile as root? Where's no need to do that!

Tom
---
There are only 10 types of people in the world:
Those who understand binary and those who don't.
---

shock_ez

Beginner

  • "shock_ez" started this thread

Posts: 37

  • Send private message

7

Sunday, February 8th 2004, 11:50pm

That seems to have worked...thanks so much!

I compiled as root because ... well I thought that's what you had to do... :oops:

I tried to run ./configure as a regular user and it told me permission was denied...so I just SU'd. Maybe my perms were messed up on that one directory, but I didn't really investigate...;)