In the last mail Chris Rutter said:
> On Tue, 11 May 1999, Philip Blundell wrote:
>
> > You probably want to keep them as armv4l-linux, and no I don't think there
> > should be a symlink. What actually lives in these directories, and what knows
> > about their location?
>
> Architecture-dependent bits of PERL, as far as I can see. Except
> hardly dependent between armv*.
If you've got dynamic loading the .so (or equivalent files) go in the
architecture dependent libraries. As do all the modules compiled from
extensions (whether statically or dynamicly linked), a copy of all .h files
so that you can compile further extensions without needing to keep the perl
source tree, and the perl configuration for that architecture (Config.pm, which
I believe contains a compiled config.sh)
> I certainly don't see any point in segregating `armv*' just for a load
> of PERL which AFAICT is identical across any ARM platform.
Hmm. I think it is correct that perl will be identical on any ARM (32 bit ?)
platform. However, I think you can achieve this by answering the questions
about "where do you want the architecture dependent libraries to go?" as
blah-blah-arm rather than blah-blah-armv4l at ./Configure time.
Nick
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
