Failed to locate 'tar' in path: '/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin' or at its MacPorts configuration time location, did you move it?

[lm2lm2]

Failed to locate 'tar' in path: '/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin' or at its MacPorts configuration time location, did you move it?
        while executing
"error "$eMessage or at its MacPorts configuration time location, did you move it?""
        ("macports_try ... error" body line 2)
        invoked from within
"macports_try -pass_signal {
                        return [macports::binaryInPath $prog]
                } on error {eMessage} {
                        error "$eMessage or at its M..."
        (procedure "macports::findBinary" line 5)
        invoked from within
"macports::findBinary tar ${macports::autoconf::tar_path}"
        invoked from within
"set tarcmd [macports::findBinary tar ${macports::autoconf::tar_path}]"
        (file "./src/images_to_archives.tcl" line 19)
make: *** [install] Error 1

device : mac powerpc osx : 10.4 xcode : rel 4, most recent of this os

saw ##26826 but : Does "make" in fact exist in /usr/bin? If not, did you deselect (or forget to select) the "UNIX Development" or "Command-Line Development" option when installing Xcode? If so, or if unsure, use the Xcode installer again and select that option.

=> there is no such option at xcode's wizard installer. I dont find the "tar" executable...

ty!

[jmroot (Joshua Root)]

This is indeed the same as #26826. MacPorts doesn't work without /usr/bin/tar. If that doesn't exist, your Xcode Command Line Tools installation is incomplete. ​https://guide.macports.org/#installing.xcode.other

[lm2lm2]

okay, but how do i do to install tar? it's a bit surprising to figure out that macos 10.4 or older are just concerned by this issue.. i think im not the first one who tries to install macports on powerpc ;)

[jmroot (Joshua Root)]

Actually it's worse than #26826; make is from the developer tools but tar is part of the base OS. I can't tell you how you managed to avoid having it. You probably need to reinstall the OS.