[gentoo-catalyst] Fwd: spaces in parameters

[gentoo-catalyst] Fwd: spaces in parameters

[Raúl Porcel]

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
######

Any ideas? If its too hard to fix, we can simply add this workaround on
catalyst.

Thanks
######

[gentoo-catalyst] Re: Fwd: spaces in parameters

[Rick "Zero_Chaos" Farina]

-----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-----

[gentoo-catalyst] Re: Fwd: spaces in parameters

[Raúl Porcel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/25/14 04:27, Rick "Zero_Chaos" Farina wrote:
> 
> 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
> 
> 

Regarding doing it right, let me explain why we're doing it that way,
maybe we can find some other way to do it correctly.

The ppc installcd has multiple kernels for different type of machines,
it has exactly 3 types of kernels, 2 64bit and 1 32bit. It uses a
stage3 ppc64 32ul to build the cd. Until last year ppc64 32ul used an
independent gcc(kgcc64) to build the kernel, so it could be called
with powerpc64-unknown-... to build the kernel.

However it switched to using a multilib gcc, so for building a 64bit
kernel it can use -m64.

gitweb for overlays is still down, so i can't post the link to the
spec file, but its this spec file:
releases/weekly/specs/ppc/ppc64/installcd-stage2-minimal.spec

Any suggestions are welcome.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlQSkkgACgkQuQc30/atMkAwUACfT24Rx1yvFKkuq+RQHBYUmfOL
ohsAn0pRmVh0ob2EgSHLfUF4SSgwBLYj
=DVnG
-----END PGP SIGNATURE-----