2237 2012-04-04 01:13:49 +0000 ncurses build failure 2012-05-04 21:53:59 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 1.3.1 x86 x86_64 RESOLVED NOTABUG Medium normal 1.1.2 1 415fox sgw jessica.zhang meta.mr.watcher meta.watcher scott.a.garman --- --- --- oldest_to_newest 19843 0 415fox 2012-04-04 01:13:49 +0000 So this is my first day playing with yocto project. I downloaded poky-edison-6.0.1 on my up-to-date Ubuntu 11.10 machine and just tried to build core-image-minimal for qemu following the tutorial. I did not get very far ... The build was failing on ncurses-native. I traced it back to the file: ./meta/recipes-core/ncurses/ncurses.inc Around line 128 it tries to steal some terminfo files from my build system: for x in console dumb linux rxvt screen sun vt{52,100,102,200,220} xterm-color xterm-xfree86 Actually, the original line has the terminal "ansi" listed and removing it is what fixes the problem. Ubuntu doesn't presently provide "ansi" in /usr/share/terminfo/a although they do provide like 200 other terminals starting with the letter a. I don't know why they got rid of that one, the arbitrary bastards. Anyway, I think the larger issue here is that ncurses should be built one of two ways: 1. Use the perfectly good ncurses that I have installed on my build system. This failure takes place when bitbake is still working on the toolchain, so if you want to use stuff on my system, like ncurses, that's fine with me. 2. Build ncurses from scratch and provide all of the sources including the terminfo files like Ubuntu does in their ncurses-term package. What's not okay is to build ncurses from source but also try to steal a few supporting files off my system. Because maybe they're not there. Another point I'd like to address was that this was really hard to trace back. I mean, this is my first day working with yocto but come on. I'm getting python tracebacks on screen, I'm getting logs from make, but the bug is in this ncurses.inc file and there's no indication of that in any of the output. Really I'd be fine if no one ever fixed the ncurses build issue and just found a way to let me know which line of which script it was trying to do when it borked. Then I could fix it myself. 20750 1 sgw 2012-04-20 00:52:08 +0000 (In reply to comment #0) > So this is my first day playing with yocto project. I downloaded Welcome to the Yocto Project, sorry it took a while to respond to this, we have been in release mode trying to tackle some issues. > poky-edison-6.0.1 on my up-to-date Ubuntu 11.10 machine and just tried to build > core-image-minimal for qemu following the tutorial. I did not get very far ... > > The build was failing on ncurses-native. I traced it back to the file: > ./meta/recipes-core/ncurses/ncurses.inc > > Around line 128 it tries to steal some terminfo files from my build system: > for x in console dumb linux rxvt screen sun vt{52,100,102,200,220} > xterm-color xterm-xfree86 > If I am understanding you, you are looking at the "do_install()" function in the ncurses.inc file, you will notice that it's finding files and install all relative to ${D}, which is the local root in the build area, it's not taking anything from your system directly. > Actually, the original line has the terminal "ansi" listed and removing it is > what fixes the problem. > > Ubuntu doesn't presently provide "ansi" in /usr/share/terminfo/a although they > do provide like 200 other terminals starting with the letter a. I don't know > why they got rid of that one, the arbitrary bastards. > BTW: On my machine, I have NO files in /usr/share/terminfo and have no issues building ncurses-native > Anyway, I think the larger issue here is that ncurses should be built one of > two ways: > > 1. Use the perfectly good ncurses that I have installed on my build system. > This failure takes place when bitbake is still working on the toolchain, so if > you want to use stuff on my system, like ncurses, that's fine with me. We build a known version of ncurses in order to be sure we have a tested and known working build. > 2. Build ncurses from scratch and provide all of the sources including the > terminfo files like Ubuntu does in their ncurses-term package. > It should be doing this; building from scratch and providing all the terminfo files directly. > What's not okay is to build ncurses from source but also try to steal a few > supporting files off my system. Because maybe they're not there. > > Another point I'd like to address was that this was really hard to trace back. > I mean, this is my first day working with yocto but come on. I'm getting python > tracebacks on screen, I'm getting logs from make, but the bug is in this > ncurses.inc file and there's no indication of that in any of the output. > It would be great to get the output logs and python tracebacks, this should all build out of the box. If you can repeat and attach your failures that would be very helpful. We are trying hard to address some of the exception handling and traceback issues. I look forward to seeing some attached logs, if you still have them. > Really I'd be fine if no one ever fixed the ncurses build issue and just found > a way to let me know which line of which script it was trying to do when it > borked. Then I could fix it myself. I build ncurses-native all the time on a 11.10 machine, so I am not sure what you ran into. 21121 2 sgw 2012-05-04 21:53:59 +0000 I am closing this as not a bug, If you still have this problem, please re-open this issue and attch any logs and python execptions.