This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: What should be the prefix for the platform specific package

From: querbach at realtime dot bc dot ca (David Querbach)
To: Ruslan <ruslank at softhome dot net>
Cc: crossgcc <crossgcc at sources dot redhat dot com>
Date: Wed, 19 Jun 2002 09:10:01 -0700
Subject: Re: What should be the prefix for the platform specific package
References: <134121823265.20020618202625@softhome.net>

> I build my projects for several cross-platforms on PC Linux RedHat 6.2.
> So I want to make the optimal dir-tree.

> When I build and install binutils with following configuration:
> configure --target=mipsel-linux --prefix=/usr/local/mipsel-linux ...

> The question is:
> If the prefix will:
> --prefix=/usr/local
> what will happen with native libraries in:
> /usr/local/lib
> that have the same name as the cross-specific libraries?

They shouldn't be touched.  Target-specific libraries (such as those
generated by cross-building newlib) will end up in
/usr/local/mipsel-linux/lib, and the accompanying include files will end up 
in /usr/local/mipsel-linux/include.

You will see a few additions to /usr/local/lib, but these are bfd libraries 
which can be used to build specialized cross-development tools.

Regards,

David Querbach
Real-Time Systems Inc.

Attachment: msg00068/pgp00000.pgp
Description: PGP signature

References:
- What should be the prefix for the platform specific package
  - From: Ruslan

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]