[Buildroot] [Re: Valgrind compilation, with patch 3.5.0, need help]

[Buildroot] [Re: Valgrind compilation, with patch 3.5.0, need help]

[Damien Borie]

My architecture is x86.

It's not me that say that Valgrind depends on glibc version, it's the
log...I have only added valgrind in my configuration and launch 'make
source' and 'make'. The package is downloaded without problem but during
compilation, there is a test on glibc version number. I can see it in
'configure.in' file. And it say me that Valgrind need glibc version 2.2
to 2.5. I use 2.9.

So, I tried to compile Valgrind version 3.5.0. I only change the version
number in Config.in file (in package/valgrind/). 'make source' cause the
package download without problems. Then 'make' doesn't cause error but
it try to apply a patch ('valgrind-largefile patch'). This patch modify
a file 'coregrind/m_ume.c' and ask me to type a path to a file to patch,
with no others precisions.
So I don't know how to type here. And if I ignore, the compilation end
with an error (saying that I must apply the patch).

Any idea?

Damien Borie

TERAWATT / AENERGIA S.A.S.
ZA DUBOSCOA
64990 Villefranque
FRANCE

tel : +33 (0)5 59 44 26 08
fax : +33 (0)5 59 31 15 11



Thomas Petazzoni a ?crit :
 > On Mon, 14 Jun 2010 17:10:41 +0200
 > Damien Borie <dbe@terawatt.fr> wrote:
 >
 >
 >> I Have to add Valgrind to my distribution to debug my programs. The
 >> version in buildroot doesn't compile because it needs glibc 2.2 -2.5,
 >> and I have 2.9. So I tried with the patch to bump to Valgrind 3.5.0.
 >> But it ask me fro a file to patch, and I don't understand what I must
 >> type to apply correctly the patch and compile Valgrind. In the match
 >> itself, I cannot see indications about this file to choose.
 >>
 >
 > What is your target architecture ? Remember that Valgrind only works on
 > x86, x86_64 and PowerPC 32/64.
 >
 > Moreover, I don't really see how Valgrind in Buildroot would depend on
 > a particular version of glibc. Can you be more specific about what
 > you're doing and the exact result of the commands you're using ?
 >
 > Thomas
 >


-- 
Damien Borie

TERAWATT / AENERGIA S.A.S.
ZA DUBOSCOA
64990 Villefranque
FRANCE 

tel : +33 (0)5 59 44 26 08
fax : +33 (0)5 59 31 15 11 

[Buildroot] [Re: Valgrind compilation, with patch 3.5.0, need help]

[Thomas Petazzoni]

Hello Damien,

On Tue, 15 Jun 2010 09:07:58 +0200
Damien Borie <dbe@terawatt.fr> wrote:

> So, I tried to compile Valgrind version 3.5.0. I only change the version
> number in Config.in file (in package/valgrind/). 'make source' cause the
> package download without problems. Then 'make' doesn't cause error but
> it try to apply a patch ('valgrind-largefile patch'). This patch modify
> a file 'coregrind/m_ume.c' and ask me to type a path to a file to patch,
> with no others precisions.

It means that the file the patch is modifying doesn't exist anymore in
newer versions of Valgrind. So you need to see whether the patch is
still needed or not. From a quick look, it looks like it does.

Attached is a updated version of the patch for Valgrind 3.5.0. I haven't
tested it *at all*, I haven't even built Valgrind with this patch. But
at least, it applies on Valgrind 3.5.0.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: valgrind-3.5.0-largefile.patch
Type: text/x-patch
Size: 2435 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100615/aa15e560/attachment.bin>

[Buildroot] [Re: Valgrind compilation, with patch 3.5.0, need help]

[Damien Borie]

Thanks!

Well, this patch seems to work. But then, the compilation doesn't works. 
It returns with this error :
'checking for /proc/self/fd... configure: error: cannot check for file 
existence when cross compiling'
I know I had this error in the past on other packages, but I don't 
remember how to fix it.
Note that I don't apply the patch 'valgrind.patch' because it cause 
errors. The only patch applied is 'valgrind-3.5.0-largefile.patch'.
Yesterday, I found a patch in the mailing list named 'valgrind bump to 
3.5.0' (link : 
http://lists.busybox.net/pipermail/buildroot/2010-April/033673.html) but 
I didn't succeed in applying it. I'm not sure but I think it will patch 
vargrind.patch and vargrind.mk to work with 3.5.0 version.
But how to apply it?

Damien Borie

TERAWATT / AENERGIA S.A.S.
ZA DUBOSCOA
64990 Villefranque
FRANCE 

tel : +33 (0)5 59 44 26 08
fax : +33 (0)5 59 31 15 11 



Thomas Petazzoni a ?crit :
> Hello Damien,
>
> On Tue, 15 Jun 2010 09:07:58 +0200
> Damien Borie <dbe@terawatt.fr> wrote:
>
>   
>> So, I tried to compile Valgrind version 3.5.0. I only change the version
>> number in Config.in file (in package/valgrind/). 'make source' cause the
>> package download without problems. Then 'make' doesn't cause error but
>> it try to apply a patch ('valgrind-largefile patch'). This patch modify
>> a file 'coregrind/m_ume.c' and ask me to type a path to a file to patch,
>> with no others precisions.
>>     
>
> It means that the file the patch is modifying doesn't exist anymore in
> newer versions of Valgrind. So you need to see whether the patch is
> still needed or not. From a quick look, it looks like it does.
>
> Attached is a updated version of the patch for Valgrind 3.5.0. I haven't
> tested it *at all*, I haven't even built Valgrind with this patch. But
> at least, it applies on Valgrind 3.5.0.
>
> Regards,
>
> Thomas
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

[Buildroot] [Re: Valgrind compilation, with patch 3.5.0, need help]

[Damien Borie]

Ok I've applied successfully the patch 'bump to 3.5.0' and the large 
file patch. But I still have the same error
'checking for /proc/self/fd... configure: error: cannot check for file 
existence when cross compiling'
In 'configure' file, I can see that it result of a test of variable 
'cross-compiling'. If true, this error appears. I wonder if i can 
comment this and ignore this test...

Damien Borie

TERAWATT / AENERGIA S.A.S.
ZA DUBOSCOA
64990 Villefranque
FRANCE 

tel : +33 (0)5 59 44 26 08
fax : +33 (0)5 59 31 15 11 



Damien Borie a ?crit :
> Thanks!
>
> Well, this patch seems to work. But then, the compilation doesn't 
> works. It returns with this error :
> 'checking for /proc/self/fd... configure: error: cannot check for file 
> existence when cross compiling'
> I know I had this error in the past on other packages, but I don't 
> remember how to fix it.
> Note that I don't apply the patch 'valgrind.patch' because it cause 
> errors. The only patch applied is 'valgrind-3.5.0-largefile.patch'.
> Yesterday, I found a patch in the mailing list named 'valgrind bump to 
> 3.5.0' (link : 
> http://lists.busybox.net/pipermail/buildroot/2010-April/033673.html) 
> but I didn't succeed in applying it. I'm not sure but I think it will 
> patch vargrind.patch and vargrind.mk to work with 3.5.0 version.
> But how to apply it?
>
> Damien Borie
>
> TERAWATT / AENERGIA S.A.S.
> ZA DUBOSCOA
> 64990 Villefranque
> FRANCE
> tel : +33 (0)5 59 44 26 08
> fax : +33 (0)5 59 31 15 11
>
>
> Thomas Petazzoni a ?crit :
>> Hello Damien,
>>
>> On Tue, 15 Jun 2010 09:07:58 +0200
>> Damien Borie <dbe@terawatt.fr> wrote:
>>
>>  
>>> So, I tried to compile Valgrind version 3.5.0. I only change the 
>>> version
>>> number in Config.in file (in package/valgrind/). 'make source' cause 
>>> the
>>> package download without problems. Then 'make' doesn't cause error but
>>> it try to apply a patch ('valgrind-largefile patch'). This patch modify
>>> a file 'coregrind/m_ume.c' and ask me to type a path to a file to 
>>> patch,
>>> with no others precisions.
>>>     
>>
>> It means that the file the patch is modifying doesn't exist anymore in
>> newer versions of Valgrind. So you need to see whether the patch is
>> still needed or not. From a quick look, it looks like it does.
>>
>> Attached is a updated version of the patch for Valgrind 3.5.0. I haven't
>> tested it *at all*, I haven't even built Valgrind with this patch. But
>> at least, it applies on Valgrind 3.5.0.
>>
>> Regards,
>>
>> Thomas
>>   
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
>

[Buildroot] [Re: Valgrind compilation, with patch 3.5.0, need help]

[Damien Borie]

It's ok. Valgrind is compiled and works OK. Finally I've commented all 
test on /proc/self/* files in 'configure' file, else it says that it 
cannot test in cross compiling and exit. And it's work.

Thanks!

Damien Borie

TERAWATT / AENERGIA S.A.S.
ZA DUBOSCOA
64990 Villefranque
FRANCE 

tel : +33 (0)5 59 44 26 08
fax : +33 (0)5 59 31 15 11 



Damien Borie a ?crit :
> Ok I've applied successfully the patch 'bump to 3.5.0' and the large 
> file patch. But I still have the same error
> 'checking for /proc/self/fd... configure: error: cannot check for file 
> existence when cross compiling'
> In 'configure' file, I can see that it result of a test of variable 
> 'cross-compiling'. If true, this error appears. I wonder if i can 
> comment this and ignore this test...
>
> Damien Borie
>
> TERAWATT / AENERGIA S.A.S.
> ZA DUBOSCOA
> 64990 Villefranque
> FRANCE
> tel : +33 (0)5 59 44 26 08
> fax : +33 (0)5 59 31 15 11
>
>
> Damien Borie a ?crit :
>> Thanks!
>>
>> Well, this patch seems to work. But then, the compilation doesn't 
>> works. It returns with this error :
>> 'checking for /proc/self/fd... configure: error: cannot check for 
>> file existence when cross compiling'
>> I know I had this error in the past on other packages, but I don't 
>> remember how to fix it.
>> Note that I don't apply the patch 'valgrind.patch' because it cause 
>> errors. The only patch applied is 'valgrind-3.5.0-largefile.patch'.
>> Yesterday, I found a patch in the mailing list named 'valgrind bump 
>> to 3.5.0' (link : 
>> http://lists.busybox.net/pipermail/buildroot/2010-April/033673.html) 
>> but I didn't succeed in applying it. I'm not sure but I think it will 
>> patch vargrind.patch and vargrind.mk to work with 3.5.0 version.
>> But how to apply it?
>>
>> Damien Borie
>>
>> TERAWATT / AENERGIA S.A.S.
>> ZA DUBOSCOA
>> 64990 Villefranque
>> FRANCE
>> tel : +33 (0)5 59 44 26 08
>> fax : +33 (0)5 59 31 15 11
>>
>>
>> Thomas Petazzoni a ?crit :
>>> Hello Damien,
>>>
>>> On Tue, 15 Jun 2010 09:07:58 +0200
>>> Damien Borie <dbe@terawatt.fr> wrote:
>>>
>>>  
>>>> So, I tried to compile Valgrind version 3.5.0. I only change the 
>>>> version
>>>> number in Config.in file (in package/valgrind/). 'make source' 
>>>> cause the
>>>> package download without problems. Then 'make' doesn't cause error but
>>>> it try to apply a patch ('valgrind-largefile patch'). This patch 
>>>> modify
>>>> a file 'coregrind/m_ume.c' and ask me to type a path to a file to 
>>>> patch,
>>>> with no others precisions.
>>>>     
>>>
>>> It means that the file the patch is modifying doesn't exist anymore in
>>> newer versions of Valgrind. So you need to see whether the patch is
>>> still needed or not. From a quick look, it looks like it does.
>>>
>>> Attached is a updated version of the patch for Valgrind 3.5.0. I 
>>> haven't
>>> tested it *at all*, I haven't even built Valgrind with this patch. But
>>> at least, it applies on Valgrind 3.5.0.
>>>
>>> Regards,
>>>
>>> Thomas
>>>   
>>> ------------------------------------------------------------------------ 
>>>
>>>
>>> _______________________________________________
>>> buildroot mailing list
>>> buildroot at busybox.net
>>> http://lists.busybox.net/mailman/listinfo/buildroot
>>
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>>
>>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
>