This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author liuqianhn
Recipients liuqianhn, loewis
Date 2012-03-07.09:35:21
SpamBayes Score 4.3518078e-11
Marked as misclassified No
Message-id <CALAhSX37ADVvTSu-FkhiANZAQHJghw86p1wTWCDfhkStqhKmyw@mail.gmail.com>
In-reply-to <CALAhSX2bDyR01HfnP4upeaxV=BRHOFTvP87ohstms6QK-fOvxw@mail.gmail.com>
Content
Dear Martin,

I did the following operations
./configure --prefix=
"/img01/home/liuqian1/PLAprediction/software/PythonInstall"
make
make install

and then

MPYTHONHOME="/img01/home/liuqian1/PLAprediction/software/PythonInstall"
PATH="$MPYTHONHOME/bin":$PATH

However, when I try ' python -c "import binascii;" ', *I still got the same
error.*

By the way, I can run ' python -c "import binascii;" ' on Window XP and in
python 2.5.5.

Our technician also installed python 3.0 in our Linux server without the
'prefex' in the "./configure" but we got the same error also.

Any more comments about this?

Thanks for your help in advance.

Best regards,
Qian Liu

On Wed, Mar 7, 2012 at 5:12 PM, Qian Liu <report@bugs.python.org> wrote:

>
> Qian Liu <liuq0011@e.ntu.edu.sg> added the comment:
>
> Dear Martin,
>
> Many thanks for your help and your reply. I will correct the errors and let
> you know the result.
>
> best regards,
> Qian Liu
>
> On Wed, Mar 7, 2012 at 5:07 PM, Martin v. Löwis <report@bugs.python.org
> >wrote:
>
> >
> > Martin v. Löwis <martin@v.loewis.de> added the comment:
> >
> > There are some minor errors indeed: the syntax for PATH and PYTHONPATH is
> > wrong (don't use quotes (") in the middle of the value). Also, putting
> > site-packages into PYTHONPATH should not be necessary.
> >
> > I think the main cause might be the incorrect --prefix argument. Don't
> use
> > "~/PythonInstall", but "$HOME/PythonInstall". Also, when I try this, I
> get
> >
> > configure: error: expected an absolute directory name for --prefix:
> > ~/PythonInstall
> >
> > so you must have made something different (or you have used a shell
> > different from bash), else you would have gotten the same error.
> >
> > ----------
> >
> > _______________________________________
> > Python tracker <report@bugs.python.org>
> > <http://bugs.python.org/issue14216>
> > _______________________________________
> >
> >
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue14216>
> _______________________________________
>
>
History
Date User Action Args
2012-03-07 09:35:22liuqianhnsetrecipients: + liuqianhn, loewis
2012-03-07 09:35:21liuqianhnlinkissue14216 messages
2012-03-07 09:35:21liuqianhncreate