ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] XFree86 package


From: Stuart Hughes
Subject: Re: [Ltib] XFree86 package
Date: Wed, 15 Aug 2007 16:39:23 +0100

Hi Ken,

I don't have /var/frescale? however there is an /opt/freescale/pkgs
directory on the Freescale released iso image, did you mean this?  If so
that directory is just a staging area (same as /opt/ltib/pkgs for the
savannah version).  It just holds any downloaded packages or packages
distributed with the iso image (to save downloading them).

As far as supported packages goes, here are the rules:

* If you're using an ISO image from Freescale then only the packages
selected in the default configuration are actively supported by
Freescale.  You may ask about others, but no guarantees.

* Any packages that are selectable from './ltib -m config' are supported
by me on an ad-hoc best effort basis on this mailing list.  Normally
these packages will at least have been built on a large number of
different architectures/toolchain on our internal autobuilder.  As far
as testing goes, that is left in the hands of the individual BSP teams
and so whether or not it has been thoroughly tested will depend on
whether the BSP team has required it for their release.

* There are some other packages references (spec files) you can see in
dist/lfs-5.1.  If these don't show up then they're not supported, but
you're welcome to ask about them.  Normally these are packages that I've
used on other projects and have intended to one day integrate into LTIB.

I hope to do a complete re-merge update before the end of September, but
that depends a lot on how my other project progresses.  If you're using
an ISO image from Freescale, you already have these updates.  The reason
I haven't merged out is because I want to do some major re-structuring
before I do so and didn't want to confuse people with 2 big updates.
The purpose of the re-structure is to move all the BSP specific parts
(kernel spec files mostly) into the config/platform/<target> directory.
This would separate out the LTIB tool from the platform part completely.
The idea being that maintenance is easier and "writing a new BSP" is
simplified to just adding a new directory with a few files.

The distinction in my head for distribution vs LTIB was that I'd stop at
a thin-client (e.g. no graphics), however having said that the imx31 do
ship with qtopia graphics, touchscreen etc.  So it's not really a hard
line, more a mental note to myself not to be deluded into trying to
feature creep into being a full up distro.  As you rightly eluded to a
lot of the boundary comes with technical difficulty of cross compiling
higher order packages.  The problem is that the higher up the food chain
you get the more complex the indirect package dependencies get
(libraries etc) and also very often you need to actually run
intermediate executables as part of a package build.  Other "fuller"
embedded distributions tackle this in different ways, some using
scratchbox (emulate the architecture so you can run the intermediate
executable) or others swap to native building once they get so far along
the way it becomes impractical to cross compile (openembedded I think).
I don't plan to do either of these, my focus is more on being able to do
the small stuff well and to support a common package set across a wide
range of architectures and toolchains (uClibc and glibc).

Regards, Stuart


On Wed, 2007-08-15 at 10:35 -0400, Ken Gilmer wrote:
> Hey Stuart,
> 
>    Ok, thanks for that.  I just looked in the dist/lfs directory, saw  
> that package, and assumed it would work.  I have some questions  
> still :).  So is the general rule that packages in /var/freescale/ 
> pkgs are supported packages and those in dist/lfs are not?  IRT the  
> new LTIB features that you mentioned, do you have a rough time when  
> you expect to release?
> 
>    Also, in terms of full distribution vs LTIB, could you clarify  
> where the line is?  What else beside XFree86 do you as out of scope.   
> And, is the reason for this distinction technical or simply a matter  
> of overhead and maintenence time?
> 
> Thanks!
> Ken Gilmer
> 
> Bug Labs
> 
> On Aug 15, 2007, at 3:42 AM, Stuart Hughes wrote:
> 
> > Hi Ken,
> >
> > This package is not supported, only the ones selectable from the  
> > config
> > system are likely to build, but sometimes even then not on all  
> > platforms
> > (as sometimes a package gets put in for one architecture, but not  
> > fully
> > built/tested for all).
> >
> > I have a lot of pending changes to go into LTIB which I hope to get in
> > once I've finished another internal project.  One of these changes  
> > is to
> > add proper handling of pkg-config and linking indirect library
> > references.  This would help a great deal with something like XFree86.
> >
> > In terms of philosophical approach LTIB is not intended to be a full
> > distribution as there are many good ones about.  For me it's there to
> > address the availability of a common userspace package set that can
> > scale down to smaller devices.
> >
> > Regards, Stuart
> >
> > On Tue, 2007-08-14 at 17:32 -0400, Ken Gilmer wrote:
> >>
> >> Hello ~
> >>
> >>     I'm trying to build the XFree86 LTIB package and am running into
> >> errors very early in the build process.  Is this package supported?
> >> I'm using a BSP provided with the i.MX31 development board.
> >>
> >> Thanks!
> >> Ken
> >>
> >> Build output:
> >>
> >> address@hidden ltib-imx31ads-20070128]$ ./ltib -m scbuild -p
> >> XFree86.spec
> >>
> >> Processing: XFree86
> >> =====================
> >> rpmbuild --dbpath /home/kgilmer/julyeffort/ltib-imx31ads-20070128/
> >> rpmdb --define '_unpackaged_files_terminate_build 0' --define
> >> '_target_cpu arm' --define '__strip strip' --define '_topdir /home/
> >> kgilmer/julyeffort/ltib-imx31ads-20070128/rpm' --define '_prefix /
> >> usr' --define '_tmppath /home/kgilmer/julyeffort/ltib-
> >> imx31ads-20070128/tmp' --define '_mandir /usr/share/man' --define
> >> '_sysconfdir /etc' --define '_localstatedir /var' -bc --short-
> >> circuit  /home/kgilmer/julyeffort/ltib-imx31ads-20070128/dist/ 
> >> lfs-5.1/
> >> XFree86/XFree86.spec
> >> Executing(%build): /bin/sh -e /home/kgilmer/julyeffort/ltib-
> >> imx31ads-20070128/tmp/rpm-tmp.64030
> >> + umask 022
> >> + cd /home/kgilmer/julyeffort/ltib-imx31ads-20070128/rpm/BUILD
> >> + cd /home/kgilmer/julyeffort/ltib-imx31ads-20070128/rpm/BUILD/
> >> XFree86/xc
> >> + make World WORLDOPTS=
> >>
> >> /bin/sh: ./config/util/printver.exe: cannot execute binary file
> >> Building XFree86.
> >>
> >> I hope you checked the configuration parameters in ./config/cf
> >> to see if you need to pass BOOTSTRAPCFLAGS.
> >>
> >> Tue Aug 14 15:42:45 EDT 2007
> >>
> >> cd ./config/imake && make  -f Makefile.ini BOOTSTRAPCFLAGS=""
> >> CC="gcc" clean
> >> make[1]: Entering directory `/home/kgilmer/julyeffort/ltib-
> >> imx31ads-20070128/rpm/BUILD/XFree86/xc/config/imake'
> >> rm -f ccimake imake.o imake
> >> rm -f *.CKP *.ln *.BAK *.bak *.o core errs ,* *~ *.a tags TAGS
> >> make.log \#*
> >> rm -f -r Makefile.proto Makefile Makefile.dep bootstrap
> >> rm -f imakemdep_cpp.h
> >> make[1]: Leaving directory `/home/kgilmer/julyeffort/ltib-
> >> imx31ads-20070128/rpm/BUILD/XFree86/xc/config/imake'
> >> make  Makefile.boot
> >> make[1]: Entering directory `/home/kgilmer/julyeffort/ltib-
> >> imx31ads-20070128/rpm/BUILD/XFree86/xc'
> >> cd ./config/imake && make -w -f Makefile.ini BOOTSTRAPCFLAGS=""  
> >> CC="gcc"
> >> make[2]: Entering directory `/home/kgilmer/julyeffort/ltib-
> >> imx31ads-20070128/rpm/BUILD/XFree86/xc/config/imake'
> >> making imake with BOOTSTRAPCFLAGS= and CROSSCOMPILEFLAGS=-
> >> DCROSSCOMPILEDIR="" in config/imake
> >> gcc -o ccimake -DCROSSCOMPILEDIR=\"\"  -O -I../../include -I../../
> >> imports/x11/include/X11 ccimake.c
> >> if [ -n "" ] ; then \
> >> /cc -E `./ccimake` \
> >> -DCROSSCOMPILE_CPP imakemdep.h > imakemdep_cpp.h; \
> >> else touch imakemdep_cpp.h; fi
> >> gcc -c  -O -I../../include -I../../imports/x11/include/X11 `./
> >> ccimake` imake.c
> >> /bin/sh: ./ccimake: cannot execute binary file
> >> gcc -o imake  -O -I../../include -I../../imports/x11/include/X11  
> >> imake.o
> >> make[2]: Leaving directory `/home/kgilmer/julyeffort/ltib-
> >> imx31ads-20070128/rpm/BUILD/XFree86/xc/config/imake'
> >> rm -f ./config/makedepend/Makefile.proto
> >> ./config/imake/imake -I./config/cf  -s ./config/makedepend/
> >> Makefile.proto -f ./config/makedepend/Imakefile -DTOPDIR=../.. -
> >> DCURDIR=./config/makedepend
> >> ./config/imake/imake: ./config/imake/imake: cannot execute binary  
> >> file
> >> make[1]: *** [config/makedepend/Makefile.proto] Error 126
> >> make[1]: Leaving directory `/home/kgilmer/julyeffort/ltib-
> >> imx31ads-20070128/rpm/BUILD/XFree86/xc'
> >> make: *** [World] Error 2
> >> error: Bad exit status from /home/kgilmer/julyeffort/ltib-
> >> imx31ads-20070128/tmp/rpm-tmp.64030 (%build)
> >>
> >>
> >> RPM build errors:
> >>      Bad exit status from /home/kgilmer/julyeffort/ltib-
> >> imx31ads-20070128/tmp/rpm-tmp.64030 (%build)
> >> Build time for XFree86: 3 seconds
> >>
> >> Failed building XFree86
> >>
> >>
> >> _______________________________________________
> >> LTIB home page: http://bitshrine.org
> >>
> >> Ltib mailing list
> >> address@hidden
> >> http://lists.nongnu.org/mailman/listinfo/ltib
> >
> 





reply via email to

[Prev in Thread] Current Thread [Next in Thread]