[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PVWave, IRIX and o32/n32 objects
- Subject: Re: PVWave, IRIX and o32/n32 objects
- From: "Adrian Clark" <adrian.clark(at)gecm.com>
- Date: 15 Oct 1999 09:50:00 GMT
- Newsgroups: comp.lang.idl-pvwave
- References: <01bf118d$d36e37e0$160b9482@basit47307033> <email@example.com>
- Xref: news.doit.wisc.edu comp.lang.idl-pvwave:16849
Thanks for your response.
Unfortunately compiling with the -o32 flag won't work as this will fail to
link in n32 objects from IRIS Explorer.
However, I recently discovered that PV-Wave v7.0 is compiled with n32 - so
my problem should be solved :-)
I don't know if this is of interest to you, but I understand that IDL 5.2.1
is built on n32 for IRIX (whereas 5.2 is o32), so perhaps this will help
with you applications.
firstname.lastname@example.org wrote in article <email@example.com>...
> In article <01bf118d$d36e37e0$160b9482@basit47307033>,
> "Adrian Clark" <firstname.lastname@example.org> wrote:
> > Dear All,
> > I am trying to compile a number of applications linking pvwave
> > objects/shared objects with objects from other products.
> > The difficulty I am encountering is that the PVWave objects are in o32
> > format while the objects from the other products are all in n32
> format. It
> > is impossible to combine these incompatible formats, and the only
> > way round would be if I could obtain PVWave n32 objects.
> > The last thing I heard was that VNI had no intention of releasing
> > objects in n32 format. Does anybody know if this is still the case?
> > n32 objects available under the recently released version 7.0 of
> > Thanks for any help.
> > apc
> Hi Adrian,
> I use IDL on a Silicon Graphics and had similar trouble recently
> when the operating system was upgraded to 6.2 (which meant n32). I had
> to re-compile my C programs with a flag for -o32. Then I was able to
> use them in IDL. Maybe this will work for you also.
> I heard that the standard for SG is going to be n32
> in the future so PVWAVE will eventually be forced to comply with it.
> IDL also isn't ready for it, as far as I know.
> There was some discussion on this group about this a while ago (Try
> doing a search for n32 and o32). This included someone who understood
> the problem more than I.
> Sent via Deja.com http://www.deja.com/
> Before you buy.