This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: flag day for Solaris portions of config.{guess,sub}


    >The point is that most programs nowadays use Autoconf, so other uses are
    >few.
    >  
    >
    Sorry to barge in again, but config.guess is used by lots of things
    besides programs that use Autoconf; e.g., various sysadmin scripts,
    testing and compilation frameworks, etc. etc., where Autoconf is
    inappropriate but config.guess is immensely useful.

Are you talking about configure scripts that don't use Autoconf?
Or something else entirely?

    Config.guess is not just a utility for Autoconf;

We are miscommunicating; you're arguing against something that is not what
I said.  config.guess is not "a utility for Autoconf".  It's a utility for
configure scripts.  When we developed the configure spec, there was no
such thing as Autoconf.

When Autoconf was developed, it made it possible to write configure scripts
so that they don't need to care about the name of the system.  So
config.guess, and configuration names, are less important than they were in
the past.  Some programs such as GDB still need to check them, but most new
programs rely on Autoconf for the whole job.  At least I think that's the
case for configure scripts.

Are you saying that config.guess is widely used outside of configure
scripts?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]