Fw: [SciPy-dev] Link problem with scipy on SUN ?

ERIC JONES ejones17 at austin.rr.com
Tue Oct 23 12:39:15 CDT 2001


Hey,

Sorry that was a typo.

I meant

    f90 -dryrun dummy.f90

eric

----- Original Message -----
From: "Arnd Baecker" <a.backer at bristol.ac.uk>
To: "eric jones" <eric at enthought.com>
Sent: Tuesday, October 23, 2001 6:49 PM
Subject: Re: Fw: [SciPy-dev] Link problem with scipy on SUN ?


> Hi Eric,
>
> thank you very much for your response!
>
> Looking at the output of [1] and [2] this might explain
> (at least ;-) where the (null) comes from.
> So there it is: (sorry, the lines wrap around in my mailer,
> I could send you the output as attachment if you want)
>
>
> wega$ f77 -dryrun dummy.f
> ###     command line files and options (expanded):
> ### -dryrun dummy.f
> ### f77: Note: LM_LICENSE_FILE = (null)
> ### f77: Note: NLSPATH =
> /soft/local/lpp/opt/SUNWspro/bin/../WS6U2/bin/../lib/lo
>
cale/%L/LC_MESSAGES/%N.cat:/soft/local/lpp/opt/SUNWspro/bin/../WS6U2/bin/../
../l
> ib/locale/%L/LC_MESSAGES/%N.cat
> /soft/local/lpp/opt/SUNWspro/bin/../WS6U2/bin/f77pass1 -y-o -ydummy.o
> -y-fbe -y/
> soft/local/lpp/opt/SUNWspro/bin/../WS6U2/bin/fbe -y-xarch=generic -y-s
> -ptk "/so
> ft/local/lpp/opt/SUNWspro/bin/../WS6U2/bin/f77 -dryrun " -xcache=generic
> -I/soft
> /local/lpp/opt/SUNWspro/WS6U2/include/f77 -xhasc=yes dummy.f
> /tmp/f77pass1.10091
> .s.0.s dummy.o /tmp/f77pass1.10091.d.1.s
> rm /tmp/f77pass1.10091.s.0.s
> rm /tmp/f77pass1.10091.d.1.s
> ### f77: Note: LD_LIBRARY_PATH =
> /soft/local/lpp/nagftn/flsol19da/:/soft/local/l
> pp/nagc/clsol06da:
> ### f77: Note: LD_RUN_PATH     = (null)
> ### f77: Note: LD_OPTIONS = (null)
> /usr/ccs/bin/ld -t -R/soft/local/lpp/opt/SUNWspro/lib:/opt/SUNWspro/lib -o
> a.out
>  /soft/local/lpp/opt/SUNWspro/WS6U2/lib/crti.o
> /soft/local/lpp/opt/SUNWspro/WS6U
> 2/lib/crt1.o /soft/local/lpp/opt/SUNWspro/WS6U2/lib/values-xi.o -Y
> P,/soft/local
>
/lpp/opt/SUNWspro/lib:/soft/local/lpp/opt/SUNWspro/WS6U2/lib:/usr/ccs/lib:/u
sr/l
> ib dummy.o -lF77 -lM77 -lsunmath -lm -lcx -lc
> /soft/local/lpp/opt/SUNWspro/WS6U2
> /lib/crtn.o
> rm dummy.o
>
>
> The second one gives:
>
> wega$ f90 -fdryrun dummy.f90
> f90: Warning: Option -fdryrun passed to ld, if ld is invoked, ignored
> otherwise
> ERROR: Cannot open source file "dummy.f90".
>
> Presumably not quite what you wanted ...
>
> Creating some dummy Fortran File then gives
> wega$ f90 -dryrun tst.f
> ###     command line files and options (expanded):
> ### -dryrun tst.f
> ### f90: Note: LM_LICENSE_FILE = (null)
> ### f90: Note: NLSPATH =
>
/soft/local/lpp/opt/SUNWspro/bin/../WS6U2/bin/../lib/locale/%L/LC_MESSAGES/%
N.cat:/soft/local/lpp/opt/SUNWspro/bin/../WS6U2/bin/../../lib/locale/%L/LC_M
ESSAGES/%N.cat
> /soft/local/lpp/opt/SUNWspro/bin/../WS6U2/bin/f90comp -y-o -ytst.o -ev
> -y-ftrap=common -m3 -dq -y-fbe
> -y/soft/local/lpp/opt/SUNWspro/bin/../WS6U2/bin/fbe -y-xarch=generic -y-s
> -H "/soft/local/lpp/opt/SUNWspro/bin/../WS6U2/bin/f90 -dryrun "
> -y-xcache=generic -xcache=generic
> -I/soft/local/lpp/opt/SUNWspro/WS6U2/include/f90/v8
> -p/soft/local/lpp/opt/SUNWspro/WS6U2/lib -xall tst.f
> ### f90: Note: LD_LIBRARY_PATH =
> /soft/local/lpp/nagftn/flsol19da/:/soft/local/lpp/nagc/clsol06da:
> ### f90: Note: LD_RUN_PATH     = (null)
> ### f90: Note: LD_OPTIONS = (null)
> /usr/ccs/bin/ld -t -R/soft/local/lpp/opt/SUNWspro/lib:/opt/SUNWspro/lib -o
> a.out /soft/local/lpp/opt/SUNWspro/WS6U2/lib/crti.o
> /soft/local/lpp/opt/SUNWspro/WS6U2/lib/crt1.o
> /soft/local/lpp/opt/SUNWspro/WS6U2/lib/values-xi.o -Y
>
P,/soft/local/lpp/opt/SUNWspro/lib:/soft/local/lpp/opt/SUNWspro/WS6U2/lib:/u
sr/ccs/lib:/usr/lib
> tst.o -lfui -lfai -lfai2 -lfsumai -lfprodai -lfminlai -lfmaxlai -lfminvai
> -lfmaxvai -lfsu -lsunmath -lm -lc
> /soft/local/lpp/opt/SUNWspro/WS6U2/lib/crtn.o
> rm tst.o
>
>
> Hope this helps ...
>
> Best wishes,
>
> Arnd
>
>
>
>
>
>
>
>
>
> On Tue, 23 Oct 2001, eric jones wrote:
>
> > Hey Arnd,
> >
> > Forgot to but you in the response list for this email.
> >
> > eric
> >
> > ----- Original Message -----
> > From: "ERIC JONES" <ejones17 at austin.rr.com>
> > To: <scipy-dev at scipy.org>
> > Sent: Tuesday, October 23, 2001 11:59 AM
> > Subject: Re: [SciPy-dev] Link problem with scipy on SUN ?
> >
> >
> > > Hey Arnd,
> > >
> > > Short answer:
> > >
> > > Sun has only been tested on a single machine, and I hardcoded the
> > libraries
> > > for it to work.  Can you run the following commands on your machine
and
> > send
> > > me the output?
> > >
> > >         [1]$ f77 -dryrun dummy.f
> > >         ...
> > >         [2]$ f90 -fdryrun dummy.f90
> > >
> > > This will help me make a more generic solution.
> > >
> > > Longer Answer:
> > >
> > > SciPy tries to inspect your machine,learn what Fortran compiler you
are
> > > using, and provide the correct libraries and library paths to get
> > everything
> > > to link correctly.
> > >
> > > A little background:
> > >
> > > The -L directives specify the library directories where the linker
(gcc)
> > > should look for needed libraries.  The -l directories specify the
> > libraries
> > > themselves.  -lF77 will look for a file called libF77.a or libF77.so
in
> > the
> > > directories you specified with the -L directives, and also a few other
> > > standard locations.
> > >
> > > It is a little worrisome that you have -L(null) in some places on the
> > > command line.  I don't think this should happen and it is likely a bug
in
> > > build_flib.py.  I'll look into this.  2nd, its strange that the
> > directories
> > > following your -L directives are not full paths.  This can't be right.
> > >
> > > The trick you played just kept the linker from looking for the Fortran
> > > libraries (although I'm not quite sure how...), and since vw_wrap
doesn't
> > > need them, it will link fine.  However, many of the other modules will
> > need
> > > them, so this is just a temporary fix.
> > >
> > > see ya,
> > > eric
> > >
> > >
> > > ----- Original Message -----
> > > From: "Arnd Baecker" <a.backer at bristol.ac.uk>
> > > To: <scipy-dev at scipy.net>
> > > Sent: Sunday, October 21, 2001 4:49 PM
> > > Subject: [SciPy-dev] Link problem with scipy on SUN ?
> > >
> > >
> > > > Hi,
> > > >
> > > > when trying to install scipy I ran into the following
> > > > link problem under SUN
> > > > (uname -a: SunOS wega 5.8 Generic_108528-07 sun4u sparc
> > > > - I can provide further details if necessary)
> > > >
> > > >
> > > > [...]
> > > > cluster/src/vq_wrap.cpp: In function `int char_to_numtype(char)':
> > > > cluster/src/vq_wrap.cpp:590: warning: control reaches end of
non-void
> > > > function `char_to_numtype(char)'
> > > > cluster/src/vq_wrap.cpp: At top level:
> > > > cluster/src/vq_wrap.cpp:516: warning: `struct PyObject *
> > > > l_output_helper(struct PyObject *, struct PyObject *)' defined but
not
> > > > used
> > > > gcc -shared
> > build/temp.solaris-2.8-sun4u-2.1/vq_wrap.o -L(null) -LSun/lib
> > > > -L(null) -LSun/lib -Lbuild/temp.solaris-2.8-sun4u-2.1
> > > > -Lbuild/temp.solaris-2.8-sun4u-2.1 -R(null) -RSun/lib -lamos -ltoms
> > >
> >
> -lfitpack -lminpack -lquadpack -lodepack -llinpack_lite -lmach -lf90 -lF77
> > > > -lM77 -lsunmath -lm -lgist -lc_misc -lcephes -o
> > > > build/lib.solaris-2.8-sun4u-2.1/scipy/cluster/_vq.so -mimpure-text
> > > > ld: fatal: library -lf90: not found
> > > > ld: fatal: library -lF77: not found
> > > > ld: fatal: library -lM77: not found
> > > > ld: fatal: library -lsunmath: not found
> > > > ld: fatal: File processing errors. No output written to
> > > > build/lib.solaris-2.8-sun4u-2.1/scipy/cluster/_vq.so
> > > > collect2: ld returned 1 exit status
> > > > error: command 'gcc' failed with exit status 1
> > > >
> > > >
> > > > If I replace the above line by
> > > >
> > > > gcc -shared
> > build/temp.solaris-2.8-sun4u-2.1/vq_wrap.o -L(null) -LSun/lib
> > > > -L(null) -LSun/lib -Lbuild/temp.solaris-2.8-sun4u-2.1
> > > > -Lbuild/temp.solaris-2.8-sun4u-2.1 -R(null) -RSun/lib -lamos -ltoms
> > >
> >
> -lfitpack -lminpack -lquadpack -lodepack -llinpack_lite -lmach -L -lf90 -L
> > > > -lF77 -L -lM77 -L -lsunmath -lm -lgist -lc_misc -lcephes -o
> > > > build/lib.solaris-2.8-sun4u-2.1/scipy/cluster/_vq.so -mimpure-text
> > > >
> > > > then there is no problem anymore.
> > > > (i.e. adding -L in front of the above libraries does the job ...)
> > > >
> > > > What do I have to change to get rid of this problem ?
> > > > (All the above four libraries seem to be defined in
> > > > the variable self.libraries in build_flib.py.
> > > > but I don't understand enough python yet ... ;-)
> > > >
> > > > Best,
> > > >
> > > > Arnd
> > > >
> > > > _______________________________________________
> > > > Scipy-dev mailing list
> > > > Scipy-dev at scipy.net
> > > > http://www.scipy.net/mailman/listinfo/scipy-dev
> > > >
> > >
> > >
> > > _______________________________________________
> > > Scipy-dev mailing list
> > > Scipy-dev at scipy.net
> > > http://www.scipy.net/mailman/listinfo/scipy-dev
> > >
> >
> >
> >





More information about the Scipy-dev mailing list