Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 12
i am compilaing and glib for my ARM baord and i am getting one error see Code: checking for format to printf and scanf a guint64... none checking for an ...
  1. #1
    Linux User
    Join Date
    Aug 2008
    Location
    Trichy,India
    Posts
    308

    glib cross compilation

    i am compilaing and glib for my ARM baord and i am getting one error
    see
    Code:
    checking for format to printf and scanf a guint64... none
    checking for an ANSI C-conforming const... yes
    checking if malloc() and friends prototypes are gmem.h compatible... yes
    checking for growing stack pointer... configure: error: in `/mnt/freescale/sources/glib-2.22.0':
    configure: error: cannot run test program while cross compiling
    See `config.log' for more details.
    Configuration of glib library  has failed
    sharief@sharief-desktop:/mnt/freescale/sources/glib-2.22.0$
    can anyone help me..what is this? and how to clear that?
    Thanks in advance...

  2. #2
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
    Posts
    8,970
    The configure command / script checks for available capabilities in many cases by compiling/running a simple test program. However, when you are cross-compiling (building for one target on another type of system), then this is not possible. Check the configure options (./configure --help) to see if there is one that will disable certain tests when cross-compiling.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  3. #3
    Linux User
    Join Date
    Aug 2008
    Location
    Trichy,India
    Posts
    308
    yes i did "make distclean" and again i run that configuration script. Now it works fine for me. Thank you
    Thanks in advance...

  4. #4
    Linux User
    Join Date
    Aug 2008
    Location
    Trichy,India
    Posts
    308
    it works fine for me. now when i tried to compile again i am getting the following error

    Code:
    checking for special C compiler options needed for large files... no
    checking for _FILE_OFFSET_BITS value needed for large files... 64
    checking for pkg-config... /mnt/freescale//toolchain/bin//pkg-config
    configure: error: *** pkg-config too old; version 0.16 or better required.
    Configuration of glib library  has failed
    sharief@sharief-desktop:/mnt/freescale/sources/glib-2.22.0$
    Can anyone help me
    Thanks in advance...

  5. #5
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
    Posts
    8,970
    It sounds like your code needs to handle files > 4GB in size and the configuration options in pkg-config are out of date. Whether one is related to the other is something I don't know, but you need to check your sources to be sure you have the components you need. At least you are making progress. You just aren't on the ground as yet...
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  6. #6
    Linux User
    Join Date
    Aug 2008
    Location
    Trichy,India
    Posts
    308
    yes i fixed this problem when i download one new pkg-config and compiled it.Thanks a lot
    Thanks in advance...

  7. #7
    Just Joined! striker07's Avatar
    Join Date
    Jul 2010
    Location
    Santa Rita do Sapucaí, Brazil
    Posts
    47
    Sorry for reopen this topic, but I have the same problem described - when I run the configure script, it returns 'cannot run test program while cross compiling'.

    I run the 'make distclean', but the same error remains...

  8. #8
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
    Posts
    8,970
    It sounds like the configure script and make file(s) have a dependency problem on the test suite, which since your build host is not of the same architecture as the target host, it cannot run and you get this error. Check the configure options (./configure --help) to see if you can disable the autotest suite.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  9. #9
    Just Joined! striker07's Avatar
    Join Date
    Jul 2010
    Location
    Santa Rita do Sapucaí, Brazil
    Posts
    47
    I didn't found any option. Here the result of ./configure --help:

    Code:
    `configure' configures glib 2.29.2 to adapt to many kinds of systems.
    
    Usage: ./configure [OPTION]... [VAR=VALUE]...
    
    To assign environment variables (e.g., CC, CFLAGS...), specify them as
    VAR=VALUE.  See below for descriptions of some of the useful variables.
    
    Defaults for the options are specified in brackets.
    
    Configuration:
      -h, --help              display this help and exit
          --help=short        display options specific to this package
          --help=recursive    display the short help of all the included packages
      -V, --version           display version information and exit
      -q, --quiet, --silent   do not print `checking ...' messages
          --cache-file=FILE   cache test results in FILE [disabled]
      -C, --config-cache      alias for `--cache-file=config.cache'
      -n, --no-create         do not create output files
          --srcdir=DIR        find the sources in DIR [configure dir or `..']
    
    Installation directories:
      --prefix=PREFIX         install architecture-independent files in PREFIX
                              [/usr/local]
      --exec-prefix=EPREFIX   install architecture-dependent files in EPREFIX
                              [PREFIX]
    
    By default, `make install' will install all the files in
    `/usr/local/bin', `/usr/local/lib' etc.  You can specify
    an installation prefix other than `/usr/local' using `--prefix',
    for instance `--prefix=$HOME'.
    
    For better control, use the options below.
    
    Fine tuning of the installation directories:
      --bindir=DIR            user executables [EPREFIX/bin]
      --sbindir=DIR           system admin executables [EPREFIX/sbin]
      --libexecdir=DIR        program executables [EPREFIX/libexec]
      --sysconfdir=DIR        read-only single-machine data [PREFIX/etc]
      --sharedstatedir=DIR    modifiable architecture-independent data [PREFIX/com]
      --localstatedir=DIR     modifiable single-machine data [PREFIX/var]
      --libdir=DIR            object code libraries [EPREFIX/lib]
      --includedir=DIR        C header files [PREFIX/include]
      --oldincludedir=DIR     C header files for non-gcc [/usr/include]
      --datarootdir=DIR       read-only arch.-independent data root [PREFIX/share]
      --datadir=DIR           read-only architecture-independent data [DATAROOTDIR]
      --infodir=DIR           info documentation [DATAROOTDIR/info]
      --localedir=DIR         locale-dependent data [DATAROOTDIR/locale]
      --mandir=DIR            man documentation [DATAROOTDIR/man]
      --docdir=DIR            documentation root [DATAROOTDIR/doc/glib]
      --htmldir=DIR           html documentation [DOCDIR]
      --dvidir=DIR            dvi documentation [DOCDIR]
      --pdfdir=DIR            pdf documentation [DOCDIR]
      --psdir=DIR             ps documentation [DOCDIR]
    
    Program names:
      --program-prefix=PREFIX            prepend PREFIX to installed program names
      --program-suffix=SUFFIX            append SUFFIX to installed program names
      --program-transform-name=PROGRAM   run sed PROGRAM on installed program names
    
    System types:
      --build=BUILD     configure for building on BUILD [guessed]
      --host=HOST       cross-compile to build programs to run on HOST [BUILD]
    
    Optional Features:
      --disable-option-checking  ignore unrecognized --enable/--with options
      --disable-FEATURE       do not include FEATURE (same as --enable-FEATURE=no)
      --enable-FEATURE[=ARG]  include FEATURE [ARG=yes]
      --enable-silent-rules          less verbose build output (undo: `make V=1')
      --disable-silent-rules         verbose build output (undo: `make V=0')
      --enable-maintainer-mode  enable make rules and dependencies not useful
    			  (and sometimes confusing) to the casual installer
      --disable-dependency-tracking  speeds up one-time build
      --enable-dependency-tracking   do not reject slow dependency extractors
      --enable-debug=[no/minimum/yes]
                              turn on debugging [default=yes]
      --enable-gc-friendly    turn on garbage collector friendliness [default=no]
      --disable-mem-pools     disable all glib memory pools
      --enable-threads        turn on basic thread support [default=yes] ([=no]
                              will override --with-threads)
      --disable-rebuilds      disable all source autogeneration rules
      --disable-largefile     omit support for large files
      --enable-iconv-cache=[yes/no/auto]
                              cache iconv descriptors [default=auto]
      --enable-static[=PKGS]  build static libraries [default=no]
      --enable-shared[=PKGS]  build shared libraries [default=yes]
      --enable-fast-install[=PKGS]
                              optimize for fast installation [default=yes]
      --disable-libtool-lock  avoid locking (might break parallel builds)
      --enable-included-printf
                              use included printf [default=auto]
      --disable-selinux       build without selinux support
      --disable-fam          build without enabling fam for file system monitoring
      --disable-xattr           build without xattr support
      --disable-regex         disable the compilation of GRegex
      --enable-gtk-doc        use gtk-doc to build documentation [[default=no]]
      --enable-gtk-doc-html   build documentation in html format [[default=yes]]
      --enable-gtk-doc-pdf    build documentation in pdf format [[default=no]]
      --enable-man            regenerate man pages from Docbook [default=no]
      --enable-dtrace         Enable inclusion of dtrace trace support
      --enable-systemtap      Enable inclusion of systemtap trace support
      --enable-gcov           Enable gcov
      --disable-Bsymbolic     avoid linking with -Bsymbolic
    
    Optional Packages:
      --with-PACKAGE[=ARG]    use PACKAGE [ARG=yes]
      --without-PACKAGE       do not use PACKAGE (same as --with-PACKAGE=no)
      --with-runtime-libdir=RELPATH
                              Install runtime libraries relative to libdir
      --with-libiconv=[no/gnu/native]
                              use the libiconv library
      --with-pic              try to use only PIC/non-PIC objects [default=use
                              both]
      --with-gnu-ld           assume the C compiler uses GNU ld [default=no]
      --with-sysroot=DIR Search for dependent libraries within DIR
                            (or the compiler's sysroot if not specified).
      --with-gio-module-dir=PATH
                              Load gio modules from this directory
                              [LIBDIR/gio/modules]
      --with-threads=[none/posix/dce/win32]
                              specify a thread implementation to use
      --with-pcre=[internal/system]
                              specify whether to use the internal or the
                              system-supplied PCRE library
      --with-html-dir=PATH    path to installed docs
      --with-xml-catalog=CATALOG
                              path to xml catalog to use
      --with-tapset-install-dir
                              The absolute path where the systemtap tapsets will
                              be installed
    
    Some influential environment variables:
      CC          C compiler command
      CFLAGS      C compiler flags
      LDFLAGS     linker flags, e.g. -L<lib dir> if you have libraries in a
                  nonstandard directory <lib dir>
      LIBS        libraries to pass to the linker, e.g. -l<library>
      CPPFLAGS    (Objective) C/C++ preprocessor flags, e.g. -I<include dir> if
                  you have headers in a nonstandard directory <include dir>
      CPP         C preprocessor
      CXX         C++ compiler command
      CXXFLAGS    C++ compiler flags
      PKG_CONFIG  path to pkg-config utility
      PKG_CONFIG_PATH
                  directories to add to pkg-config's search path
      PKG_CONFIG_LIBDIR
                  path overriding pkg-config's built-in search path
      ZLIB_CFLAGS C compiler flags for ZLIB, overriding pkg-config
      ZLIB_LIBS   linker flags for ZLIB, overriding pkg-config
      CXXCPP      C++ preprocessor
      PCRE_CFLAGS C compiler flags for PCRE, overriding pkg-config
      PCRE_LIBS   linker flags for PCRE, overriding pkg-config
      DBUS1_CFLAGS
                  C compiler flags for DBUS1, overriding pkg-config
      DBUS1_LIBS  linker flags for DBUS1, overriding pkg-config
    
    Use these variables to override the choices made by `configure' or to help
    it to find libraries and programs with nonstandard names/locations.
    
    Report bugs to <http://bugzilla.gnome.org/enter_bug.cgi?product=glib>.
    By the way, I've configured the arm-linux.cache (as required in the official doc) file with this content:

    Code:
    glib_cv_long_long_format=ll
    glib_cv_stack_grows=no
    ac_cv_func_posix_getpwuid_r=yes
    glib_cv_uscore=yes

  10. #10
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
    Posts
    8,970
    You might try the option --disable-dependency-tracking
    Worth a try.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
...