|
From: Zvi V. <ver...@gm...> - 2012-07-07 00:19:18
|
Hello, Using crosstool-ng I created a gcc for Pentium-M running vanlilla 2.6.27.35 I used this compiler to build the kernel, busy box and a device driver I wrote. Now I want to use this toolchain to compile valgrind 3.7.0 (last release). So I ran "export CC=/home/zvivered/gnu/toolchain/release/bin/i686-nptl-linux-gnu-gcc" before running ./configure I got the following output: .... checking dependency style of /home/zvivered/gnu/toolchain/release/bin/i686-nptl-linux-gnu-gcc... gcc3 checking for diff -u... yes checking for a supported version of gcc... no (686) configure: error: please use gcc >= 3.0 or clang >= 2.9 If I run gcc --version (on my gcc) I get: .i686-nptl-linux-gnu-gcc (crosstool-NG-1.5.2) 4.3.2 Copyright (C) 2008 Free Software Foundation, Inc. If I run gcc --version on the default gcc installed on my Centos 5.3 I get: gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-52) Copyright (C) 2006 Free Software Foundation, Inc. With the default gcc, valgrind is built OK. I found a similar question in google but the fix in ./configure did not help. Can you help ? Thanks, Zvika. |
|
From: Philippe W. <phi...@sk...> - 2012-07-07 00:32:24
|
On Sat, 2012-07-07 at 03:19 +0300, Zvi Vered wrote:
> If I run gcc --version (on my gcc) I get:
> .i686-nptl-linux-gnu-gcc (crosstool-NG-1.5.2) 4.3.2
> Copyright (C) 2008 Free Software Foundation, Inc.
>
> If I run gcc --version on the default gcc installed on my Centos 5.3 I get:
> gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-52)
> Copyright (C) 2006 Free Software Foundation, Inc.
>
> With the default gcc, valgrind is built OK.
>
> I found a similar question in google but the fix in ./configure did not help.
>
> Can you help ?
modify configure.in around line 130 :
case "${is_clang}-${gcc_version}" in
to add a pattern matching what your gcc does.
(or, somewhat more kludgy, edit configure, and replace an existing
pattern by a *).
Tested none of the above suggestions ...
Philippe
|
|
From: John R. <jr...@bi...> - 2012-07-07 00:40:45
|
> Now I want to use this toolchain to compile valgrind 3.7.0 (last release).
> So I ran "export
> CC=/home/zvivered/gnu/toolchain/release/bin/i686-nptl-linux-gnu-gcc"
> before running ./configure
> configure: error: please use gcc >= 3.0 or clang >= 2.9
>
> If I run gcc --version (on my gcc) I get:
> .i686-nptl-linux-gnu-gcc (crosstool-NG-1.5.2) 4.3.2
Look in ./configure where the compiler version is obtained:
-----
# Obtain the compiler version.
#
# A few examples of how the ${CC} --version output looks like:
[[snip]]
gcc_version=`${CC} -dumpversion 2>/dev/null`
if test "x$gcc_version" = x; then
gcc_version=`${CC} --version \
| $SED -n -e 's/[^ ]*gcc[^ ]* ([^)]*) \([0-9.]*\).*$/\1/p' \
-e 's/[^ ]*clang version \([0-9.]*\).*$/\1/p'`
fi
-----
Change that so that gcc_version becomes "4.3.2". You can try to be clever
by enhancing the editing parameters that are specified to $SED,
or you can just add a statement
gcc_version=4.3.2
after the existing statement "gcc_version=`$(CC) --version ..." and before the "fi".
--
|
|
From: Zvi V. <ver...@gm...> - 2012-07-07 19:39:11
|
Dear Members,
Thanks. Fixing "configure" helped.
Best regards,
Zvika.
On 7/7/12, John Reiser <jr...@bi...> wrote:
>> Now I want to use this toolchain to compile valgrind 3.7.0 (last
>> release).
>> So I ran "export
>> CC=/home/zvivered/gnu/toolchain/release/bin/i686-nptl-linux-gnu-gcc"
>> before running ./configure
>
>> configure: error: please use gcc >= 3.0 or clang >= 2.9
>>
>> If I run gcc --version (on my gcc) I get:
>> .i686-nptl-linux-gnu-gcc (crosstool-NG-1.5.2) 4.3.2
>
> Look in ./configure where the compiler version is obtained:
> -----
> # Obtain the compiler version.
> #
> # A few examples of how the ${CC} --version output looks like:
> [[snip]]
> gcc_version=`${CC} -dumpversion 2>/dev/null`
> if test "x$gcc_version" = x; then
> gcc_version=`${CC} --version \
> | $SED -n -e 's/[^ ]*gcc[^ ]* ([^)]*) \([0-9.]*\).*$/\1/p' \
> -e 's/[^ ]*clang version \([0-9.]*\).*$/\1/p'`
> fi
> -----
>
> Change that so that gcc_version becomes "4.3.2". You can try to be clever
> by enhancing the editing parameters that are specified to $SED,
> or you can just add a statement
> gcc_version=4.3.2
> after the existing statement "gcc_version=`$(CC) --version ..." and before
> the "fi".
>
> --
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>
|