From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: "Mauricio R. Perez - Centro de Computos"
<mauricio_perez@pergamino.gov.ar>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel argument list too long
Date: Thu, 26 Aug 2004 22:04:33 +0200 [thread overview]
Message-ID: <20040826200433.GS18334@lug-owl.de> (raw)
In-Reply-To: <008601c48b84$d7211530$643caf0a@pergamino.gov.ar>
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
On Thu, 2004-08-26 12:53:33 -0300, Mauricio R. Perez - Centro de Computos <mauricio_perez@pergamino.gov.ar>
wrote in message <008601c48b84$d7211530$643caf0a@pergamino.gov.ar>:
> Kernel limitation of argument list it's a problem, not for things I do, else
> is for things that others do, i "need" to compile aubit4gl, but configure
> gives me Argument List Too long, and I need to have more memory for
> arguments, how can y solve this?
> kernel: 2.6.7
> gcc: 3.3.2
$ vi .../linux-2.6.x/include/linux/binfmts.h +/MAX_ARG_PAGES
However, another fix would be to limit the size of supplied arguments,
possibly by placing the source files not into a deep directory (thus
avoiding long absolute paths) etc.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-08-26 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 15:53 kernel argument list too long Mauricio R. Perez - Centro de Computos
2004-08-26 17:56 ` Arthur Perry
2004-08-26 20:04 ` Jan-Benedict Glaw [this message]
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=20040826200433.GS18334@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mauricio_perez@pergamino.gov.ar \
/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