emerge homeassistant-full : Argument list too long #190

New Issue

gcampagnoli · 2020-12-05T14:55:25+01:00

gcampagnoli commented

2020-12-05 14:55:25 +01:00

During emerge homeassistant-full, environment variables passed to ebuild exceed MAX_ARG_PAGES defined in kernel, and die with "Argument list too long"...

I changed the MAX_ARG_PAGES value in /usr/src/linux/include/linux/binfmts.h to 64
and recompiled the kernel as suggested by “Argument list too long”: How do I deal with it, without changing my command?

During emerge homeassistant-full, environment variables passed to ebuild exceed MAX_ARG_PAGES defined in kernel, and die with "Argument list too long"... I changed the MAX_ARG_PAGES value in /usr/src/linux/include/linux/binfmts.h to 64 and recompiled the kernel as suggested by [“Argument list too long”: How do I deal with it, without changing my command?](https://unix.stackexchange.com/questions/45583/argument-list-too-long-how-do-i-deal-with-it-without-changing-my-command#:~:text=In%20order%20to%20increase%20the,as%20you%20would%20do%20normally.)

onkelbeh self-assigned this 2020-12-05 17:36:48 +01:00

onkelbeh added the

Bug

label 2020-12-05 17:36:54 +01:00

onkelbeh commented

2020-12-05 18:00:30 +01:00

Last time I used this one (for tests) was around 0.114.x, will have to dig to see what exactly changed. Perhaps it simply grew over some limits.

Did it compile with MAX_ARG_PAGES 64?

The -full Ebuild should not be used for production anyway, use either app-misc/homeassistant-min or app-misc/homeassistant.

We could add more (needed) components to one of the others.

Last time I used this one (for tests) was around 0.114.x, will have to dig to see what exactly changed. Perhaps it simply grew over some limits. Did it compile with MAX_ARG_PAGES 64? The -full Ebuild should not be used for production anyway, use either app-misc/homeassistant-min or app-misc/homeassistant. We could add more (needed) components to one of the others.

gcampagnoli commented

2020-12-05 19:57:46 +01:00

Is not enough recompile the kernel, now is time of glibc, i will keep you updated, zzzZZZ, is a mini computer with an Intel Atom, maybe tomorrow I will know something

Yes it is, the environment variable passed to ebuild is over 170Kb length, with MAX_ARG_PAGES = 32 the max size is 128kb...

Now I finish to build maybe can be usefull to someone

Is not enough recompile the kernel, now is time of glibc, i will keep you updated, zzzZZZ, is a mini computer with an Intel Atom, maybe tomorrow I will know something Yes it is, the environment variable passed to ebuild is over 170Kb length, with MAX_ARG_PAGES = 32 the max size is 128kb... Now I finish to build maybe can be usefull to someone

👍 1

onkelbeh commented

2020-12-06 00:26:06 +01:00

Yes, I am very interested. The whole purpose of this Ebuild is to have the ability to test all components against others. If the -full Ebuild won't work anymore, testing would be a bit more difficult.

Especially with an Atom, why are you trying to use the 'fat' Ebuild?

I offered (in README.md) to add more integrations to the 'mid' Ebuild. All I need to know is that somebody is using it. This would also include better build testing for these integrations. Testing all 980 integrations (and the libraries they depend on) is far beyond my capabilities.

What kind of Atom are you using?

Yes, I am very interested. The whole purpose of this Ebuild is to have the ability to test all components against others. If the -full Ebuild won't work anymore, testing would be a bit more difficult. Especially with an Atom, why are you trying to use the 'fat' Ebuild? I offered (in README.md) to add more integrations to the 'mid' Ebuild. All I need to know is that somebody is using it. This would also include better build testing for these integrations. Testing all 980 integrations (and the libraries they depend on) is far beyond my capabilities. What kind of Atom are you using?

gcampagnoli commented

2020-12-10 12:48:59 +01:00

Hi, I am using an Intel(R) Atom(TM) x5-Z8350 CPU @ 1.44GHz, is on a mini pc Minisforum Z83-F, an 100$ computer.

I solved "Argument list too long" it wasnt about MAX_ARG_PAGES but in include/uapi/linux/binfmts.h

#define MAX_ARG_STRLEN (PAGE_SIZE * 32)

to change in

#define MAX_ARG_STRLEN (PAGE_SIZE * 64)

recompile kernel, reboot
emerge glibc

Now I am facing other errors but not this one

Hi, I am using an Intel(R) Atom(TM) x5-Z8350 CPU @ 1.44GHz, is on a mini pc Minisforum Z83-F, an 100$ computer. I solved "Argument list too long" it wasnt about MAX_ARG_PAGES but in include/uapi/linux/binfmts.h #define MAX_ARG_STRLEN (PAGE_SIZE * 32) to change in #define MAX_ARG_STRLEN (PAGE_SIZE * 64) recompile kernel, reboot emerge glibc Now I am facing other errors but not this one

gcampagnoli closed this issue

2020-12-10 12:49:06 +01:00

onkelbeh commented

2020-12-12 06:24:32 +01:00

Thanks for reporting.

onkelbeh referenced this issue

2021-06-30 18:11:07 +02:00

homeassistant openweathermap component need dev-python/pyowm-3.2.0 #217

Sign in to join this conversation.