Hi all,
I apologize for the off-topic question. I'm having a problem using the
MinGW repo for OpenSUSE [1] and I wondered if anyone here would know
what to do or where I could ask for help about it. The error I'm
getting when trying to install is this:
Problem: nothing provides libmpfr.so.4 neede
On Wed, Sep 9, 2009 at 11:44 PM, JonY <10wa...@gmail.com> wrote:
> On 9/10/2009 11:22, Matthew Talbert wrote:
>>>> /opt/w64/bin/x86_64-w64-mingw32-gcc -print-prog-name=as
>>>> as
>>
>>> According to your build script, you should have cross binuti
> Hi,
> I see the problem now. GCC-4.4.0 doesn't support a multilib setup, use
> GCC from svn trunk instead.
>
> The GCC, mingw-w64 headers and CRT have undergone huge changes since
> then, lots of bugfixes and etc, its a good advice to use svn versions
> instead of the release versions.
OK, thank
>>
>> Perhaps I should have mentioned earlier, I'm compiling from the 4.4.0
>> release, not from svn. Still, the directions are wrong, yes? (They
>> neglect the trailing "include" directory, so you would be copying the
>> contents of include to /mypath/x86_64-mingw32).
>>
>
> Hi,
> I was referring
> > /opt/w64/bin/x86_64-w64-mingw32-gcc -print-prog-name=as
> > as
> According to your build script, you should have cross binutils already
> installed, -print-prog-name=as is to make sure it is calling the correct
> cross binutils. Do post the output, thanks.
That was the command and the outpu
> Use 'svn export include /mypath/x86_64-w64-mingw32/include'. It will
> create the missing directory and copy the headers without the svn
> metadata. The metadata is in a .svn subdirectory in each directory you
> checkout via svn.
Perhaps I should have mentioned earlier, I'm compiling from the 4.
> Hi,
> it should really be svn export, you don't need the svn metadata.
Sorry, I don't follow you here.
> Maybe the wrong binutils got called, check your $PATH, make sure
> /opt/w64/bin is in it.
Yes, /opt/w64/bin is in it. I've done this manually as well and it has
the same problem.
Thanks,
> You aren't building with a separate prefix, so you are installing
> right into your root. This can cause issues if you have conflicting
> versions of things installed. You are best to install into some
> prefix outside of your main tree until you get the hang of it.
>
> I suggest building every
Hi Wolfgang,
> I'm currently building up a debianized cross-compiler toolchain for ubuntu
> hardy and jaunty. Please consider to use our PPA
>
> https://www.launchpad.net/~clazzes.org/+archive/ppa
>
> and give us feedback on the toolchain there. I'm currently relying on
> gcc-4.4.0-1 and will up
Hi all,
I'm attempting to build a cross-compile toolchain on Ubuntu-JJ. I'm
building with the following script:
#! /bin/sh
top_dir=`pwd`
cd binutils/src
mkdir build
cd build
../configure --target=x86_64-w64-mingw32 \
--enable-targets=x86_64-w64-mingw32,i686-w64-mingw32
if make ; then
e
10 matches
Mail list logo
