Quantcast

Linux build (-DVGO_linux=1)

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Linux build (-DVGO_linux=1)

Felipe Pena
Hello,
I was just trying to build Valgrind using ./configure without options,
and got an error, see below:

m_debuginfo/readstabs.c:57:39: fatal error: a.out.h: No such file or directory
compilation terminated.

Changing the related code as follow below fixes it.

Index: coregrind/m_debuginfo/readstabs.c
===================================================================
--- coregrind/m_debuginfo/readstabs.c (revision 13710)
+++ coregrind/m_debuginfo/readstabs.c (working copy)
@@ -54,7 +54,7 @@

/* --- !!! --- EXTERNAL HEADERS start --- !!! --- */
#if defined(VGO_linux)
-# include <a.out.h> /* stabs defns */
+# include <linux/a.out.h> /* stabs defns */
#elif defined(VGO_darwin)
# include <mach-o/nlist.h>
# define n_other n_sect

--
Regards,
Felipe Pena

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Valgrind-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Linux build (-DVGO_linux=1)

Rich Coe
What os distribution and version were you compiling on ?
What version of linux is this?

Rich

On Thu, 7 Nov 2013 19:26:10 -0200
Felipe Pena <[hidden email]> wrote:

> Hello,
> I was just trying to build Valgrind using ./configure without options,
> and got an error, see below:
>
> m_debuginfo/readstabs.c:57:39: fatal error: a.out.h: No such file or directory
> compilation terminated.
>
> Changing the related code as follow below fixes it.
>
> Index: coregrind/m_debuginfo/readstabs.c
> ===================================================================
> --- coregrind/m_debuginfo/readstabs.c (revision 13710)
> +++ coregrind/m_debuginfo/readstabs.c (working copy)
> @@ -54,7 +54,7 @@
>
> /* --- !!! --- EXTERNAL HEADERS start --- !!! --- */
> #if defined(VGO_linux)
> -# include <a.out.h> /* stabs defns */
> +# include <linux/a.out.h> /* stabs defns */
> #elif defined(VGO_darwin)
> # include <mach-o/nlist.h>
> # define n_other n_sect
>
> --
> Regards,
> Felipe Pena
>
> ------------------------------------------------------------------------------
> November Webinars for C, C++, Fortran Developers
> Accelerate application performance with scalable programming models. Explore
> techniques for threading, error checking, porting, and tuning. Get the most
> from the latest Intel processors and coprocessors. See abstracts and register
> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
> _______________________________________________
> Valgrind-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/valgrind-developers


--
Rich Coe     [hidden email]

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Valgrind-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Linux build (-DVGO_linux=1)

Tom Hughes-2
On 08/11/13 15:41, Rich Coe wrote:
> What os distribution and version were you compiling on ?
> What version of linux is this?

My guess is a recent Ubuntu and he hasn't got all the C library
development headers (both 32 and 64 bit) installed.

Tom

> Rich
>
> On Thu, 7 Nov 2013 19:26:10 -0200
> Felipe Pena <[hidden email]> wrote:
>> Hello,
>> I was just trying to build Valgrind using ./configure without options,
>> and got an error, see below:
>>
>> m_debuginfo/readstabs.c:57:39: fatal error: a.out.h: No such file or directory
>> compilation terminated.
>>
>> Changing the related code as follow below fixes it.
>>
>> Index: coregrind/m_debuginfo/readstabs.c
>> ===================================================================
>> --- coregrind/m_debuginfo/readstabs.c (revision 13710)
>> +++ coregrind/m_debuginfo/readstabs.c (working copy)
>> @@ -54,7 +54,7 @@
>>
>> /* --- !!! --- EXTERNAL HEADERS start --- !!! --- */
>> #if defined(VGO_linux)
>> -# include <a.out.h> /* stabs defns */
>> +# include <linux/a.out.h> /* stabs defns */
>> #elif defined(VGO_darwin)
>> # include <mach-o/nlist.h>
>> # define n_other n_sect
>>
>> --
>> Regards,
>> Felipe Pena
>>
>> ------------------------------------------------------------------------------
>> November Webinars for C, C++, Fortran Developers
>> Accelerate application performance with scalable programming models. Explore
>> techniques for threading, error checking, porting, and tuning. Get the most
>> from the latest Intel processors and coprocessors. See abstracts and register
>> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Valgrind-developers mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/valgrind-developers
>
>


--
Tom Hughes ([hidden email])
http://compton.nu/

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Valgrind-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Linux build (-DVGO_linux=1)

Felipe Pena
On Fri, Nov 8, 2013 at 1:57 PM, Tom Hughes <[hidden email]> wrote:
> On 08/11/13 15:41, Rich Coe wrote:
>>
>> What os distribution and version were you compiling on ?
>> What version of linux is this?
>
>
> My guess is a recent Ubuntu and he hasn't got all the C library development
> headers (both 32 and 64 bit) installed.
>

Actually it's a Debian 7 running Linux 3.2.0-4-amd64.

> Tom
>
>
>> Rich
>>
>> On Thu, 7 Nov 2013 19:26:10 -0200
>> Felipe Pena <[hidden email]> wrote:
>>>
>>> Hello,
>>> I was just trying to build Valgrind using ./configure without options,
>>> and got an error, see below:
>>>
>>> m_debuginfo/readstabs.c:57:39: fatal error: a.out.h: No such file or
>>> directory
>>> compilation terminated.
>>>
>>> Changing the related code as follow below fixes it.
>>>
>>> Index: coregrind/m_debuginfo/readstabs.c
>>> ===================================================================
>>> --- coregrind/m_debuginfo/readstabs.c (revision 13710)
>>> +++ coregrind/m_debuginfo/readstabs.c (working copy)
>>> @@ -54,7 +54,7 @@
>>>
>>> /* --- !!! --- EXTERNAL HEADERS start --- !!! --- */
>>> #if defined(VGO_linux)
>>> -# include <a.out.h> /* stabs defns */
>>> +# include <linux/a.out.h> /* stabs defns */
>>> #elif defined(VGO_darwin)
>>> # include <mach-o/nlist.h>
>>> # define n_other n_sect
>>>
>>> --
>>> Regards,
>>> Felipe Pena
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> November Webinars for C, C++, Fortran Developers
>>> Accelerate application performance with scalable programming models.
>>> Explore
>>> techniques for threading, error checking, porting, and tuning. Get the
>>> most
>>> from the latest Intel processors and coprocessors. See abstracts and
>>> register
>>>
>>> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Valgrind-developers mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/valgrind-developers
>>
>>
>>
>
>
> --
> Tom Hughes ([hidden email])
> http://compton.nu/



--
Regards,
Felipe Pena

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Valgrind-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Linux build (-DVGO_linux=1)

Philippe Waroquiers
On Fri, 2013-11-08 at 19:01 -0200, Felipe Pena wrote:

> On Fri, Nov 8, 2013 at 1:57 PM, Tom Hughes <[hidden email]> wrote:
> > On 08/11/13 15:41, Rich Coe wrote:
> >>
> >> What os distribution and version were you compiling on ?
> >> What version of linux is this?
> >
> >
> > My guess is a recent Ubuntu and he hasn't got all the C library development
> > headers (both 32 and 64 bit) installed.
> >
>
> Actually it's a Debian 7 running Linux 3.2.0-4-amd64.
And have you all the C library development headers (both 32 and 64 bit)
installed ?

Does installing them fix the problem ?

Is valgrind configure doing a bi-arch build ?
Or only a 64 bits build ?

Philippe


------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Valgrind-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Linux build (-DVGO_linux=1)

Felipe Pena
On Fri, Nov 8, 2013 at 7:44 PM, Philippe Waroquiers
<[hidden email]> wrote:

> On Fri, 2013-11-08 at 19:01 -0200, Felipe Pena wrote:
>> On Fri, Nov 8, 2013 at 1:57 PM, Tom Hughes <[hidden email]> wrote:
>> > On 08/11/13 15:41, Rich Coe wrote:
>> >>
>> >> What os distribution and version were you compiling on ?
>> >> What version of linux is this?
>> >
>> >
>> > My guess is a recent Ubuntu and he hasn't got all the C library development
>> > headers (both 32 and 64 bit) installed.
>> >
>>
>> Actually it's a Debian 7 running Linux 3.2.0-4-amd64.
> And have you all the C library development headers (both 32 and 64 bit)
> installed ?
>

Yes. (I have built a lot of project without problem)

ii libc6-dev:amd64 2.13-38 amd64 Embedded GNU C Library: Development
Libraries and Header Files
ii libc6-dev-i386 2.13-38 amd64 Embedded GNU C Library: 32-bit
development libraries for AMD64
ii linux-headers-3.2.0-4-amd64 3.2.51-1 amd64 Header files for Linux
3.2.0-4-amd64
ii linux-headers-3.2.0-4-common 3.2.51-1 amd64 Common header files for
Linux 3.2.0-4

> Does installing them fix the problem ?
>
> Is valgrind configure doing a bi-arch build ?
> Or only a 64 bits build ?
>

Yes, It's doing a bi-arch build.

--
Regards,
Felipe Pena

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Valgrind-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Linux build (-DVGO_linux=1)

Philippe Waroquiers
On Fri, 2013-11-08 at 19:56 -0200, Felipe Pena wrote:

> >> Actually it's a Debian 7 running Linux 3.2.0-4-amd64.
> > And have you all the C library development headers (both 32 and 64 bit)
> > installed ?
> >
>
> Yes. (I have built a lot of project without problem)
>
> ii libc6-dev:amd64 2.13-38 amd64 Embedded GNU C Library: Development
> Libraries and Header Files
> ii libc6-dev-i386 2.13-38 amd64 Embedded GNU C Library: 32-bit
> development libraries for AMD64
> ii linux-headers-3.2.0-4-amd64 3.2.51-1 amd64 Header files for Linux
> 3.2.0-4-amd64
> ii linux-headers-3.2.0-4-common 3.2.51-1 amd64 Common header files for
> Linux 3.2.0-4
>
> > Does installing them fix the problem ?
> >
> > Is valgrind configure doing a bi-arch build ?
> > Or only a 64 bits build ?
> >
>
> Yes, It's doing a bi-arch build.
>
Thanks for the info.
>From some web search, it seems that recent Debians (and Ubuntu) have
moved a.out.h from /usr/include to /usr/include/linux/a.out.h

So, it looks like some configure machinery will be needed to detect
if /usr/include/a.out.h is there or if /usr/include/linux/a.out.h is
there (or else disable the stabs format reading).

Philippe




------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Valgrind-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Linux build (-DVGO_linux=1)

Tom Hughes-2
On 08/11/13 22:43, Philippe Waroquiers wrote:

> From some web search, it seems that recent Debians (and Ubuntu) have
> moved a.out.h from /usr/include to /usr/include/linux/a.out.h

I don't think so. I went through this with somebody on IRC and I'm sure
it was just a question of getting the right packages instlled.

> So, it looks like some configure machinery will be needed to detect
> if /usr/include/a.out.h is there or if /usr/include/linux/a.out.h is
> there (or else disable the stabs format reading).

The two are different things I think - linux/a.out.h is a kernel header
while a.out.h is a libc header that wraps it.

Tom

--
Tom Hughes ([hidden email])
http://compton.nu/

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Valgrind-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Linux build (-DVGO_linux=1)

Tom Hughes-2
On 08/11/13 22:49, Tom Hughes wrote:
> On 08/11/13 22:43, Philippe Waroquiers wrote:
>
>> From some web search, it seems that recent Debians (and Ubuntu) have
>> moved a.out.h from /usr/include to /usr/include/linux/a.out.h
>
> I don't think so. I went through this with somebody on IRC and I'm sure
> it was just a question of getting the right packages instlled.

Actually it was Julian that ran into this and we didn't work out exactly
what fixed it because he installed a bunch more stuff and it went away.

>> So, it looks like some configure machinery will be needed to detect
>> if /usr/include/a.out.h is there or if /usr/include/linux/a.out.h is
>> there (or else disable the stabs format reading).
>
> The two are different things I think - linux/a.out.h is a kernel header
> while a.out.h is a libc header that wraps it.

So I beliveve the replacement for /usr/include/a.out.h is:

/usr/include/i386-linux-gnu/a.out.h
/usr/include/x86_64-linux-gnu/a.out.h

and you will need both of those. If one is missing then find out what
package is providing the other one and install it's counterpart from the
other architecture.

Tom

--
Tom Hughes ([hidden email])
http://compton.nu/

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Valgrind-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Linux build (-DVGO_linux=1)

Felipe Pena
On Fri, Nov 8, 2013 at 9:00 PM, Tom Hughes <[hidden email]> wrote:

> On 08/11/13 22:49, Tom Hughes wrote:
>>
>> On 08/11/13 22:43, Philippe Waroquiers wrote:
>>
>>> From some web search, it seems that recent Debians (and Ubuntu) have
>>> moved a.out.h from /usr/include to /usr/include/linux/a.out.h
>>
>>
>> I don't think so. I went through this with somebody on IRC and I'm sure
>> it was just a question of getting the right packages instlled.
>
>
> Actually it was Julian that ran into this and we didn't work out exactly
> what fixed it because he installed a bunch more stuff and it went away.
>
>
>>> So, it looks like some configure machinery will be needed to detect
>>> if /usr/include/a.out.h is there or if /usr/include/linux/a.out.h is
>>> there (or else disable the stabs format reading).
>>
>>
>> The two are different things I think - linux/a.out.h is a kernel header
>> while a.out.h is a libc header that wraps it.
>
>
> So I beliveve the replacement for /usr/include/a.out.h is:
>
> /usr/include/i386-linux-gnu/a.out.h
> /usr/include/x86_64-linux-gnu/a.out.h
>
> and you will need both of those. If one is missing then find out what
> package is providing the other one and install it's counterpart from the
> other architecture.
>

Got it. You're right. It was just missing libc6-dev:i386... sorry for the noisy.

Thanks guys for the help, and for this nice project.

--
Regards,
Felipe Pena

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Valgrind-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
Loading...