/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! */
> -----Original Message-----
> From: Gregory Leblanc [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 30, 1999 2:41 PM
> To: 'Ken Long'; Masquerade List (E-mail)
> Subject: RE: [Masq] New ip_masq_icq module problems and solution
>
>
> /* HINT: Search archives @ http://www.indyramp.com/masq/
> before posting! */
>
>
> > -----Original Message-----
> > From: Ken Long [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, December 30, 1999 11:42 AM
> > To: Gregory Leblanc
> > Subject: RE: [Masq] New ip_masq_icq module problems and solution
> >
> > Did you see my post about the makefile? It wouldn't work
> for me out
> > of the box either until it was modified.
>
> I'm back again. :) I think I've tracked the problem down,
> but I have no
> idea how to fix it. On my RedHat based Linux Distros the
> command 'uname -m'
> returns the processor type that it's running on. So, on my
> K6-2, it returns
> i586, and on my Intel 486, it returns i486. It's getting
> confused because
> it can't find 'i386' anywhere in the string returned from
> 'uname -m'. I
> think I'm going to go back and try manually replacing this in
> 'Makefile.arch1' and 'Makefile.arch2' with 'i386' (hard
> coding it in a way)
> and I'll get back to you if it works.
Yes, that fixes it. I'm not sure exactly why I had to do this, but I've got
it up and running. Testing with the AOL/ICQ 99b v3.14 client, gicq, and
GNOMEICU, and well see how things go.
Greg
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
Admin requests can be handled at http://www.indyramp.com/masq-list/ -- THIS INCLUDES
UNSUBSCRIBING!
or email to [EMAIL PROTECTED]
PLEASE read the HOWTO and search the archives before posting.
You can start your search at http://www.indyramp.com/masq/
Please keep general linux/unix/pc/internet questions off the list.
