On 9/2/02 8:54 PM, "Dimitris Dimitriadis" <[EMAIL PROTECTED]> wrote:
> Thanks for your feedback. I had already changed the paths in the build
> script to point to /sw/..., but it didn't do the trick. It didn't work
> after using the information in the updated FAQ either.
I haven't downloaded pyth
Fernando, Ben,
Thanks for your feedback. I had already changed the paths in the build
script to point to /sw/..., but it didn't do the trick. It didn't work
after using the information in the updated FAQ either.
I suppose I have to dig a bit deeper.
/Dimitris
On Tuesday, September 3, 2002,
On 9/2/02 8:42 PM, "Ben Hines" <[EMAIL PROTECTED]> wrote:
> ... but you didn't tell him how.
Good point, I assumed that he would go and read the package's "README" or
"INSTALL", which typically say what to do to change the default library
path.
>
> In the future, you can point folks at the new
On Monday, September 2, 2002, at 05:23 PM, Fernando Pereira wrote:
> On 9/2/02 8:03 PM, "Dimitris Dimitriadis" <[EMAIL PROTECTED]>
> wrote:
>
>> New to the list. I was scanning through the archives and saw that
>> python-mysql is not among the existing packages, so I tried to build
>> it
>> m
On 9/2/02 8:03 PM, "Dimitris Dimitriadis" <[EMAIL PROTECTED]> wrote:
> New to the list. I was scanning through the archives and saw that
> python-mysql is not among the existing packages, so I tried to build it
> myself. Having failed (for anyone interested, the errors are inlined
> below), I wan
Hi all,
New to the list. I was scanning through the archives and saw that
python-mysql is not among the existing packages, so I tried to build it
myself. Having failed (for anyone interested, the errors are inlined
below), I wanted to ask if anyone has built/is planning to include this
in the
