Re: [gentoo-user] Re: crossdev runtime version
On Tuesday, August 04, 2015 5:16:09 PM walt wrote: > On Tue, 04 Aug 2015 18:40:49 +0200 > Cor Legemaat wrote: > > > Hi: > > > > I want to install a mingw64 compiler with =dev-util/mingw64-runtime- > > 4.0.1, tried with the cmd: > > > crossdev --lenv 'CFLAGS="-march=generic -mtune=generic -O2 -pipe" > > > CXXFLAGS="-march=generic -mtune=generic -O2 -pipe"' --ex-gdb -t > > > x86_64-w64-mingw32 --ov-output /usr/local/portage-crossdev --l > > > 4.0.1 --k 4.0.1 -P '-v' > > but cross-x86_64-w64-mingw32/mingw64-runtime-3.2.0-r1 get installed. > > > > What am I doing wrong? > > I notice you are using a version of Evolution that is not available > yet in gentoo. Are you using gentoo package overlays, or installing > packages from non-gentoo source repositories? (I see /usr/local in > your message :) > > Sometimes these little details can give important clues. It should give you 4.0.1 even without the --l 4.0.1 as that's the latest unstable version. Are you sure that crossdev went all the way through? I usually have to disable the fortran use flag or it fails half way. If you have a previous version maybe the 3.2.0 version is from another build. What's the output of: qlop -gvH mingw64-runtime You could also use crossdev -C to remove it completely and start fresh (after cleaning any leftovers in /etc/portage). What is the contents of /etc/portage/package.keywords/cross-x86_64-w64-mingw32 after the build completes? It should have ~amd64 amd64 for mingw64-runtime. Also check that you don't have any cross-x86_64-w64-mingw32 entries anywhere else on your /etc/portage/package.* files and directories. You can also verify that /usr/local/portage-crossdev/cross-x86_64-mingw32 points to the right directory on /usr/portage just in case. If all that checks then I at a loss. It installed 4.0.1 for me without any arguments but the triplet. You could try: emerge -pv cross-x86_64-w64-mingw32/mingw64-runtime or emerge -pv =cross-x86_64-w64-mingw32/mingw64-runtime-4.0.1 and see if it gives you any clues. -- Fernando Rodriguez signature.asc Description: This is a digitally signed message part.
[gentoo-user] crossdev runtime version
Hi: I wand to install a mingw64 compiler with =dev-util/mingw64-runtime- 4.0.1, tried with the cmd: > crossdev --lenv 'CFLAGS="-march=generic -mtune=generic -O2 -pipe" > CXXFLAGS="-march=generic -mtune=generic -O2 -pipe"' --ex-gdb -t > x86_64-w64-mingw32 --ov-output /usr/local/portage-crossdev --l 4.0.1 > --k 4.0.1 -P '-v' but cross-x86_64-w64-mingw32/mingw64-runtime-3.2.0-r1 get installed. What am I doing wrong? Regards: Cor signature.asc Description: This is a digitally signed message part
Re: [gentoo-user] Re: crossdev runtime version
On Wed, 2015-08-05 at 00:45 -0400, Fernando Rodriguez wrote: > On Tuesday, August 04, 2015 5:16:09 PM walt wrote: > > On Tue, 04 Aug 2015 18:40:49 +0200 > > Cor Legemaat wrote: > > > > > Hi: > > > > > > I want to install a mingw64 compiler with =dev-util/mingw64- > > > runtime- 4.0.1, tried with the cmd: > > > > crossdev --lenv 'CFLAGS="-march=generic -mtune=generic -O2 - > > > > pipe" CXXFLAGS="-march=generic -mtune=generic -O2 -pipe"' --ex- > > > > gdb -t x86_64-w64-mingw32 --ov-output /usr/local/portage- > > > > crossdev --l 4.0.1 --k 4.0.1 -P '-v' > > > but cross-x86_64-w64-mingw32/mingw64-runtime-3.2.0-r1 get > > > installed. > > > > > > What am I doing wrong? > > > > I notice you are using a version of Evolution that is not > > available yet in gentoo. Are you using gentoo package overlays, > > or installing packages from non-gentoo source repositories? (I > > see /usr/local in your message :) > > > > Sometimes these little details can give important clues. > > It should give you 4.0.1 even without the --l 4.0.1 as that's the > latest > unstable version. Are you sure that crossdev went all the way > through? I > usually have to disable the fortran use flag or it fails half way. > If you have > a previous version maybe the 3.2.0 version is from another build. > What's the > output of: > > qlop -gvH mingw64-runtime > > You could also use crossdev -C to remove it completely and start > fresh (after > cleaning any leftovers in /etc/portage). > > What is the contents of /etc/portage/package.keywords/cross-x86_64- > w64-mingw32 > after the build completes? It should have ~amd64 amd64 for mingw64- > runtime. > > Also check that you don't have any cross-x86_64-w64-mingw32 entries > anywhere > else on your /etc/portage/package.* files and directories. > > You can also verify that /usr/local/portage-crossdev/cross-x86_64- > mingw32 > points to the right directory on /usr/portage just in case. > > If all that checks then I at a loss. It installed 4.0.1 for me > without any > arguments but the triplet. You could try: > > emerge -pv cross-x86_64-w64-mingw32/mingw64-runtime > or > emerge -pv =cross-x86_64-w64-mingw32/mingw64-runtime-4.0.1 > > and see if it gives you any clues. > Found it, tnx. I changed my portage from syncing over rsync to git according to https://wiki.gentoo.org/wiki/Project:Git_mirror that changed my repository from /usr/portage to /usr/portage/db and crossdev -C didn't delete the symlinks to the portage repository. Removed them manual now every thing fine. Regards: Cor signature.asc Description: This is a digitally signed message part
[gentoo-user] Re: crossdev runtime version
On Tue, 04 Aug 2015 18:40:49 +0200 Cor Legemaat wrote: > Hi: > > I want to install a mingw64 compiler with =dev-util/mingw64-runtime- > 4.0.1, tried with the cmd: > > crossdev --lenv 'CFLAGS="-march=generic -mtune=generic -O2 -pipe" > > CXXFLAGS="-march=generic -mtune=generic -O2 -pipe"' --ex-gdb -t > > x86_64-w64-mingw32 --ov-output /usr/local/portage-crossdev --l > > 4.0.1 --k 4.0.1 -P '-v' > but cross-x86_64-w64-mingw32/mingw64-runtime-3.2.0-r1 get installed. > > What am I doing wrong? I notice you are using a version of Evolution that is not available yet in gentoo. Are you using gentoo package overlays, or installing packages from non-gentoo source repositories? (I see /usr/local in your message :) Sometimes these little details can give important clues.
Re: [gentoo-user] Re: crossdev runtime version
On Tue, 2015-08-04 at 17:16 -0700, walt wrote: > On Tue, 04 Aug 2015 18:40:49 +0200 > Cor Legemaat wrote: > > > Hi: > > > > I want to install a mingw64 compiler with =dev-util/mingw64- > > runtime- > > 4.0.1, tried with the cmd: > > > crossdev --lenv 'CFLAGS="-march=generic -mtune=generic -O2 -pipe" > > > CXXFLAGS="-march=generic -mtune=generic -O2 -pipe"' --ex-gdb -t > > > x86_64-w64-mingw32 --ov-output /usr/local/portage-crossdev --l > > > 4.0.1 --k 4.0.1 -P '-v' > > but cross-x86_64-w64-mingw32/mingw64-runtime-3.2.0-r1 get > > installed. > > > > What am I doing wrong? > > I notice you are using a version of Evolution that is not available > yet in gentoo. Are you using gentoo package overlays, or installing > packages from non-gentoo source repositories? (I see /usr/local in > your message :) > > Sometimes these little details can give important clues. > > The pc with my mail on is a Funtoo current install but that is not the one where I try the crossdev on, will check later but I'm pretty sure my evolution is in gentoo overlay also 3.13.6. The one where I try the crossdev build on is a Gentoo Hardened stable install. The /usr/local/portage-crossdev is the path to the repository to install the cross compiler. Regards: Cor signature.asc Description: This is a digitally signed message part
Re: [gentoo-user] OT: GCC 5 Offloading
file (build.specs) to use when building gcc.
if ! tc_version_is_at_least 4.4 && want_minispecs ; then
setup_minispecs_gcc_build_specs
fi
local confgcc=( --host=${CHOST} --enable-as-accelerator-for=${CHOST} )
if is_crosscompile || tc-is-cross-compiler ; then
# Straight from the GCC install doc:
# "GCC has code to correctly determine the correct value for
target
# for nearly all native systems. Therefore, we highly recommend
you
# not provide a configure target when configuring a native
compiler."
confgcc+=( --target=${CTARGET} )
fi
[[ -n ${CBUILD} ]] && confgcc+=( --build=${CBUILD} )
confgcc+=(
--prefix="${PREFIX}"
--bindir="${BINPATH}"
--includedir="${INCLUDEPATH}"
--datadir="${DATAPATH}"
--mandir="${DATAPATH}/man"
--infodir="${DATAPATH}/info"
--with-gxx-include-dir="${STDCXX_INCDIR}"
)
# Stick the python scripts in their own slotted directory (bug #279252)
#
# --with-python-dir=DIR
# Specifies where to install the Python modules used for aot-compile.
DIR
# should not include the prefix used in installation. For example, if
the
# Python modules are to be installed in
/usr/lib/python2.5/site-packages,
# then --with-python-dir=/lib/python2.5/site-packages should be passed.
#
# This should translate into
"/share/gcc-data/${CTARGET}/${GCC_CONFIG_VER}/python"
if tc_version_is_at_least 4.4 ; then
confgcc+=( --with-python-dir=${DATAPATH/$PREFIX/}/python )
fi
### language options
local GCC_LANG="c"
is_cxx && GCC_LANG+=",c++"
is_d && GCC_LANG+=",d"
is_gcj && GCC_LANG+=",java"
is_go && GCC_LANG+=",go"
if is_objc || is_objcxx ; then
GCC_LANG+=",objc"
if tc_version_is_at_least 4 ; then
use objc-gc && confgcc+=( --enable-objc-gc )
fi
is_objcxx && GCC_LANG+=",obj-c++"
fi
# fortran support just got sillier! the lang value can be f77 for
# fortran77, f95 for fortran95, or just plain old fortran for the
# currently supported standard depending on gcc version.
is_fortran && GCC_LANG+=",fortran"
is_f77 && GCC_LANG+=",f77"
is_f95 && GCC_LANG+=",f95"
# We do NOT want 'ADA support' in here!
# is_ada && GCC_LANG+=",ada"
confgcc+=( --enable-languages=${GCC_LANG} )
### general options
confgcc+=(
--enable-obsolete
--enable-secureplt
--disable-werror
--with-system-zlib
)
if use nls ; then
confgcc+=( --enable-nls --without-included-gettext )
else
confgcc+=( --disable-nls )
fi
tc_version_is_at_least 3.4 || confgcc+=( --disable-libunwind-exceptions
)
# Use the default ("release") checking because upstream usually neglects
# to test "disabled" so it has a history of breaking. #317217
if tc_version_is_at_least 3.4 ; then
# The "release" keyword is new to 4.0. #551636
local off=$(tc_version_is_at_least 4.0 && echo release || echo
no)
confgcc+=( --enable-checking="${GCC_CHECKS_LIST:-$(usex debug
yes ${off})}" )
fi
# Branding
tc_version_is_at_least 4.3 && confgcc+=(
--with-bugurl=https://bugs.gentoo.org/
--with-pkgversion="${BRANDING_GCC_PKGVERSION}"
)
# If we want hardened support with the newer piepatchset for >=gcc 4.4
if tc_version_is_at_least 4.4 && want_minispecs ; then
confgcc+=( $(use_enable hardened esp) )
fi
# allow gcc to search for clock funcs in the main C lib.
# if it can't find them, then tough cookies -- we aren't
# going to link in -lrt to all C++ apps. #411681
if tc_version_is_at_least 4.4 && is_cxx ; then
confgcc+=( --enable-libstdcxx-time )
fi
# # Turn on the -Wl,--build-id flag by default for ELF targets. #525942
# # This helps with locating debug files.
# case ${CTARGET} in
# *-linux-*|*-elf|*-eabi)
# tc_version_is_at_least 4.5 && confgcc+=(
# --e
