Here as attachment config.log files ----------------------- ptxdist opkg config.log $ ./configure --prefix= --disable-libopkg-api --disable-static --disable-pathfinder --disable-xz --disable-bzip2 --disable-curl --disable-sha256 --disable-openssl --disable-ssl-curl --disable-gpg --without-l ibsolv --without-static-libopkg
## --------- ## ## Platform. ## ## --------- ## hostname = sumo uname -m = x86_64 uname -r = 4.19.4-arch1-1-ARCH uname -s = Linux uname -v = #1 SMP PREEMPT Fri Nov 23 09:06:58 UTC 2018 -------------------------- my opkg config.log $ ./configure ## --------- ## ## Platform. ## ## --------- ## hostname = sumo uname -m = x86_64 uname -r = 4.19.4-arch1-1-ARCH uname -s = Linux uname -v = #1 SMP PREEMPT Fri Nov 23 09:06:58 UTC 2018 Am Di., 4. Dez. 2018 um 12:47 Uhr schrieb Andreas Friesen <ms.f...@gmail.com >: > Also rootfs and rootfs0 exists not! > > $ DESTDIR="/home/friesen/rootfs/rootfs" > /home/friesen/gitlab/quantumx-master/projects/ppc/ptx-multi/platform-soc/sysroot-host/bin/opkg > -f "/home/friesen/rootfs/opkg.conf" -o "/home/friesen/rootfs/rootfs/" > install rootfs_1.0.0_armhf.ipk > Installing rootfs (1.0.0) on root. > To remove package debris, try `opkg remove rootfs`. > To re-attempt the install, try `opkg install rootfs`. > Collected errors: > * check_data_file_clashes: Package rootfs wants to install file > /home/friesen/rootfs/rootfs//var/run > But that path is currently a directory > * opkg_solver_install: Cannot install package rootfs. > > [$] <> ls -all rootfs/var > total 20 > drwxr-xr-x 5 friesen friesen 4096 Dec 4 12:42 . > drwxr-xr-x 3 friesen friesen 4096 Dec 4 12:42 .. > drwxr-xr-x 3 friesen friesen 4096 Dec 4 12:42 cache > drwxr-xr-x 3 friesen friesen 4096 Dec 4 12:42 lib > drwxr-xr-x 2 friesen friesen 4096 Dec 4 12:42 run <------ !!!!! is a > directory > > > DESTDIR="/home/friesen/rootfs/rootfs0" opkg -f > "/home/friesen/rootfs/opkg.conf" -o "/home/friesen/rootfs/rootfs0/" install > rootfs_1.0.0_armhf.ipk > Installing rootfs (1.0.0) on root. > > > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//proc/': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//mnt/': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//sys/': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//etc/': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//etc/profile': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//etc/resolv.conf': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//etc/hostname': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//etc/group': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//etc/issue': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//etc/passwd': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//etc/shadow': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//etc/nsswitch.conf': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//etc/mtab': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//etc/services': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//etc/hosts': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//etc/profile.environment': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//etc/fstab': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//etc/protocols': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//run/': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//root/': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//dev/': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//dev/zero': Can't create > '/home/friesen/rootfs/rootfs0/dev/zero' > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//dev/console': Can't create > '/home/friesen/rootfs/rootfs0/dev/console' > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//dev/null': Can't create > '/home/friesen/rootfs/rootfs0/dev/null' > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//home/': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//tmp/': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//media/': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//var/': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//var/lock/': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//var/run': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//var/log/': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//var/tmp/': Can't set UID=0 > Warning when extracting archive entry > '/home/friesen/rootfs/rootfs0//var/cache/': Can't set UID=0 > Configuring rootfs. > > ls -all rootfs0/var > total 24 > drwxr-xr-x 6 friesen friesen 4096 Nov 1 01:00 . > drwxr-xr-x 14 friesen friesen 4096 Dec 4 12:44 .. > drwxr-xr-x 2 friesen friesen 4096 Nov 1 01:00 cache > drwxr-xr-x 2 friesen friesen 4096 Nov 1 01:00 lock > drwxr-xr-x 2 friesen friesen 4096 Nov 1 01:00 log > lrwxrwxrwx 1 friesen friesen 6 Nov 1 01:00 run -> ../run <--- is > a link ! > drwxr-xr-x 2 friesen friesen 4096 Nov 1 01:00 tmp > > > > > > Am Di., 4. Dez. 2018 um 11:40 Uhr schrieb Michael Olbrich < > m.olbr...@pengutronix.de>: > >> On Tue, Dec 04, 2018 at 10:40:11AM +0100, Andreas Friesen wrote: >> > Hi Michael. >> > >> > I compiled opkg for my host system (archlinux) with : "./configure ; >> make ; >> > make install" and installed all packages from ptxdist without any >> errors: >> > DESTDIR="/home/friesen/rootfs/rootfs" opkg -f >> > "/home/friesen/rootfs/opkg.conf" -o "/home/friesen/rootfs/rootfs/" >> install >> > /home/friesen/ptx-multi/platform-soc/packages/*.ipk >> > >> > but >> > >> > DESTDIR="/home/friesen/rootfs/rootfs" >> > /home/friesen/gitlab/ptx-multi/platform-soc/sysroot-host/bin/opkg >> > -f "/home/friesen/rootfs/opkg.conf" -o "/home/friesen/rootfs/rootfs/" >> > install >> > >> /home/friesen/gitlab/quantumx-master/projects/ppc/ptx-multi/platform-soc/packages/*,pkg >> > >> > produced this error: >> > >> > * check_data_file_clashes: Package rootfs wants to install file >> > /home/faix/ptx-multi/platform-soc/build-target/image-nor-mxfs4/var/run >> > But that path is currently a directory >> > >> > I finded out with try-and-error method, that opkg do not like "prefix= >> " ! >> >> Very strange. I don't see this issue here. Also, did you copy the correct >> error message? The path there is not inside the specified DESTDIR. And is >> var/run inside the generated rootfs an empty directory? >> >> Also, calling opkg manually may work for other reasons: If rootfs is >> installed before another package created the directory, then I think it >> will just work. >> >> Michael >> >> -- >> Pengutronix e.K. | | >> Industrial Linux Solutions | http://www.pengutronix.de/ >> | >> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | >> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | >> >> _______________________________________________ >> ptxdist mailing list >> ptxdist@pengutronix.de > >
_______________________________________________ ptxdist mailing list ptxdist@pengutronix.de
