something about aclocal.m4 is outdated

This is a discussion on something about aclocal.m4 is outdated within the Linux Programming forums, part of the Platform Specific Boards category; I'm using KDevelop under gnome, and i'll start a new console c++ project. But when I go to compile it, ...

  1. #1
    Advanced Novice linucksrox's Avatar
    Join Date
    Apr 2004
    Location
    Michigan
    Posts
    198

    something about aclocal.m4 is outdated

    I'm using KDevelop under gnome, and i'll start a new console c++ project. But when I go to compile it, it gives me a message about having to remake aclocal.m4 and I'm not sure how to go about doing that.
    I did go to terminal though and compile the same file using
    g++ filename.cpp -o filename.o
    and then i could run it fine by doing
    ./filename.o

    any thoughts? maybe i should just use the terminal for now while I'm still learning c++
    "What are all you parallelograms doing here?" - Peter Griffin (to Joe and his wheelchair buddies)

  2. #2
    Registered User
    Join Date
    Aug 2004
    Posts
    77
    Thats something in the KDE project, I believe, the KDevelop tries to use autoconf to create the makefile for your project before compiling it. If I remember right aclocal.m4 is a set of macros for autoconf.

    Its not a problem with your code (obviously, since it compiled outside of KDevelop). Its possibly something that is expected in the KDE environment, thats missing in Gnome.

    You may want to try using Anjuta, a fairly good C IDE for Gnome, since it won't have the KDE dependencies.

    Personally speaking I use jEdit and compile from the command line. Makefiles aren't terribly hard to write so I haven't seen much real need for an IDE to handle those for me.
    So, do you understand everything you know about this yet?

    "Begin at the beginning," the King said, very gravely, "and go on till you come to the end; then stop."

  3. #3
    Cat without Hat CornedBee's Avatar
    Join Date
    Apr 2003
    Posts
    8,892
    aclocal.m4 isn't KDevelop-specific, though. It's a part of the GNU autoconf system.
    The problem must lie in the settings of KDevelop.
    All the buzzt!
    CornedBee

    "There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
    - Flon's Law

  4. #4
    Advanced Novice linucksrox's Avatar
    Join Date
    Apr 2004
    Location
    Michigan
    Posts
    198
    thanks for the comments, I think I'll just stay away from KDevelop, at least for now, since I don't even know what a makefile is...
    all i know is how to program in C and C++ and sometimes get it to compile and run
    for right now I'm just doing console stuff anyway so it doesn't matter if I have to use the terminal to compile and run
    plus KDevelop doesn't seem to be everyone's favorite IDE anyway...
    "What are all you parallelograms doing here?" - Peter Griffin (to Joe and his wheelchair buddies)

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. apperently the c++ manual im reading is outdated.
    By MegaManZZ in forum C++ Programming
    Replies: 6
    Last Post: 01-18-2008, 05:34 AM
  2. Outdated Printer Drivers
    By sean in forum Tech Board
    Replies: 1
    Last Post: 07-27-2003, 10:14 AM
  3. Getting rid of precompiled crap and outdated object files
    By Lynux-Penguin in forum Linux Programming
    Replies: 0
    Last Post: 05-16-2002, 12:08 AM
  4. Outdated equipment
    By Govtcheez in forum A Brief History of Cprogramming.com
    Replies: 2
    Last Post: 09-26-2001, 06:36 PM

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21