How to run autoconf?

Hi!

I want to build something but autoconf doesn't work.

I downloaded new autoconf from OS4depot and set the S-flag on them, but they won't execute:

> sh
abc:/Project> autoconf
/SDK/Local/C/autoconf[510]: /SDK/Local/C/autom4te: No such file or directory

But the file is there and has s+rwed flags.

Any idea?

It's all the same as i told you before: once you need to use cmake, autoconf, automake or anything of that sort: just use crosscompiler, where everything works without any problems, always :)

I have to agree with Kas1e. Autoconf barely works properly even on Linux in my experience. Most source packages thankfully already have had it run on them, sometimes it happens that the datestamps have been screwed up and it thinks it needs running again. You can "touch" some files to fix this, but I don't remember which ones off-hand.

@Deniil

Ah, the horrible autoconf. I avoid anything that needs it. Apart from not working on AmigaOS, the config scripts tend to be huge and cryptic (to me), and I've got no idea how to add AmigaOS specific stuff.

CMake is a bit better on AmigaOS, but still problematic. I still haven't found reliable instructions to use CMake with a cross-compiler. The ones I tried all failed.

Anyway, building on kas1e's suggestion, you'll find instructions to get a working AmigaOS cross-compiler for Windows here.

Hans

@Hans

I've sent you an e-mail with my cmake toolchain file for cross-compiling. It's not perfect has helped me in the past.

Thanks all!

@Hans

That's quite some description, just to install a compiler!

I guess I'll install all this and then snapshot the directory as a backup...

@Deniil

OK so you installed autoconf.

Did you make sure you had m4 and perl installed?

m4 is http://os4depot.net/index.php?functio ... e=development/misc/m4.lha

perl is here:

http://os4depot.net/index.php?functio ... /language/perl_newlib.lha

Run snoopy while testing autconf to check what file it's looking for, when you get nested abc-shell / perl lauched programs it's not always obvious.

Quote:

s flag is abit meaningless to abc-shell or perl, but what can matter occasionally is if the group and user flags are set

If the snoopy log shows that it really is autom4te that it can't see then try the below.

11.RAM Disk:> ls -l SDK/Local/C/autom4te
-rwx------ 1 root wheel 32206 2017-08-02 20:14 SDK/Local/C/autom4te
11.RAM Disk:> chmod 755 SDK/Local/C/autom4te
11.RAM Disk:> ls -l SDK/Local/C/autom4te
-rwxr-xr-x 1 root wheel 32206 2017-08-02 20:14 SDK/Local/C/autom4te


autoconf is a perl script so please do report any further problems both to henning as the porter and myself as the maintainer of perl.

Further note, if you have installed one of the gcc 5.x archives please make sure there no core-utils commands in GCC:bin

1. that was the wrong place
2. but thanksfully since they are broken, (linked against newlib rather thanclib2) them being in the wrong place makes them easily remaovable.

IN the case the last section of my previous, has anything to do with your issues here is quick perl script to cleanup gcc:bin



redirect the output to a file, do a quick visual sanity check, then execute it.

Not sure about m4, but I probably have perl since the script starts and looks for its companion autom4te.

Haven't installed new gcc or binutils.

@Hans

Quote:

I used cmake with cross-compiler to create the openjpeg 2.0.0 port on OS4Depot.

Basically what you have to do is write a config file for your cross-compiler setup which you then specify to cmake on the commandline with some long ass parameter that I can't remember. Documentation on how to write the config file is pretty much nonexistent as I recall so you have to look at other such files to see how it's done. I would post the file I made but I don't think I have it any more and I haven't used cmake since because I find it easier not to have to deal with this annoying build system.

Personally I find autoconf/configure much easier to work with than cmake.