libiconv package no longer exists for ppc darwin9 on macports repo

[dotexe1337 (Michael Shipley)]

On packages.macports.org, ema.uk.packages.macports.org, and nue.de.packages.macports.org (the default repos), there is no longer a package for 1.17 on ppc/ppc64 darwin9. This is strange because just earlier today there was a package and I was attempting to install it (although getting the error mentioned in the previous ticket - ​https://trac.macports.org/ticket/65200) So, the package just disappeared within the last couple hours.

[jmroot (Joshua Root)]

It seems very unlikely that there ever was a ppc archive for libiconv 1.17, given how recently the port was updated to that version and how long the ppc builder has been down. There is one for 1.16.

[dotexe1337 (Michael Shipley)]

Replying to jmroot:

It seems very unlikely that there ever was a ppc archive for libiconv 1.17, given how recently the port was updated to that version and how long the ppc builder has been down. There is one for 1.16.

Hi, there is an issue that was just closed (the one I linked in my first post) about fixing 1.17 on ppc. If you read the summary of that issue, it says: Summary: libiconv fails to upgrade to 1.17 on Leopard for ppc+ppc64: ./iconv.c:200: error: duplicate 'static' → libiconv @1.17: ./iconv.c:200: error: duplicate 'static' I downloaded the archive earlier today and ran into that issue, so I wanted to try it again now to see if it would work since it has presumably been fixed, but the archive no longer exists.

[jmroot (Joshua Root)]

If you were building it then you didn't download an archive of it from packages.macports.org, those are binaries. Please show the actual error you are getting now.

[dotexe1337 (Michael Shipley)]

Replying to jmroot:

If you were building it then you didn't download an archive of it from packages.macports.org, those are binaries. Please show the actual error you are getting now.

Hi, thank you for the help. I ran port install libiconv and it attempts to download the .tbz2 file from all of the different package repos, but it fails since the file does not exist:

:msg:archivefetch ---> Attempting to fetch libiconv-1.17_0.darwin_9.ppc.tbz2 from http://packages.macports.org/libiconv :debug:archivefetch Fetching archive failed: The requested URL returned error: 404

[jmroot (Joshua Root)]

That's all the output you get? The normal behaviour is to go on to attempt to build from source when fetching a binary archive fails, unless you have configured binary-only mode.

[dotexe1337 (Michael Shipley)]

Replying to jmroot:

That's all the output you get? The normal behaviour is to go on to attempt to build from source when fetching a binary archive fails, unless you have configured binary-only mode.

Hi, today I tried to do sudo port -s install libiconv, which to my understanding will compile the port from source. When I do this, it tells me the checksums are mismatched. If I manually update the Portfile with the right checksum, it then gives me some kind of compile error relating to patching:

can't find the file to patch at input line 3

Perhaps you used the wrong -p or --strip option?

The text leading up to this was:

--- src/Makefile.in.orig

+++ src/Makefile.in

[kencu (Ken)]

It seems like your system is pretty messed up right now. To try to get it back to a reasonable state, I would suggest you do this:

1. make sure that you have no unusual enhancements to MacPorts, no special overlays of portfiles or any other modifications from a stock, standard, MacPorts installation
2. sudo port clean libiconv
3. sudo port -v selfupdate
4. sudo port -v upgrade outdated

Don't try to force a build from source or a build from a binary. MacPorts will take care of that automatically.

If libiconv then again fails, please post of the log file of the failed build, by attaching that log to this ticket.

The location of the log file is given to you in the information line right where MacPorts tells you the build failed, and we need that to see what is happening.

[kencu (Ken)]

If you don't have any version of libiconv installed at all now, after the above upgrade outdated process finishes, then do this:

sudo port -v install libiconv

and if it fails, post the log as above.

[ryandesign (Ryan Carsten Schmidt)]

Replying to dotexe1337:

Hi, today I tried to do sudo port -s install libiconv, which to my understanding will compile the port from source. When I do this, it tells me the checksums are mismatched. If I manually update the Portfile with the right checksum, it then gives me some kind of compile error relating to patching:

The checksums of the port are correct. You should revert the change you made to the portfile.

Delete the evidently wrong distfile that MacPorts downloaded for you by running sudo port clean --all libiconv. Then try installing libiconv again.

If it again says checksums are wrong, attach the main.log file so that we can help you interpret it.

[dotexe1337 (Michael Shipley)]

Replying to ryandesign:

Replying to dotexe1337:

Hi, today I tried to do sudo port -s install libiconv, which to my understanding will compile the port from source. When I do this, it tells me the checksums are mismatched. If I manually update the Portfile with the right checksum, it then gives me some kind of compile error relating to patching:

The checksums of the port are correct. You should revert the change you made to the portfile.

Delete the evidently wrong distfile that MacPorts downloaded for you by running sudo port clean --all libiconv. Then try installing libiconv again.

If it again says checksums are wrong, attach the main.log file so that we can help you interpret it.

Hello, thank you for the advice. I ended up switching to a completely different machine as I was having some other problems with the G4 I was using before. I did a fresh install of Leopard, installed XCode 3.1.4 & MacPorts, and then I did sudo port -v -s install libiconv and it compiled and worked perfectly, with no errors. So I'm not sure what the issue originally was on my other system, considering that was a fresh install of Leopard, XCode & MacPorts too. I will try to figure out what's going on with the other system in the future.