trietptm / pentoo

Automatically exported from code.google.com/p/pentoo
1 stars 0 forks source link

xmount bump test #342

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

some times i Get lucky bumping an ebuild , some of the forensic tools etc EAPI 
is stale , so just doing a few test bumps see is luck holds. if not try again 
aim hear is to try to get a few things out working etc, and or fixed so some 
en-danged/or/blood still dripping security packages will continue to work or 
bang on them till they do. or share what i found as the crash test ...monkey. 

however the newest version cmake ewwe weird via comandline  wants a build dir 
and all  and acting odd , unfortunately what cmake version is the pest. and 
build instructions or cmdline feedback is oddly sparse , to try to make it even 
by hand.  

any new ebuild is mocked up however PATCH ??? 

win some lose some , failing is a lesson. i had hoped Blshvk's prior patch-set 
might just work,  no dice ...  

learn something repoman bitched so I changed to virtual/pkgconfig form 
dev-util/pkgconfig 
inherit cmake-utils multilib-minimal seams more compatible for multiple 
$arch(cpu's)
~x86/~AMD64 etc.. 

and a partial manifest for the tarballs. 

I have no qualms testing other things , its always worth a shot , may get a 
nice tasty steak fail log for devs  or a shiny package out. 

 * Messages for package app-forensics/xmount-0.7.3:

 * ERROR: app-forensics/xmount-0.7.3::spike-community-overlay failed (configure phase):
 *   no configure script found
 * 
 * Call stack:
 *          ebuild.sh, line   93:  Called src_configure
 *        environment, line 3168:  Called econf
 *   phase-helpers.sh, line  589:  Called die
 * The specific snippet of code:
 *          die "no configure script found"
 * 
 * If you need support, post the output of `emerge --info '=app-forensics/xmount-0.7.3::spike-community-overlay'`,
 * the complete build log and the output of `emerge -pqv '=app-forensics/xmount-0.7.3::spike-community-overlay'`.
 * The complete build log is located at '/var/tmp/portage/app-forensics/xmount-0.7.3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-forensics/xmount-0.7.3/temp/environment'.
 * Working directory: '/var/tmp/portage/app-forensics/xmount-0.7.3/work/xmount-0.7.3'
 * S: '/var/tmp/portage/app-forensics/xmount-0.7.3/work/xmount-0.7.3'

ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored. muti-lib upgrade & NOD32 
un-install 
need to clear this but is irritating in the log my apologies. 

I mean not to add more work load but hopefully it helps down the road. 

Original issue reported on code.google.com by m...@michaellawrenceit.com on 26 Mar 2015 at 6:57

Attachments: