From: augustus@linuxhardware.org
To: Ciaran McCreesh <ciaranm@gentoo.org>
Cc: linux-kernel@vger.kernel.org, tseng@gentoo.org,
jnagyjr@joseph-a-nagy-jr.homelinux.org
Subject: Re: vim doesn't like the command line
Date: Mon, 19 Jul 2004 09:57:41 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0407190956070.29213@penguin.linuxhardware.org> (raw)
In-Reply-To: <20040717233654.102579e1@snowdrop.home>
Thanks for that link. I'll see if I can produce anything helpful. This
is an odd one but it may be header related. Someone (possibly me), should
try building using the 2.6.8-r1 headers. The odd thing here though is
that vim is the only app that seems to be affected. Got any others?
Thanks,
Kris Kersey (Augustus)
LinuxHardware.org Site Manager
augustus@linuxhardware.org
Gentoo Linux AMD64 Developer
augustus@gentoo.org
On Sat, 17 Jul 2004, Ciaran McCreesh wrote:
> On Wed, 14 Jul 2004 23:44:16 -0400 (EDT) augustus@linuxhardware.org
> wrote:
> | This is odd but it seems that vim 6.3 does not function properly with
> | kernel 2.6.8-rc1. It will not take command line arguement filenames.
> | No matter what you pass it, it always goes to the file browser. This
> | is not the case with 2.6.7 kernels. Any ideas? I have attached my
> | kernel .config.
>
> I've been trying to track this down as well. Kinda tricky, since it
> WORKSFORME(TM). The following may be of help to you:
>
> http://bugs.gentoo.org/show_bug.cgi?id=57378
>
> Basically, argv is getting nuked by something.
>
> Seems rebuilding without a -march in CFLAGS fixes it for some people,
> reason unknown...
>
> --
> Ciaran McCreesh : Gentoo Developer (Sparc, MIPS, Vim, Fluxbox)
> Mail : ciaranm at gentoo.org
> Web : http://dev.gentoo.org/~ciaranm
>
>
prev parent reply other threads:[~2004-07-19 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 3:44 augustus
2004-07-15 3:44 ` augustus
2004-07-17 22:36 ` Ciaran McCreesh
2004-07-17 23:19 ` Joseph A. Nagy, Jr.
2004-07-19 13:57 ` augustus [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=Pine.LNX.4.58.0407190956070.29213@penguin.linuxhardware.org \
--to=augustus@linuxhardware.org \
--cc=ciaranm@gentoo.org \
--cc=jnagyjr@joseph-a-nagy-jr.homelinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tseng@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
all inboxes | Powered by JetHome®