[PD] .pdrc (was:Can't get zexy to load)

[Timothy Rolls]

I have the source code, but when I tried to compile it I got the error
"could not find g_canvas" or some such thing (I know it was the g_canvas.c
that was the problem). Since I was in the middle of a project I couldn't
wait and figure it out, so I downloaded the rpm. However, I have some time
now and maybe I'll try it later today. One thing, should I compile it as
root, or as user? I think I compiled zexy as root and that's why I am having
the problem with permissions. Thanks again.

Regards,
Tim

----- Original Message -----
From: "mik" <mik at antwerpen.be>
To: "Timothy Rolls" <trolls at binghamton.edu>
Sent: Monday, September 24, 2001 9:01 AM
Subject: Re: [PD] .pdrc (was:Can't get zexy to load)


> Did you install the the rpm? If so, i'd suggest getting the tar.gz instead
> from Miller's site (see http://www.pure-date.org for the URL). Untar it in
> your home directory. Now you'll have everything pd related in one
directory.
> The executables are in the bin directory. Normally they should work. If
not,
> you'll to recompile: go to the src directory, do "make clean", "configure"
> and finally "make".
> !!! Do not forget to remove the rpm.
>
> mik
> ----- Original Message -----
> From: "Timothy Rolls" <trolls at binghamton.edu>
> To: "mik" <mik at antwerpen.be>
> Sent: Monday, September 24, 2001 2:31 PM
> Subject: Re: [PD] .pdrc (was:Can't get zexy to load)
>
>
> > "mik" wrote:
> >
> > >
> > > You can only change permissions as root. The best thing to do is
always
> to
> > > log in as normal user and to change to root with "su"  for
> administrative
> > > tasks (like changing permissions).
> > >
> > > mik
> > >
> >
> > Yeah, I tried that. I also tried loging on as root, and that didn't work
> > either. I'll try it with an absolute path and see if that works. I
thought
> > this was supposed to work like in UNIX, but maybe there is a difference.
> My
> > Red Hat book didn't show an absolute path, but it wouldn't be the first
> > mistake I found in there. Thanks for the response.
> >
> > Regards,
> > Tim
> >
> >
>
>