From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hartmut Goebel Subject: Re: Difference between search-paths and native-search-path Date: Sat, 26 Aug 2017 11:20:16 +0200 Message-ID: <0a1c045c-4c4b-ba05-b6fd-9994a741e859@crazy-compilers.com> References: <3af1bc90-9218-f45c-bd90-9632b744e352@crazy-compilers.com> <87d17kvzt9.fsf@elephly.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------623B84F850A82921B2B97E8F" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56317) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dlXGR-0006uN-Vl for guix-devel@gnu.org; Sat, 26 Aug 2017 05:20:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dlXGO-0007LD-Qb for guix-devel@gnu.org; Sat, 26 Aug 2017 05:20:23 -0400 Received: from mail-out.m-online.net ([212.18.0.9]:51114) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dlXGO-0007L4-Fz for guix-devel@gnu.org; Sat, 26 Aug 2017 05:20:20 -0400 In-Reply-To: <87d17kvzt9.fsf@elephly.net> Content-Language: en-US List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ricardo Wurmus Cc: guix-devel This is a multi-part message in MIME format. --------------623B84F850A82921B2B97E8F Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am 25.08.2017 um 10:04 schrieb Ricardo Wurmus: >> what is the difference between search-paths and native-search-path? T= he >> manual describes search-paths at [1], but native-search-paths are only >> named at [2] without any description. > =E2=80=9Cnative-search-paths=E2=80=9D are used when cross-building. Th= e arm eabi > cross-compiler, for example, declares CROSS_C_INCLUDE_PATH and > CROSS_LIBRARY_PATH as a native search path, because these are needed > when cross-building applications for the arm eabi target. Thanks. Does this mean: - native-search-paths are set when building a packages, They are constructed based on the native-inputs only. - search-paths are set when installing a package, based on all inputs. These paths are *not* available then builiding the package. Is this correct? What happens if $KLM_PATH is defined as "native-search-path" by package A and defined as "search-path" by package B? --=20 Regards Hartmut Goebel | Hartmut Goebel | h.goebel@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible | --------------623B84F850A82921B2B97E8F Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Am 25.08.2017 um 10:04 schrieb Ricardo Wurmus:
what is  the difference between search-paths and n=
ative-search-path? The
manual describes search-paths at [1], but native-search-paths are only
named at [2] without any description.

=E2=80=9Cnative-search-paths=E2=80=9D are used when =
cross-building.  The arm eabi
cross-compiler, for example, declares CROSS_C_INCLUDE_PATH and
CROSS_LIBRARY_PATH as a native search path, because these are needed
when cross-building applications for the arm eabi target.

Thanks. Does this mean:

- native-search-paths are set when building a packages, They are constructed based on the native-inputs only.

- search-paths are set when installing a package, based on all inputs. These paths are *not* available then builiding the package.

Is this correct?

What happens if $KLM_PATH is defined as "native-search-path" by package A and defined as "search-path" by package B?

--=20
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com   =
            |
| www.crazy-compilers.com | compilers which you thought are impo=
ssible |
--------------623B84F850A82921B2B97E8F--