Re: C compiler path of GHC

"OBATA Akio" <[email protected]> writes:

> On Tue, 23 Apr 2013 23:27:21 +0900, Greg Troxel <[email protected]> wrote:
>
>> Isn't it just a build bug in ghc that it is using an absolute path, and
>> we should configure/patch it to use wrapper path instead?  We already have
>> wrappers for C, I thought.
>
> Then, result ghc binary will contain C wrapper in ${WRKDIR}.
> It is not expected situation.

I see.  so ghc wants to use the C compiler at *run* time, and your
concern is to somehow make that run-time compiler only see
libraries/etc. that were declared dependencies of the ghc package at
build time?   If so, it sounds like we need a way to install per-package
wrappers and the whole bl3 tree.

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr

_______________________________________________
pkgsrc-wip-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pkgsrc-wip-discuss

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (NetBSD)

iEYEARECAAYFAlF2qqgACgkQ+vesoDJhHiVRzgCdFLFeqCySHUZnCEoDdG8ELqJ5
1pMAoJ2ujXktzg9PrDiK1nw8WyQ9dhXf
=oP4c
-----END PGP SIGNATURE-----