Hi Josmar, the problem with this package is that it has a conflict with the package util-linux. Actually the conflict is the sulogin utility and the associated man page.
to fix this you have to go back a little and do the following: 1. find the util-linux configuration in packages, edit the configuration util-linux.conf and append to the confopt argument '-disable-sulogin" if i remember corectly. basically you have to disable the build of sulogin from util-linux. now you have 2 options: 2A. cleanup the build and start over ( time consuming but i recommend it) 2B. Delete the offending files from build ( the man and the utility) and go forward.( sort of a test until you get everything fixed up) this is not the first time you will encounter this kind of issue with util-linux. it might happen a little bit later on while you are building other packages. Regards, Iulian > Iulian, > > Suggestion accepted. I will build and reinstall a new minimal, so I > reconfigured and restarted the build. > I followed the mailing list archives (as you suggested) and could come > around the gawk failure as well as a few other minor glitches. > > Now, however, I think I'm officially stuck again, with this: > > == 16:21:31 =[1]=> Building base/sysvinit [2.88 9.0-trunk]. > -> Parallel build using 2 jobs enabled. > -> Reading package config: package/base/sysvinit/sysvinit.conf > -> Preparing build in > src.sysvinit.default.20131125.162131.355.TCC-T2 > -> Building. Writing output to $root/var/adm/logs/1-sysvinit.out > !> Clear (old) md5sums ... > !> Creating md5sum files ... done. > !> Creating package description ... > !> Making post-install adaptions. > !> Found shared files with other packages: > !> sbin/sulogin: sysvinit util-linux > !> usr/share/man/man8/sulogin.8: sysvinit util-linux > !> Due to previous errors. > == 11/25/13 16:21:37 =[1]=> Aborted building package sysvinit. > -> Unmounting loop mounts ... > > I already applied the fix from Jan Rovins ( +var_append makeopt ' ' > 'SULOGINLIBS=-lcrypt LUTIL=-lutil ROOT=$root DISTRO=$DISTRO all' ), but > it seems to have no effect on the issue above. > > I hope you have a remedy for this too ... > :) > > Thanks, > Josmar > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] > Sent: Monday, November 25, 2013 9:27 AM > To: Josmar Calin De Pierri > Cc: [email protected]; T2 developers mailing list > Subject: RE: [t2] Build T2-TRUNK > > hi Josmar, > > it would be good if you update perl also. It depends very much on what > you > intend to build. My advice would be to build a minimal and fix issues, > reinstall the new minimal as a building base and go from there. I know > it > is painfull but if you have the processing power it will not take too > long. Be carefull at the dependencies, and if possible read the mailing > list for hints on how to go over several issues. If you get stuck again, > send a mail and we will try to help. > > > regards, > > Iulian > >
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
