FreeBSD: libiconv update fails

Kropotkin · 04-08-2014, 04:00 AM

Hi all,

Portupgrade is failing to upgrade a few packages on my FreeBSD v10-RELEASE server and I am trying to figure out how to fix this.

Here is where libiconv fails:

Code:

===>  Building package for libiconv-1.14_3
Creating package /usr/ports/converters/libiconv/work/pkg/libiconv-1.14_3.tbz
Registering depends:.
Creating bzip'd tar ball in '/usr/ports/converters/libiconv/work/pkg/libiconv-1.14_3.tbz'
tar: lib/libcharset.so: Cannot stat: No such file or directory
tar: lib/libcharset.so.1: Cannot stat: No such file or directory
tar: lib/libiconv.so: Cannot stat: No such file or directory
tar: lib/libiconv.so.3: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256
*** [do-package] Error code 1

In the past, when I encountered something like this, I had the habit of uninstalling a port and then reinstalling it. But if this fails then all kinds of stuff stops working.

What is the smart approach for solving this problem?

Thank you

cynwulf · 04-08-2014, 07:16 AM

Updated your ports tree? http://www.freebsd.org/doc/en/books/...rts-using.html

Then

Code:

# cd /usr/ports/converters/libiconv/
# make clean deinstall

Code:

# make clean install

Run portupgrade again

Kropotkin · 04-08-2014, 07:52 AM

Thanks. I run daily periodic job which updates the ports tree every night.

Just now I did this:

Code:

# cd /usr/ports/converters/libiconv/
# make clean deinstall

but now I can't log in as root to run make, as bash no long works:

Code:

]$ su
Password:
Shared object "libiconv.so.3" not found, required by "bash"

Do you know of a way of forcing 'sh' when logging in? Just took a look at the su manpage but didn't see anything.

cynwulf · 04-08-2014, 10:09 AM

Ouch, and this is why you don't ever change root's shell. The bash shell is not part of any *BSD system, it's built from ports, which is why you should never change root's shell to it. Use the bourne shell (sh) and if you want to do bash stuff just enter 'bash' and proceed from there.

To get a working shell you will need to boot in single user mode (at boot loader menu "Welcome to FreeBSD" option 4)

Then mount file systems:

Code:

# mount -u
# mount -a

Then

Code:

# vipw /etc/passwd

Change root's shell back to /bin/sh

Or this should work

Code:

# chsh -s /bin/sh root

Reboot and that should be it.

Kropotkin · 04-08-2014, 10:29 AM

OK, back in business, thanks.

Code:

# cd /usr/ports/converters/libiconv/
# make clean deinstall
# make clean install

This still produces the same error I mention above.

It seems to have a cascading effect on my system as now around 20 ports are skipped when I run portupgrade.

Any thoughts?

cynwulf · 04-09-2014, 08:21 AM

Quote:

Originally Posted by Kropotkin

Here is where libiconv fails:

Code:

===>  Building package for libiconv-1.14_3
Creating package /usr/ports/converters/libiconv/work/pkg/libiconv-1.14_3.tbz
Registering depends:.
Creating bzip'd tar ball in '/usr/ports/converters/libiconv/work/pkg/libiconv-1.14_3.tbz'
tar: lib/libcharset.so: Cannot stat: No such file or directory
tar: lib/libcharset.so.1: Cannot stat: No such file or directory
tar: lib/libiconv.so: Cannot stat: No such file or directory
tar: lib/libiconv.so.3: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256
*** [do-package] Error code 1

The build seems to go ok?

It looks like the package build which fails as it can't find the binaries which were built, so perhaps the paths are incorrect.

What happens if you "make clean" the port and rebuild it from a root login shell?

If it still fails I would next try moving your ports tree to a backup and fetch a new ports tree snapshot.

Also if possible switch to portmaster instead of portupgrade

nickbeee · 04-27-2014, 03:29 PM

Quote:

Originally Posted by cynwulf

The build seems to go ok?

It looks like the package build which fails as it can't find the binaries which were built, so perhaps the paths are incorrect.

What happens if you "make clean" the port and rebuild it from a root login shell?

If it still fails I would next try moving your ports tree to a backup and fetch a new ports tree snapshot.

Also if possible switch to portmaster instead of portupgrade

I would echo your comments on portmaster, Since I started using it, updating ports became a whole lot easier. It is a shell script and doesn't rely on anything else from the ports tree. Occasionally it will fall over when building a port but it gives you clues where to look. Another important point to be aware of is when updating the ports tree, ALWAYS read /usr/ports/UPDATING.