On 09/08/2015 09:52 AM, hosein bahari wrote: hi peter thanks for your emails know i can run my code by replacing with hello_world code . what i want next is automatically running my code when the board boots up . what should i do ? i dont want to face with compiling kernel by myself and i want to do sth using ltib (a way witch needs few information about linux ) . is there any way? i tried the ltib choice : "load these modules at boot" and i entered /usr/bin/hello but it said module /usr/bin/hello not found . could you plz help me? thanks
modules are just that - kernel modules. What you want to do is to modify skel package (via ./ltib -p skel -m prep) and then edit rpm/build/skell-*/etc/rc.d/rc.local and add a command "/usr/bin/hello" to run /usr/bin/hello in the background. Once you make the change, then "./ltib -p skel" should rebuild skel (if it finds you modified a file in rpm/BUILD/skell-*/) and re-deploy to the rootfs image. Give it a whirl. If it works and you want to keep the change, then "./ltib -p skel -m patchmerge" will make a patch of the modification and incorporate it into the skel .spec file. Hope this helps! On Thursday, 20 August 2015, 17:57, Peter Barada <[email protected]><mailto:[email protected]> wrote: Seriously, you have to analyse your log for reasons that can cause the build to fail and investigate before asking for help. Consider this response your one free mulligan (see https://en.wikipedia.org/wiki/Mulligan_%28games%29). As your log clearly states: You don't have a working TeX binary (tex) installed anywhere in your PATH, and texi2dvi cannot proceed without one. If you want to use this script, you'll need to install TeX (if you don't have it) or change your PATH or TEX environment variable (if you do). See the --help output for more details. You'll want to install TeX. Question - why do you want to build a native GCC to run on the target? Do you _really_ need to compile code inside the target itself (I'm not talking about the cross-compilation LTIB does to create the target image, but running binutils on the target itself)? Peter Barada // principal software engineer Logic PD 5 Clock Tower Place West Lobby, Suite 400 Maynard, MA 01754 <mailto:[email protected]>[email protected]<mailto:[email protected]> ________________________________ From: hosein bahari <[email protected]><mailto:[email protected]> Sent: Thursday, August 20, 2015 2:27 AM To: Peter Barada; [email protected]<mailto:[email protected]> Subject: Re: [Ltib] problem with selecting some of packages hi i attached a log of my terminal. "Also a description of you are trying to do that fails and how its different from a working build would really help us understand what could be going wrong." the problem is adding gcc package ,in ltib configurations .when i select it,the error will appear . On Wednesday, 19 August 2015, 8:21, Peter Barada <[email protected]><mailto:[email protected]> wrote: On 08/18/2015 07:24 AM, hosein bahari wrote: hi i have MPC8568MDS_20080328-ltib .normally,it is built successfully but when i select some of packages that are available at: ./ltib --config --> package list , like gcc or openssh ,then there is an error : ... RPM build errors: Bad exit status from /home/zaim/Desktop/new_bsp4/ltib/ltib-mpc8568mds-20080327/tmp/rpm-tmp.37604 (%install) Build time for binutils: 9 seconds Failed building binutils f_buildrpms() returned an error, exiting traceback: main:491 Started: Tue Aug 18 13:51:23 2015 Ended: Tue Aug 18 13:56:12 2015 Elapsed: 289 seconds These packages failed to build: binutils Build Failed what is the problem? No one can tell. Your log is clipped - and most inconvenient is that it's clipped right where building binutils would give a clue of why it failed. Back up the log about 50 lines or so to give us an idea of why binutils failed (i.e. to before the actual error that caused rpm/make to return non-zero. Also a description of you are trying to do that fails and how its different from a working build would really help us understand what could be going wrong. Not that we may be able to help since I think you are using a Freescale distributed LTIB tree that's more than seven _years_ old. You might want to contact Freescale for help on this tree as they may have patches or an updated LTIB tree that fixes the issue. _______________________________________________ LTIB home page: <http://ltib.org/> http://ltib.org Ltib mailing list [email protected]<mailto:[email protected]> https://lists.nongnu.org/mailman/listinfo/ltib -- Peter Barada [email protected]<mailto:[email protected]>
_______________________________________________ LTIB home page: http://ltib.org Ltib mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/ltib
