Hi Mika

If you can just post your changes to the list, I'm sure that they will
find their way into the t2-trunk.

The dialog package is listed as a dependency to mine, but it isn't being
built. Your comments seem right on.

Bob G

On Mon, 2009-10-26 at 19:45 +0200, Mika Pesu wrote:
> Hi,
> 
> I noticed this my self too, the key is to include dialog package as well 
> and modify it's build stages and priority. Dont remember offhand but i 
> think dialog package was missing stage 1 build and it's build priority 
> was after mine package. I think this was the cause of mine build fail, 
> that it is, if you get the same error on stage 1 mine build.
> 
> I can't commit the changes my self to svn at the moment, but if someone 
> with svn write access could do it and verify dialog build options that 
> those are right.
> 
> -Mika
> 
> 
> Bob Gustafson kirjoitti:
> > I am just following the Documentation and am trying to build the T2
> > system itself. My build system was a small old laptop which seemed to
> > trundle on ok, except when the Build-Target couldn't find dialog.h
> >
> > I now have a new system which has the Intel virtual bit and lots of
> > horsepower. Just brought it up a couple of hours ago running
> > Fedora-12-Beta. F12 seems to install and run pretty well, even with
> > hardware RAID, which was a problem with Fedora-11
> >
> > My intention is to bring up T2 as a virtual client with Fedora-12 as the
> > base. Lots of moving parts at the moment though.
> >
> > I would appreciate if you would take a look at the Build-Target of the
> > current t2-trunk as it is in svn. My build broke in mine where it could
> > not find the dialog package. I sent several emails to the list detailing
> > my progress and problem.
> >
> > Thanks for your clues. I will take them into account when I get my
> > virtual T2 client installed.
> >
> > Bob G
> >
> >
> > On Sun, 2009-10-25 at 10:22 +0100, Rene Rebe wrote:
> >   
> >> Hi,
> >>
> >> On 22.10.2009, at 20:41, Bob Gustafson wrote:
> >>
> >>     
> >>> Reading some of the handbook, it seems that Build-Pkg does not check
> >>> dependencies, but that Build-Target does (??) Perhaps this is the
> >>> problem.
> >>>
> >>>       
> >> Neither does. Emerge-Pkg does, but it is only meant for in-system
> >> package installation and updates.
> >>
> >>     
> >>>  mine fails looking for dialog.h
> >>>
> >>> There are lots of dialog.h files sprinkled around in the t2-trunk
> >>> directory, and there is a [DEP] dialog in the mine.cache file.
> >>>
> >>> ./scripts/Build-Pkg mine works fine:
> >>>
> >>> == 13:28:04 =[9]=> Building archiver/mine [0.23 8.0-trunk].
> >>> -> Reading package config: package/archiver/mine/mine.conf
> >>> -> Preparing build in src.mine.default.20091022.132759.329.susie
> >>> -> Building. Writing output to $root/var/adm/logs/9-mine.out
> >>> -> $root/var/adm/logs/9-mine.out -> 9-mine.log
> >>> == 10/22/09 13:30:02 =[9]=> Finished building package mine
> >>>
> >>>       
> >> Build-Pkg without any other option installs into your running system
> >> (like Emerge-Pkg).
> >>
> >>     
> >>> The local var/adm/logs directory shows an err file which happened
> >>> about
> >>> ten minutes ago during the Build-Target run and a much older
> >>> 0-mine.log file
> >>>
> >>> Note that the 9-mine.log file from the above Build-Pkg run appears
> >>> in
> >>> the system root directory /var/adm/logs
> >>>
> >>>       
> >> That's the default of Build-Pkg. You would need to specify some more
> >> options like -chroot and -root etc to exactly mimic what happens
> >> during the target build.
> >>
> >>     
> >>> These things are a puzzle to me. Why are these files scattered
> >>> around
> >>> and more importantly, why is mine failing to build under
> >>> Build-Target?
> >>>
> >>>       
> >> Because then it builds in the cross compile / sandbox, most probably
> >> some dependency or so is missing. I also recently changed mine to
> >> cross compile with the gasgui fronted, because I needed that. Maybe a
> >> typo slipped in.
> >>
> >>
> >> What kind of target and configuration do you build?
> >>
> >> -- 
> >>   René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin
> >>   http://exactcode.com | http://t2-project.org | http://rene.rebe.name
> >>
> >>
> >>     
> >
> >
> >
> > ----------------------------------------------------------- 
> > If you wish to unsubscribe from this mailing, send mail to
> > [email protected] with a subject of: unsubscribe t2
> >
> >
> >   
> 



----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2

Reply via email to