[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Using Chirp and Parrot



Let's continue this discussion on the appropriate mailing list.

On Tue, 5 Dec 2006 leo@xxxxxxxxxxxxxxxxxxxxx wrote:

> Hi Doug,
>
> Thanks for the reply. I tried the latest CVS version...but I still get the
> same result/errors. By the way , how can I call "unsetenv GLOBUS_LOCATION"
> (I am using Scientific Linux). Should I include "unsetenv GLOBUS_LOCATION"
> in .bashrc? (I am using EXPORT instead of setenv, what is equivalent of
> "unsetenv"?)
>
> Leo
>
> >
> > Hello Leo -
> >
> > It's better if you report bugs about Parrot to the cctools mailing list:
> > 	http://www.cse.nd.edu/~ccl/software/help.shtml
> >
> > To avoid linking Parrot against Globus, call "unsetenv GLOBUS_LOCATION"
> > before invoking configure.
> >
> > The link error you describe below is fixed in the "latest cvs" version of
> > Parrot on our web page.
> >
> > Cheers,
> > Doug
> >
> >
> > On Mon, 4 Dec 2006 leo@xxxxxxxxxxxxxxxxxxxxx wrote:
> >
> >> Hi all,
> >>
> >> I have read from this website:
> >> http://www.cse.nd.edu/~ccl/software/howto/remotelink.shtml
> >>
> >> ...that Parrot allows unmodified applications to connect to remote
> >> storage
> >> while Chirp is a server that exports filesystem data (including all the
> >> libraries needed). And this is especially designed for jobs which uses
> >> dynamic linking in a distributed system. (Am I right?)
> >>
> >> ....then I followed the manual in installing the cctools, but I found
> >> out
> >> that even if I did not include the --with-globus-path /usr/local/globus
> >> option in configuring the software, it still examines the globus
> >> installation in my computer!!! (I don't want to use Globus yet). How can
> >> I
> >> get around with this?
> >>
> >> Then, another problem is when I fire the "make" command, I got the
> >> following errors:
> >>
> >> [condor@phys-ugradlab02 cctools]$ make
> >> for p in dttools ftp_lite chirp ftsh maptools parrot ; do cd $p && make
> >> all && cd .. ; done
> >> make[1]: Entering directory `/home/condor/cctools/dttools'
> >> for p in src doc ; do cd $p && make all && cd .. ; done
> >> make[2]: Entering directory `/home/condor/cctools/dttools/src'
> >> LINK auth_test
> >> /home/globus/globus/lib/libltdl_gcc32dbg.a(ltdl.o)(.text+0x3b2): In
> >> function `sys_dl_open':
> >> /home/globus/globus/source-trees/mds/libtool/libtool-1.5.8/libltdl/ltdl.c:1101:
> >> warning: Using 'dlopen' in statically linked applications requires at
> >> runtime the shared libraries from the glibc version used for linking
> >> /home/globus/globus/lib/libglobus_gsi_sysconfig_gcc32dbg.a(globus_gsi_system_config.o)(.text+0x5aab):
> >> In function `globus_gsi_sysconfig_get_unique_proxy_filename':
> >> /home/globus/globus/source-trees/gsi/sysconfig/source/library/globus_gsi_system_config.c:7154:
> >> warning: the use of `tmpnam' is dangerous, better use `mkstemp'
> >> /usr/lib/gcc/i386-redhat-linux/3.4.6/../../../libkrb5.a(cc_file.o)(.text+0x1add):
> >> In function `krb5_fcc_generate_new':
> >> : warning: the use of `mktemp' is dangerous, better use `mkstemp'
> >> /usr/lib/gcc/i386-redhat-linux/3.4.6/../../../libdl.a(dlopen.o)(.text+0x10):
> >> In function `dlopen':
> >> : undefined reference to `__dlopen'
> >> /usr/lib/gcc/i386-redhat-linux/3.4.6/../../../libdl.a(dlclose.o)(.text+0x5):
> >> In function `dlclose':
> >> : undefined reference to `__dlclose'
> >> /usr/lib/gcc/i386-redhat-linux/3.4.6/../../../libdl.a(dlsym.o)(.text+0xd):
> >> In function `dlsym':
> >> : undefined reference to `__dlsym'
> >> /usr/lib/gcc/i386-redhat-linux/3.4.6/../../../libdl.a(dlerror.o)(.text+0x5):
> >> In function `dlerror':
> >> : undefined reference to `__dlerror'
> >> collect2: ld returned 1 exit status
> >> make[2]: *** [auth_test] Error 1
> >> make[2]: Leaving directory `/home/condor/cctools/dttools/src'
> >> /bin/sh: line 0: cd: doc: No such file or directory
> >> make[1]: *** [all] Error 1
> >> make[1]: Leaving directory `/home/condor/cctools/dttools'
> >> /bin/sh: line 0: cd: ftp_lite: No such file or directory
> >> /bin/sh: line 0: cd: chirp: No such file or directory
> >> /bin/sh: line 0: cd: ftsh: No such file or directory
> >> /bin/sh: line 0: cd: maptools: No such file or directory
> >> /bin/sh: line 0: cd: parrot: No such file or directory
> >> make: *** [all] Error 1
> >>
> >> Thanks in advance,
> >> Leo
> >>
> >>
> >> _______________________________________________
> >> Condor-users mailing list
> >> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with
> >> a
> >> subject: Unsubscribe
> >> You can also unsubscribe by visiting
> >> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> >>
> >> The archives can be found at either
> >> https://lists.cs.wisc.edu/archive/condor-users/
> >> http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR
> >>
> > _______________________________________________
> > Condor-users mailing list
> > To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> > subject: Unsubscribe
> > You can also unsubscribe by visiting
> > https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> >
> > The archives can be found at either
> > https://lists.cs.wisc.edu/archive/condor-users/
> > http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR
> >
>
>
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at either
> https://lists.cs.wisc.edu/archive/condor-users/
> http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR
>