installing 3.04

[Roger Mason]

Hello,

I'm trying to install AMRITAv3.04_R30-06-2009 on a linux machine:

Linux pyrope 2.6.30-gentoo-r5 #10 SMP Sun Nov 15 08:31:36 NST 2009
x86_64 Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz GenuineIntel GNU/Linux

I ran ./AMRITAsystem -verbose -check all after editing which-gcc and
that succeeded. However the next step fails:

**********************
failed to build Amrita
**********************
src3p::perl ok!
src3p::mpeg failed!
src3p::origami failed!
plugin::amrita ok!
plugin::amr_sol ok!
plugin::foo ok!
amrmake:
Consult Chapter 3 of Amrita's installation notes and try again.

I can't find the installation notes mentioned in the output. I remember
from installing amrita on a different machine this summer that the
problem with origami is likey to do with libtermcap, but the mpeg error
is new to me.

Thanks for any help.

Roger

[James Quirk]

Roger,

> I ran ./AMRITAsystem -verbose -check all after editing which-gcc and
> that succeeded. However the next step fails:
>
> **********************
> failed to build Amrita
> **********************
> src3p::perl ok!
> src3p::mpeg failed!
> src3p::origami failed!
> plugin::amrita ok!
> plugin::amr_sol ok!
> plugin::foo ok!
> amrmake:
> Consult Chapter 3 of Amrita's installation notes and try again.
>
> I can't find the installation notes mentioned in the output. I remember
> from installing amrita on a different machine this summer that the
> problem with origami is likey to do with libtermcap, but the mpeg error
> is new to me.

To see how the builds are failing, you can run:

amrmake -verbose src3p::origami
amrmake -verbose src3p::mpeg

and as you note, src3p::origami is almost certainly missing libtermcap. I
suspect the problem with src3p::mpeg is that it's a 32-bit build on a
64-bit system. For instance, on my machine I have to backtrack to gcc-4.2
(from 4.3) when doing a 32-bit build owing to an internal bug in gcc. This
is done automatically via the callback file:

$AMRITA/SYSTEM/Linux/x86_64/which-gcc

which contains:

$g77 = 'gfortran-4.3';
$gcc = 'gcc-4.3';
$gxx = 'g++-4.3';
$g2c = 'gfortran';

if($word eq '32') {
$gcc = 'gcc-4.2'; # gcc-4.3 is broken!
}

In any event, src3p::mpeg is not critical to AMRITA's operation, so you
can safely ignore the problem. Moreover, it's worth noting that AMRITA's
mpeg functionality will likely soon be deprecated as the generation of
SWF's is a better route for adding animations to PDF's.

James

>
> Thanks for any help.
>
> Roger
>

> --
>
> You received this message because you are subscribed to the Google Groups "amrita-ebook" group.
> To post to this group, send email to amrita...@googlegroups.com.
> To unsubscribe from this group, send email to amrita-ebook...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/amrita-ebook?hl=en.
>
>

[James Quirk]

Roger,

On Mon, 30 Nov 2009, Roger Mason wrote:

> I built a libtermcap.a using my system package installer & gcc-4.3. It
> was built as 64 bit (as far as I know). However, when I try to build
> origami & mpeg amrita looks for gcc-4.2. I could install gcc-4.2, but I'm
> curious as to why amrita thinks it should build these parts in 32 bit
> mode. In other words, where does the value of '$word' in which-gcc come
> from?
If you take a look at the file:

$AMRITA/src3p/origami/amrita.make

you'll see a line:

CC = amrcc -word 32 -def $(DEFS) -ar $(libORIGAMI) -ccsrc ccsrc

The option "-word 32" sets the value of $word which then causes
which-gcc to select gcc-4.2 rather than gcc-4.3 .

This is done because Origami does not work with 64-bit pointers.
For a variety of reasons, I've not had a chance to track down the problem.
I will do so when the matter becomes more urgent.

In the mean time, I'm working on a folding-editor that can be added
directly to a PDF document. I've reached the stage where I have the
outline of a source-browser. For example, attached is a PDF that contains
the full source for src3p::origami. The next step is to allow the text to
be edited. This work is currently on hold, however, owing to some bugs in
the Linux version of Adobe Reader's Flash Player which messes up keyboard
input. Nevertheless, the path I'm going down, and the reasons for it,
should be reasonably clear.

James