Re: [Plplot-devel] netbsd portability effort status--- one showstopper and 3 other problems

[<jc...@fe...>]

On Wednesday 26 March 2003 15:33, Alan W. Irwin wrote:
| On Wed, 26 Mar 2003, [iso-8859-1] Jo=E3o Cardoso wrote:
| > On Wednesday 26 March 2003 03:05, Alan W. Irwin wrote:
| > | Have you been able to build octave on your OSF1 system?
| >
| > I have not tried, but the system mkoctfile says:
| > : ${SH_LD=3D"c++"}
| > : ${SH_LDFLAGS=3D"-shared -Xlinker -expect_unresolved -Xlinker '*'"}
|
| At least these flags are not near-empty like on netbsd so there is
| some hope you will be able to build octave on OSF1.

I really don't know how the netbsd packager was able to link octave with=20
those options, as "g++" links with "-lstdc++", which "ld" does not.

|  Anyhow, I
| suggest you do that experiment so that at least we can claim the
| octave interface to plplot works on at least one Unix system before
| the release.

The problem is that the system has gcc-3.0.3

Octave 2.0.xx needs gcc-2.8/9.xx while octave-2.1.4x needs gcc > 3.0.x
I tried to compile octave-2.0.17, 2.1.40 and 2.1.46. None succeeded.

I could try to compile gcc-3.2.2, but I probably would need to compile=20
other tools as well. As I use this machine just to test Plplot, I don't=20
think it is worth the effort.

If a system has octave, than it can have plplot_octave. This is for=20
sure.
This is not true in this particular machine because the gcc version that=20
was used to compile octave (gcc-2.8.0) was removed by the system adm=20
when he upgrade to gcc-3.0.3
 I could try to add a further test to configure, trying to compile a=20
hello.cc into a hello.oct, but I don't think it to be necessary.

I attach a small file that you can try to compile in the bsd machine=20
with "mkoctfile hello.cc" and then call from octave as "hello". It=20
works in my system with octave-mkoctfile-2.0.16/17-2.1.36/43.
If it works, then I will widthdraw my "This is for sure" comment above=20
:-)

Joao