*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I had this same issue the last time I attempted to install Fbsd 5.2.1 on my other computer. I install the system, updated the ports, compiled xorg, tested and configured xorg, started it too. Then I did a pkg_add of fluxbox. Fluxbox during the install showed that a lot of the stuff was already installed. I made a .xinitrc file in my home directory and typed "fluxbox" on the first line. Proceeded to type "Startx". It thinks for a little bit, screen goes black, and Im back in cosole with the message "/libexex/ld-elf.so.1: shared object "libexpat.so.4" not fount. It is repeated 4 times one after the other.
I googled this problem but nothing turned up results that pertained to FreeBSD and any connection to xorg or fluxbox.
This is the same spot where I got stuck dead last time.
Problem solved and its a big thanks to my bestest friend in the whole world.
First I dloaded Expat 1.95 from there website at sourceforge.expat.com using links. Unziped it, read the README, Configured it, and compiled it. Then I ran startx, the same thing happened so I IMED my bestest buddy and he says make a symlink. Well when I updated my file DB it found libexpat.so.5, not 4. So he said make a symlink from 5 to 4. Then I typed startx and it worked.
OH MAN IM SO FREAKING HAPPY. I would scream if my parents werent sleeping.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
Well ports automatically satisfies dependencies, so yes it most likely was a method of installation problem. Now you have some rogue software on your system because how are you going to keep libexpat up to date with FreeBSD?
You really should read the handbook documentation on ports. There's no reason to be downloading things as source and rolling the dice as to whether they build correctly, and even if they do then they're pretty much unupdatable and the FreeBSD ports system won't be aware that they're there. There are over 10,000 packages in the ports tree, so it's pretty likely that anything you want is in there.
I think I searched the ports for Libexpat and even performed a port upgrade and it didnt fix the problem. What bothers me is that it seems I am the only that has run into this problem.
Good Luck - hope you do not run into issues with sym-linking like that. I prefer to do it the "correct" way per the FreeBSD team, but it does take quite a bit more time.....
Well downgrading to the old expat to have the so.4 then upgrading back to the latest to get so.6 is a pain in the ass. To bad you cant just dload that one library.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.