TC 6 for x86 linux-kernel-sources-env.sh

[zhudock]

After downloading and running linux-kernel-sources-env.sh in TinyCore 6, I'm running into errors when trying to run

Code: [Select]

make menuconfig
It appears the ncurses libraries fail to load. I've confirmed they are installed. Could it be because they're in /usr/local/lib instead of /lib?  Is there something else going wrong here?

[Rich]

Hi zhudock
It would probably be helpful if you post the exact error message(s) you received.

[zhudock]

Here is the text of the errors. It looks like the system things ncurses is not installed. Indeed if I copy the ncurses libraries from /usr/local/lib to /lib a majority of the errors go away, but menuconfig still fails to load. Instead I get the 2nd error message shown below

Code: [Select]

tc@box:/usr/src/linux-3.16.6$ make menuconfig
  HOSTCC  scripts/kconfig/lxdialog/checklist.o
  HOSTCC  scripts/kconfig/lxdialog/inputbox.o
  HOSTCC  scripts/kconfig/lxdialog/menubox.o
  HOSTCC  scripts/kconfig/lxdialog/textbox.o
  HOSTCC  scripts/kconfig/lxdialog/util.o
  HOSTCC  scripts/kconfig/lxdialog/yesno.o
  HOSTCC  scripts/kconfig/mconf.o
  HOSTLD  scripts/kconfig/mconf
scripts/kconfig/mconf.o: In function `show_help':
mconf.c:(.text+0xa0e): undefined reference to `stdscr'
scripts/kconfig/lxdialog/checklist.o: In function `print_arrows':
checklist.c:(.text+0x3d): undefined reference to `wmove'
checklist.c:(.text+0x5a): undefined reference to `acs_map'
checklist.c:(.text+0x66): undefined reference to `waddch'
checklist.c:(.text+0x80): undefined reference to `waddnstr'
checklist.c:(.text+0x94): undefined reference to `wmove'
... break for more of the same ...
menubox.c:(.text+0xc47): undefined reference to `wrefresh'
menubox.c:(.text+0xc8b): undefined reference to `delwin'
menubox.c:(.text+0xc97): undefined reference to `delwin'
menubox.c:(.text+0x11c3): undefined reference to `waddch'
menubox.c:(.text+0x1266): undefined reference to `scrollok'
scripts/kconfig/lxdialog/menubox.o: In function `do_print_item':
menubox.c:(.text+0x1b7): undefined reference to `wrefresh'
scripts/kconfig/lxdialog/menubox.o: In function `print_buttons':
menubox.c:(.text+0x381): undefined reference to `wrefresh'
scripts/kconfig/lxdialog/menubox.o: In function `print_arrows.constprop.0':
menubox.c:(.text+0x4ab): undefined reference to `wrefresh'
collect2: error: ld returned 1 exit status
scripts/Makefile.host:127: recipe for target 'scripts/kconfig/mconf' failed
make[1]: *** [scripts/kconfig/mconf] Error 1
Makefile:545: recipe for target 'menuconfig' failed
make: *** [menuconfig] Error 2


Code: [Select]

tc@box:/usr/src/linux-3.16.6$ make menuconfig
  HOSTLD  scripts/kconfig/mconf
/usr/local/bin/ld: scripts/kconfig/mconf.o: undefined reference to symbol 'stdscr'
/usr/local/lib/libtinfow.so.5: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
scripts/Makefile.host:127: recipe for target 'scripts/kconfig/mconf' failed
make[1]: *** [scripts/kconfig/mconf] Error 1
Makefile:545: recipe for target 'menuconfig' failed
make: *** [menuconfig] Error 2

[Juanito]

If you manually prepare the kernel source, it works fine with the ncurses-dev extension

[KingTutt]

@zhudock
I can confirm that problem with tc 6.1. The output is the same and all required packages are present including ncurses-dev

@Juanitocan you give some more hints what you mean with "manually prepare the kernel source"? Juast running make clean, make prepare, make scripts does not solve the problem for me and without kernel source I'm not able to build and activate nouveau graphic driver.

[Juanito]

Code: [Select]

$ make mrproper
$ cp config-3.16.6-tinycore .config
$ make oldconfig

$ make prepare
$ make modules_prepare

$ gunzip Module.symvers-3.16.6-tinycore.gz
$ cp Module.symvers-3.16.6-tinycore.gz Module.symvers
$ make SUBDIRS=scripts/mod

[KingTutt]

ok, it seems that we are talking about two different aspects.
With the manually way you mentioned it is possible to compile the kernel, but what zhudock reported is the fact, that

Code: [Select]

make menuconfig is not working. So configuring the kernel to your needs is not possible.

e.g. what would be the manually way to activate kernel support/module for nouveau driver and compile it afterwards in order to integrate it into your system start?

[Juanito]

"make menuconfig" works for me and isn't the nouveau driver an out of tree module?

BTW, for a small change to the kernel config, you can edit the file directly.

[Juanito]

I take that back, I was using corepure64.

The ncurses-dev extension in the x86 repo appears to be missing the start-up script and the *config* files.

You can fix things temporarily by copying or symlinking the dev files from /usr/local to /usr

[KingTutt]

"make menuconfig" works for me and isn't the nouveau driver an out of tree module?

Unfortunately not. I thought that, too but looking into the kernel config file

Code: [Select]

CONFIG_DRM_NOUVEAU is not setTherefore KMS is not activated and than the xorg driver nouveau fails to load for X

[curaga]

It's in-tree, but rather unstable.

[KingTutt]

It's in-tree, but rather unstable.

Why unstable? Because of the relatively old kernel version 3.16?

[curaga]

Generally unstable in all versions. It's really recommended to use vesa or the Nvidia binary driver with those cards.

For example, every time Phoronix runs a nouveau test, there's new regressions, with old cards that should be supported like gf9 series suddenly not showing a picture, corruption, various bugs.

[KingTutt]

I take that back, I was using corepure64.

The ncurses-dev extension in the x86 repo appears to be missing the start-up script and the *config* files.

Is there another place where that has to be reported in order to get fixed or can you trigger the person responsible therefore?

You can fix things temporarily by copying or symlinking the dev files from /usr/local to /usr

Ugh, I assume my knowledge is not good enough to narrow down which files (may be plenty) would have to be symlinked in order to get it working. If it is foreseeable that package will be fixed in near future I will probable wait for a fix...

@curaga
Thx for the info regarding nouveau driver

[Juanito]

Is there another place where that has to be reported in order to get fixed or can you trigger the person responsible therefore?

Please the extension maintainer a pm to request a fix

Ugh, I assume my knowledge is not good enough to narrow down which files (may be plenty) would have to be symlinked in order to get it working.

You could always run the start-up script from the x86_64 version of the extension...