It's also because all tutorials on the internet pointed to macports so by doing this paths for more advanced set-ups and tutorials still worked. It installs the same dependencies as samba for macports at the time the installer was created (and warns the users it'll do so, since it actually works if Macports Samba is installed already and mentions MacPorts already exists if it's the case). Indeed, one of the ideas behind the way SMBUp installs stuff is to mimic Macports' paths so it's possible to force upgrades on it and keep SMBUp working. I feel I should add a note, should this popup in the future. The port upgrade to the outdated ports completed without error. I then followed up by performing the selfupdate and upgrade to the outdated ports: The port cleaning and the port forced upgrade completed without error. Sudo port -n upgrade -force expat libiconv ncurses zlib openssl gettext popt Sudo port clean expat libiconv ncurses zlib openssl gettext popt Replying to commands should rebuild them all: Then, I completed your suggested commands below.
To clean up from any earlier attempt to build Pango. Thank you for your guidance on how to rebuild. I am guessing that the author might fix if he knew the issues.Īny other suggestions? I will proceed to see about fixing - one "application" at a time. I guess I may need to "-force" upgrades for each application installed or modified by SMBup. The SMB server works well, all other issues disregarded. Scroll down on the SMBup page and you can see all of the "applications" checked off that are the problem (helps to corroborate the culprit). I am now thinking that it was (perhaps) an SMB server application that I found from: I noticed these folders created on that date.
You can then use "port provides" to figure out what port provided it, and then rebuild it, for example to rebuild expat: If not, you might want to look at the modification date of your libexpat.1.dylib:Īnd then look for any other files in MacPorts that were installed around the same time, within a minute or five. If you can remember installing any such third-party software, let us know what it was that might help us figure out what all has been overwritten and now needs to be rebuilt. You'll need to reinstall expat, but there may be other affected ports as well. We've encountered some third-party software thusly mispackaged before see for example wiki:ProblemHotlist#xmlwf. We also see that although MacPorts claims to have installed an i386/x86_64 universal version of expat, your libexpat is actually x86_64 only.īoth of these observations point to the likelyhood that you have installed a third-party software package that has overwritten some of your MacPorts libraries.
It confirms that your libexpat really is version 7.0.0, although expat 2.1.0 is supposed to contain libexpat version 8.0.0 (and does on my system). Ok, that shows us two things that are wrong: To report a bug, follow the instructions in the guide:Ĭraigdenman:~ craigdenman$ sudo port clean pangoĬraigdenman:~ craigdenman$ sudo port upgrade outdated opt/local/var/macports/logs/_opt_local_var_macports_sources_release_tarballs_ports_x11_pango/pango/main.log Please see the log file for port pango for details: Gnuplot 4.6.0_0 Computing dependencies for pangoĮrror: for port pango returned: command execution failed The following installed ports are outdated: To upgrade your installed ports, you should run > MacPorts base is already the latest version > Updating MacPorts base sources using rsync If anyone has any ideas I would greatly appreciate them.Craigdenman:~ craigdenman$ sudo port selfupdate I have searched the internet and tried every solution offered. I think the solution to this will also fix my original problem to my program Select New Connection, Pick Microsoft Access Data File, Pick ContinueĮnter Database File Name (A good MS Access (2010) database)Ī Window "Windows Installer" pops up saying "Preparing to Install." Select Database, Pick Next, Select Dataset. Select View, Other Windows, Data Sources, Add New Data Source Here is what I tried using VB 2015 Express I have tried vb 2008, 2012, 2013, and 2015 all with the same results. I have since tried to create a new application with vb using an Access DB and they get hung up. I have tried to clear the exception, then the system gets hung up with a "preparing to install". Debugging it now fails with a "LoaderLock" error. I have a VB app which accessed an Access database (and it worked).
0 kommentar(er)
