public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Казанков Александр Владимирович" <johnrdoe63@cregion.ru>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Standalone libstdc++
Date: Fri, 26 Jun 2009 21:24:22 +0400	[thread overview]
Message-ID: <1246037062.15270.16.camel@dsk01> (raw)

[-- Attachment #1: Type: text/plain, Size: 6419 bytes --]

Hello.

I wish to compile library libstdc ++ being based on
sys-dev/gcc/gcc-4.3.2-r3.ebuild:

src_compile() {

    gcc_do_filter_flags
    einfo "CFLAGS=\"${CFLAGS}\""
    einfo "CXXFLAGS=\"${CXXFLAGS}\""

    # Build in a separate build tree
    mkdir -p "${WORKDIR}"/build
    pushd "${WORKDIR}"/build > /dev/null

    einfo "Configuring ${PN} ..."
    gcc_do_configure

    touch "${S}"/gcc/c-gperf.h

    einfo "Compiling ${PN} ..."
    gcc_do_make all-target-libstdc++-v3

    popd > /dev/null

}


But compilation does not pass successfully:

Checking multilib configuration for libgcc...
Configuring stage 1 in i686-pc-linux-gnu/libgcc
configure: creating cache ./config.cache
checking for --enable-version-specific-runtime-libs... no
checking for a BSD-compatible install... /usr/bin/install -c
checking for gawk... gawk
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for i686-pc-linux-gnu-ar... /usr/i686-pc-linux-gnu/bin/ar
checking for i686-pc-linux-gnu-lipo... lipo
checking for i686-pc-linux-gnu-nm... /var/tmp/portage/sys-libs/libstdc
++-v3-4.3.2/work/build/./gcc/nm
checking for
i686-pc-linux-gnu-ranlib... /usr/i686-pc-linux-gnu/bin/ranlib
checking for i686-pc-linux-gnu-strip... /usr/i686-pc-linux-gnu/bin/strip
checking whether ln -s works... yes
checking for i686-pc-linux-gnu-gcc... /./gcc/xgcc -B/./gcc/
-B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/
-isystem /usr/i686-pc-linux-gnu/include
-isystem /usr/i686-pc-linux-gnu/sys-include
checking for suffix of object files... configure: error: cannot compute
suffix of object files: cannot compile
See `config.log' for more details.
make[2]: *** [configure-stage1-target-libgcc] Ошибка 1
make[2]: Leaving directory `/var/tmp/portage/sys-libs/libstdc
++-v3-4.3.2/work/build'
make[1]: *** [stage1-bubble] Ошибка 2
make[1]: Leaving directory `/var/tmp/portage/sys-libs/libstdc
++-v3-4.3.2/work/build'
make: *** [stage_last] Ошибка 2
 * 
 * ERROR: sys-libs/libstdc++-v3-4.3.2 failed.
 * Call stack:
 *               ebuild.sh, line   48:  Called src_compile
 *             environment, line 4837:  Called gcc_do_make
'all-target-libstdc++-v3'
 *             environment, line 2873:  Called die
 * The specific snippet of code:
 *       emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}"
LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} ||
die "emake failed with ${GCC_MAKE_TARGET}";
 *  The die message:
 *   emake failed with all-target-libstdc++-v3


In config.log:

configure:1798: checking for i686-pc-linux-gnu-nm
configure:1824: result: /var/tmp/portage/sys-libs/libstdc
++-v3-4.3.2/work/build/./gcc/nm
configure:1877: checking for i686-pc-linux-gnu-ranlib
configure:1903: result: /usr/i686-pc-linux-gnu/bin/ranlib
configure:1957: checking for i686-pc-linux-gnu-strip
configure:1983: result: /usr/i686-pc-linux-gnu/bin/strip
configure:2034: checking whether ln -s works
configure:2038: result: yes
configure:2055: checking for i686-pc-linux-gnu-gcc
configure:2081: result: /./gcc/xgcc -B/./gcc/
-B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/
-isystem /usr/i686-pc-linux-gnu/include
-isystem /usr/i686-pc-linux-gnu/sys-include
configure:2363: checking for C compiler version
configure:2366: /./gcc/xgcc -B/./gcc/ -B/usr/i686-pc-linux-gnu/bin/
-B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include
-isystem /usr/i686-pc-linux-gnu/sys-include --version </dev/null >&5
/var/tmp/portage/sys-libs/libstdc
++-v3-4.3.2/work/gcc-4.3.2/libgcc/configure: line 2367: /./gcc/xgcc: No
such file or directory
configure:2369: $? = 127
configure:2371: /./gcc/xgcc -B/./gcc/ -B/usr/i686-pc-linux-gnu/bin/
-B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include
-isystem /usr/i686-pc-linux-gnu/sys-include -v </dev/null >&5
/var/tmp/portage/sys-libs/libstdc
++-v3-4.3.2/work/gcc-4.3.2/libgcc/configure: line 2372: /./gcc/xgcc: No
such file or directory
configure:2374: $? = 127
configure:2376: /./gcc/xgcc -B/./gcc/ -B/usr/i686-pc-linux-gnu/bin/
-B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include
-isystem /usr/i686-pc-linux-gnu/sys-include -V </dev/null >&5
/var/tmp/portage/sys-libs/libstdc
++-v3-4.3.2/work/gcc-4.3.2/libgcc/configure: line 2377: /./gcc/xgcc: No
such file or directory
configure:2379: $? = 127
configure:2398: /./gcc/xgcc -B/./gcc/ -B/usr/i686-pc-linux-gnu/bin/
-B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include
-isystem /usr/i686-pc-linux-gnu/sys-include -o conftest -O   conftest.c
>&5
/var/tmp/portage/sys-libs/libstdc
++-v3-4.3.2/work/gcc-4.3.2/libgcc/configure: line 2399: /./gcc/xgcc: No
such file or directory
configure:2401: $? = 127
configure:2567: checking for suffix of object files
configure:2588: /./gcc/xgcc -B/./gcc/ -B/usr/i686-pc-linux-gnu/bin/
-B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include
-isystem /usr/i686-pc-linux-gnu/sys-include -c -O  conftest.c >&5
/var/tmp/portage/sys-libs/libstdc
++-v3-4.3.2/work/gcc-4.3.2/libgcc/configure: line 2589: /./gcc/xgcc: No
such file or directory
configure:2591: $? = 127
configure: failed program was:
| /* confdefs.h.  */
|
| #define PACKAGE_NAME "GNU C Runtime Library"
| #define PACKAGE_TARNAME "libgcc"
| #define PACKAGE_VERSION "1.0"
| #define PACKAGE_STRING "GNU C Runtime Library 1.0"
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:2605: error: cannot compute suffix of object files: cannot
compile

## ---------------- ##
## Cache variables. ##
## ---------------- ##

.....
ac_cv_env_CC_value='/./gcc/xgcc -B/./gcc/
-B/usr/i686-pc-linux-gnu/bin/.........
....
ac_cv_prog_CC='/./gcc/xgcc -B/./gcc/
...
ac_cv_prog_NM=/var/tmp/portage/sys-libs/libstdc
++-v3-4.3.2/work/build/./gcc/nm

## ----------------- ##
## Output variables. ##
## ----------------- ##

...
CC='/./gcc/xgcc ....
....
NM='/var/tmp/portage/sys-libs/libstdc++-v3-4.3.2/work/build/./gcc/nm'
......

Such sensation that the prefix of a place of assemblage vanishes. That's
bug!?

-- 
С уважением,
Александр,
web: http://www.cregion.ru
jabber: johnrdoe63@jabber.ru
mailto:johnrdoe63@cregion.ru
(pgp: http://blackhole.pca.dfn.de)

[-- Attachment #2: Эта часть сообщения подписана цифровой подписью --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-06-26 17:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26 17:24 Казанков Александр Владимирович [this message]
2009-06-26 17:29 ` [gentoo-dev] Standalone libstdc++ Mike Auty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1246037062.15270.16.camel@dsk01 \
    --to=johnrdoe63@cregion.ru \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox