fortran and octave

fortran and octave

[Alain2210]

Hello,

I would like to bitbake octave for org.openembedded.dev.
But octave needs fortran ou f2c.
It seems that fortran has been remove from gcc-cross_4.1.2.bb (or perhaps
before).
So I have tried to
1) add fortran in gcc-cross_4.1.2.bb but I get an error.
2) compile octave with f2c without success. (even with the f2c of the host)

So what is the good way to compile octave and/or fortran and/or f2c ?

Thanks,

Alain

Re: fortran and octave

[Koen Kooi]

Alain2210 schreef:
> Hello,
> 
> I would like to bitbake octave for org.openembedded.dev.
> But octave needs fortran ou f2c.
> It seems that fortran has been remove from gcc-cross_4.1.2.bb (or perhaps
> before).
> So I have tried to
> 1) add fortran in gcc-cross_4.1.2.bb but I get an error.
> 2) compile octave with f2c without success. (even with the f2c of the host)
> 
> So what is the good way to compile octave and/or fortran and/or f2c ?

For gcc 3.4 through 4.1.x fortran is broken for arm (gcc ICEs on compiling gcc), Lennert
Buytenhek had some patches for it, I don't know if they fix and and if yes, I don't know
if they are in 4.2.1. I'm firing of a build of 4.2.1 with fortran enabled anyway :)

regards,

Koen

Re: fortran and octave

[Alain2210]

Selon Koen Kooi <koen@dominion.kabel.utwente.nl>:

> Alain2210 schreef:
> > Hello,
> >
> > I would like to bitbake octave for org.openembedded.dev.
> > But octave needs fortran ou f2c.
> > It seems that fortran has been remove from gcc-cross_4.1.2.bb (or perhaps
> > before).
> > So I have tried to
> > 1) add fortran in gcc-cross_4.1.2.bb but I get an error.
> > 2) compile octave with f2c without success. (even with the f2c of the host)
> >
> > So what is the good way to compile octave and/or fortran and/or f2c ?
>
> For gcc 3.4 through 4.1.x fortran is broken for arm (gcc ICEs on compiling
> gcc), Lennert
> Buytenhek had some patches for it, I don't know if they fix and and if yes, I
> don't know
> if they are in 4.2.1. I'm firing of a build of 4.2.1 with fortran enabled
> anyway :)
>

Thanks for the quick answer. I will try 4.2.1

Sincerely,

Alain

Re: fortran and octave

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Koen Kooi schreef:
> Alain2210 schreef:
>> Hello,
>>
>> I would like to bitbake octave for org.openembedded.dev.
>> But octave needs fortran ou f2c.
>> It seems that fortran has been remove from gcc-cross_4.1.2.bb (or perhaps
>> before).
>> So I have tried to
>> 1) add fortran in gcc-cross_4.1.2.bb but I get an error.
>> 2) compile octave with f2c without success. (even with the f2c of the host)
>>
>> So what is the good way to compile octave and/or fortran and/or f2c ?
> 
> For gcc 3.4 through 4.1.x fortran is broken for arm (gcc ICEs on compiling gcc), Lennert
> Buytenhek had some patches for it, I don't know if they fix and and if yes, I don't know
> if they are in 4.2.1. I'm firing of a build of 4.2.1 with fortran enabled anyway :)

Same old, same old:

/media/hda4/OE/build/tmp-new/angstrom/work/armv5te-angstrom-linux-uclibcgnueabi/gcc-cross-4.2.1-r4/gcc-4.2.1/libgfortran/generated/_mod_i8.F90:
In function 'specific__mod_i8':
/media/hda4/OE/build/tmp-new/angstrom/work/armv5te-angstrom-linux-uclibcgnueabi/gcc-cross-4.2.1-r4/gcc-4.2.1/libgfortran/generated/_mod_i8.F90:42:
internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFG8B3GMkyGM64RGpERAqU7AKCp1z6hELV18erP+dMbhPayd/GhxgCcDMcN
+3tocngg8sZuIC30inMy5SM=
=xCvQ
-----END PGP SIGNATURE-----

Re: fortran and octave

[Alain2210]

Hello,


>
/media/hda4/OE/build/tmp-new/angstrom/work/armv5te-angstrom-linux-uclibcgnueabi/gcc-cross-4.2.1-r4/gcc-4.2.1/libgfortran/generated/_mod_i8.F90:
> In function 'specific__mod_i8':
>
/media/hda4/OE/build/tmp-new/angstrom/work/armv5te-angstrom-linux-uclibcgnueabi/gcc-cross-4.2.1-r4/gcc-4.2.1/libgfortran/generated/_mod_i8.F90:42:
> internal compiler error: Segmentation fault

Yes, I get exactly the same error. Now I compile the 4.2.1. So I have too wait
to see if it works.

Thanks,

Alain

Re: fortran and octave

[Alain2210]

Hello,

> Same old, same old:
>
>
/media/hda4/OE/build/tmp-new/angstrom/work/armv5te-angstrom-linux-uclibcgnueabi/gcc-cross-4.2.1-r4/gcc-4.2.1/libgfortran/generated/_mod_i8.F90:
> In function 'specific__mod_i8':
>
/media/hda4/OE/build/tmp-new/angstrom/work/armv5te-angstrom-linux-uclibcgnueabi/gcc-cross-4.2.1-r4/gcc-4.2.1/libgfortran/generated/_mod_i8.F90:42:
> internal compiler error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://gcc.gnu.org/bugs.html> for instructions.

So gcc-cross_4.2.1 with this patch
http://gcc.gnu.org/ml/gcc-patches/2007-05/msg01010.html
is compiling.... (but I get a probleme in staging).

So I wonder if I can patch also the 4.1.2 or if I have to rebuild all my oe
tree....

By the way, the angstrom distribution and the openembedded tree are very usefull
and in a state that allow to make a quite stable image for my h2200.

Thanks,

Alain

Re: fortran and octave

[Alain2210]

Hello,

> So gcc-cross_4.2.1 with this patch
> http://gcc.gnu.org/ml/gcc-patches/2007-05/msg01010.html
> is compiling.... (but I get a probleme in staging).

With this patch and FORTRAN = ",fortran" in gcc_4.1.2.bb,
Building of gcc-cross__4.1.2.bb works and gfortran is working.

Now, I'm building octave.

Sincerely,

Alain

Re: fortran and octave

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alain2210 schreef:
> Hello,
> 
>> So gcc-cross_4.2.1 with this patch
>> http://gcc.gnu.org/ml/gcc-patches/2007-05/msg01010.html
>> is compiling.... (but I get a probleme in staging).
> 
> With this patch and FORTRAN = ",fortran" in gcc_4.1.2.bb,
> Building of gcc-cross__4.1.2.bb works and gfortran is working.

Thanks for testing it! I made 2 commits that enable building and packaging for (lib)gfortran.

> Now, I'm building octave.

you need to have my second commit to get octave working on the device, because it wasn't
getting packaged.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFG8PiEMkyGM64RGpERAobpAJ4n5Qw7as8OXEQvxgOJ+CiFtAa+3QCcD2/O
2naKPgHeoIrx9HJE6uKcmLM=
=gSGl
-----END PGP SIGNATURE-----

Re: fortran and octave

[Alain2210]

Hello,

> > With this patch and FORTRAN = ",fortran" in gcc_4.1.2.bb,
> > Building of gcc-cross__4.1.2.bb works and gfortran is working.
>
> Thanks for testing it! I made 2 commits that enable building and packaging
> for (lib)gfortran.

Thanks. I will try them.

>
> > Now, I'm building octave.
>
> you need to have my second commit to get octave working on the device,
> because it wasn't
> getting packaged.
>
Before using it, I need to build it. But octave_2.1.71.bb does not compile for
gcc 4.1 (and
probably above) :
http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2006-March/001246.html
It should be upgrade to octave_2.1.73. I have not build it but copying
octave_2.1.71.bb
to octave_2.9.14.bb I have build octave_2.9.14 (with a small problem with
qa_staging
and now ipk is void...).

Thanks,

Alain

Re: fortran and octave

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Koen Kooi schreef:

> you need to have my second commit to get octave working on the device, because it wasn't
> getting packaged.
> 

'it' being libgfortran of course, not octave.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFG8QOqMkyGM64RGpERAtLpAJ9SWSAmJYHfVS68EuqtzKivvn/RRgCgnAm+
M+8A6BdPNV2TgfNvayHErQ4=
=Eork
-----END PGP SIGNATURE-----

Re: fortran and octave

[Alain2210]

Hello,

> > you need to have my second commit to get octave working on the device,
> because it wasn't
> > getting packaged.
> >
>
> 'it' being libgfortran of course, not octave.

Thanks, now I can build and use octave. The 2.1.71 does not build.

I have tried two versions : the latest stable one :
2.1.73 (I have only duplicated the octave_2.1.71.bb to octave_2.1.73.bb)
and the 2.9.14 (which is in the way of version 3). I have had some probleme with
install step
of build 2.9.14.

But on my h2200 the 2.9.14 is not usable. So the good version seems to be
2.7.13.

Sincerely,

Alain