headers
James Linder | 1 Apr 2012 03:17
Favicon

Re: installation on nfs disk


On 31/03/2012, at 10:00 PM, macports-users-request <at> lists.macosforge.org wrote:

>> ./configure --prefix=/ibpc/osx/lbt/macport/2.0.4/SL --enable-readline
>> --with-install-user=`id -un` --with-install-group=`id -gn`
>> --with-tcl-package=/ibpc/osx/lbt/macport/2.0.4/SL/share/macports/Tcl
>> 
>> And here is the error message I get.
>> 
>> Warning: No index(es) found! Have you synced your source indexes?
>> port registry doesn't exist at
>> "/ibpc/osx/lbt/macport/2.0.4/SL/var/macports/registry/registry.db" and
>> couldn't write to this location
>> 
>> I'm supprised because I specify that I should have all the permissions in
>> the configure (--with-install-user and --with-install-group).
>> 
> 
> MacPorts requires root permissions by default.  The root user is normally
> converted to "nobody" over NFS, because root is a locally privileged
> account, not a network-wide superuser account.  You could change NFS export
> options to suppress that (not recommended) or you could configure MacPorts
> to not use root privileges.

Actually if you are NOT on a trusted lan then you ought not be building on it
If you are on a trusted lan then IMHO no_root_squash is a much easier option than trying to run macports as a
non root user.
ReadTheMan on NFS options

James
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kerry Clendinning | 1 Apr 2012 03:52
Picon
Favicon

Re: Error: Failed to install p5.12-locale-gettext

Ryan Schmidt <ryandesign <at> macports.org> writes:

> 
> 
> On Jan 5, 2012, at 11:32, Andreas Wagner wrote:
> 
> > :info:configure checking for gettext... no
> > :info:configure checking for gettext in -lintl...gettext function not found.
Please install libintl
> at Makefile.PL line 18.
> 
> Looks like the same issue we've seen reported dozens of times before. Search
the issue tracker and mailing
> list archives. If anyone can come up with a solution that will fix this once
and for all I'd sure be grateful.
> 
> 

I'm brand new to macports, so don't shoot if my suggestion is hogwash, but I got
around the above error with this change in macports.conf:

macportsuser            root
Permalink | Reply | 0 comments |
headers
Chris Janton | 1 Apr 2012 19:22
Favicon

mysql55

Decided to give mysql55 a go. Switching from mysql5

Everything appeared to work just fine with the build.

deactivated mysql5 and mysql5-server (forced due to some dependencies)

installed mysql55 and mysql55-server

port select mysql mysql55

mysql won't start due to the following problems, both stemming from my.cnf defaults that worked previously

[mysqld]
pid_file=/var/mysql

If this line is included mysql fails to start complaining that /var/mysql is a directory, which is a true
statement. If I comment out, or make
'pid_file=' then the pid file is created in the data directory. That's OK, I guess. I don't know why it
stopped working.

[mysqld]
federated

If this line is included (to enable the FEDERATED engine) mysql fails to start complaining about 'unknown
option --federated'
If I comment it out, mysql starts.

How do I enable the FEDERATED engine in this case? Something missing in the build that allows it?

After getting mysqld to start I did
(Continue reading)

Permalink | Reply | 4 comments |
headers
Nick Hughes | 2 Apr 2012 05:44
Picon

Xcode 4.3.2 macports requirement (please add to FAQ)

Folks,


I was stumped on this for awhile trying to run:
sudo port -d selfupdate

I would keep getting this error:
sudo port -d selfupdate

configure: error: C compiler cannot create executables

I uninstalled all prior versions of Xcode and reinstalled the new version from the App Store.

I figured out these steps were necessary (and not really documented) to get "port -d selfupdate" to compile things again:

1. Make sure you click on the Xcode application icon in the Application folder after installing it

2. In Xcode, go to Preferences, then click DOWNLOAD, then click COMPONENTS

3. Click on "Install Command Line tools"

4. The command lines utilities will download and install.

5. At this point, you can now compile in the command line and therefore macports selfupdate should work.


You may want to add this to the FAQ if it's not there.

Nick
<div>
<p>Folks,</p>
<div><br></div>
<div>I was stumped on this for awhile trying to run:</div>
<div>sudo port -d selfupdate</div>
<div><br></div>
<div>I would keep getting this error:</div>
<div>sudo port -d selfupdate</div>
<div><br></div>
<div>
configure: error: C compiler cannot create executables</div>
<div><br></div>
<div>I uninstalled all prior versions of Xcode and reinstalled the new version from the App Store.</div>
<div><br></div>
<div>I figured out these steps were necessary (and not really documented) to get "port -d selfupdate" to compile things again:</div>
<div><br></div>
<div>1. Make sure you click on the Xcode application icon in the Application folder after installing it</div>
<div><br></div>
<div>2. In Xcode, go to Preferences, then click DOWNLOAD, then click COMPONENTS</div>
<div><br></div>
<div>3. Click on "Install Command Line tools"</div>
<div><br></div>
<div>4. The command lines utilities will download and install.</div>
<div><br></div>
<div>5. At this point, you can now compile in the command line and therefore macports selfupdate should work.</div>
<div><br></div>
<div><br></div>
<div>You may want to add this to the FAQ if it's not there.</div>
<div><br></div>
<div>Nick</div>
</div>
Permalink | Reply | 3 comments |
headers
Lawrence Velázquez | 2 Apr 2012 07:35
Picon
Gravatar

Re: Xcode 4.3.2 macports requirement (please add to FAQ)

On Apr 1, 2012, at 11:44 PM, Nick Hughes <nixon8890 <at> gmail.com> wrote:

> You may want to add this to the FAQ if it's not there.

The FAQ is a tad out of date, but this is mentioned in the guide.

http://guide.macports.org/#installing.xcode.lion.43

vq
Permalink | Reply | 2 comments |
headers
ximon | 2 Apr 2012 09:05
Picon

Re: Xcode 4.3.2 macports requirement (please add to FAQ)

Hmmm,

After upgrading a little while ago to Xcode 4.3.1, I find I am unable to install the command line tools - an
error message is displayed informing me that my developer account is "not in good standing"  and needs to be
updated. I followed the link to the member centre and logged in but there doesn't seem to be an account
update procedure. I updated my profile but that didn't help either.

Do I need to join one of the suggested (iOS, Mac or Safari) developer programs?

Macports builds are working fine BTW, perhaps using the command line tools from the previous version, but I
can see the day coming  when installing a newer set of tools will be required to keep Macports up to date….

ximon.

On 2 Apr 2012, at 06:35, Lawrence Velázquez wrote:

> On Apr 1, 2012, at 11:44 PM, Nick Hughes <nixon8890 <at> gmail.com> wrote:
> 
>> You may want to add this to the FAQ if it's not there.
> 
> The FAQ is a tad out of date, but this is mentioned in the guide.
> 
> http://guide.macports.org/#installing.xcode.lion.43
> 
> vq
> _______________________________________________
> macports-users mailing list
> macports-users <at> lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Permalink | Reply | 1 comment |
headers
Drechsel Wolf | 2 Apr 2012 09:36
Favicon

port of ige-mac-bundler won't bundle gnumeric

> I used "sudo port install" to install first gnumeric and then ige- 
> mac-bundler, apparently without error.
>
> But when I then downloaded and extracted the "definitions of  
> Gnumeric.app" and, in the Gnumerics folder thereby created, ran
>
>  ige-mac-bundler Gnumeric.bundle
>
> I got error message:
>
> Traceback (most recent call last):
>  File "/opt/local/bin/ige-mac-bundler", line 5, in <module>
>    import bundler.main
> ImportError: No module named bundler.main

I had exactly the same error with inkscape and using the local  
portfile from
https://trac.macports.org/ticket/27794

Wolf
Permalink | Reply | 0 comments |
headers
Jerry | 2 Apr 2012 10:38
Favicon

A port is clashing with another program installed in /opt that is not a port

Hi List,

Today I installed MacPorts into Lion 10.7.3. I used the pkg installer and then typed:

    sudo xcode-select -switch /Applications/Xcode.app

to expose Xcode 4.3.1

and then

    sudo port install py-spyder

(Spyder is a python IDE for technical computing.)

The installation failed with this error so that dbus and several other dependencies were not installed:

----------------------
Error: Target org.macports.activate returned: Image error:
/Library/LaunchAgents/org.freedesktop.dbus-session.plist already exists and does not belong to a
registered port.  Unable to activate port dbus. Use 'port -f activate dbus' to force the activation.
Error: Failed to install dbus
----------------------

I looked at /Library/LaunchAgents/org.freedesktop.dbus-session.plist and found that it is an alias
that points to 

    /opt/openmodelica/Library/LaunchAgents/org.freedesktop.dbus-session.plist

It turns that I had some time back installed Open Modelica using a .mpkg from a .dmg downloaded from
http://openmodelica.org/, so that my /opt at the upper levels looks like this:

    /opt/local
    /opt/openmodelica

If I take the suggestion by the MacPorts error message above to use 'port -f activate dbus' will this disturb
anything with my Open Modelica installation?

Thanks,
Jerry
Permalink | Reply | 4 comments |
headers
Arno Hautala | 2 Apr 2012 15:14
Favicon
Gravatar

Re: Xcode 4.3.2 macports requirement (please add to FAQ)

On 2012-04-02, ximon <ximon <at> ximon.karoo.co.uk> wrote:
> Hmmm,
>
> After upgrading a little while ago to Xcode 4.3.1, I find I am unable to
> install the command line tools - an error message is displayed informing me
> that my developer account is "not in good standing"  and needs to be
> updated. I followed the link to the member centre and logged in but there
> doesn't seem to be an account update procedure. I updated my profile but
> that didn't help either.
>
> Do I need to join one of the suggested (iOS, Mac or Safari) developer
> programs?

You shouldn't need to pay for a developer program in order to download
the Command Line Tools. I do recall that this was an issue when 4.3.2
was first released, but it seemed to be corrected on Apple's side
fairly quickly (I think it was only a few hours).

You might try removing / logging out of your Apple ID or Developer ID,
log back in, and try again. If you're still seeing the issue you
should probably contact Apple's Developer support.

--

-- 
arno  s  hautala    /-|   arno <at> alum.wpi.edu

pgp b2c9d448
Permalink | Reply | 0 comments |
headers
Arno Hautala | 2 Apr 2012 15:33
Favicon
Gravatar

Re: A port is clashing with another program installed in /opt that is not a port

On 2012-04-02, Jerry <lanceboyle <at> qwest.net> wrote:
>
> Error: Target org.macports.activate returned: Image error:
> /Library/LaunchAgents/org.freedesktop.dbus-session.plist already exists and
> does not belong to a registered port.  Unable to activate port dbus. Use
> 'port -f activate dbus' to force the activation.
> Error: Failed to install dbus
> ----------------------
>
> I looked at /Library/LaunchAgents/org.freedesktop.dbus-session.plist and
> found that it is an alias that points to
>
> /opt/openmodelica/Library/LaunchAgents/org.freedesktop.dbus-session.plist
>
> It turns that I had some time back installed Open Modelica using a .mpkg
> from a .dmg downloaded from http://openmodelica.org/, so that my /opt at the
> upper levels looks like this:
>
>     /opt/local
>     /opt/openmodelica
>
> If I take the suggestion by the MacPorts error message above to use 'port -f
> activate dbus' will this disturb anything with my Open Modelica
> installation?

So, the issue isn't that anything is installed into /opt/openmodelica,
it's that Open Modelica and MacPorts dbus want to install a launchd
plist to the same place.

I'm not familiar with Open Modelica, but it sounds like it installed
it's own copy of dbus. It's possible that you could force the install
without issue, but Open Modelica may be reliant on a specific version
of dbus and run into issues when using the version supplied by
MacPorts.

The dbus port does supply a "+no_startupitem" variant which should
skip installing the launchd plist. The launchd task isn't started by
default anyway and I think I recall that ports that depend on dbus are
usually intelligent enough to start it on their own if it's not
running (corrections welcome). I certainly don't recall running into
any issues with having not started the launchd task.

So, your best bet is to clean dbus and reinstall it with the
"+no_startupitem" variant.

port clean dbus
port install dbus +no_startupitem
port install py-spyder

It may also be worth while to report this issue to Open Modelica. I
doubt that their launchd plist is required for operation.

Better Solution:

I notice that Open Modelica suggest using MacPorts to install their
software. It may be best to remove the /opt/openmodelica directory,
the launchd plist that linked to that directory, and any other OM
files that you can find, and reinstall using MacPorts.

That you have files in /opt/openmodelica, a dbus plist that is linked
in a similar way to how MacPorts manages things, and that the
developers suggest using MacPorts to manage your installation suggests
that the binary release that they've provided was created by a
MacPorts installation from a custom prefix.

--

-- 
arno  s  hautala    /-|   arno <at> alum.wpi.edu

pgp b2c9d448
Permalink | Reply | 3 comments |

Gmane