Re: registry.db documentation?

On 2012/05/24 15:00, Daniel J. Luke wrote: > On May 24, 2012, at 4:33 PM, Mark Perkins wrote: >> Can someone point me to documentation of MacPorts' registry.db? > > I don't think there is any (aside from reading the source code). > >> What I'm really interested in seeing is the schema for the "ne

Re: registry.db documentation?

On May 24, 2012, at 4:33 PM, Mark Perkins wrote: > Can someone point me to documentation of MacPorts' registry.db? I don't think there is any (aside from reading the source code). > What I'm really interested in seeing is the schema for the "new" sqlite db. is just asking sqlite3 to give it to

Please remove me off the user list. Many Thanks!

___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: error installing npm

> The following seemed pertinent so I included it > > :error:install org.macports.install for port npm returned: no destroot found > at: > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_npm/npm/work/destroot > :debug:install Error co

Re: error installing npm

On May 24, 2012, at 3:32 PM, Brandon Allbery wrote: > On Thu, May 24, 2012 at 4:26 PM, Puneet Kishor wrote: > >> Please see the log file for port npm for details: >> >> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_npm/npm/main.log

registry.db documentation?

Can someone point me to documentation of MacPorts' registry.db? The info at looks to be for an old version. What I'm really interested in seeing is the schema for the "new" sqlite db. Thanks, Mark _

Re: error installing npm

On Thu, May 24, 2012 at 4:26 PM, Puneet Kishor wrote: > Please see the log file for port npm for details: > > > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_npm/npm/main.log > And this contains...? -- brandon s allbery

error installing npm

one of those (rare) days of trouble with macports $port -v MacPorts 2.1.1 Entering interactive mode... ("help" for help, "quit" to quit) [Users/punkish] > quit $sudo port install npm Password: ---> Computing dependencies for npm ---> Installing npm @1.1.22_0 Error: org.macports.install for por

Re: error install GRASS

On May 24, 2012, at 1:17 PM, Brandon Allbery wrote: > On Thu, May 24, 2012 at 2:13 PM, Puneet Kishor wrote: > >> I got the following error in the log. Hopefully someone can help me find a >> solution >> > > You have managed to copy your "error" at a spot which appears to be a > summary coming

Re: error install GRASS

On Thu, May 24, 2012 at 2:13 PM, Puneet Kishor wrote: > I got the following error in the log. Hopefully someone can help me find a > solution > You have managed to copy your "error" at a spot which appears to be a summary coming right after the actual error, thus telling us nothing other than th

error install GRASS

I got the following error in the log. Hopefully someone can help me find a solution grass/grass/work/grass-6.4.0/visualization/nviz :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_grass/grass/work/grass-6.4.0/visualization/n

Re: Qt debug

Hi James - Is your qt4-mac-devel installed with the +debug vartiant? Try "port installed qt4-mac-devel" and that should show you what variants are installed. If it's not installed as +debug, then there will be very few "_debug" libraries, if any -- no supposed to be any, but the default Qt instal

Re: XCode command line tools enough for MacPorts?

> Start with a fresh system, install Xcode 4.3 and the Command line tools and > Mac Ports will not work. You have to jump through additional hoops. Right: accepting xcode's license agreement comes to mind, which was mentioned. On a clean system I don't believe you'd have to set xcode-select eith

Re: XCode command line tools enough for MacPorts?

On May 22, 2012, at 14:29, Phillip Koebbe wrote: > Just upgraded to Xcode 4.3 this morning and didn't have any problems Start with a fresh system, install Xcode 4.3 and the Command line tools and Mac Ports will not work. You have to jump through additional hoops. ___

Re: XCode command line tools enough for MacPorts?

> Downloading and instating Xcode and installing the command line tools is not > enough to get MacPorts working. You mean it is? smime.p7s Description: S/MIME cryptographic signature ___ macports-users mailing list macports-users@lists.macosforge.org

Re: proposal - make all ports independent of which version of Perl is installed or the major one

> Oh? There are significant differences between it and the system provided bash? Snow Leopard is using 3.2 and MacPorts has 4.2 available... that's a whole major version of difference. smime.p7s Description: S/MIME cryptographic signature ___ macport

Re: XCode command line tools enough for MacPorts?

On May 22, 2012, at 12:56, Ryan Schmidt wrote: > think things are as straightened out now as they're going to get. To use > Xcode 4.3, you have to agree to its license agreement, and install its > command line tools afterward. I believe this is all documented in our > documentation. Downloadi

Re: proposal - make all ports independent of which version of Perl is installed or the major one

On May 23, 2012, at 21:36, Bjarne D Mathiesen wrote: > I do recommend installing bash from MacPorts and using that :-) Oh? There are significant differences between it and the system provided bash? ___ macports-users mailing list macports-users@lists.m

Re: gcc44 installs correctly but default gcc is still used

Thanks guys, I get it now. :) Best, Josie On Wed, May 23, 2012 at 5:54 PM, Lawrence Velázquez wrote: > On May 23, 2012, at 5:19 p.m., Josie Reinhardt wrote: > >> Still at least now /opt/local/bin are in front...  but where did the >> other stuff come from??? > > > The system-level shell startup

Re: Qt debug

On 24/05/2012, at 7:28 PM, Craig Treleaven wrote: > At 10:58 AM +0800 5/24/12, James Linder wrote: >> Hi >> If anyone can save me ages of hunting I'd appreciate it lots: >> >> I built Qt [port install qt4-mac-devel] >> >> I then built my application which fails with: >> >> ... >> /usr/bin/g++-

Re: Qt debug

At 10:58 AM +0800 5/24/12, James Linder wrote: Hi If anyone can save me ages of hunting I'd appreciate it lots: I built Qt [port install qt4-mac-devel] I then built my application which fails with: ... /usr/bin/g++-4.2 -headerpad_max_install_names -arch x86_64 -Xarch_x86_64 -mmacosx-version-m