Re: port install painfully slow
On Sun, Dec 8, 2013 at 8:49 AM, Brian D. McGrew br...@visionpro.commailto:br...@visionpro.com wrote: dyld: DYLD_ environment variables being ignored because main executable (/usr/bin/sudo) is setuid or setgid I suggest you find out what is setting these, as MacPorts executes most things *not* as root and they can be causing problems (which could be minor or quite major). OS X isn't Linux; setting DYLD_* variables for anything other than temporary specific testing is almost always wrong. That is very interesting… I unset the DYLD_* stuff and all is good. Never, ever seen that before. We set the DLYD_* stuff on our own for our software running on the Mac. Our package is a native Linux app, however, a few of us prefer the Mac so an enterprising architect got us compiling on the Mac and it's just worked all along. Never seen any problems until now. -b ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: port install painfully slow
On Dec 9, 2013, at 06:06, Brian D. McGrew wrote: On Sun, Dec 8, 2013 at 8:49 AM, Brian D. McGrew wrote: dyld: DYLD_ environment variables being ignored because main executable (/usr/bin/sudo) is setuid or setgid I suggest you find out what is setting these, as MacPorts executes most things *not* as root and they can be causing problems (which could be minor or quite major). OS X isn't Linux; setting DYLD_* variables for anything other than temporary specific testing is almost always wrong. That is very interesting… I unset the DYLD_* stuff and all is good. Never, ever seen that before. We set the DLYD_* stuff on our own for our software running on the Mac. Our package is a native Linux app, however, a few of us prefer the Mac so an enterprising architect got us compiling on the Mac and it's just worked all along. Never seen any problems until now. Don’t use DYLD_LIBRARY_PATH; it tells the OS you know better than it where libraries are located, and to look only in the paths you specify; that’s seldom what you want. You can use DYLD_FALLBACK_LIBRARY_PATH as a stopgap measure; it tells the OS to look in the specified locations *after* all the other locations where it would normally look. The correct long-term solution is to fix your libraries so they’re compiled with the correct -install_name parameter so that these variables aren’t needed at runtime. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: port install painfully slow
On Dec 9, 2013, at 06:06, Brian D. McGrew wrote: On Sun, Dec 8, 2013 at 8:49 AM, Brian D. McGrew wrote: dyld: DYLD_ environment variables being ignored because main executable (/usr/bin/sudo) is setuid or setgid I suggest you find out what is setting these, as MacPorts executes most things *not* as root and they can be causing problems (which could be minor or quite major). OS X isn't Linux; setting DYLD_* variables for anything other than temporary specific testing is almost always wrong. That is very interesting… I unset the DYLD_* stuff and all is good. Never, ever seen that before. We set the DLYD_* stuff on our own for our software running on the Mac. Our package is a native Linux app, however, a few of us prefer the Mac so an enterprising architect got us compiling on the Mac and it's just worked all along. Never seen any problems until now. Don’t use DYLD_LIBRARY_PATH; it tells the OS you know better than it where libraries are located, and to look only in the paths you specify; that’s seldom what you want. You can use DYLD_FALLBACK_LIBRARY_PATH as a stopgap measure; it tells the OS to look in the specified locations *after* all the other locations where it would normally look. The correct long-term solution is to fix your libraries so they’re compiled with the correct -install_name parameter so that these variables aren’t needed at runtime. Ah, right, thanks for the clarification. We set DYLD_FALLBACK_LIBRARY_PATH, not the other. But, I don't set that in a new terminal. I have to run a script that sets up my build environment, which is 'usually' the first thing I do. So popping a new terminal and running port without my build environment works fine. But, if I set my env and DYLD_FALLBACK… is set, it no workee… very slow, don't know why. but the fix, I just won't have DYLD_ set when I run port. Still, never seen this before and if anyone knows why it's happening, I'd be interested in knowing. -b ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: port install painfully slow
On Mon, Dec 9, 2013 at 7:43 AM, Brian D. McGrew br...@visionpro.com wrote: Ah, right, thanks for the clarification. We set DYLD_FALLBACK_LIBRARY_PATH, not the other. But, I don't set that in a new terminal. I have to run a script that sets up my build environment, which is 'usually' the first thing I do. So popping a new terminal and running port without my build environment works fine. But, if I set my env and DYLD_FALLBACK… is set, it no workee… very slow, don't know why. but the fix, I just won't have DYLD_ set when I run port. Still, never seen this before and if anyone knows why it's happening, I'd be interested in knowing. We can't tell for certain without knowing what your environment looks like, but it is very likely that your replacement libraries are shadowing some standard function in a way that breaks MacPorts (and may affect other OS X native software although perhaps not as drastically). There are some debugging DYLD_ variables you can set to show what is getting bound from where, but without knowing what's in the libraries you have been forcing it to use we can't even guess. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
port install painfully slow
All of the sudden, a port install is painfully slow. Not sure why, not seeing any debug as to what's going on??? See my comments to the debug out below in red. 57_ sudo port -dv install mysql55 dyld: DYLD_ environment variables being ignored because main executable (/usr/bin/sudo) is setuid or setgid Password: DEBUG: Copying /Users/brian/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/databases/mysql55http://rsync.macports.org/release/tarballs/ports/databases/mysql55 DEBUG: OS darwin/12.5.0 (Mac OS X 10.8) arch i386 DEBUG: Sourcing PortGroup archcheck 1.0 from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/archcheck-1.0.tclhttp://rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/archcheck-1.0.tcl DEBUG: Sourcing PortGroup cmake 1.0 from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/cmake-1.0.tclhttp://rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/cmake-1.0.tcl DEBUG: Sourcing PortGroup select 1.0 from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/select-1.0.tclhttp://rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/select-1.0.tcl DEBUG: adding the default universal variant DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.confhttp://rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf DEBUG: Running callback portconfigure::add_automatic_compiler_dependencies DEBUG: Finished running callback portconfigure::add_automatic_compiler_dependencies DEBUG: Running callback portbuild::add_automatic_buildsystem_dependencies DEBUG: Finished running callback portbuild::add_automatic_buildsystem_dependencies DEBUG: Attempting ln -sf /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_mysql55/mysql55/work /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/databases/mysql55/workhttp://rsync.macports.org/release/tarballs/ports/databases/mysql55/work DEBUG: changing euid/egid - current euid: 0 - current egid: 0 DEBUG: egid changed to: 501 DEBUG: euid changed to: 502 DEBUG: Starting logging for mysql55 -- Hang here for up to 10 minutes??? … DEBUG: Searching for dependency: mysql_select DEBUG: Didn't find receipt, going to depspec regex for: mysql_select DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/databases/mysql_selecthttp://rsync.macports.org/release/tarballs/ports/databases/mysql_select DEBUG: OS darwin/12.5.0 (Mac OS X 10.8) arch i386 DEBUG: Sourcing PortGroup select 1.0 from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/select-1.0.tclhttp://rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/select-1.0.tcl DEBUG: universal_variant is false, so not adding the default universal variant DEBUG: Running callback portconfigure::add_automatic_compiler_dependencies DEBUG: Finished running callback portconfigure::add_automatic_compiler_dependencies DEBUG: Running callback portbuild::add_automatic_buildsystem_dependencies DEBUG: Finished running callback portbuild::add_automatic_buildsystem_dependencies DEBUG: tcp_wrappers has no conflicts DEBUG: mysql_select has no conflicts --- Hang here for up to 10 minutes??? … Not really sure what's going on. Don't see anything in any log files and of course no output to the screen while it's hanging out waiting. What should I go look at to figure out what's going on??? It's not just the mysql55 package, it's any package I install. That was just the example I'm using right now. I've blown out ports and reinstalled from binary. When that didn't work I reinstalled from svn source as well. Thanks, -b ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: port install painfully slow
On Sun, Dec 8, 2013 at 8:49 AM, Brian D. McGrew br...@visionpro.com wrote: dyld: DYLD_ environment variables being ignored because main executable (/usr/bin/sudo) is setuid or setgid I suggest you find out what is setting these, as MacPorts executes most things *not* as root and they can be causing problems (which could be minor or quite major). OS X isn't Linux; setting DYLD_* variables for anything other than temporary specific testing is almost always wrong. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
