On Tuesday, August 04, 2015 5:16:09 PM walt wrote:
> On Tue, 04 Aug 2015 18:40:49 +0200
> Cor Legemaat <c...@cor.za.net> 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

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to