The continuing saga of trying to get Pybliographer compiled seems to be
coming down to the fact that somehow python 2.4 got installed and I may
not have switched over to 2.3 cleanly. I think it is correct now
[Kettlebridge:~] donpaul% python -V
Python 2.3.5
but get a new error
./configure
On Feb 27, 2005, at 2:05 PM, Don McKenzie Paul wrote:
The continuing saga of trying to get Pybliographer compiled seems to
be coming down to the fact that somehow python 2.4 got installed and I
may not have switched over to 2.3 cleanly. I think it is correct now
[Kettlebridge:~] donpaul% python
On 21 Feb 2005, at 02:51, David R. Morrison wrote:
Sorry to be so slow to respond here: I've only just begun to track
down what's happening.
When I compile this, I have no problem because the python setup script
does not find a value for DISPLAY in the environment, and so reports
cannot
On 20 Feb 2005, at 01:44, Alexander K. Hansen wrote:
Don McKenzie Paul wrote:
./configure --prefix=/sw
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether
On Feb 20, 2005, at 4:53 AM, Don McKenzie Paul wrote:
On 20 Feb 2005, at 01:44, Alexander K. Hansen wrote:
Don McKenzie Paul wrote:
./configure --prefix=/sw
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
On 20 Feb 2005, at 14:58, Alexander K. Hansen wrote:
Ah---I didn't realize that pybibliographer isn't a Fink package.
There's a couple of things to do:
was that based on something I wrote? It is a fink package isn't it?
1) Check the config.log file in the pybibliographer build directory
to
Ah---I didn't realize that pybibliographer isn't a Fink package.
There's a couple of things to do:
1) Check the config.log file in the pybibliographer build directory
to see what file it can't find.
2) Make sure you've set your environment up as per
On 20 Feb 2005, at 21:07, Alexander K. Hansen wrote:
snip
Am I correct in thinking that this means it is trying to use python
form /usr/bin, see line Python='/usr/bin/python' and
configure:1659: found /usr/bin/python
configure:1672: result: /usr/bin/python
configure:1688: checking python
On Feb 20, 2005, at 5:09 PM, Alexander K. Hansen wrote:
On Feb 20, 2005, at 4:22 PM, Don McKenzie Paul wrote:
On 20 Feb 2005, at 21:07, Alexander K. Hansen wrote:
snip
Am I correct in thinking that this means it is trying to use
python form /usr/bin, see line Python='/usr/bin/python' and
Sorry to be so slow to respond here: I've only just begun to track down
what's happening.
When I compile this, I have no problem because the python setup script
does not find a value for DISPLAY in the environment, and so reports
cannot test gtk [no DISPLAY]. My first guess was that this
./configure --prefix=/sw
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether ln -s works... yes
checking for python... /sw/bin/python
checking python
Don McKenzie Paul wrote:
./configure --prefix=/sw
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether ln -s works... yes
checking for python...
12 matches
Mail list logo
