Per http://gcc.gnu.org/ml/gcc/2006-10/msg00141.html it is possible to
build GMP/MPFR in the local tree with the current Trunk. This build
method may ease issues with building gcc. Would it be possible to
document this for 4.3?
Thanks,
Matt
> I would say that gets is much more dangerous than %n in printf, but
> presumably Microsoft does not disable gets
Actually, for gets, and essentially the entire stdio.h, Visual Studio 2005
generates:
warning C4996: 'gets': This function or variable may be unsafe. Consider
using gets_s
>From: Ben Elliston <[EMAIL PROTECTED]>
>> gcc --coverage appears to be broken on x86_64 in gcc 4.1.1 on FC6
>> (works fine with Trunk). I'm almost certain that this is a known
>> issue, but cannot find a reference in Bugzilla.
>
>I implemented that option, so can probably help you. Contact me in
Having searched in bugzilla and asked on gcc-help to no avail ...
gcc --coverage appears to be broken on x86_64 in gcc 4.1.1 on FC6 (works fine
with Trunk). I'm almost certain that this is a known issue, but cannot find a
reference in Bugzilla.
Could someone please give me a pointer to the bug?
>From: drizzle drizzle <[EMAIL PROTECTED]>
>
>svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk gcc_3_4_6_release
This is checking out the latest trunk, not version 3.4. The last argument only
changes the name of the directory name on your local machine. The 'svn://' is
what specifies the tag (in
>From: drizzle drizzle <[EMAIL PROTECTED]>
>Still no luck so far .. I got the gcc3.4 from the gcc archive. Any way
>I can make gcc 3.4 not use these libraries ?
What is the exact file name and URL? I will download the same tarball and try
to build it on my fc6 box.
- M
> drizzle drizzle wrote:
>And as matt suggested if mpfr is not needed by 3.4, how can I
>configure it that way. --disable -mpfr did not help.
MPFR should not have _anything_ to do with any gcc prior to 4.x. Where did you
get gcc 3.4? A tarball from a gnu mirror or somewhere else? I think either t
You do mean gcc 4.3 right (either a snapshot, or from svn)?
Since you're running on x86_64, do you know that the libraries are
the correct bitness (running 'file' on the mpfr and gmp libraries
will tell). By default gcc on x86_64 will build 64-bit, but
libraries in /usr/local/lib should on
>> ../../../trunk/libgfortran/mk-kinds-h.sh: Unknown type
>> grep '^#' < kinds.h > kinds.inc
>> /bin/sh: kinds.h: No such file or directory
>> make[2]: *** [kinds.inc] Error 1
>> make[2]: Leaving directory
>> `/home/daney/gccsvn/native-trunk/x86_64-unknown-linux-gnu/libgfortran'
>> make[1]: *** [
>From: "Kaveh R. GHAZI" <[EMAIL PROTECTED]>
>> Matt Fago wrote:
>> One issue here is that '--with-mpfr=path' assumes that 'libmpfr.a' is
>> in 'path/lib' (not true for how I installed it), while '--with-mpfr-
>> dir=path
I have been struggling with this issue, and now that I have
successfully built GCC I thought I would share my results. Hopefully
it can help someone better versed in autotools to improve the build
of GCC with GMP/MPFR.
For reference, a few older threads I've found:
http://gcc.gnu.org/ml/gc
11 matches
Mail list logo
