All of lore.kernel.org
 help / color / mirror / Atom feed
* sanity test problems at end of build
@ 2008-11-27 10:42 Valentin Longchamp
  2008-11-27 10:55 ` Koen Kooi
  0 siblings, 1 reply; 10+ messages in thread
From: Valentin Longchamp @ 2008-11-27 10:42 UTC (permalink / raw)
  To: openembedded-devel

Hello,

Sorry if it is a repost, but I have got not answer and have not seen my mail 
in the mailing-list archives, so I send it again

I have seen various people that have experienced the same problem during the 
last months, but I have never read a clear answer or fix to what is wrong with 
this issue.

OE builds just fine all the needed packages for my system, but in the I get a 
failed sanity check for various libraries. Here is the log for a console-image 
for instance:

> NOTE: Running task 1589 of 1960 (ID: 217,
> /usr/local/OE/openembedded/packages/angstrom/angstrom-version.bb,
> do_populate_staging) NOTE: package angstrom-version-2008.1-test-20081120:
> started
> NOTE: package angstrom-version-1_2008.1-test-20081120-r1: task
> do_populate_staging: started NOTE: package
> angstrom-version-1_2008.1-test-20081120-r1: task do_populate_staging:
> completed NOTE: package angstrom-version-2008.1-test-20081120: completed
> NOTE: Running task 1861 of 1960 (ID: 216,
> /usr/local/OE/openembedded/packages/angstrom/angstrom-version.bb,
> do_package_write) NOTE: package angstrom-version-2008.1-test-20081120:
> started
> NOTE: package angstrom-version-1_2008.1-test-20081120-r1: task
> do_package_write: started NOTE: package
> angstrom-version-1_2008.1-test-20081120-r1: task do_package_write:
> completed NOTE: package angstrom-version-2008.1-test-20081120: completed
> NOTE: Running task 1862 of 1960 (ID: 215,
> /usr/local/OE/openembedded/packages/angstrom/angstrom-version.bb,
> do_package_stage) NOTE: package angstrom-version-2008.1-test-20081120:
> started
> NOTE: package angstrom-version-1_2008.1-test-20081120-r1: task
> do_package_stage: started NOTE: package
> angstrom-version-1_2008.1-test-20081120-r1: task do_package_stage:
> completed NOTE: package angstrom-version-2008.1-test-20081120: completed
> NOTE: Running task 1892 of 1960 (ID: 5,
> /usr/local/OE/openembedded/packages/images/console-image.bb, do_qa_staging)
> NOTE: package console-image-1.0: started
> NOTE: package console-image-1.0-r0: task do_qa_staging: started
> NOTE: QA checking staging
> ERROR: QA Issue: libpanel.la failed sanity test (workdir) in path
> /usr/local/OE/angstrom//staging/armv6-angstrom-linux-gnueabi/usr/lib ERROR:
> QA Issue: libncurses.la failed sanity test (workdir) in path
> /usr/local/OE/angstrom//staging/armv6-angstrom-linux-gnueabi/usr/lib ERROR:
> QA Issue: libmenu.la failed sanity test (workdir) in path
> /usr/local/OE/angstrom//staging/armv6-angstrom-linux-gnueabi/usr/lib ERROR:
> QA Issue: libform.la failed sanity test (workdir) in path
> /usr/local/OE/angstrom//staging/armv6-angstrom-linux-gnueabi/usr/lib ERROR:
> QA staging was broken by the package built above
> ERROR: Error in executing:
> ERROR: Exception:<type 'exceptions.SystemExit'> Message:1
> ERROR: Printing the environment of the function
> ERROR: Build of /usr/local/OE/openembedded/packages/images/console-image.bb
> do_qa_staging failed ERROR: Task 5
> (/usr/local/OE/openembedded/packages/images/console-image.bb,
> do_qa_staging) failed NOTE: Waiting for 1 active tasks to finish
> NOTE: 1: /usr/local/OE/openembedded/packages/gnutls/gnutls_2.4.2.bb,
> do_configure (13056) NOTE: package gnutls-2.4.2-r3: task do_configure:
> completed
> NOTE: package gnutls-2.4.2: completed
> NOTE: Tasks Summary: Attempted 1890 tasks of which 1873 didn't need to be
> rerun and 1 failed. ERROR:
> '/usr/local/OE/openembedded/packages/images/console-image.bb' failed

I had read that this could have something to do with the fact that -tmp was in 
the name of the tmp build dir. However it is not the case for me and the 
problem is still here. Here is my local.conf file:

> # Where to store sources
> DL_DIR = "/usr/local/OE/downloads"
>
> # Which files do we want to parse:
> BBFILES := "/usr/local/OE/openembedded/packages/*/*.bb"
> BBMASK = ""
>
> # qemu has a few problems with our architecture
> #ENABLE_BINARY_LOCALE_GENERATION = "0"
> # We only need a few locales
> # does not work with ENABLE_BINARY_LOCALE_GENERATION = "0"
> GLIBC_GENERATE_LOCALES = "en_GB.UTF-8 fr_CH.UTF-8"
>
> # ccache always overfill $HOME....
> CCACHE=""
>
> # What kind of images do we want?
> IMAGE_FSTYPES = "jffs2 tar.gz"
>
> # Set TMPDIR instead of defaulting it to $pwd/tmp
> TMPDIR = "/usr/local/OE/${DISTRO}/"
>
> # Make use of my SMP box
> PARALLEL_MAKE="-j4"
> BB_NUMBER_THREADS = "2"
>
> # Set the Distro
> DISTRO = "angstrom-2008.1"
>
> # 'uclibc' or 'glibc' or 'eglibc'
> #ANGSTROM_MODE = "glibc"
>
> MACHINE = "mx31moboard"

Thank you for your help, that would be really nice to fix this, because I am 
not able to build rootfs images at this point because of this problem.

Regards

Valentin



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: sanity test problems at end of build
  2008-11-27 10:42 sanity test problems at end of build Valentin Longchamp
@ 2008-11-27 10:55 ` Koen Kooi
  2008-11-27 11:27   ` Stanislav Brabec
  0 siblings, 1 reply; 10+ messages in thread
From: Koen Kooi @ 2008-11-27 10:55 UTC (permalink / raw)
  To: openembedded-devel

On 27-11-08 11:42, Valentin Longchamp wrote:
> Hello,
>
> Sorry if it is a repost, but I have got not answer and have not seen my mail
> in the mailing-list archives, so I send it again

I know the problem exists for some people, but I have never been able to 
reproduce it. People having this problem should debug why ncurses 
suddenly decides to mess up its .la files. Or better, look at the .la 
files to see what's triggering insane.bbclass

regards,

Koen



> I have seen various people that have experienced the same problem during the
> last months, but I have never read a clear answer or fix to what is wrong with
> this issue.
>
> OE builds just fine all the needed packages for my system, but in the I get a
> failed sanity check for various libraries. Here is the log for a console-image
> for instance:
>
>> NOTE: Running task 1589 of 1960 (ID: 217,
>> /usr/local/OE/openembedded/packages/angstrom/angstrom-version.bb,
>> do_populate_staging) NOTE: package angstrom-version-2008.1-test-20081120:
>> started
>> NOTE: package angstrom-version-1_2008.1-test-20081120-r1: task
>> do_populate_staging: started NOTE: package
>> angstrom-version-1_2008.1-test-20081120-r1: task do_populate_staging:
>> completed NOTE: package angstrom-version-2008.1-test-20081120: completed
>> NOTE: Running task 1861 of 1960 (ID: 216,
>> /usr/local/OE/openembedded/packages/angstrom/angstrom-version.bb,
>> do_package_write) NOTE: package angstrom-version-2008.1-test-20081120:
>> started
>> NOTE: package angstrom-version-1_2008.1-test-20081120-r1: task
>> do_package_write: started NOTE: package
>> angstrom-version-1_2008.1-test-20081120-r1: task do_package_write:
>> completed NOTE: package angstrom-version-2008.1-test-20081120: completed
>> NOTE: Running task 1862 of 1960 (ID: 215,
>> /usr/local/OE/openembedded/packages/angstrom/angstrom-version.bb,
>> do_package_stage) NOTE: package angstrom-version-2008.1-test-20081120:
>> started
>> NOTE: package angstrom-version-1_2008.1-test-20081120-r1: task
>> do_package_stage: started NOTE: package
>> angstrom-version-1_2008.1-test-20081120-r1: task do_package_stage:
>> completed NOTE: package angstrom-version-2008.1-test-20081120: completed
>> NOTE: Running task 1892 of 1960 (ID: 5,
>> /usr/local/OE/openembedded/packages/images/console-image.bb, do_qa_staging)
>> NOTE: package console-image-1.0: started
>> NOTE: package console-image-1.0-r0: task do_qa_staging: started
>> NOTE: QA checking staging
>> ERROR: QA Issue: libpanel.la failed sanity test (workdir) in path
>> /usr/local/OE/angstrom//staging/armv6-angstrom-linux-gnueabi/usr/lib ERROR:
>> QA Issue: libncurses.la failed sanity test (workdir) in path
>> /usr/local/OE/angstrom//staging/armv6-angstrom-linux-gnueabi/usr/lib ERROR:
>> QA Issue: libmenu.la failed sanity test (workdir) in path
>> /usr/local/OE/angstrom//staging/armv6-angstrom-linux-gnueabi/usr/lib ERROR:
>> QA Issue: libform.la failed sanity test (workdir) in path
>> /usr/local/OE/angstrom//staging/armv6-angstrom-linux-gnueabi/usr/lib ERROR:
>> QA staging was broken by the package built above
>> ERROR: Error in executing:
>> ERROR: Exception:<type 'exceptions.SystemExit'>  Message:1
>> ERROR: Printing the environment of the function
>> ERROR: Build of /usr/local/OE/openembedded/packages/images/console-image.bb
>> do_qa_staging failed ERROR: Task 5
>> (/usr/local/OE/openembedded/packages/images/console-image.bb,
>> do_qa_staging) failed NOTE: Waiting for 1 active tasks to finish
>> NOTE: 1: /usr/local/OE/openembedded/packages/gnutls/gnutls_2.4.2.bb,
>> do_configure (13056) NOTE: package gnutls-2.4.2-r3: task do_configure:
>> completed
>> NOTE: package gnutls-2.4.2: completed
>> NOTE: Tasks Summary: Attempted 1890 tasks of which 1873 didn't need to be
>> rerun and 1 failed. ERROR:
>> '/usr/local/OE/openembedded/packages/images/console-image.bb' failed
>
> I had read that this could have something to do with the fact that -tmp was in
> the name of the tmp build dir. However it is not the case for me and the
> problem is still here. Here is my local.conf file:
>
>> # Where to store sources
>> DL_DIR = "/usr/local/OE/downloads"
>>
>> # Which files do we want to parse:
>> BBFILES := "/usr/local/OE/openembedded/packages/*/*.bb"
>> BBMASK = ""
>>
>> # qemu has a few problems with our architecture
>> #ENABLE_BINARY_LOCALE_GENERATION = "0"
>> # We only need a few locales
>> # does not work with ENABLE_BINARY_LOCALE_GENERATION = "0"
>> GLIBC_GENERATE_LOCALES = "en_GB.UTF-8 fr_CH.UTF-8"
>>
>> # ccache always overfill $HOME....
>> CCACHE=""
>>
>> # What kind of images do we want?
>> IMAGE_FSTYPES = "jffs2 tar.gz"
>>
>> # Set TMPDIR instead of defaulting it to $pwd/tmp
>> TMPDIR = "/usr/local/OE/${DISTRO}/"
>>
>> # Make use of my SMP box
>> PARALLEL_MAKE="-j4"
>> BB_NUMBER_THREADS = "2"
>>
>> # Set the Distro
>> DISTRO = "angstrom-2008.1"
>>
>> # 'uclibc' or 'glibc' or 'eglibc'
>> #ANGSTROM_MODE = "glibc"
>>
>> MACHINE = "mx31moboard"
>
> Thank you for your help, that would be really nice to fix this, because I am
> not able to build rootfs images at this point because of this problem.
>
> Regards
>
> Valentin





^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: sanity test problems at end of build
  2008-11-27 10:55 ` Koen Kooi
@ 2008-11-27 11:27   ` Stanislav Brabec
  2008-11-27 11:44     ` Koen Kooi
  0 siblings, 1 reply; 10+ messages in thread
From: Stanislav Brabec @ 2008-11-27 11:27 UTC (permalink / raw)
  To: openembedded-devel

Koen Kooi wrote:
> On 27-11-08 11:42, Valentin Longchamp wrote:
> > Hello,
> >
> > Sorry if it is a repost, but I have got not answer and have not seen my mail
> > in the mailing-list archives, so I send it again
> 
> I know the problem exists for some people, but I have never been able to 
> reproduce it. People having this problem should debug why ncurses 
> suddenly decides to mess up its .la files. Or better, look at the .la 
> files to see what's triggering insane.bbclass

>>I had read that this could have something to do with the fact that -tmp was in 
>>the name of the tmp build dir. However it is not the case

I guess it may be the case. Somebody mentioned a theory, that it is
caused by TMPDIR set in the local.conf. Your local.conf sets TMPDIR.

Could you comment TMPDIR out and then rebuild your image from scratch?

-- 
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus




^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: sanity test problems at end of build
  2008-11-27 11:27   ` Stanislav Brabec
@ 2008-11-27 11:44     ` Koen Kooi
  2008-11-27 14:53       ` Valentin Longchamp
  0 siblings, 1 reply; 10+ messages in thread
From: Koen Kooi @ 2008-11-27 11:44 UTC (permalink / raw)
  To: openembedded-devel

On 27-11-08 12:27, Stanislav Brabec wrote:
> Koen Kooi wrote:
>> On 27-11-08 11:42, Valentin Longchamp wrote:
>>> Hello,
>>>
>>> Sorry if it is a repost, but I have got not answer and have not seen my mail
>>> in the mailing-list archives, so I send it again
>> I know the problem exists for some people, but I have never been able to
>> reproduce it. People having this problem should debug why ncurses
>> suddenly decides to mess up its .la files. Or better, look at the .la
>> files to see what's triggering insane.bbclass
>
>>> I had read that this could have something to do with the fact that -tmp was in
>>> the name of the tmp build dir. However it is not the case
>
> I guess it may be the case. Somebody mentioned a theory, that it is
> caused by TMPDIR set in the local.conf. Your local.conf sets TMPDIR.
>
> Could you comment TMPDIR out and then rebuild your image from scratch?

That theory has already been debunked. Not setting TMPDIR opens up a 
whole other can of worms.

regards,

Koen




^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: sanity test problems at end of build
  2008-11-27 11:44     ` Koen Kooi
@ 2008-11-27 14:53       ` Valentin Longchamp
  2008-11-27 15:12         ` Koen Kooi
  2008-11-27 18:46         ` Stanislav Brabec
  0 siblings, 2 replies; 10+ messages in thread
From: Valentin Longchamp @ 2008-11-27 14:53 UTC (permalink / raw)
  To: openembedded-devel@lists.openembedded.org

On Thursday 27 November 2008 12:44:24 Koen Kooi wrote:
> On 27-11-08 12:27, Stanislav Brabec wrote:
> > Koen Kooi wrote:
> >> On 27-11-08 11:42, Valentin Longchamp wrote:
> >>> Hello,
> >>>
> >>> Sorry if it is a repost, but I have got not answer and have not seen my
> >>> mail in the mailing-list archives, so I send it again
> >>
> >> I know the problem exists for some people, but I have never been able to
> >> reproduce it. People having this problem should debug why ncurses
> >> suddenly decides to mess up its .la files. Or better, look at the .la
> >> files to see what's triggering insane.bbclass
> >>
> >>> I had read that this could have something to do with the fact that -tmp
> >>> was in the name of the tmp build dir. However it is not the case
> >
> > I guess it may be the case. Somebody mentioned a theory, that it is
> > caused by TMPDIR set in the local.conf. Your local.conf sets TMPDIR.
> >
> > Could you comment TMPDIR out and then rebuild your image from scratch?
>
> That theory has already been debunked. Not setting TMPDIR opens up a
> whole other can of worms.
>

Well, maybe it has been debunked, but it did the trick for me ... but I really 
don't understand why.

Could it be possible that it is a dash/bash issue ? (both the systems I work 
on are ubuntu-based and use dash).

Regards

Valentin




^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: sanity test problems at end of build
  2008-11-27 14:53       ` Valentin Longchamp
@ 2008-11-27 15:12         ` Koen Kooi
  2008-11-27 18:46         ` Stanislav Brabec
  1 sibling, 0 replies; 10+ messages in thread
From: Koen Kooi @ 2008-11-27 15:12 UTC (permalink / raw)
  To: openembedded-devel

On 27-11-08 15:53, Valentin Longchamp wrote:
> On Thursday 27 November 2008 12:44:24 Koen Kooi wrote:
>> On 27-11-08 12:27, Stanislav Brabec wrote:
>>> Koen Kooi wrote:
>>>> On 27-11-08 11:42, Valentin Longchamp wrote:
>>>>> Hello,
>>>>>
>>>>> Sorry if it is a repost, but I have got not answer and have not seen my
>>>>> mail in the mailing-list archives, so I send it again
>>>> I know the problem exists for some people, but I have never been able to
>>>> reproduce it. People having this problem should debug why ncurses
>>>> suddenly decides to mess up its .la files. Or better, look at the .la
>>>> files to see what's triggering insane.bbclass
>>>>
>>>>> I had read that this could have something to do with the fact that -tmp
>>>>> was in the name of the tmp build dir. However it is not the case
>>> I guess it may be the case. Somebody mentioned a theory, that it is
>>> caused by TMPDIR set in the local.conf. Your local.conf sets TMPDIR.
>>>
>>> Could you comment TMPDIR out and then rebuild your image from scratch?
>> That theory has already been debunked. Not setting TMPDIR opens up a
>> whole other can of worms.
>>
>
> Well, maybe it has been debunked, but it did the trick for me ... but I really
> don't understand why.
>
> Could it be possible that it is a dash/bash issue ? (both the systems I work
> on are ubuntu-based and use dash).

Don't use dash as shell, too many things have bashisms, like libtool.

regards,

Koen




^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: sanity test problems at end of build
  2008-11-27 14:53       ` Valentin Longchamp
  2008-11-27 15:12         ` Koen Kooi
@ 2008-11-27 18:46         ` Stanislav Brabec
  2008-11-28 13:56           ` Valentin Longchamp
  1 sibling, 1 reply; 10+ messages in thread
From: Stanislav Brabec @ 2008-11-27 18:46 UTC (permalink / raw)
  To: openembedded-devel

Valentin Longchamp wrote:

> > > Could you comment TMPDIR out and then rebuild your image from scratch?
> >
> > That theory has already been debunked. Not setting TMPDIR opens up a
> > whole other can of worms.

> Well, maybe it has been debunked, but it did the trick for me ... but I really 
> don't understand why.

Do you have a copy of the build dir of ncurses of failed build? Can you
compare them? Are files in image and install subdirs correct (i. e. no
reference to staging dir)? Does temp/run.do_install correct code to fix
la files? Recipe seems to call autotools_do_install, which should fix
it.

-- 
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus




^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: sanity test problems at end of build
  2008-11-27 18:46         ` Stanislav Brabec
@ 2008-11-28 13:56           ` Valentin Longchamp
  0 siblings, 0 replies; 10+ messages in thread
From: Valentin Longchamp @ 2008-11-28 13:56 UTC (permalink / raw)
  To: openembedded-devel@lists.openembedded.org

On Thursday 27 November 2008 19:46:32 Stanislav Brabec wrote:
> Valentin Longchamp wrote:
> > > > Could you comment TMPDIR out and then rebuild your image from
> > > > scratch?
> > >
> > > That theory has already been debunked. Not setting TMPDIR opens up a
> > > whole other can of worms.
> >
> > Well, maybe it has been debunked, but it did the trick for me ... but I
> > really don't understand why.
>
> Do you have a copy of the build dir of ncurses of failed build? Can you
> compare them? Are files in image and install subdirs correct (i. e. no
> reference to staging dir)? Does temp/run.do_install correct code to fix
> la files? Recipe seems to call autotools_do_install, which should fix
> it.

Yes I do have a copy of the both builds and I have tried to compare their 
logs. However I have not found something fundamentally different for both 
builds in the logs, they look identical except for the paths for work 
directory (but I haven't proofed all the log files precisely, would take me 
ages and don't have time for this now).

The files of the succeeding build are correct in both image and install (no 
more references):
- wrong build (libncurses.la snip):
# Libraries that this one depends upon.
dependency_libs=' -L/home/valentin/OE/angstrom/work/armv6-angstrom-linux-
gnueabi/ncurses-5.4-r15/ncurses-5.4/lib'

- correct build (libncurses.la snip):
# Libraries that this one depends upon.
dependency_libs='

I don't really know where to look at more precisely, if you point me to 
somewhere, I'll have a look.

Regards

Valentin



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: sanity test problems at end of build
@ 2008-11-29 11:44 代尔欣
  2008-11-30 17:44 ` Stanislav Brabec
  0 siblings, 1 reply; 10+ messages in thread
From: 代尔欣 @ 2008-11-29 11:44 UTC (permalink / raw)
  To: openembedded-devel

Hello..,
   I also met this problem. In may case, from  the log:

ERROR: QA Issue: paragui.pc failed sanity check
....
>> QA staging was broken by the package built above
>> ERROR: Error in executing:
>> ERROR: Exception:<type 'exceptions.SystemExit'>  Message:1
>> ERROR: Printing the environment of the function


if it is because the file paragui.pc:

prefix=/usr
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include
Name: ParaGUI
Description: cross-platform widget library
Version: 1.1.8
Libs: -lparagui -lsigc-1.2   -L/usr/lib -Wl,-rpath,/usr/lib -lSDL -lpthread
-lexpat -lfreetype -lz  -lstdc++
Cflags: -I/usr/lib/sigc++-1.2/include -I/usr/include/sigc++-1.2
-I/usr/include/freetype2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT
After some debug, I found if I remove below lines from paragui.pc

Libs: -lparagui -lsigc-1.2   -L/usr/lib -Wl,-rpath,/usr/lib -lSDL -lpthread
-lexpat -lfreetype -lz  -lstdc++
Cflags: -I/usr/lib/sigc++-1.2/include -I/usr/include/sigc++-1.2
-I/usr/include/freetype2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT

The error is gone. But I don't think it is a correct fix. Because some
packages may use pkgconfig with this file. To find the clue, I have question
about this error, hope someone can answer me.

Q:
1. What is the purpose of the QA sanity check? And How this check do?

2. Just a guess, QA sanity check, Is it for checking the lib or include file
installed correctly base on the .pc file or the .la(mail in Valentin
Longchamp)? If it is, I think the error is in the bb files or Makefile in
the package, it can't install the lib correctly.

Best Regards.


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: sanity test problems at end of build
  2008-11-29 11:44 代尔欣
@ 2008-11-30 17:44 ` Stanislav Brabec
  0 siblings, 0 replies; 10+ messages in thread
From: Stanislav Brabec @ 2008-11-30 17:44 UTC (permalink / raw)
  To: openembedded-devel

代尔欣 wrote:

> Q:
> 1. What is the purpose of the QA sanity check? And How this check do?

.pc or .la files referring to the build time paths not existing target
system will break native compilation in the best case, and causes run
time failures in worst case.

In general, all references to the build system paths (except debug info
source code references) are incorrect, and QA check will reject them.

> 2. Just a guess, QA sanity check, Is it for checking the lib or include file
> installed correctly base on the .pc file or the .la(mail in Valentin
> Longchamp)? If it is, I think the error is in the bb files or Makefile in
> the package, it can't install the lib correctly.

It is not so easy. Pkgconfig nor libtool are not aware of advanced
techniques of cross compilation. Packager must find potential problems
and create tricks to prevent them.

The most often sources of problems:

- There is no simple way to discriminate between calling of build time
binaries as tools (must be native), calling build time binaries as
source of compilation info (must be native, but must return info for
target platform), actual path to target binary or library and finally
target path to target binary or library.

- Combining of differnt approaches to get information together. For
example use of output of binconfig (*-config) as a source for pkgconfig
file (*.pc) will most probably cause problems - binconfig requires
custom patching, pkg-config has support for sysroot and needs target
paths.


________________________________________________________________________
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus




^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2008-11-30 17:48 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-11-27 10:42 sanity test problems at end of build Valentin Longchamp
2008-11-27 10:55 ` Koen Kooi
2008-11-27 11:27   ` Stanislav Brabec
2008-11-27 11:44     ` Koen Kooi
2008-11-27 14:53       ` Valentin Longchamp
2008-11-27 15:12         ` Koen Kooi
2008-11-27 18:46         ` Stanislav Brabec
2008-11-28 13:56           ` Valentin Longchamp
  -- strict thread matches above, loose matches on Subject: below --
2008-11-29 11:44 代尔欣
2008-11-30 17:44 ` Stanislav Brabec

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.