gcc-4.5-RH in F14

Caolán McNamara caolanm at redhat.com
Fri Jul 9 07:34:21 UTC 2010


On Thu, 2010-07-08 at 17:51 -0700, Ulrich Drepper wrote:

> That's not so easy to generalize.  As Jakub wrote, you need some form of
> workload.  After the binaries are built this workload has to be
> executed.  How to do that cannot really be summarized.  Some packages
> might need to be installed to function.  Others need permissions etc.
> Some might need interaction.  For console programs you can do that using
> expect but for GUI programs...
> 
> After the workload is run you need to rebuild everything again while
> pointing to the files created by running the workload.  The first stage
> binaries automatically create those files.

As an aside, OpenOffice.org has a smoketest where OOo is run headless,
i.e. without DISPLAY, to open/save various documents and other brief
representative sanity tests. Might be tempting, maybe too tempting, to
experiment with that. Though double building OOo every time isn't
massively appetising.

C.



More information about the devel mailing list