1 |
On 11/23/2010 04:27 AM, Jeffrey Ratcliffe wrote: |
2 |
> On 23 November 2010 10:04, Jeffrey Ratcliffe |
3 |
> <jeffrey.ratcliffe@×××××.com> wrote: |
4 |
>> Cairo is complaining that is can't link with -lpthread or -pthread, |
5 |
>> therefore configures with pthread: no, meaning that the compile fails, |
6 |
>> telling me to define CAIRO_NO_MUTEX to 1. I have put the complete |
7 |
>> build log on pastebin[1]. |
8 |
> |
9 |
> It must be an environment problem, as if I cd to the work directory |
10 |
> and retry exactly the same configure command, then pthreads are found. |
11 |
> And indeed |
12 |
> |
13 |
> $ LDFLAGS="" emerge cairo |
14 |
> |
15 |
> succeeds, but is very hacky, and I can't seem to find a setting for |
16 |
> etc/portage/env/x11-libs/cairo to replicate it. |
17 |
> |
18 |
> Moving on, I have similar problems with gtk+ and libXi, which is, of |
19 |
> course, present on the host. Unfortunately, the above trick doesn't |
20 |
> work here. |
21 |
> |
22 |
> So, how can I get emerge to additionally use libraries from the host? |
23 |
> Writing ebuilds to maintain symlinks to libraries in /lib feels wrong. |
24 |
> |
25 |
> Regards |
26 |
> |
27 |
> Jeff |
28 |
> |
29 |
|
30 |
You really shouldn't *need* to set per-package LDFLAGS. You also |
31 |
shouldn't use "additional libraries from the host" as that is asking for |
32 |
trouble. It is difficult to debug a specific system on the ML, can you |
33 |
open a bug report for the failing package and attach the build.log |
34 |
instead of linking to a pastebin that will eventually expire? |
35 |
-Jeremy |