Hello everyone. Just to inform that some gnu utility (autoconf/automake/sed) have been ported/updated by Henning Nielsen Lund. This utilities are really usefull for porting software. Henning doesn't had an amiga for long time. We want To thanks Cloanto and MB for providing a free copy of Amiga forever 2017 to Henning that he used for The Port. Thank you To henning and Cloanto ☺
may i suggest that in our small community devs that want to but cant, for whatever reason, develop, make that public, please? (especially in case of broken hardware)
i would have tried to help, even add to a bounty, to get that dev access to new or used hardware.
Something doesn't seem right about the binary archive (coreutils-bin.lha). There are no individual coreutils commands in the archive. The installer deletes the current coreutils in SDK:local/C and replaces them with a single file named "coreutils".
Amiga X1000 with 2GB memory & OS 4.1FE + Radeon HD 5450
Is the autoconf basically useful for cases where there is not a "configure" script? For example from svn repository. I believe so, but - to save time - might it be useful to recreate a configure file when it does come with the source?
About coreutils, if that one file is not a (tape) archive, how does it work?
About coreutils, if that one file is not a (tape) archive, how does it work?
Not sure if that is what you are looking for, but quoting from one of Henning's replies:
Quote:
> This version also has the big advantage that it is only consisting of > one binary (where the individual commands are symbolic links). > That at least makes sure that it is not using more space than needed > (much of the GNUlib code is used by all commands).
@Raziel Saving some disk space back in the day when Amigas had 20MB hard disks might have been useful but it's an unnecessary gimmick is this age of multi-terabyte hard drives. However, if it works for you that's fine. I just think that the unusual method for installing coreutils should be explained in a readme file in the root directory of the archive.
It also might be worth noting that the adtools.lha archive at OS4Depot and more recent version at Github place the coreutils in SDK:gcc/bin along with the binutils so the coreutils in SDK:local/C will never get used. If you are still using the original SDK (containing gcc 4.2.4) then there's no problem; Henning's coreutils will be used.
Amiga X1000 with 2GB memory & OS 4.1FE + Radeon HD 5450
If the adtools is installed parallel to gcc 4.2.4 (I do not remember if that is default) the path is not SDK:gcc/bin but GCC:bin .
In my SDK:S/gcc-startup GCC: is assigned to SDK:gcc, so it is really the same place. Unless you've changed your SDK startup files, GCC:bin is SDK:gcc/bin.
Amiga X1000 with 2GB memory & OS 4.1FE + Radeon HD 5450
It also might be worth noting that the adtools.lha archive at OS4Depot and more recent version at Github place the coreutils in SDK:gcc/bin along with the binutils so the coreutils in SDK:local/C will never get used. If you are still using the original SDK (containing gcc 4.2.4) then there's no problem; Henning's coreutils will be used.
It is a mistake if someone has placed coreutils in the gcc:bin directory. Coreutils has nothing to do with gcc, only gcc and binutils should be located in that directory.
Best regards, hnl_dk - Henning Nielsen Lund [Denmark]
It is a mistake if someone has placed coreutils in the gcc:bin directory. Coreutils has nothing to do with gcc, only gcc and binutils should be located in that directory.
Agreed but I think someone uploaded that adtools compile because people wanted to compile a program that required GCC 5.x or better. I think it's an adtools binary snapshot and not an official release. I recently D/L a binary snapshot of gcc 5.4.0 from https://dl.bintray.com/sba1/adtools-native and it also has the coreutils mixed in with bintutils & gcc.
I just thought it was worth mentioning because if people are installing newer adtools that way, your coreutils in SDK:local/C might not get used.
Amiga X1000 with 2GB memory & OS 4.1FE + Radeon HD 5450
Agreed but I think someone uploaded that adtools compile because people wanted to compile a program that required GCC 5.x or better. I think it's an adtools binary snapshot and not an official release. I recently D/L a binary snapshot of gcc 5.4.0 from https://dl.bintray.com/sba1/adtools-native and it also has the coreutils mixed in with bintutils & gcc.
Does not sound good. Quote:
I just thought it was worth mentioning because if people are installing newer adtools that way, your coreutils in SDK:local/C might not get used.
I am at the moment cleaning up my coreutils code and fixing minor problems... when I am done, do I plan to setup a repository on the https://github.com/adtools/
Best regards, hnl_dk - Henning Nielsen Lund [Denmark]
I am at the moment cleaning up my coreutils code and fixing minor problems... when I am done, do I plan to setup a repository on the https://github.com/adtools/
In case you aren't aware, there are 3 adtools repositories.
There is https://github.com/sba1/adtools where Sebastion has set up a system for merging OS4 specific changes with more recent GCC toolchains. I think you might need Linux to obtain code from there. The last time I tried to get code from there, OS4 Python couldn't handle the scripts that Sebastion used.
There is https://github.com//adtools which Jens Maus has set up and contains other development tools. I don't know why everything has gotten split up between several repositories but it has.
Amiga X1000 with 2GB memory & OS 4.1FE + Radeon HD 5450
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
