1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 06/24/2014 12:49 PM, Raúl Porcel wrote: |
5 |
> I never got any answer from genkernel. |
6 |
> |
7 |
> Can we implement the workaround in catalyst somehow? |
8 |
> |
9 |
> Thanks |
10 |
> |
11 |
> |
12 |
> -------- Original Message -------- |
13 |
> Subject: spaces in parameters |
14 |
> Date: Wed, 21 Aug 2013 11:11:00 +0200 |
15 |
> From: Raúl Porcel <armin76@g.o> |
16 |
> To: gentoo-genkernel@l.g.o |
17 |
> CC: release@g.o |
18 |
> |
19 |
> Hi, |
20 |
> |
21 |
> when using catalyst, it passes some parameters to genkernel. Now it |
22 |
> turns out I need to use some parameters with spaces in genkernel and |
23 |
> seems it doesn't like them. |
24 |
> |
25 |
> Right now catalyst does something like this script: |
26 |
> |
27 |
> ####### |
28 |
> parm="--kernel-cc='gcc -m64' |
29 |
> --kernel-config=/root/installcd-ibm-2.6.34.config all" |
30 |
> |
31 |
> genkernel ${parm} |
32 |
> ####### |
33 |
> |
34 |
> This returns: |
35 |
> Error: Unknown option '-m64''! |
36 |
> |
37 |
> If we quote ${parm}, it returns the help. |
38 |
> |
39 |
> |
40 |
> If we modify it a little: |
41 |
> |
42 |
> ###### |
43 |
> parm="--kernel-cc='gcc -m64' |
44 |
> --kernel-config=/root/installcd-ibm-2.6.34.config" |
45 |
> |
46 |
> genkernel "${parm}" all |
47 |
> ###### |
48 |
> |
49 |
> It says it can't find the configuration file. |
50 |
> |
51 |
> A workaround i've found is: |
52 |
> |
53 |
> ###### |
54 |
> parm="--kernel-cc='gcc -m64' |
55 |
> --kernel-config=/root/installcd-ibm-2.6.34.config all" |
56 |
> |
57 |
> echo "genkernel ${parm}" > /tmp/tmp.sh |
58 |
> bash /tmp/tmp.sh |
59 |
> ###### |
60 |
|
61 |
It kinda looks to me like you are abusing --kernel--cc for something |
62 |
it's not meant for, which makes me think the "fix" is either doing it |
63 |
right, or fixing genkernel. If you can work up a sane patch I'll drop |
64 |
it in genkernel myself, but please hit me directly or I'll completely |
65 |
miss it. |
66 |
|
67 |
Thanks, |
68 |
Zero |
69 |
|
70 |
> |
71 |
> Any ideas? If its too hard to fix, we can simply add this workaround on |
72 |
> catalyst. |
73 |
> |
74 |
> Thanks |
75 |
> ###### |
76 |
> |
77 |
> |
78 |
> |
79 |
|
80 |
-----BEGIN PGP SIGNATURE----- |
81 |
Version: GnuPG v2.0.22 (GNU/Linux) |
82 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
83 |
|
84 |
iQIcBAEBAgAGBQJTqjOBAAoJEKXdFCfdEflKc2kQAKEuNMQ9E/PBrPncXi1GqBUL |
85 |
tjQxXMh65/J3K+pV4Qi9ROjMgqZmjTY6uZFKd/egAef7wh9a1mT33huqyf8xxDhL |
86 |
nRBp3Sw9CRSEMRYJOOHIvwVvrMUdnDem7wqikmIj7KsoT57Sq1Osx8hxQEy+2V+F |
87 |
7S9uchZylTox136t5FAtcvQRjMqtbYGz2Y0QiuD+bGRfaqP19BG0vFFbx7gi123Q |
88 |
8yHxoc0bMIE90d+Z6/7khuLIxKmbAzZnmE8FHFKWJ9a8j1pa84+Q1DLfo4dC60A1 |
89 |
eN1DAU0RfVHc016oBkkLlSaZalVW1C2FzyAzkpU9UJ1cGX2zoi+nQissDmUcTUog |
90 |
g+8lZS+rLB4+1rcLLufxY0lddC1+i1TdES4dEXfNyPd2fL6d6C8S3Sam3oTXEi8N |
91 |
nyJYmGWE/d5wWj0JIZqTI5uIG/z49jWTgVrANSU1JdSOHgdm9IL5DFSP8o7hyZ6Z |
92 |
9oYytUt/tkGcMlSktUDhKJeJs/gkdnlokEffV0yoytYYFyHm9+UPNEX7Dpo6OPoN |
93 |
lsxZE4TuGRc8XqIqhUID7QdYjRn9cehY/CtoCKURNJPrG5IYSvYcwPsygYvEka6T |
94 |
798F5jTkqYjvW336dPlpn3s/sZS8Uq8YJQZSgTxDFcklK4S1hTRqmkafTh0+TKVv |
95 |
1atgIZWvb2+yoC4tLcwi |
96 |
=SWN5 |
97 |
-----END PGP SIGNATURE----- |