PPC vs Intel apps and Kernel Headers

[Bjorn van der Meer]

Hi Ed,
Yes, you=B4re absolutely right. I have just talked to one other person on=20
#yellowdog, his work-around is to run OSX inside Mac-on-Linux and run a VPN=
 client
on that.

Looks like using freeswan is the only hope. Judging from compatibility lists
like the one on
http://www.freeswan.org/freeswan_trees/freeswan-1.5/doc/compatibility.html#=
Cisco
it could possibly work, probably using the user supported "superfreeswan" s=
ources
with patches.

There is also a installation hint at=20
http://www.freeswan.org/freeswan_trees/freeswan-1.5/doc/compatibility.html#=
yellowdog
, albeit for a much older YDL.

I am trying myself now with a "superfreeswan" source package:

ftp://tis.foobar.fi/tis/super-freeswan-1.99.8-2foo.src.rpm

, but I am apparently out of my league, knowledge-wise, so don=B4t hold you=
r breath.

Once again, if someone has succesfully done this....I=B4d be elated to hear=
 from you.

Cheers, Bj=F6rn.


On Sun, 12 Oct 2003 12:40:47 -0700
Ed McKnight <edward.mcknight@sun.com> wrote:

> My experioence with the linux Cisco clients for VPN is that you are=20
> building kernel modules on your local machine: fine; then you're linking=
=20
> with precompiled libraries provided by Cisco: not fine, because they=20
> provide libs only for x86.
>=20
> If you can make this work somehow I'd like to hear about it; I don't see=
=20
> how unless you can get the lib source or get someone at Cisco to turn=20
> the crank on a linux PPC machine...
>=20
> I use their clients on x86 linux and Mac OSX, but no joy on linux ppc.
>=20
> --emk
>=20
>=20
> Bjorn van der Meer wrote:
> >=20
> >>Thanks,=20
> >>=20
> >>I thought I'd installed this rpm, but obviously I never did
> >>successfully.
> >>
> >>Now I have and got a /usr/src/linux-2.4 link and a
> >>/usr/src/linux-2.4.20-8d directory.
> >>
> >>I'm trying to install a Cisco VPN client.  It allows for the creation of
> >>a new driver.
> >>This was the reason for needing kernel source and headers.
> >>
> >>I attempted to create the new driver and got lines and lines of output
> >>that began with this:
> >>
> >>'
> >>In file included from /usr/include/linux/fs.h:23,
> >>                 from /usr/include/linux/capability.h:17,
> >>                 from /usr/include/linux/binfmts.h:5,
> >>                 from /usr/include/linux/sched.h:9,
> >=20
> > *snip*
> >=20
> >=20
> >>It goes on and on.
> >>The last two lines are:
> >>ld: libdriver.so: Relocations in generic ELF (EM: 3)
> >>libdriver.so: could not read symbols: File in wrong format
> >>
> >>This client was targeted for "Intel x86" platforms, but I had hopes that
> >>the driver configuration script could leverage the PPC assembler.
> >>Does the output above suggest that this is a hopeless cause on a PPC
> >>system?
> >>
> >>Cisco does provide a client for OS X, but I have no intention of
> >>installing that on this Powerbook G3.
> >>
> >>John Van Hoorn
> >>
> >>On Thu, 2003-09-04 at 09:42, Jann R=F6der wrote:
> >>
> >>>There is a package called kernel-source-2.4.20-8d.rpm . It can be found
> >>>on CD 2, or you simply do a "yum install kernel-source" . Usually you=
=20
> >>>can compile any linux application on YDL.
> >>>
> >>>Jann
> >>
> >>
> >=20
> > Hello John,
> >=20
> > just writing to say, "same problem here". If you find a way to compile =
a VPN client or if you get freeswan running
> > or find any other solution, please do let me know.
> >=20
> >=20
> > Cheers, Bj=F6rn van der Meer
> >=20
> >=20
> > _______________________________________________
> > yellowdog-general mailing list
> > yellowdog-general@lists.terrasoftsolutions.com
> > http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
> >=20
>=20
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
>=20