1 |
I've just tried: |
2 |
|
3 |
# USE=-ldap emerge gnupg |
4 |
|
5 |
and got a compilation failure (wrong format of parameters passed to |
6 |
functions). So I created a file thus: |
7 |
|
8 |
# cat /etc/portage/env/app-crypt/gnupg |
9 |
CFLAGS=${CFLAGS//-combine} |
10 |
|
11 |
and tried again and got the same result. |
12 |
|
13 |
Just to be sure, I emerged gnupg with the ldap USE flag and that same env |
14 |
file, and it worked ok. I thought it should, since that's the same as the |
15 |
existing version. Next I changed the env file thus: |
16 |
|
17 |
# cat /etc/portage/env/app-crypt/gnupg |
18 |
CFLAGS="-march=k8 -O2 -pipe" |
19 |
CXXFLAGS="${CFLAGS}" |
20 |
|
21 |
Now gnupg compiled just fine with USE=-ldap. So now I suppose I have a lot |
22 |
of CFLAGS to juggle to find out which one hurts gnupg so that I can report |
23 |
it. Unless anyone else has already done the work, of course... |
24 |
|
25 |
-- |
26 |
Rgds |
27 |
Peter |
28 |
-- |
29 |
gentoo-amd64@g.o mailing list |