On Wed, Apr 17, 2013 at 5:48 PM, Mike Goins <[email protected]> wrote: > > I have just run into the same issue. I am working on a couple packages > that require pkgconfig, but I am having problems building the current version > in ltib. This pkgconfig has a built-in glib which has difficulties > cross-compiling and doesn't appear to be an obvious way to disable it. The > best thing I can tell you is just to avoid using it (internal) if at all > possible.
Ah, now I understand. pkg-config in ltib was not designed to be installed on targets, it's there for the host. ltib also automatically sets up the PKG_CONFIG_PATH when calling it. > > > On Sat, Apr 13, 2013 at 4:54 AM, Stuart Hughes <[email protected]> wrote: >> >> Hi Francios, >> >> Without looking at the code you're looking at I can't say. I'd suggest >> looking at the source, identifying why gcc is complaining and then >> seeing if there's an update to the package that fixes this. >> >> One possibility is that you cannot simply comment out the cross-compile >> test. You may need to set the result that the test would have set, had >> it been run. Often the tests are probing the system to see what it can >> use, maybe the error you have is as a consequence of not running that >> configure test. >> >> Regards, Stuart >> >> On 12/04/13 17:02, Francois Bouchard wrote: >> > Hi Stuart, >> > >> > I disabled all lines in the script where it was exiting with code '1' >> > (at the cross compiling test error). Now it seems ok ( configure: exit >> > 0), but I got new errors: >> > ./glibconfig.h:82: error: flexible array member in union. >> > >> > Does it mean that I have to tweak the source code? >> > >> > Regards, >> > >> > Francois >> > >> > >> > >> > >> > 2013/4/6 Stuart Hughes <[email protected] <mailto:[email protected]>> >> > >> > Hi Francios, >> > >> > You can't fool the configure by setting cross-compile = no if you are >> > cross compiling. >> > >> > What you need to do is change configure to bypass that test, setting >> > the >> > result as you expect it to be (that is passed). >> > >> > Look at the current pkg-config in LTIB and see if there are any patches >> > that do this already, if so you need to forward port this to the later >> > version. >> > >> > Regards, Stuart >> > >> > On 05/04/13 21:09, Francois Bouchard wrote: >> > > Hi Stuart, >> > > >> > > >> > >> What package are you trying to build? >> > > Quite a few actually by calling $ ./ltib, but it is failing at >> > glib, in >> > > pkg-config. >> > > >> > >>The pkg-config in LTIB is setup to work with cross compile. It's a >> > >>"special" patched version in /opt/ltib/usr/bin/pkg-config that is >> > able >> > >>to use a relative path to figure out include/libs. >> > > ok so I reverted to the version in LTIB, which is 0.21. I can see a >> > > glib copy with it, version 1.2.8. >> > > >> > >> Am I right in thinking the problem you have is you're trying to >> > build a >> > >> package and are getting this error: >> > > Yes, and here is a longer part of the message : >> > > (...) >> > > checking for gcc option to accept ANSI C... none needed >> > > checking for a BSD-compatible install... /usr/bin/install -c >> > > checking for extra flags to get ANSI library prototypes... >> > configure: >> > > error: cannot run test program while cross compiling >> > > See `config.log' for more details. >> > > configure: error: /bin/bash './configure' failed for glib-1.2.8 >> > > error: Bad exit status from >> > > /home/fbouchard/ltib/ltib-modelo-20100709/tmp/rpm-tmp.88102 (%build) >> > > >> > > >> > > RPM build errors: >> > > Bad exit status from >> > > /home/fbouchard/ltib/ltib-modelo-20100709/tmp/rpm-tmp.88102 (%build) >> > > Build time for pkgconfig: 16 seconds >> > > >> > > Failed building pkgconfig >> > > --------------------------------------------------- >> > > >> > > >> > >> If so, then I don't think pkg-config (being called from configure) >> > is >> > >> the problem. As I tried to say before you need to fix the configure >> > >> script in the package you are adding so that it does not have to >> > run the >> > >> cross compiled test. >> > > Yes. There is some FIXME labels in it, and there is the variable >> > > 'cross_compiling' in there that I have assigned to 'no'. That made >> > it >> > > work, the error is gone. Now there is a different one in the same >> > > module, but it is progressing:) >> > > >> > > checking size of char... configure: error: cannot compute sizeof >> > (char), 77 >> > > See `config.log' for more details. >> > > configure: error: /bin/bash './configure' failed for glib-1.2.8 >> > > ------------------------------------------- >> > > >> > > Got to continue fixing the configure script I guess. Thanks. >> > > >> > > Thank you, >> > > >> > > Francois >> > > >> > > >> > > >> > > >> > > 2013/4/4 Stuart Hughes <[email protected] <mailto:[email protected]> >> > <mailto:[email protected] <mailto:[email protected]>>> >> > > >> > > Hi Francois, >> > > >> > > I didn't really follow that completely what you are saying. >> > > >> > > The pkg-config in LTIB is setup to work with cross compile. >> > It's a >> > > "special" patched version in /opt/ltib/usr/bin/pkg-config that >> > is able >> > > to use a relative path to figure out include/libs. >> > > >> > > Am I right in thinking the problem you have is you're trying >> > to build a >> > > package and are getting this error: >> > > >> > > >> checking for growing stack pointer... configure: error: in >> > > >> `/ltib/ltib-modelo-20100709/rpm/BUILD/pkg-config-0.28/glib': >> > > >> *configure: error: cannot run test program while cross >> > compiling* >> > > >> See `config.log' for more details >> > > >> > > If so, then I don't think pkg-config (being called from >> > configure) is >> > > the problem. As I tried to say before you need to fix the >> > configure >> > > script in the package you are adding so that it does not have >> > to run the >> > > cross compiled test. >> > > >> > > What package are you trying to build? >> > > >> > > Regards, Stuart >> > > >> > > On 03/04/13 20:30, Francois Bouchard wrote: >> > > > Hi Stuart, >> > > > >> > > > Having read a lot on the subject, it is indeed hard to >> > cross-compile >> > > > module pkg-config. I have read that since pkg-config ver >> > 0.28, glib >> > > > must be built before it, and by setting GLIB_FLAGS and >> > GLIB_LIBS, >> > > > pkg-config won't be used. >> > > > >> > > > But there is differences in the options we have for glib >> > > > (--with-internal-glib which is the one bundled with it, and >> > > > --with-installed-glib) >> > > > >> > > > So my guess is that for pkg-config, as we build glib first, >> > the option >> > > > passed to ./configure is --with-installed-glib, but then again >> > > GLIB_LIBS >> > > > and GLIB_FLAGS must be assigned. I'm there now. >> > > > >> > > > But, again here we are cross-compiling so what it is written on >> > > the net >> > > > doesn't always apply. >> > > > >> > > > Francois >> > > > >> > > > >> > > > >> > > > >> > > > 2013/3/28 Stuart Hughes <[email protected] <mailto:[email protected]> >> > <mailto:[email protected] <mailto:[email protected]>> >> > > <mailto:[email protected] <mailto:[email protected]> >> > <mailto:[email protected] <mailto:[email protected]>>>> >> > > > >> > > > Hi Francios, >> > > > >> > > > In the new package you are trying to add you will need >> > to add >> > > a patch to >> > > > change the configure script so that it does not try to >> > run the >> > > test that >> > > > is failing. >> > > > >> > > > As the output is showing, the test it is trying to do won't >> > > work when >> > > > cross compiling. This is fairly common and you can >> > check in other >> > > > packages (sorry I can't recall) that have similar >> > changes applied. >> > > > >> > > > If you're lucky sometimes a package has an option to >> > configure >> > > that will >> > > > make it work for cross compiling. You will need to >> > google to >> > > find out >> > > > if this applied for your package (what is it?) >> > > > >> > > > Regards, Stuart >> > > > >> > > > On 27/03/13 19:31, Francois Bouchard wrote: >> > > > > Hi, >> > > > > >> > > > > We are trying since a couple of days to add some >> > package to litb >> > > > and it >> > > > > basically won't compile with package pkg-config. We >> > build >> > > it using >> > > > > --with-internal-glib >> > > > > >> > > > > The following error occurs when using >> > --with-internal-glib >> > > flag to >> > > > > configure pkg-config: >> > > > > (.....) >> > > > > checking for growing stack pointer... configure: error: >> > in >> > > > > >> > `/ltib/ltib-modelo-20100709/rpm/BUILD/pkg-config-0.28/glib': >> > > > > *configure: error: cannot run test program while cross >> > > compiling* >> > > > > See `config.log' for more details >> > > > > configure: error: ./configure failed for glib >> > > > > >> > > > > Now from where can you disable the test program, in which >> > > script? >> > > > > >> > > > > Thanks, >> > > > > Francois >> > > > > >> > > > > >> > > > > _______________________________________________ >> > > > > LTIB home page: http://ltib.org >> > > > > >> > > > > Ltib mailing list >> > > > > [email protected] <mailto:[email protected]> >> > <mailto:[email protected] <mailto:[email protected]>> >> > > <mailto:[email protected] <mailto:[email protected]> >> > <mailto:[email protected] <mailto:[email protected]>>> >> > > > > https://lists.nongnu.org/mailman/listinfo/ltib >> > > > > >> > > > >> > > > >> > > >> > > >> > >> > >> >> _______________________________________________ >> LTIB home page: http://ltib.org >> >> Ltib mailing list >> [email protected] >> https://lists.nongnu.org/mailman/listinfo/ltib > > _______________________________________________ LTIB home page: http://ltib.org Ltib mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/ltib
