James Stroud schrieb:
> Though great for self development, I'm not so sure such
> lessons should be necessary to build these tools.
Yes. The lesson you should take from this is: don't try to be smarter
than the authors of the software. It should build out of the box, if
you follow the build instru
Robert Kern wrote:
> Okay, this is possibly part of the problem. numpy.distutils handles
> FORTRAN code differently than other extension modules; this is why pure
> C extension modules both inside numpy and elsewehere were linking fine.
> Try unsetenving $CPPFLAGS and $LDFLAGS and adding those a
Martin v. Löwis wrote:
> James Stroud schrieb:
>> I think I would like to know how to avoid or correct these sort of
>> issues in the future, which seem to be limited, for me at least, to
>> scipy and numpy, with the possible exception of MySQLdb and its
>> dependency on zlib. Ideally, I would like
Ben Finney wrote:
> James Stroud <[EMAIL PROTECTED]> writes:
>
>> I try things until a build works. I consider everything I do
>> until acquiring a working build as necessary. Going back to see
>> exactly what I did to make things work is not a viable option
>
> Before trying such "I don't know w
James Stroud schrieb:
> I think I would like to know how to avoid or correct these sort of
> issues in the future, which seem to be limited, for me at least, to
> scipy and numpy, with the possible exception of MySQLdb and its
> dependency on zlib. Ideally, I would like to understand exactly what
>
James Stroud <[EMAIL PROTECTED]> writes:
> I try things until a build works. I consider everything I do
> until acquiring a working build as necessary. Going back to see
> exactly what I did to make things work is not a viable option
Before trying such "I don't know what I need to do, but I'm goi
James Stroud wrote:
> Robert Kern wrote:
>>> Sorry. To clarify, making libpython2.5a available in a
>>> $LD_LIBRARY_PATH was necessary to build numpy and scipy.
>> I don't see how that could have affected anything. Static libraries
>> aren't looked up in $LD_LIBRARY_PATH. Certainly not for build-
Martin v. Löwis wrote:
> James Stroud schrieb:
>
>>>What happens if you omit these flags?
>>
>>Please see my last message to Robert Kern.
>
>
> If you don't want me to help you, that's fine, then I won't.
>
> I couldn't find an answer to this question in any of your
> messages in this thread.
James Stroud schrieb:
>> What happens if you omit these flags?
>
> Please see my last message to Robert Kern.
If you don't want me to help you, that's fine, then I won't.
I couldn't find an answer to this question in any of your
messages in this thread.
Still, it *should* work out of the box. I
Robert Kern wrote:
> James Stroud wrote:
>
>> Well I added those arguments to $LDFLAGS, but it seemed like a pretty
>> miserable hack, especially the "-shared" part.
>
>
> Hmmm. Did you have $LDFLAGS set to anything (or more likely, nothing)
> before? I.e. did you have something like this?
>
Robert Kern wrote:
>> Sorry. To clarify, making libpython2.5a available in a
>> $LD_LIBRARY_PATH was necessary to build numpy and scipy.
>
> I don't see how that could have affected anything. Static libraries
> aren't looked up in $LD_LIBRARY_PATH. Certainly not for build-time linking.
OK--new
James Stroud wrote:
> Robert Kern wrote:
>> James Stroud wrote:
>>> The build process, by the way, required my copying libpython2.5.a to
>>> $HOME/Programs/lib.
>> Hmm. That doesn't quite sound right, but it's been a while since I
>> compiled the interpreter from source.
>
> Sorry. To clarify,
Robert Kern wrote:
> James Stroud wrote:
>> I did build my own python 2.5, yesterday, requiring me to rebuild all
>> extensions.
>
> Do other extensions build correctly? If so, it's beginning to look like
> a problem in numpy.distutils .
Actually, I just found that MySQLdb had a similar problem
Martin v. Löwis wrote:
> James Stroud schrieb:
>> This is annoying. I am trying to build scipy right now but every .so
>> file requires my adding "-lpython2.5 -lpthread -lm -lutil -ldl -shared"
>> to the ld flags.
>
> That shouldn't be necessary. Linking without this should work just fine.
Unfort
Robert Kern wrote:
> James Stroud wrote:
>> I did build my own python 2.5, yesterday, requiring me to rebuild all
>> extensions.
>
> Do other extensions build correctly? If so, it's beginning to look like
> a problem in numpy.distutils .
It seems that every thing has built without incident (num
James Stroud schrieb:
> This is annoying. I am trying to build scipy right now but every .so
> file requires my adding "-lpython2.5 -lpthread -lm -lutil -ldl -shared"
> to the ld flags.
That shouldn't be necessary. Linking without this should work just fine.
That way, since you made libpython2.5.
James Stroud wrote:
> Well I added those arguments to $LDFLAGS, but it seemed like a pretty
> miserable hack, especially the "-shared" part.
Hmmm. Did you have $LDFLAGS set to anything (or more likely, nothing) before?
I.e. did you have something like this?
export LDFLAGS=""
python setup.
James Stroud wrote:
> I did build my own python 2.5, yesterday, requiring me to rebuild all
> extensions.
Do other extensions build correctly? If so, it's beginning to look like a
problem in numpy.distutils .
> Everything I do is compiled by hand as joe-user. I'm in a
> situation where I can't
Robert Kern wrote:
> James Stroud wrote:
>
>> Hello All,
>>
>> This is annoying. I am trying to build scipy right now but every .so
>> file requires my adding "-lpython2.5 -lpthread -lm -lutil -ldl
>> -shared" to the ld flags.
>
>
>> I'm running Linux FC4 on a dual intel p4 (~3.2 GHz) with sun
James Stroud wrote:
> Hello All,
>
> This is annoying. I am trying to build scipy right now but every .so
> file requires my adding "-lpython2.5 -lpthread -lm -lutil -ldl -shared"
> to the ld flags.
> I'm running Linux FC4 on a dual intel p4 (~3.2 GHz) with sundry
> libraries in non-standard p
James Stroud wrote:
> Hello All,
>
> This is annoying. I am trying to build scipy right now but every .so
> file requires my adding "-lpython2.5 -lpthread -lm -lutil -ldl -shared"
> to the ld flags.
>
> Main Question: When building with "setup.py", where can I include this
> information so I d
James Stroud wrote:
> Hello All,
>
> This is annoying. I am trying to build scipy right now but every .so
> file requires my adding "-lpython2.5 -lpthread -lm -lutil -ldl -shared"
> to the ld flags.
>
> Main Question: When building with "setup.py", where can I include this
> information so I d
Hello All,
This is annoying. I am trying to build scipy right now but every .so
file requires my adding "-lpython2.5 -lpthread -lm -lutil -ldl -shared"
to the ld flags.
Main Question: When building with "setup.py", where can I include this
information so I don't have to link every .so file by
23 matches
Mail list logo
