Custom Query (532 matches)
Results (22 - 24 of 532)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#117 | fixed | Invalid commands to create ppc-tools | ||
Description |
jhalfs produces invalid sequence of commands for the powerpc-utils. 151-powerpc-utils: 150-parted @$(call echo_message, Building) @$(SHELL) progress_bar.sh $@ $$PPID & @echo "$(nl_)`date`$(nl_)" >logs/$@ @$(PRT_DU_CR) >>logs/$@ @( time { source envars && $(crCMDSDIR)/final-system/$@ >>logs/$@ 2>&1 ; } ) 2>>logs/$@ && \ $(PRT_DU_CR) >>logs/$@ @$(call housekeeping) |
|||
#123 | fixed | PPC: Textual blur in 10.7.4 (32bit) and 10.8.4 (Multilib) (Cfg dynlinker) | ||
Description |
In chapter 10.7.4 of 32 bit powerpc book and chapter 10.8.4 of ppc64 multilib book (Configuring the dynamic linker) there is /lib/ld-linux.so.2 named as default linker, mostly true but not on PPC systems. There it should read as /lib/ld.so.1 and/or /lib64/ld64.so. |
|||
#131 | fixed | Binutils-2.18 Libiberty.a Placement | ||
Description |
Book: Version SVN-20070910-x86_64-Pure64 Section: 10.8. Binutils-2.18 When I install Binutils-2.18 it is not putting libiberty.a into the correct directory /usr/lib. Instead it creates /usr/lib64 and places /usr/lib64/libiberty.a there. |
Note: See TracQuery
for help on using queries.