ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Ltib] Ltib Build failed for texinfo


From: Estevam Fabio-R49496
Subject: RE: [Ltib] Ltib Build failed for texinfo
Date: Tue, 5 May 2009 13:45:06 -0300

Nirmala wrote:
> Hi
>   Trying to install ltib for Linux version 2.6.18 Before installing
> ltib (using ./ltib), verified and installed all the necessary tools
> listed at (What is required on your host before installing LTIB at
> http://www.bitshrine.org/autodocs/LtibFaq.html#ref_1)   
> 
> 
> But the ltib build failed, below is the error log  snippet:
> ---------------------------------------------------------------------
> 
> make  all-recursive
> make[1]: Entering directory `/opt/ltib/usr/src/rpm/BUILD/texinfo-4.8'
> Making all in tools
> make[2]: Entering directory
> `/opt/ltib/usr/src/rpm/BUILD/texinfo-4.8/tools'
> make[2]: *** No rule to make target `all'.  Stop.
> make[2]: Leaving directory
> `/opt/ltib/usr/src/rpm/BUILD/texinfo-4.8/tools'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/opt/ltib/usr/src/rpm/BUILD/texinfo-4.8'
> make: *** [all] Error 2
> error: Bad exit status from /home/edgedeveloper/ltib/tmp/rpm-tmp.6956
> (% 
> build)
> 
> 
> RPM build errors:
>     Bad exit status from /home/edgedeveloper/ltib/tmp/rpm-tmp.6956 (%
> build)
> Build time for texinfo: 17 seconds
> 
> Failed building texinfo
> Died at ./ltib line 1377.
> traceback:
>  main::build_host_rpms:1377
>   main::host_checks:1432
>    main:539
> 
> 
> Started: Tue May  5 11:01:33 2009
> Ended:   Tue May  5 11:01:51 2009
> Elapsed: 18 seconds
> 
> These packages failed to build:
> texinfo
> 
> Build Failed

I have a colleague that have had the same issue you describe.

This is what he did to fix it:

"This is the exact fail I had, so the fix is to modify
ltib/config/userspace/pkg_map

Look for the lines -

PKG_DISTCC = distcc
PKG_CCACHE = ccache

Lines 228 and 229 in my release. Cut and past them to a new position
directly below -

PKG_BUSYBOX = busybox

Which should be line 12, this was all I had to do. "

Regards,

Fabio Estevam





reply via email to

[Prev in Thread] Current Thread [Next in Thread]