Aah, ignore this please. Somehow I missed the two other recent mail chains
about this very thing, and my patch only covers part of it anyways.--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
Fixes the following :
scripts/kconfig/menu.c: In function 'get_symbol_str':
scripts/kconfig/menu.c:590:18: warning: 'jump' may be used uninitialized in
this function [-Wmaybe-uninitialized]
jump->offset = strlen(r->s);
^
scripts/kconfig/menu.c:551:19: note: 'jump' was declar
Hi Michal.
Thanks for your report.
On Sat, Feb 02, 2008 at 06:29:59PM +0100, Michal Zachar wrote:
> I dont know if it was not reported yet or not fixed yet.
>
> It apeared about in version 2.6.20.xx or there about so it is broken already
> awhile.
>
> Problem:
>
> changing settings manualy se
I dont know if it was not reported yet or not fixed yet.
It apeared about in version 2.6.20.xx or there about so it is broken already
awhile.
Problem:
changing settings manualy seem to work. Where problem apears is that loading
alternate config file changes settings but on exit '.config' file
moment and consider the actual scale and impact of
the problem at hand.
Do "make menuconfig" with the .config you are normally using, count the
number of options that are visible, and ask yourself whether we can
really expect users to read the help texts for every single option shown.
Pe
> - So, which criteria influence whether HPET_EMULATE_RTC should be
> enabled on x86_64 or not?
If there is one it needs to be a runtime switch anyways.
>
> - In case that there is no compelling reason to disable it if its
> dependencies are satisfied, shouldn't it rather be invisible
I take the liberty to modify the CC list.
Paul Rolland wrote:
> Stefan Richter <[EMAIL PROTECTED]> wrote:
>> I assert that a Kconfig prompt (a visible Kconfig variable) _without_
>> help text is a bug.
>
> Here is an example from 2.6.34-rc6 :
> .config - Linux Kernel v2.6.23-rc6 Configuration
>
Hello Stefan,
On Sat, 15 Sep 2007 10:25:39 +0200
Stefan Richter <[EMAIL PROTECTED]> wrote:
> Paul Rolland wrote:
> > getting too much of "No help text available"
> > usually results in people no more reading the help text.
>
> I assert that a Kconfig prompt (a visible Kconfig variable) _without_
Paul Rolland wrote:
> getting too much of "No help text available"
> usually results in people no more reading the help text.
I assert that a Kconfig prompt (a visible Kconfig variable) _without_
help text is a bug.
--
Stefan Richter
-=-=-=== =--= -
http://arcgraph.de/sr/
-
To unsubscribe
tep back a moment and consider the actual scale and impact of
> > >> the problem at hand.
> Do "make menuconfig" with the .config you are normally using, count the
> number of options that are visible, and ask yourself whether we can
> really expect users to read th
Goswin von Brederlow wrote:
> Helge Hafting <[EMAIL PROTECTED]> writes:
>> Randy Dunlap wrote:
>>> NOTE: ATA enables basic SCSI support; *however*,
>>> 'SCSI disk support', 'SCSI tape support', or
>>> 'SCSI CDROM support' may also be needed,
>>> depending on your hardware configuration.
>
Adrian Bunk wrote:
> On Fri, Sep 14, 2007 at 05:37:37PM +0200, Stefan Richter wrote:
>> In
>> practice, this takes too much time, hence you take an existing .config
>> (yours or somebody else's) and go from there.
>
> Kconfig let's you start with the
Helge Hafting <[EMAIL PROTECTED]> writes:
> Randy Dunlap wrote:
>> On Fri, 7 Sep 2007 14:48:00 +0200 Folkert van Heusden wrote:
>>
>>
>>> Hi,
>>>
>>> Maybe it is a nice enhancement for make menuconfig to more explicitly
>>> give a
igrate to different drivers without
> >> reading Kconfig help texts.
> >
> > Nothing about the patch is only about migration.
> >
> > The same applies if you configure a kernel from scratch.
> >
> > Do "make menuconfig" with the .config
Nothing about the patch is only about migration.
>
> The same applies if you configure a kernel from scratch.
>
> Do "make menuconfig" with the .config you are normally using, count the
> number of options that are visible, and ask yourself whether we can
> really expe
wards users
> who are convinced that they can migrate to different drivers without
> reading Kconfig help texts.
Nothing about the patch is only about migration.
The same applies if you configure a kernel from scratch.
Do "make menuconfig" with the .config you are normally using,
Adrian Bunk wrote:
> On Sun, Sep 09, 2007 at 05:11:44PM -0400, Jeff Garzik wrote:
>> Let's step back a moment and consider the actual scale and impact of the
>> problem at hand.
>>
>> The vast majority of users are consumers of pre-compiled kernels, built by
>> People With Clue(tm), who figured t
Randy Dunlap wrote:
On Fri, 7 Sep 2007 14:48:00 +0200 Folkert van Heusden wrote:
Hi,
Maybe it is a nice enhancement for make menuconfig to more explicitly
give a pop-up or so when someone selects for example a sata controller
while no 'scsi-disk' support was selected?
I
On Sun, Sep 09, 2007 at 05:11:44PM -0400, Jeff Garzik wrote:
> Andi Kleen wrote:
>>> I can see where you're coming from, but logically, this is wrong.
>>> There's a huge slew of enterprise machines that only have DVD on SATA.
>> ... and enterprise systems don't really care about a few KB more of co
Andi Kleen wrote on 09-09-07 23:22:
When it costs 1 people half an hour to learn and correct this it
wasted 5000 hours of previous livetime.
^^ ^
Poor me. Here I am -- still waiting for my 15 minutes of fame in /this/ life...
;-)
bjd
-
To unsubscribe fr
On 09/10/2007 08:38 AM, Stefan Richter wrote:
Nevertheless we should try to arrange the menus in a way that makes
sense to as many people as possible. The difficulty is, different
environments call for different menu layouts, as your previous example
of SATA DVD-only boxes demonstrates.
Howeve
James Bottomley wrote:
> On Sun, 2007-09-09 at 23:22 +0200, Andi Kleen wrote:
>> When it costs 1 people half an hour to learn and correct this it
>> wasted 5000 hours of previous livetime.
>>
>> Besides there is no good reason to have ever learned this imho.
>
> The process of becoming an exp
On Sun, 2007-09-09 at 23:22 +0200, Andi Kleen wrote:
> > The current setup expresses the dependencies as they exist -- OPTIONAL
> > extras, and that is a problem once a year or so, when someone builds
>
> Disk support over SCSI/SATA is hardly an "optional extra". It's more the 99+%
> case.
Usin
> The current setup expresses the dependencies as they exist -- OPTIONAL
> extras, and that is a problem once a year or so, when someone builds
Disk support over SCSI/SATA is hardly an "optional extra". It's more the 99+%
case.
> their own kernel but must learn this fact anew.
When it costs 10
Andi Kleen wrote:
I can see where you're coming from, but logically, this is wrong.
There's a huge slew of enterprise machines that only have DVD on SATA.
... and enterprise systems don't really care about a few KB more of code.
In fact you definitely want to have SATA compiled in in case you n
> I can see where you're coming from, but logically, this is wrong.
> There's a huge slew of enterprise machines that only have DVD on SATA.
... and enterprise systems don't really care about a few KB more of code.
In fact you definitely want to have SATA compiled in in case you need
to recover th
On Sat, 2007-09-08 at 18:07 +0200, Andi Kleen wrote:
> Folkert van Heusden <[EMAIL PROTECTED]> writes:
>
> > Hi,
> >
> > Maybe it is a nice enhancement for make menuconfig to more explicitly
> > give a pop-up or so when someone selects for example a sat
Al Boldi wrote:
> Alan Cox wrote:
> > > I once sent a patch to make libata a submenu of scsi.
> >
> > Which is wrong
> >
> > Nakked-by: Alan Cox <[EMAIL PROTECTED]>
> >
> > The general comments about moving this stuff around and making it
> > clearer what sd/sr etc are nowdays are good but hiding l
Randy Dunlap wrote:
> On Sat, 08 Sep 2007 18:44:46 +0200 Stefan Richter wrote:
>> Randy Dunlap wrote:
>>> The problem with 'select' here is that it will enable BLK_DEV_SD,
>>> but if SCSI is not enabled, it will not become enabled -- i.e.,
>>> select does not follow the dependency chain. So usuall
Andi Kleen wrote:
> On Sat, Sep 08, 2007 at 08:30:06PM +0200, Stefan Richter wrote:
>> Andi Kleen wrote:
>>> when you've been using CONFIG_IDE before it is not completely
>>> obvious you need BLK_SD for your hard disk.
>> Switching to different drivers without reading the help text?
>> Tough.
>
>
On Sat, Sep 08, 2007 at 08:30:06PM +0200, Stefan Richter wrote:
> Andi Kleen wrote:
> > when you've been using CONFIG_IDE before it is not completely
> > obvious you need BLK_SD for your hard disk.
>
> Switching to different drivers without reading the help text?
> Tough.
The individual driver de
On Sat, 08 Sep 2007 18:52:35 +0200 Bodo Eggert wrote:
> BTW2: I think that menu needs very much reordering. "Block devices" should
> be renamed to "Other block devices", AGP support should belong into graphics
> support, and many other things I don't even know need to be pushed around.
> Even orde
Andi Kleen wrote:
> when you've been using CONFIG_IDE before it is not completely
> obvious you need BLK_SD for your hard disk.
Switching to different drivers without reading the help text?
Tough.
--
Stefan Richter
-=-=-=== =--= -=---
http://arcgraph.de/sr/
-
To unsubscribe from this list: se
Bodo Eggert wrote:
> The real problem is hiding devices attached to some controlers between
> one kind of the controllers. This has been correct whern they were bus-
> specific, but since they are now shared by three busses, they should get
> their own menu called "(S)ATA/USB/SCSI attached devices"
> I'd say that someone needs to use a vendor kernel, or at least
> begin with a vendor .config file...
Vendor kernels tend to compile forever and require initrds. For
just testing a kernel quickly compiling only a few drivers in
is much more convenient.
Also when you've been using CONFIG_IDE bef
On Sat, Sep 08, 2007 at 09:50:08AM -0700, Randy Dunlap wrote:
> On 08 Sep 2007 18:07:00 +0200 Andi Kleen wrote:
> > This has also bitten me one or two times. A reasonable way would
> > be to just select SD automatically for !EMBEDDED
>
> I'd say that someone needs to use a vendor kernel, or at lea
Al Boldi <[EMAIL PROTECTED]> wrote:
> Alan Cox wrote:
>> > I once sent a patch to make libata a submenu of scsi.
>>
>> Which is wrong
>>
>> Nakked-by: Alan Cox <[EMAIL PROTECTED]>
>>
>> The general comments about moving this stuff around and making it clearer
>> what sd/sr etc are nowdays are good
On Sat, 08 Sep 2007 18:44:46 +0200 Stefan Richter wrote:
> Randy Dunlap wrote:
> > Stefan Richter wrote:
> >> I am not a friend of 'select', but maybe the following actually helps.
> ...
> > The problem with 'select' here is that it will enable BLK_DEV_SD,
> > but if SCSI is not enabled, it will n
On 08 Sep 2007 18:07:00 +0200 Andi Kleen wrote:
> Folkert van Heusden <[EMAIL PROTECTED]> writes:
>
> > Hi,
> >
> > Maybe it is a nice enhancement for make menuconfig to more explicitly
> > give a pop-up or so when someone selects for example a sata control
Randy Dunlap wrote:
> Stefan Richter wrote:
>> I am not a friend of 'select', but maybe the following actually helps.
...
> The problem with 'select' here is that it will enable BLK_DEV_SD,
> but if SCSI is not enabled, it will not become enabled -- i.e.,
> select does not follow the dependency cha
Stefan Richter wrote:
(added Cc linux-ide)
Folkert van Heusden wrote:
A popup makes some sense, but I don't know if menuconfig knows how to
do popup warnings... and it needs to be done for all *configs,
not just menuconfig.
Maybe add a new type?
How about
comment "Note: 'SCSI disk support' is
On Sep 8 2007 17:03, Al Boldi wrote:
>Alan Cox wrote:
>> > I once sent a patch to make libata a submenu of scsi.
>>
>> Which is wrong
>>
>> Nakked-by: Alan Cox <[EMAIL PROTECTED]>
>>
>> The general comments about moving this stuff around and making it clearer
>> what sd/sr etc are nowdays are good
Folkert van Heusden <[EMAIL PROTECTED]> writes:
> Hi,
>
> Maybe it is a nice enhancement for make menuconfig to more explicitly
> give a pop-up or so when someone selects for example a sata controller
> while no 'scsi-disk' support was selected?
This has als
Alan Cox wrote:
> > I once sent a patch to make libata a submenu of scsi.
>
> Which is wrong
>
> Nakked-by: Alan Cox <[EMAIL PROTECTED]>
>
> The general comments about moving this stuff around and making it clearer
> what sd/sr etc are nowdays are good but hiding libata under SCSI will
> cause even
> I once sent a patch to make libata a submenu of scsi.
Which is wrong
Nakked-by: Alan Cox <[EMAIL PROTECTED]>
The general comments about moving this stuff around and making it clearer
what sd/sr etc are nowdays are good but hiding libata under SCSI will
cause even more confusion than it cures
On Fri, Sep 07, 2007 at 08:35:22AM -0700, Randy Dunlap wrote:
> On Fri, 7 Sep 2007 14:48:00 +0200 Folkert van Heusden wrote:
>
> > Hi,
> >
> > Maybe it is a nice enhancement for make menuconfig to more explicitly
> > give a pop-up or so when someone selects
Jan Engelhardt wrote:
> On Sep 8 2007 09:05, Stefan Richter wrote:
>> config ATA_SD
>> tristate "SATA/PATA HDD support (via SCSI disk support)"
>> depends on ATA
>> select BLK_DEV_SD
>> help
>>'SCSI disk support' is required to access SATA HDDs. It is
[...]
>>Yo
On Sep 8 2007 09:05, Stefan Richter wrote:
>config ATA
> [...]
>
>comment "Controller drivers"
>
>[...low-level drivers go here...]
>
>comment "Storage device drivers"
>
>config ATA_SD
> tristate "SATA/PATA HDD support (via SCSI disk support)"
> depends on ATA
> select BLK_
On Sep 8 2007 01:02, Jan Engelhardt wrote:
>On Sep 7 2007 21:38, Krzysztof Halasa wrote:
>>> Ok, but that's not the most common situaties. What I'm suggesting is a
>>> warning or a please note popup. Not neccessarily an error or refusing to
>>> continue thing.
>>
>>What IMHO makes sense is changin
(added Cc linux-ide)
Folkert van Heusden wrote:
A popup makes some sense, but I don't know if menuconfig knows how to
do popup warnings... and it needs to be done for all *configs,
not just menuconfig.
>>> Maybe add a new type?
>> How about
>> comment "Note: 'SCSI disk support' is r
Krzysztof Halasa wrote:
>> Ok, but that's not the most common situaties. What I'm suggesting is a
>> warning or a please note popup. Not neccessarily an error or refusing to
>> continue thing.
>
>What IMHO makes sense is changing all references to SCSI CDROM,
>SCSI DISK etc. to just CDROM, DISK, an
> >> I know that it's difficult to get people to read docs & help text,
> >> and maybe it is needed in more places, but CONFIG_ATA (SATA/PATA)
> >> help text says:
> >> NOTE: ATA enables basic SCSI support; *however*,
> >> 'SCSI disk support', 'SCSI tape support', or
> >> 'SCSI CDROM support'
On Sep 7 2007 21:38, Krzysztof Halasa wrote:
>> Ok, but that's not the most common situaties. What I'm suggesting is a
>> warning or a please note popup. Not neccessarily an error or refusing to
>> continue thing.
>
>What IMHO makes sense is changing all references to SCSI CDROM,
>SCSI DISK etc. t
Folkert van Heusden <[EMAIL PROTECTED]> writes:
> Ok, but that's not the most common situaties. What I'm suggesting is a
> warning or a please note popup. Not neccessarily an error or refusing to
> continue thing.
What IMHO makes sense is changing all references to SCSI CDROM,
SCSI DISK etc. to j
Folkert van Heusden wrote:
>> I know that it's difficult to get people to read docs & help text,
>> and maybe it is needed in more places, but CONFIG_ATA (SATA/PATA)
>> help text says:
>> NOTE: ATA enables basic SCSI support; *however*,
>> 'SCSI disk support', 'SCSI tape support', or
>> 'SCSI
> > Maybe it is a nice enhancement for make menuconfig to more explicitly
> > give a pop-up or so when someone selects for example a sata controller
> > while no 'scsi-disk' support was selected?
>
> I know that it's difficult to get people to read docs &
On Fri, 7 Sep 2007 14:48:00 +0200 Folkert van Heusden wrote:
> Hi,
>
> Maybe it is a nice enhancement for make menuconfig to more explicitly
> give a pop-up or so when someone selects for example a sata controller
> while no 'scsi-disk' support was selected?
I know t
> >Maybe it is a nice enhancement for make menuconfig to more explicitly
> >give a pop-up or so when someone selects for example a sata controller
> >while no 'scsi-disk' support was selected?
>
> Having no sd support is perfectly valid. Imagine a diskless boo
On Sep 7 2007 14:48, Folkert van Heusden wrote:
>
>Maybe it is a nice enhancement for make menuconfig to more explicitly
>give a pop-up or so when someone selects for example a sata controller
>while no 'scsi-disk' support was selected?
Having no sd support is perfectly val
Hi,
Maybe it is a nice enhancement for make menuconfig to more explicitly
give a pop-up or so when someone selects for example a sata controller
while no 'scsi-disk' support was selected?
Folkert van Heusden
--
Multi tail barnamaj mowahib li mora9abat attasjilat wa nataij awamir
figuration file for
> makeconfig and then save it without making any changes. The newly saved
> file has been restructured for 32bit. Does this sound like a bug?
did you set ARCH=x86_64 in the make menuconfig command too ?
Dave
--
http://www.codemonkey.org.uk
-
To unsubscribe from
27;linux-kernel@vger.kernel.org'
Subject: make menuconfig refuses to let CONFIG_X86_64=y and CONFIG_64BIT
remain
Hello I'm new to the list. In the process of using make menuconfig, I
used an older config(2.6.11) to start my new configuration (2.6.17) and
notice that original settings for CONFIG_
Hello I'm new to the list. In the process of using make menuconfig, I
used an older config(2.6.11) to start my new configuration (2.6.17) and
notice that original settings for CONFIG_X86_64=y and CONFIG_64BIT=y are
being over ridden and replace by CONFIG_M686=y setting and
CONFIG_X86_32=y
On Tue, 13 Feb 2007 09:17:51 + Dominic Newton wrote:
> Just a small issue with the latest kernel 2.6.20. When compiling make
> menuconfig our ncurses library is not being detected. I currently use
> 2.6.15 with no problem and comparing the 2 I found a script (
> scripts/kcon
Just a small issue with the latest kernel 2.6.20. When compiling make
menuconfig our ncurses library is not being detected. I currently use
2.6.15 with no problem and comparing the 2 I found a script (
scripts/kconfig/lxdialog/check-lxdialog.sh ) in the lxdialog directory
that checks for the
On Wed, Jul 27, 2005 at 02:14:00PM -0400, Keenan Pepper wrote:
> Quiet some silly warnings.
Applied, please add Signed-off-by for your next patch.
Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo inf
Quiet some silly warnings.
--- linux-2.6.13-rc3-mm2/scripts/lxdialog/dialog.orig.h 2005-07-27
13:59:02.389806392 -0400
+++ linux-2.6.13-rc3-mm2/scripts/lxdialog/dialog.h 2005-07-27
13:59:13.437126944 -0400
@@ -163,7 +163,7 @@
int dialog_checklist (const char *title, const char *prompt,
Hi,
On Wed, Mar 09, 2005 at 03:15:19PM +0100, Gustav Lidberg wrote:
> Hi
>
> There is a bug in "make menuconfig". If one chooses 386 or 486 for cpu
> type, CONFIG_X86_TSC=y is set in .config. This creates a kernel that is
> unbootable on 386. Testing shows that it
Hi
There is a bug in "make menuconfig". If one chooses 386 or 486 for cpu
type, CONFIG_X86_TSC=y is set in .config. This creates a kernel that is
unbootable on 386. Testing shows that it worked in 2.4.19, but is broken
from 2.4.20 onwards. Someone should definetely look into this
On Monday 14 February 2005 12:45, Roman Zippel wrote:
> On Mon, 14 Feb 2005, Nick Warne wrote:
> > So I can ignore the debug prints?
>
> Yes.
OK, thanks for your replies. I am since trying 2.6.10 again (with new GCC
version and system memory this time), and the messages do not appear in later
Hi,
On Mon, 14 Feb 2005, Nick Warne wrote:
> So I can ignore the debug prints?
Yes.
bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read t
On Monday 14 February 2005 12:12, you wrote:
> Hi,
>
> On Mon, 14 Feb 2005, Nick Warne wrote:
> > Are the optimize && ? lines normal?
>
> They are only debug prints, but I'm quite sure they are fixed in recent
> versions.
>
> > This is from a current tree that has an uptime of > 50 days
>
> Coul
Hi,
On Mon, 14 Feb 2005, Nick Warne wrote:
> Are the optimize && ? lines normal?
They are only debug prints, but I'm quite sure they are fixed in recent
versions.
> This is from a current tree that has an uptime of > 50 days
Could you specify "current tree"?
bye, Roman
-
To unsubscribe f
Hi all,
I only just noticed this, but been building kernel source for a long time. On
my 233 over ssh, it is a bit slow, and I just noticed this output when doing
a 'make menuconfig':
make[1]: `scripts/fixdep' is up to date.
scripts/kconfig/mconf arch/i386/Kconfig
optimize
On Thu, 2005-01-27 at 22:45 +0100, Timo Kamph wrote:
> I guess you did somthing like this:
>
> 2.6.7 -patch-> 2.6.8 -patch-> 2.6.8.1 -patch-> 2.6.9 -patch-> 2.6.10.
>
> And you didn't noticed that the 2.6.9 patch failed, because it is diffed
> against 2.6.8 and not 2.6.8.1!
You're perfectly rig
On Thu, 27 Jan 2005, Viktor Horvath wrote:
> Hello everybody,
>
> today I patched myself up from 2.6.7 vanilla to 2.6.10 vanilla, but
> after all patches succeeded, "make menuconfig" shows "v2.6.8.1
> Configuration". Even worse, a compiled kernel calls in hi
Viktor Horvath wrote:
Hello everybody,
today I patched myself up from 2.6.7 vanilla to 2.6.10 vanilla, but
after all patches succeeded, "make menuconfig" shows "v2.6.8.1
Configuration". Even worse, a compiled kernel calls in his bootlog
himself "2.6.8.1".
I guess you
On Thu, 27 Jan 2005, Viktor Horvath wrote:
Hello everybody,
today I patched myself up from 2.6.7 vanilla to 2.6.10 vanilla, but
after all patches succeeded, "make menuconfig" shows "v2.6.8.1
Configuration". Even worse, a compiled kernel calls in his bootlog
himself "2.6.
Hello everybody,
today I patched myself up from 2.6.7 vanilla to 2.6.10 vanilla, but
after all patches succeeded, "make menuconfig" shows "v2.6.8.1
Configuration". Even worse, a compiled kernel calls in his bootlog
himself "2.6.8.1". When installing the whole
I was trying to configure 2.4.5-ac21 when I ran into some problems. First
off i noticed this when I went to make menuconfig :
root@fire-eyes:/usr/src/linux # make menuconfig
rm -f include/asm
( cd include ; ln -sf asm-i386 asm)
make -C scripts/lxdialog all
make[1]: Entering directory `/usr/src
hi,
i encountered following err during make menuconfig/net device/10mbitcards
selection.
axel
---
Menuconfig has encountered a possible error in one of the kernel's
configuration files and is unable to continue. Here is the error
report:
Q> scripts/Menuconfig: MCmenu31: command n
>On Thu, 28 Jun 2001, f5ibh wrote:
>> make[4]: Entre dans le répertoire
>> `/usr/src/kernel-sources-2.4.5-ac20/drivers/pnp'
>> gcc -D__KERNEL__ -I/usr/src/kernel-sources-2.4.5-ac20/include -Wall
>> -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
>> -fno-strict-aliasing -fno-common -p
On Thu, 28 Jun 2001, f5ibh wrote:
> make[4]: Entre dans le répertoire
> `/usr/src/kernel-sources-2.4.5-ac20/drivers/pnp'
> gcc -D__KERNEL__ -I/usr/src/kernel-sources-2.4.5-ac20/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> -fno-strict-aliasing -fno-common -pipe -mp
nfigure and
which menu you were trying to enter when this error occurred.
make: *** [menuconfig] Erreur 1
If I try to compile this kernel with the .config from -ac19, I get the
following errors :
make[4]: Entre dans le répertoire
`/usr/src/kernel-sources-2.4.5-ac20/drivers/pnp'
gcc -D__
"Martin.Knoblauch" wrote:
>
>
> Not sure whether this is worth to put into the next release - maybe
> someone can spend two minutes to crosscheck.
>
This looks more complete.
lx/linux > diff -u scripts/Menuconfig.orig scripts/Menuconfig
--- scripts/Menuconfig.orig Thu May 17 17:19:21 2
Bjorn Wesen wrote:
>
> While we're on cosmetics... how about imprisonment for the person who
> chose yellow on light grey for the first letters in each option...
>
> /Bjorn
>
> On Thu, 17 May 2001, Martin.Knoblauch wrote:
> > this is most likely just a small issue. If I knew where to look, I
>
On Thu, 17 May 2001 16:07:40 +0200,
"Martin.Knoblauch" <[EMAIL PROTECTED]> wrote:
>This is a multi-part message in MIME format.
Please turn off MIME when sending to linux-kernel, especially those
useless vcards at the end of your mail.
> When I diff config files pocessed by "make [old]config" a
While we're on cosmetics... how about imprisonment for the person who
chose yellow on light grey for the first letters in each option...
/Bjorn
On Thu, 17 May 2001, Martin.Knoblauch wrote:
> this is most likely just a small issue. If I knew where to look, I
> would try to fix it and submit a p
Hi,
this is most likely just a small issue. If I knew where to look, I
would try to fix it and submit a patch :-)
When I diff config files pocessed by "make [old]config" and "make
menueconfig", it seems that menuconfig is not writing out some of the
"comments" that the other versions do write.
"Joachim Backes wrote:"
> I made an update from Kernel 2.2.19 to 2.4.4, and I made
> a copy from the 2.2.19 .config file into the 2.4.4 directory.
>
> After that, I was wondering about the following fact:
>
> "make menuconfig" for kernel 2.4.4 showed (what
I made an update from Kernel 2.2.19 to 2.4.4, and I made
a copy from the 2.2.19 .config file into the 2.4.4 directory.
After that, I was wondering about the following fact:
"make menuconfig" for kernel 2.4.4 showed (what seems to
be correct) for ATA/IDE the same kernel configuration,
Hi!
If I do a make distclean then make menuconfig, I get the following error
message on the "Processor type and features --->" entry (maybe a bit
corrupted because I had to do a ctrl_c to avoid the curses display to
owerwrite it). The other entries seems to be ok :
scrip
when I use make menuconfig on the /usr/src/linux directory which linux
was symbolic link to /usr/src/linux-2.4.3 , I can see menu , but when I
press space or enter key will exit menu and show follow message :
Menuconfig has encountered a possible error in one of the kernel's
configur
I need
to do a 'make menuconfig' even though I don't make any changes in it, or
the subsequent
'make dep' fails. Maybe this is well-known, but it struck me as odd.
My 700Mhz Duron w/128M ram stalled thrashing once. After 20 mins, I did
a ctl-alt-del and it was still swapp
On Fri, Jan 05, 2001, Keith Owens <[EMAIL PROTECTED]> wrote:
> On Fri, 5 Jan 2001 02:42:11 -0200,
> Fr d ric L . W . Meunier <[EMAIL PROTECTED]> wrote:
> >Is this just me? Configuring 2.4.0 with make menuconfig with
> >CONFIG_EXPERIMENTAL=y I get no prompt fo
On Fri, 5 Jan 2001 02:42:11 -0200,
Fr d ric L . W . Meunier <[EMAIL PROTECTED]> wrote:
>Is this just me? Configuring 2.4.0 with make menuconfig with
>CONFIG_EXPERIMENTAL=y I get no prompt for USB Mass Storage,
>but the .config is saved with # CONFIG_USB_STORAGE is not set
CONFIG
Is this just me? Configuring 2.4.0 with make menuconfig with
CONFIG_EXPERIMENTAL=y I get no prompt for USB Mass Storage,
but the .config is saved with # CONFIG_USB_STORAGE is not set
I have the following:
#
# USB support
#
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set
CONFIG_USB_DEVICEFS=y
97 matches
Mail list logo
