12.04.2015, 17:15, Peter Kerpedjiev kirjoitti:
[clip]
> numpy/random/mtrand/distributions.c:892:1: internal compiler error:
> Illegal instruction
An internal compiler error means your compiler (in this case, gcc) is
broken. The easiest solution is to use a newer version of the compiler,
assuming t
Dear all,
Upon trying to install numpy using 'pip install numpy' in a virtualenv,
I get the following error messages:
creating build/temp.linux-x86_64-2.7/numpy/random/mtrand
compile options: '-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE=1
-D_LARGEFILE64_SOURCE=1 -Inumpy/core/include
-Ibuild/
Thanks. That works.
2010/4/29 David Cournapeau
> On Fri, Apr 30, 2010 at 5:23 AM, Pradeep Jha
> wrote:
> > Hi,
> >
> > I have a few questions:
> >
> > 1)
> > I downloaded numpy1.3.0 and installed it in a directory using the command
> > python setup.py install --prefix=$HOME/src/numpy
> > and I
On Fri, Apr 30, 2010 at 5:23 AM, Pradeep Jha wrote:
> Hi,
>
> I have a few questions:
>
> 1)
> I downloaded numpy1.3.0 and installed it in a directory using the command
> python setup.py install --prefix=$HOME/src/numpy
> and I see that numpy files have been generated in that directory.
>
> Now wh
Hi,
I have a few questions:
1)
I downloaded numpy1.3.0 and installed it in a directory using the command
*python setup.py install --prefix=$HOME/src/numpy
*and I see that numpy files have been generated in that directory.
Now when I tried to install matplotlib, it complained that my numpy versio
On Thu, Apr 22, 2010 at 2:23 AM, Christopher Barker
wrote:
> I hadn't read the thread carefully enough to realize that the OP was
> asking about a non-root install, but in any case, I'd still encourage
> that folks set ONE standard place in their PYTHONPATH, rather than one
> for each package, an
David Cournapeau wrote:
> I don't think it is wise to advocate the use of develop for python
> newcomers.
Fair enough.
What I know is that every scheme I've come up with for working with my
own under-development packages has been a pain in the #$@, and -develop
has worked well for me.
> The ea
On Tue, Apr 20, 2010 at 10:34 AM, Christopher Barker
wrote:
>
>
> Pradeep Jha wrote:
>> Thank you so much Robert. You are awesome :) That totally the problem.
>> One more question for you. Which are the things that you have to
>> declare in PYTHONPATH manually?
>
> I never put anything in PYTHONP
On Mon, Apr 19, 2010 at 20:34, Christopher Barker wrote:
>
>
> Pradeep Jha wrote:
>> Thank you so much Robert. You are awesome :) That totally the problem.
>> One more question for you. Which are the things that you have to
>> declare in PYTHONPATH manually?
>
> I never put anything in PYTHONPATH
Pradeep Jha wrote:
> Thank you so much Robert. You are awesome :) That totally the problem.
> One more question for you. Which are the things that you have to
> declare in PYTHONPATH manually?
I never put anything in PYTHONPATH -- if you install everything you
need, you won't need to. When I'
On Mon, Apr 19, 2010 at 09:58, Pradeep Jha wrote:
> Thank you so much Robert. You are awesome :) That totally the problem.
> One more question for you. Which are the things that you have to declare in
> PYTHONPATH manually?
In your case, just the site-packages/ directory you installed to.
--
R
Thank you so much Robert. You are awesome :) That totally the problem.
One more question for you. Which are the things that you have to declare in
PYTHONPATH manually?
2010/4/18 Robert Kern
> On Sun, Apr 18, 2010 at 19:49, Pradeep Jha
> wrote:
> > Hi,
> >
> > I am setting NUMPY_INC_DIR to what
On Sun, Apr 18, 2010 at 19:49, Pradeep Jha wrote:
> Hi,
>
> I am setting NUMPY_INC_DIR to what you said but still am getting the same
> error. Basically,
> there is no directory path like "***/include/python/***" anywhere in the
> installed numpy directory.
This is correct. No such directory
Hi,
I am setting NUMPY_INC_DIR to what you said but still am getting the same
error. Basically,
there is no directory path like "***/include/python/***" anywhere in the
installed numpy directory. whatever I am setting in my NUMPY_INC_DIR, the
preconfig file tries to add a /include/python to th
On Sun, Apr 18, 2010 at 13:32, Pradeep Jha wrote:
> Hi,
>
> I am running python 2.4.4. I installed numpy using the command
>
> python setup.py install --prefix=$HOME/bin
That's not a good prefix. --prefix=$HOME would be better. It will
create, if necessary, bin/ and lib/ underneath that.
> my si
Hi,
I am running python 2.4.4. I installed numpy using the command*
*
*python setup.py install --prefix=$HOME/**bin*
my site-packages directory got installed to the following address:*
/nfs/carv/d1/people/pradeep/bin/lib/python2.4*
in my preconfig file I changed the path to the following as yo
Hi,
how do I figure where did my numpy got installed to? I downloaded a tar.gz
file and then unzipped it at
/nfs/carv/d1/people/pradeep/src/numpy-1.3.0/.
I didn't do any additional installation steps. Also, just fyi, I don't have
root access to this system.
Thanks
2010/4/16 Robert Kern
> On Fr
On Fri, Apr 16, 2010 at 20:56, wrote:
> On Fri, Apr 16, 2010 at 9:47 PM, Pradeep Jha wrote:
>> Hi,
>>
>> before running the make command, it asks me to run the preconfig file. When
>> I run preconfig, I get the following warning message during the run:
>> checking for python2... /usr/bin/python2
On Fri, Apr 16, 2010 at 9:47 PM, Pradeep Jha wrote:
> Hi,
>
> before running the make command, it asks me to run the preconfig file. When
> I run preconfig, I get the following warning message during the run:
> checking for python2... /usr/bin/python2
> Python command set by configure to /usr/bin
Hi,
before running the make command, it asks me to run the preconfig file. When
I run preconfig, I get the following warning message during the run:
*checking for python2... /usr/bin/python2
Python command set by configure to /usr/bin/python2
WARNING: NUMPY include dir
/nfs/carv/d1/people/pradeep
On Fri, Apr 16, 2010 at 18:53, Pradeep Jha wrote:
> Hi,
>
> I changed it. I am not getting that error anymore, but I get the following
> error:
> running build
> running build_py
> running build_ext
> building 'Cantera._cantera' extension
> g++ -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall -Wp,
Hi,
I changed it. I am not getting that error anymore, but I get the following
error:
*running build
running build_py
running build_ext
building 'Cantera._cantera' extension
g++ -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector --param=ssp-buff
On Fri, Apr 16, 2010 at 17:59, Pradeep Jha wrote:
> Hi,
>
> I am trying to install a software called Cantera which uses numpy. When I
> run the make command, during the installation it gives me the following
> error:
>
> /bin/rm -f _build
> (CXX="g++"; export CXX; CC="g++"; export CC; CFLAGS="-O3
Hi,
I am trying to install a software called Cantera which uses numpy. When I
run the make command, during the installation it gives me the following
error:
*/bin/rm -f _build
(CXX="g++"; export CXX; CC="g++"; export CC; CFLAGS="-O3 -Wall -fPIC";
export CFLAGS; PURIFY=""; export PURIFY; /usr/
24 matches
Mail list logo
