what happened to stdarg.h or varargs.h

[Kevin O'Gorman]

On Sat, Aug 3, 2013 at 12:36 PM, Colin Law <clanlaw at googlemail.com> wrote:
> On 3 August 2013 19:34, Kevin O'Gorman <kogorman at gmail.com> wrote:
>> I just tried to build a package from source, and it died looking for
>> one of these headers and not finding either one.
>>
>> It's been a long time since I wrote code to use these myself, but I
>> cannot believe they just disappeared.  However, I cannot find them on
>> my system.  I have the usual dev tools, or thought
>> I did.  What am I missing?
>
> On 13.04 I have
> /usr/lib/gcc/i686-linux-gnu/4.7/include/stdarg.h
> supplied by
> libgcc-4.7-dev
>
> If you run
> apt-file search stdarg.h
> you will see which packages may provide it.  If you have not installed
> apt-file then you need to install it and run
> apt-file update
> first.
>
> Colin

Okay, I tried apt-file, and got a confusion of things.  Since my
default compiler is gcc-4.6.3, probably the most relevant are
gcc-4.6: /usr/lib/gcc/i686-linux-gnu/4.6/include/cross-stdarg.h
gcc-4.6: /usr/lib/gcc/i686-linux-gnu/4.6/include/stdarg.h
<<-- I'd guess this is the one
gcc-4.6-arm-linux-gnueabi: /usr/lib/gcc/arm-linux-gnueabi/4.6/include/stdarg.h
gcc-4.6-arm-linux-gnueabihf:
/usr/lib/gcc/arm-linux-gnueabihf/4.6/include/stdarg.h

But this leaves a secondary question: why didn't autotools find it?
You can duplicate my problem (or not) very quickly by downloading
   http://www.sourceware.org/autobook/complex-1.0.tar.gz
which is from the web page for the book on autotools

Unpack it, cd to the directory and
  ./bootstrap </dev/null
  ./configure </dev/null

and see if configure dies or finishes.  Why I need the </dev/null is
another mystery, but without them the process hangs forever.

-- 
Kevin O'Gorman

programmer, n. an organism that transmutes caffeine into software.
Please consider the environment before printing this email.