Re: [Fwd: Re: [Dpcl-user] ASC_invalid_version on 3.2.6 compiled fromscratch]
Brought to you by:
dpcl-admin,
dwootton
Menu
▾
▴
Re: [Fwd: Re: [Dpcl-user] ASC_invalid_version on 3.2.6 compiled fromscratch]
|
From: Dave W. <dwo...@us...> - 2003-11-11 17:19:17
|
Harald
What I think you are saying is that you have DPCL 3.2.5 or DPCL 3.2.6
packaged version installed as /usr/lpp/ppe.dpcl, which is where installp
will put it. You also have the version you compiled with 3.2.6 level code
residing in some other directory which was accessible across a set of
machines.
If you compiled your client with -L/usr/lpp/ppe.dpcl/lib then it worked
correctly with whatever version of DPCL was installed. If you compiled your
client with, for instance, -L /u/wootton/dpcl/src/lib/src, containing 3.2.6
level code, then it would fail the version check.
Is this correct? If so, I think this may be the problem, since I understand
that at least in some cases, the linker builds the path to the library into
the executable. I need to check with one of the other team members to be
sure and find out if there is a way around it.
Dave
Harald Servat
Gelabert To: Dave Wootton/Poughkeepsie/IBM@IBMUS
<harald@cepba.upc cc: dpc...@ww...,
.es> dpc...@ww...
Sent by: Subject: Re: [Fwd: Re: [Dpcl-user] ASC_invalid_version on 3.2.6 compiled
harald@cepba.upc. fromscratch]
es
11/11/2003 05:54
AM
Hello again,
I think I've found something interesting for this problem.
When I described the problem I was using a partition that is shared
to all disks via NFS.
Now, I've recompiled the client tool but I told the linker to use a
local disk of the node and using the compiled library. If I call the
client within this node, it fails. But when I use the client on a
different node that has dpcl 3.2.5 it works (giving Ais_version a value
of 030205).
So this makes me ask for AIX question, does the loader look for
a default library path?
Anyway.. I think this solves the 'problem'. When I used my own compiled
DPCL, it used the 3.2.6 version always (because it was visible in all
the machine).
But when I compiled with the system 3.2.6, the loader always look for
/usr/lpp/ppe.dpcl/lib/libdpcl.a. Only one node has version 3.2.6, and
others has 3.2.5, but it never failed because versions did match.
What do you think about that? Is it a possible reason?
Again, I wish to thank your patience.
Dave Wootton wrote:
>
> Harald
> The -l and -L flags should not affect this.In fact, they are required.
> /usr/lpp/ppe.dpcl/lib/libdpcl.a should be a shared library unless someone
has
> built DPCL with modified makefiles and installed that copy.
>
> Can you issue the command 'ar vt /usr/lpp/ppe.dpcl/lib/libdpcl.a' and
note the
> results? there should be a single member, shr.o, if the library is linked
as a
> shared library. If you see a list of names, then you somehow have a
static
> copy of libdpcl.a which could explain your problem.
>
> When you call Ais_version from a client compiled with the 'compiled'
version
> of DPCL, what does it report?
>
> Are you trying this with client and daemons running on the same node or
> different nodes? Does it make a difference?
>
> Dave
>
> Harald Servat Gelabert <ha...@ce...>
> Sent by: To:
> dpc...@ww...
dpc...@ww...
> cc:
> 11/10/2003 10:28 AM Subject:
[Fwd: Re:
> [Dpcl-user]
ASC_invalid_version on 3.2.6
> compiled from scratch]
>
> I resend this mail. It seems that it has not arrived to the mail list.
>
> Regards,
>
> -------- Original Message --------
> X-Mozilla-Status: 0001
> X-Mozilla-Status2: 00000000
> Message-ID: <3FA...@ce...>
> Date: Fri, 07 Nov 2003 14:43:45 +0100
> From: Harald Servat Gelabert <ha...@ce...>
> X-Mailer: Mozilla 4.77C-SGI [en] (X11; I; IRIX64 6.5 IP28)
> X-Accept-Language: ca, es, en
> MIME-Version: 1.0
> To: Dave Wootton <dwo...@us...>
> CC: dpc...@ww...
> Subject: Re: [Dpcl-user] ASC_invalid_version on 3.2.6 compiled from
scratch
> References:
> <OFD...@us...>
> Content-Type: text/plain; charset=iso-8859-1
> Content-Transfer-Encoding: 8bit
>
> Hello.
>
> I'm sorry for the delay in the answer.
>
> I've checked for LIBPATH, but it is unset.
>
> I used the usual -ldpcl and -L<directory> at the link stage.
> Does this generate a static binary?
> If so, this could explain why do those versions fail.
>
> But then, I could not understand why clients based on dpcl 3.2.5 runs on
a
> node with 3.2.6.
>
> Thanks for your patience,
>
> Dave Wootton wrote:
> >
> > Harald
> > I can't make this fail here. I compiled and installed DPCL from the
3.2.6
> > sources, built the eut_hello sample, and verified it worked. Then I
> installed
> > DPCL 3.2.5 from the installp image and ran eut_hello again without
problems.
> > Then I re-installed from 3.2.6 sources, modified eut_hello to call
> Ais_version
> > and ran it with the 3.2.6 DPCL I just installed. Ais_version reported
> > 0x03020600 as expected. I then reinstalled DPCL 3.2.5 and ran
eut_hello.
> > Ais_version then reported 0x03020500, which it should have, since
libdpcl.a
> is
> > a shared library and the version now being loaded is the 3.2.5 version
of
> > libdpcl.a.
> >
> > The code that is returning this error is in
SD/src/os/aix/SdUnsecureCB.C.
> This
> > code has always checked for an exact match for DPCL_version between the
DPCL
> > super daemon and the client, and returning ASC_invalid_version if not
an
> exact
> > match.
> >
> > The only way I can see this occurring is if you are setting LIBPATH to
point
> > to a different version (3.2.6) of libdpcl.a while DPCL is installed at
3.2.5
> > level, or if you have somehow statically linked libdpcl.a with your
> > application. Could either be the case here?
> >
> > Dave
> >
> > Harald Servat Gelabert
> > <ha...@ce...> To: Dave
> > Wootton/Poughkeepsie/IBM@IBMUS
> > 10/31/2003 10:33 AM cc:
> > Subject: Re: [Dpcl-user]
> > ASC_invalid_version on 3.2.6 compiled
from
> > scratch
> >
> > Hello,
> >
> > > Harald
> > > I want to make sure I understand the problem you are seeing. My
> > > understanding is as follows
> > >
> > > DPCL 3.2.6 as packaged means that you are using the DPCL code from
the
> > > 3.2.6 installp image which contains the DPCL binaries only.
> > > DPCL 3.2.6 compiled means that you downloaed the compressed source
tar
> > > file and compiled DPCL on your system, then used that version.
> > > If you use a DPCL client compiled/lined with the DPCL 3.2.6 library
that
> > > you compiled, it works only with DPCL daemons that are also at the
3.2.6
> > > level. DPCL 3.2.5 daemons do not work.
> > >
> > > Is this correct?
> >
> > Yes, it is. I also checked versions with Ais_version and DPCLversion
(from
> > version.h) and both of them seem to return the correct version number.
> >
> > > I suspect that the set of code updates are slightly different between
the
> > > DPCL 3.2.6 source and the installp image. I will try to check this
out
> > > once I can get time on my test systems.
> >
> > Ok, it will be fine if you can check it.
> >
> > >
> > > Dave
> > >
> >
> > Best regards and thanks,
> >
> > >
> > >
> > >
> > > Harald Servat Gelabert <ha...@ce...>
> > > Sent by: dpc...@ww...
> > > 10/29/2003 05:56 AM
> > >
> > > To: dpc...@os...
> > > cc:
> > > Subject: [Dpcl-user] ASC_invalid_version on 3.2.6
compiled
> > > from scratch
> > >
> > >
> > > Hello,
> > >
> > > We would upgrade our dpcl 3.2.5 to dpcl 3.2.6 on the IBM cluster we
have
> > > (AIX 5.1 as operating system). For test purposes we have upgraded one
> > > of the nodes to dpcl 3.2.6 and compiled dpcl 3.2.5 and 3.2.6 from
> > > scratch.
> > >
> > > When performing the tests, we obtain ASC_invalid_version when using
> > > a client tool using the compiled dpcl 3.2.6 against a node with
3.2.5.
> > > This problem does not arise when we compile the client tool in the
> > > upgraded node and execute the tool on a node with dpcl 3.2.5.
> > >
> > > As a briefing:
> > >
> > >
------------------------------------------------------------------------
> > > client--->> DPCL 3.2.6 (compiled) DPCL 3.2.6 (as
package)
> > >
------------------------------------------------------------------------
> > > daemon 3.2.5 Fails Works
> > >
------------------------------------------------------------------------
> > > daemon 3.2.6 Works Works
> > >
------------------------------------------------------------------------
> > > daemon 3.2.5 compiled Fails Works
> > >
------------------------------------------------------------------------
> > > daemon 3.2.6 compiled Works Works
> > >
------------------------------------------------------------------------
> > >
> > > When the client is compiled with any of both versions of DPCL 3.2.5
it
> > > does NOT expose this problem.
> > >
> > > So as to compile DPCLs I used configure, make depend and make.
> > >
> > > So, is it possible to obtain a compiled 3.2.6 version of DPCL without
> > > exposing this problem? And if so, how?
> > >
> > > Thanks,
> > >
> > > --
> > >
________________________________________________________________________
> > > Harald Servat Gelabert (harald at cepba dot upc dot es)
> > > o//o Centre Europeu de Paral.lelisme de Barcelona
CEPBA
> > > o//o WWW...: http://www.cepba.upc.es Tel: +34-93-401 74
23
> > > o//o e-mail: su...@ce... Fax: +34-93-401 25
77
> > > o//o CEPBA c/Jordi Girona, 1-3, M_dul D6. E-08034 Barcelona,
Catalunya
> > >
________________________________________________________________________
> > >
> > > The fundamental difference between Unix and Macintosh operating
system
> > > is that Unix was designed to please programmers, whereas the Mac was
> > > designed to please users. (Windows, on the other hand, was designed
to
> > > please accountants, but that's another story)
> > > -- from The UNIX haters handbook, page 163
> > > _______________________________________________
> > > Dpcl-user mailing list
> > > Dpc...@ww...
> > > http://www-124.ibm.com/developerworks/oss/mailman/listinfo/dpcl-user
> > >
>
> --
> ________________________________________________________________________
> Harald Servat Gelabert (harald at cepba dot upc dot es)
> o//o Centre Europeu de Paral.lelisme de Barcelona CEPBA
> o//o WWW...: http://www.cepba.upc.es Tel: +34-93-401 74 23
> o//o e-mail: su...@ce... Fax: +34-93-401 25 77
> o//o CEPBA c/Jordi Girona, 1-3, Mòdul D6. E-08034 Barcelona, Catalunya
> ________________________________________________________________________
>
> The fundamental difference between Unix and Macintosh operating system
> is that Unix was designed to please programmers, whereas the Mac was
> designed to please users. (Windows, on the other hand, was designed to
> please accountants, but that's another story)
> -- from The UNIX haters handbook, page 163
> _______________________________________________
> Dpcl-user mailing list
> Dpc...@ww...
> http://www-124.ibm.com/developerworks/oss/mailman/listinfo/dpcl-user
--
________________________________________________________________________
Harald Servat Gelabert (harald at cepba dot upc dot es)
o//o Centre Europeu de Paral.lelisme de Barcelona CEPBA
o//o WWW...: http://www.cepba.upc.es Tel: +34-93-401 74 23
o//o e-mail: su...@ce... Fax: +34-93-401 25 77
o//o CEPBA c/Jordi Girona, 1-3, Mòdul D6. E-08034 Barcelona, Catalunya
________________________________________________________________________
The fundamental difference between Unix and Macintosh operating system
is that Unix was designed to please programmers, whereas the Mac was
designed to please users. (Windows, on the other hand, was designed to
please accountants, but that's another story)
-- from The UNIX haters handbook, page 163
|