From: "Rick \"Zero_Chaos\" Farina" <zerochaos@gentoo.org>
To: "Raúl Porcel" <armin76@gentoo.org>, gentoo-catalyst@lists.gentoo.org
Cc: release@gentoo.org
Subject: [gentoo-catalyst] Re: Fwd: spaces in parameters
Date: Tue, 24 Jun 2014 22:27:13 -0400 [thread overview]
Message-ID: <53AA3381.8030406@gentoo.org> (raw)
In-Reply-To: <53A9AC32.90303@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06/24/2014 12:49 PM, Raúl Porcel wrote:
> I never got any answer from genkernel.
>
> Can we implement the workaround in catalyst somehow?
>
> Thanks
>
>
> -------- Original Message --------
> Subject: spaces in parameters
> Date: Wed, 21 Aug 2013 11:11:00 +0200
> From: Raúl Porcel <armin76@gentoo.org>
> To: gentoo-genkernel@lists.gentoo.org
> CC: release@gentoo.org
>
> Hi,
>
> when using catalyst, it passes some parameters to genkernel. Now it
> turns out I need to use some parameters with spaces in genkernel and
> seems it doesn't like them.
>
> Right now catalyst does something like this script:
>
> #######
> parm="--kernel-cc='gcc -m64'
> --kernel-config=/root/installcd-ibm-2.6.34.config all"
>
> genkernel ${parm}
> #######
>
> This returns:
> Error: Unknown option '-m64''!
>
> If we quote ${parm}, it returns the help.
>
>
> If we modify it a little:
>
> ######
> parm="--kernel-cc='gcc -m64'
> --kernel-config=/root/installcd-ibm-2.6.34.config"
>
> genkernel "${parm}" all
> ######
>
> It says it can't find the configuration file.
>
> A workaround i've found is:
>
> ######
> parm="--kernel-cc='gcc -m64'
> --kernel-config=/root/installcd-ibm-2.6.34.config all"
>
> echo "genkernel ${parm}" > /tmp/tmp.sh
> bash /tmp/tmp.sh
> ######
It kinda looks to me like you are abusing --kernel--cc for something
it's not meant for, which makes me think the "fix" is either doing it
right, or fixing genkernel. If you can work up a sane patch I'll drop
it in genkernel myself, but please hit me directly or I'll completely
miss it.
Thanks,
Zero
>
> Any ideas? If its too hard to fix, we can simply add this workaround on
> catalyst.
>
> Thanks
> ######
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJTqjOBAAoJEKXdFCfdEflKc2kQAKEuNMQ9E/PBrPncXi1GqBUL
tjQxXMh65/J3K+pV4Qi9ROjMgqZmjTY6uZFKd/egAef7wh9a1mT33huqyf8xxDhL
nRBp3Sw9CRSEMRYJOOHIvwVvrMUdnDem7wqikmIj7KsoT57Sq1Osx8hxQEy+2V+F
7S9uchZylTox136t5FAtcvQRjMqtbYGz2Y0QiuD+bGRfaqP19BG0vFFbx7gi123Q
8yHxoc0bMIE90d+Z6/7khuLIxKmbAzZnmE8FHFKWJ9a8j1pa84+Q1DLfo4dC60A1
eN1DAU0RfVHc016oBkkLlSaZalVW1C2FzyAzkpU9UJ1cGX2zoi+nQissDmUcTUog
g+8lZS+rLB4+1rcLLufxY0lddC1+i1TdES4dEXfNyPd2fL6d6C8S3Sam3oTXEi8N
nyJYmGWE/d5wWj0JIZqTI5uIG/z49jWTgVrANSU1JdSOHgdm9IL5DFSP8o7hyZ6Z
9oYytUt/tkGcMlSktUDhKJeJs/gkdnlokEffV0yoytYYFyHm9+UPNEX7Dpo6OPoN
lsxZE4TuGRc8XqIqhUID7QdYjRn9cehY/CtoCKURNJPrG5IYSvYcwPsygYvEka6T
798F5jTkqYjvW336dPlpn3s/sZS8Uq8YJQZSgTxDFcklK4S1hTRqmkafTh0+TKVv
1atgIZWvb2+yoC4tLcwi
=SWN5
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-06-25 2:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52148424.2040402@gentoo.org>
2014-06-24 16:49 ` [gentoo-catalyst] Fwd: spaces in parameters Raúl Porcel
2014-06-25 2:27 ` Rick "Zero_Chaos" Farina [this message]
2014-09-12 6:27 ` [gentoo-catalyst] " Raúl Porcel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53AA3381.8030406@gentoo.org \
--to=zerochaos@gentoo.org \
--cc=armin76@gentoo.org \
--cc=gentoo-catalyst@lists.gentoo.org \
--cc=release@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox