Re: Shared Libraries : library paths ??

From: Lawrence D¹Oliveiro (ldo_at_geek-central.gen.new_zealand)
Date: 06/09/05


Date: Thu, 09 Jun 2005 20:20:44 +1200

In article <42a702f3_1@x-privat.org>, Julián Albo <JULIANALBO@terra.es>
wrote:

>Lawrence D1Oliveiro wrote:
>
>> Except with systems running non-ANSI C compilers that won't accept
>> function prototypes, for example.
>
>I've readed in the documentation of automake and autoconf something about a
>de-ansification feature that can be used in that cases.

That's an example of the kind of feature that shouldn't be necessary in
this day and age. Any compiler that requires it should be quickly and
quietly put out of its misery.



Relevant Pages

  • Re: Shared Libraries : library paths ??
    ... I've readed in the documentation of automake and autoconf something about a ... de-ansification feature that can be used in that cases. ...
    (comp.os.linux.development.apps)
  • Re: Shared Libraries : library paths ??
    ... I've readed in the documentation of automake and autoconf something about a ... de-ansification feature that can be used in that cases. ...
    (comp.os.linux.development.system)
  • Re: Shared Libraries : library paths ??
    ... I've readed in the documentation of automake and autoconf something about a ... de-ansification feature that can be used in that cases. ...
    (comp.unix.programmer)
  • Re: Shared Libraries : library paths ??
    ... >I've readed in the documentation of automake and autoconf something about a ... >de-ansification feature that can be used in that cases. ...
    (comp.unix.programmer)
  • Re: Shared Libraries : library paths ??
    ... >I've readed in the documentation of automake and autoconf something about a ... >de-ansification feature that can be used in that cases. ...
    (comp.os.linux.development.system)