Fwd: Re: [Kolab-users] Re: kolab2 cvs-checkout

[Stefan]

Hello Sven!

Please use the address of this ML! Don't use my personal mail address! It's 
important for developers and others too, to get the infos from this ML!!!

Am Di 02.08.2005 15:36 schrieb Stefan <stefan at organet.com>:

> > obmtool:WARNING: install failure. Missing
> >
> 
> /kolab/RPM/PKG/kolab-resource-handlers-0.3.9-20050615.amd64-suse9.3-kolab.r
> >pm INSTALL: openpkg-2.2.3-2.2.3 make-3.80-2.2.0 binutils-2.14-2.2.0
> > mm-1.3.1-2.2.0 lzo-1.08-2.2.0 readline-5.0.0-2.2.0
> > sharutils-4.3.77-2.2.0 ncurses-5.4.20041009-2.2.0 bzip2-1.0.2-2.2.1
> > pcre-5.0-2.2.0 gzip-1.3.5-2.2.1 zlib-1.2.2-2.3.0 expat-1.95.8-2.2.0
> > gdbm-1.8.3-2.2.0 m4-1.4.2-2.2.0 bison-1.35-2.2.0 flex-2.5.4a-2.2.0
> > libiconv-1.9.2-2.2.0 openpkg-tools-0.8.26-2.2.1 patch-2.5.9-2.2.0
> > sed-4.1.2-2.2.0 libxml-2.6.14-2.2.1 libxslt-1.1.11-2.2.0
> > amavisd-2.1.2-2.2.0_kolab vim-6.3.30-2.2.1 dcron-2.9-2.2.0
> > kolabd-1.9.4-20050615 kolab-webadmin-0.4.0-20050620
> > MISSSRC: none
> > MISSPKG: gcc-3.4.2-2.2.0 fsl-1.5.0-2.2.0 perl-5.8.5-2.2.2
> 
> Are you sure you've fetched the gcc-package during your download
> procedure?
> Did you really copy all packages to your destination machine??

I thik yes. The complete fetch + build + install process work's fine. I
copy both /kolab and /kolabtemp to the amd64-system and start the
install.

Wild guess: Did you copy the directory from machine "a" to "b" with scp???
scp doesn't copy file links!! 
Often there is a link to the gcc binary in your file system!! Check this on 
machine "a"!
Install the "locate" package, start updatedb as root (needs a few minutes) and 
run:
locate gcc |grep -i bin

Do the same on machine "b" and compare both outputs!
In case you are to lazy installing "locate" you can do similar things with 
"find"!
cd /kolab 
find . -name "*gcc*" |grep -i bin

Stefan

Savest way is: tar czvf ./kolab.tgz /kolab