[solved] Errors when building a kernel
On Sat, 22 Aug 2015 22:54:22 +0200, I wrote: >Tom's hint is useful, menuconfig's search option does the trick, I >seemingly got rid of MPILIB=m. > >Thank you. Thank you Tom :) I was able to build the kernel packages and the Wily install currently runs the kernel successfully. [weremouse@moonstudio ~]$ uname -a Linux moonstudio 3.10.61-rt65-1-moonstudio #1 SMP PREEMPT RT Sun Aug 23 02:13:10 CEST 2015 x86_64 x86_64 x86_64 GNU/Linux In edition I needed to "disable" CONFIG_MEGARAID CONFIG_PCH_GBE Building was done in around 1½ hours, from Sun Aug 23 02:00:09 to Sun Aug 23 03:28:47 CEST 2015. [weremouse@moonstudio ~]$ /etc/init.d/rtirq status PID CLS RTPRIO NI PRI %CPU STAT COMMAND 441 FF 90 - 130 0.0 Sirq/18-snd_hdsp 547 FF 85 - 125 0.0 Sirq/20-snd_ice1 566 FF 84 - 124 0.0 Sirq/21-snd_ice1 [snip] [weremouse@moonstudio src]$ grep CONFIG_X86 config-3.10.61-rt65-1-rt-lts_x86_64.Arch_Linux_original|head -n3 CONFIG_X86_64=y CONFIG_X86=y CONFIG_X86_64_SMP=y [weremouse@moonstudio src]$ grep CONFIG_X86 /boot/config-3.10.61-rt65-1-moonstudio|head -n3 CONFIG_X86_64=y CONFIG_X86=y CONFIG_X86_64_SMP=y [weremouse@moonstudio src]$ diff config-3.10.61-rt65-1-rt-lts_x86_64.Arch_Linux_original /boot/config-3.10.61-rt65-1-moonstudio 3c3 < # Linux/x86 3.10.61 Kernel Configuration --- > # Linux/x86_64 3.10.61 Kernel Configuration 52c52 < CONFIG_LOCALVERSION="-1-rt-lts" --- > CONFIG_LOCALVERSION="-1-moonstudio" 162c162 < CONFIG_CHECKPOINT_RESTORE=y --- > # CONFIG_CHECKPOINT_RESTORE is not set 321d320 < CONFIG_ASN1=m 1734c1733 < CONFIG_SCSI_ADVANSYS=m --- > # CONFIG_SCSI_ADVANSYS is not set 1738,1740c1737,1739 < CONFIG_MEGARAID_MAILBOX=m < CONFIG_MEGARAID_LEGACY=m < CONFIG_MEGARAID_SAS=m --- > # CONFIG_MEGARAID_MAILBOX is not set > # CONFIG_MEGARAID_LEGACY is not set > # CONFIG_MEGARAID_SAS is not set 2179c2178 < CONFIG_PCH_GBE=m --- > # CONFIG_PCH_GBE is not set 4116,4117c4115 < CONFIG_DRM_I915=m < CONFIG_DRM_I915_KMS=y --- > # CONFIG_DRM_I915 is not set 5186c5184 < CONFIG_R8187SE=m --- > # CONFIG_R8187SE is not set 5192,5193c5190,5191 < CONFIG_RTL8192E=m < CONFIG_R8712U=m --- > # CONFIG_RTL8192E is not set > # CONFIG_R8712U is not set 5207,5208c5205,5206 < CONFIG_WLAGS49_H2=m < CONFIG_WLAGS49_H25=m --- > # CONFIG_WLAGS49_H2 is not set > # CONFIG_WLAGS49_H25 is not set 6040,6042c6038 < CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE=m < CONFIG_PUBLIC_KEY_ALGO_RSA=m < CONFIG_X509_CERTIFICATE_PARSER=m --- > # CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE is not set 6125d6120 < CONFIG_CLZ_TAB=y 6128d6122 < CONFIG_MPILIB=m Build with [root@moonstudio src]# export CONCURRENCY_LEVEL=2;wget https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.10.61.tar.gz https://www.kernel.org/pub/linux/kernel/projects/rt/3.10/older/patch-3.10.61-rt65.patch.gz && tar zxf linux-3.10.61.tar.gz && mv linux-3.10.61 linux-3.10.61-rt65 && cd linux-3.10.61-rt65 && gzip -dc ../patch-3.10.61-rt65.patch.gz | patch -p1 && cp ../config-3.10.61-rt65-1-rt-lts.01.edit .config && make oldconfig && make menuconfig && make oldconfig && date && make-kpkg clean && make-kpkg --initrd kernel-image kernel-headers && make-kpkg clean && date Regards, Ralf -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Jump start help needed.
On Sun, Aug 23, 2015 at 08:49:42AM +0530, Vishnu Vivekanand wrote: > a. The kind of programming I have done is that I am given access to a > code base repository from where I download the entire codebase. Once I > am assigned a bug I look into the code file that has the highest > likelihood of being the home of that bug and once I have ascertained > the same, I go ahead and correct/fix the code/bug. This transfers well to what's called "upstream development": working on a single part of the system in conjunction with its primary maintainers, who occasionally make releases that then flow "downstream" to distributions such as Ubuntu. It does not necessarily transfer well to development of a distribution, where the key point is integration of many packages into a coherent whole. Of course some of the same skills apply, but people from a single-code-base background tend to find that they have to become much better at quickly finding and navigating unfamiliar code bases. > b. As far as what I have seen here, I need to download > packages/tarballs, then install them. I have even went through > tutorials of modifying code files using nano/vi/gedit editors, learnt > to update changelogs, package/unpackage changes, create binary files > (.deb). That sort of thing is certainly important: it's bread-and-butter development routine. > I have also learnt the process of development in Ubuntu viz., take up > bugs from Harvest --> find out if they have been already fixed by > debian/future releases of Ubuntu or if someone else is already working > on it --> if not, fix the bug --> update changelog, create package and > request any Ubuntu Member to sponsor the fix. I wouldn't call Harvest part of "the" process - it's one tool that may be useful for some people to find bugs to work on, and if it works well for you then great, but don't get hung up on it being the place to expect to find everything. Also, only people with upload access (Ubuntu developers) can sponsor fixes, not the wider group of Ubuntu members. > Now my questions here are > > 1. Is it wise to look for the entire code base and browse > through all code files to understand the landscape of what I am > getting into? The entire code base for Ubuntu is ENORMOUS. I don't think that approach will tell you very much. If you're talking about individual packages, perhaps, although it's not a very efficient approach in general if you plan to work on more than a very small number of packages: it's better to hone the skill of finding the parts you need without having to browse through everything. It may be a useful approach in the very early stages when you're still trying to get the hang of how source packages tend to be laid out. > 2. Once I have a bug assigned to me, how do I go about > identifying the exact location of fix? Don't expect anyone to "manage" you and assign you bugs: that's not how it works, unless you're a paid developer and thus somebody is actually employed to tell you what to do. (Even then, paid developers don't usually need to have somebody micromanage every bug they choose to work on.) As for the main body of your question, you're asking how to perform a fundamentally skilled and creative task which varies substantially depending on the details of the bug, so there's no short answer. In no particular order, strategies include: * searching for things such as error messages in the code and guessing from there * using language-appropriate debugging tools to debug directly via tracebacks etc. * using static analysis tools (compilers with warnings turned all the way up to 11, things like cppcheck, etc.) to find mechanically-analysable problems that might contribute to the bug * using instrumentation frameworks (e.g. valgrind) to run code in an environment that can help track down problems where the cause is distant from the symptom * building unit tests that exhibit the bug you're trying to track down so that you don't have to run the full program to trigger it and so that you can help ensure that it doesn't come back after being fixed * investigating other bug reports on a similar subject, possibly in upstream bug trackers or other distributions * plain old experience of diagnosing many similar bugs Lots of packages are relatively easy to start work on given an appropriate base skill set (general familiarity with Ubuntu development, experience in the implementation language(s) in question, etc.). Some are very specialised and it may be better to diagnose the bug as accurately as you can and hand over to an expert. Collaboration is an important skill for Ubuntu developers too: we cannot work in glorious isolation. > 3. Is there one central package that I need to download and > lookup files/directories within it for possible location(s) of > fix? No. Ubuntu is a distribution: it is assembled out of many packages, some of which (e.g. most of the Un
Re: Jump start help needed.
hi, Am Samstag, den 22.08.2015, 18:01 +0530 schrieb Vishnu Vivekanand: > I have a few years of programming in the Windows environment. I have > just started to explore the Unix/Linux/Ubuntu world. I have been > spending a week or two around the Ubuntu home page and I am not able > to get started in programming. Using some tutorials I have been able > to, no further than, run some commands to setup the development > toolkit for Ubuntu development. I request some assistance in > transitioning into the Ubuntu world of programming, at least upto a > point where I understand where-to-get-what to get to submitting actual > code here. Any help/pointers would be most appreciated. > there are wikipages at https://wiki.ubuntu.com/UbuntuDevelopment and https://wiki.ubuntu.com/ContributeToUbuntu#Writing_Code that should cover the very basics. what exactly are you interested in working on (do you want to develop apps on ubuntu, do you rather want to work on packaging, do you want to fix bugs, etc)? the community team has created a nice little interactive guide for finding the documentation and contacts for right area of your interests at http://community.ubuntu.com/contribute/find-a-task/#!/toplevel/develop/null if you want to work directly on ubuntu i would also advise to get a launchpad account on launchpad.net, this is essential for any bug work (and for some ubuntu projects for submitting code) many of the more direct development conversations usually happen on IRC channels on irc.freenode.net. if you found your area of interest i'd recommed to lurk a little in the respective channels to get familiar with the team working on this specific part of ubuntu. welcome aboard :) ciao oli -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Errors when building a kernel
On Sat, Aug 22, 2015 at 9:56 AM, Ralf Mardorf wrote: > On Sat, 22 Aug 2015 08:32:35 -0400, Tom H wrote: >> >> There's nothing difficult with "make menuconfig" because you can >> search for a specific config value with "/" except that you like to >> ask for help but never seem to like the advice that's given. > > This is the first reply to help me with the issue ;). > > So I can search for "CONFIG_MPILIB" and likely will find what options I > need to check and/or uncheck to get rid of it? > > Thank you. You're welcome. The search'll give you the path to get to and set/unset the option. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: [solved] Errors when building a kernel
On Sun, Aug 23, 2015 at 4:04 AM, Ralf Mardorf wrote: > On Sat, 22 Aug 2015 22:54:22 +0200, I wrote: >> Tom's hint is useful, menuconfig's search option does the trick, I >> seemingly got rid of MPILIB=m. >> >>Thank you. > > Thank you Tom :) You're welcome. > I was able to build the kernel packages and the Wily install currently > runs the kernel successfully. Good :) > [weremouse@moonstudio ~]$ uname -a > Linux moonstudio 3.10.61-rt65-1-moonstudio #1 SMP PREEMPT RT Sun Aug 23 > 02:13:10 CEST 2015 x86_64 x86_64 x86_64 GNU/Linux > > In edition I needed to "disable" > > CONFIG_MEGARAID > CONFIG_PCH_GBE Dependencies... > Build with > > [root@moonstudio src]# export CONCURRENCY_LEVEL=2;wget > https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.10.61.tar.gz > https://www.kernel.org/pub/linux/kernel/projects/rt/3.10/older/patch-3.10.61-rt65.patch.gz > && tar zxf linux-3.10.61.tar.gz > && mv linux-3.10.61 linux-3.10.61-rt65 > && cd linux-3.10.61-rt65 && gzip -dc ../patch-3.10.61-rt65.patch.gz | patch > -p1 > && cp ../config-3.10.61-rt65-1-rt-lts.01.edit .config > && make oldconfig && make menuconfig && make oldconfig > && date > && make-kpkg clean && make-kpkg --initrd kernel-image kernel-headers && > make-kpkg clean > && date Thanks. Much more clear! -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
