Re: Macports not working

2016-08-05 Thread Ignatios Athanasiadis 
Hi Davide,

This suggestion solved my problem.
Thank you.

All best,
Ignatios


> On 5 Aug 2016, at 10:59, Davide Liessi  wrote:
> 
> 2016-08-05 11:25 GMT+02:00 Ignatios Athanasiadis :
>> making a file .bash_profile in my root that in includes a piece of code
> 
> Oh, and maybe if you needed to create .bash_profile, then all your
> terminal settings were in .profile (including the PATH for MacPorts).
> I'd suggest you try removing ~/.bash_profile and adding the PATH="..."
> line at the end of ~/.profile .
> 
> (Sorry for the double message, I first overlooked the .bash_profile thing.)
> 
> Best wishes.
> Davide

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

Re: Macports not working

2016-08-05 Thread Brandon Allbery 
On Fri, Aug 5, 2016 at 5:25 AM, Ignatios Athanasiadis 
wrote:

> then I tried to make a shortcut for mysql that I installed using macports
> making a file .bash_profile in my root that in includes a piece of code
>
> PATH="/usr/local/mysql/bin:$PATH”
>
> as suggested in https://coolestguidesontheplanet.com/
> get-apache-mysql-php-and-phpmyadmin-working-on-osx-10-
> 11-el-capitan/#disqus_thread
>

That page appears to be assuming Homebrew or some other installation
method. MacPorts does not use /usr/local, it uses /opt/local. Also, because
multiple mysql versions may be installed concurrently, paths may differ for
direct access; you can use `port select` to make one directly available.

-- 
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

Re: Macports not working

2016-08-05 Thread Davide Liessi 
2016-08-05 11:25 GMT+02:00 Ignatios Athanasiadis :
> making a file .bash_profile in my root that in includes a piece of code

Oh, and maybe if you needed to create .bash_profile, then all your
terminal settings were in .profile (including the PATH for MacPorts).
I'd suggest you try removing ~/.bash_profile and adding the PATH="..."
line at the end of ~/.profile .

(Sorry for the double message, I first overlooked the .bash_profile thing.)

Best wishes.
Davide
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Macports not working

2016-08-05 Thread Davide Liessi 
2016-08-05 11:25 GMT+02:00 Ignatios Athanasiadis :
> PATH="/usr/local/mysql/bin:$PATH”

I think you are using the wrong closing quotes here: they should be
the straight quotes, i.e. " instead of ”.

Best wishes.
Davide
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Macports not working

2016-08-05 Thread Ignatios Athanasiadis 
Hi all,

My macports seem to be out of use at the moment. I have not tried to uninstall 
them.
Yesterday I tried to make apache2 working according to the suggestions 
presented in this link:

http://digitalshore.io/local-web-development-environment-apache-osx-10-11-el-capitan/
 


then I tried to make a shortcut for mysql that I installed using macports 
making a file .bash_profile in my root that in includes a piece of code 

PATH="/usr/local/mysql/bin:$PATH”

as suggested in 
https://coolestguidesontheplanet.com/get-apache-mysql-php-and-phpmyadmin-working-on-osx-10-11-el-capitan/#disqus_thread
 


Finally, I copied the phpmyadmin file from the location that my macports 
installed it, /opt/local/www/, to ~/Sites/ as described in 
https://coolestguidesontheplanet.com/get-apache-mysql-php-and-phpmyadmin-working-on-osx-10-11-el-capitan/#disqus_thread
 
.
Eventually what the last presented link describes was working on my pc and then 
I switched the pc off.

However, today not only this does not work but I get the next message when I 
use the port command.
-bash: port: command not found

Has anybody else encountered such a problem before?

All best,
Ignatios___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

MacPorts not working on 10.10.3

2015-04-19 Thread Brad Allison 
I just did a fresh install of MacPorts (downloaded from the website), and
tried to install my first package and this is the error I get:

bash-3.2$ sudo /opt/local/bin/port install ircii

---  Computing dependencies for ircii

---  Cleaning ircii

---  Updating database of binaries

---  Scanning binaries for linking errors

---  Found 17 broken file(s), matching files to ports

Warning: No port eggdbus found in the index; can't rebuild

Warning: No port gst-plugins-base found in the index; can't rebuild

Warning: No port gstreamer found in the index; can't rebuild

---  Found 2 broken port(s), determining rebuild order

---  Rebuilding in order

 nmap @5.51

 wget @1.13.4 +ssl

---  Configuring libpcap

Error: org.macports.configure for port libpcap returned: configure failure:
command execution failed

Please see the log file for port libpcap for details:


/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_libpcap/libpcap/main.log

Error: Problem while installing libpcap

Error rebuilding nmap

while executing

error Error rebuilding $portname

(procedure revupgrade_scanandrebuild line 395)

invoked from within

revupgrade_scanandrebuild broken_port_counts $opts

(procedure macports::revupgrade line 5)

invoked from within

macports::revupgrade $opts

(procedure action_revupgrade line 2)

invoked from within

action_revupgrade $action $portlist $opts

(procedure action_target line 96)

invoked from within

$action_proc $action $portlist [array get global_options]

(procedure process_cmd line 103)

invoked from within

process_cmd $remaining_args

invoked from within

if { [llength $remaining_args]  0 } {


# If there are remaining arguments, process those as a command

set exit_status [process_cmd $remaining...

(file /opt/local/bin/port line 5268)
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: MacPorts not working on 10.10.3

2015-04-19 Thread Ryan Schmidt 

On Apr 19, 2015, at 5:54 PM, Brad Allison wrote:

 I just did a fresh install of MacPorts (downloaded from the website), and 
 tried to install my first package and this is the error I get:
 
 bash-3.2$ sudo /opt/local/bin/port install ircii
 ---  Computing dependencies for ircii
 ---  Cleaning ircii

This indicates that ircii was already successfully installed before you even 
ran the sudo port install ircii command.

 ---  Updating database of binaries
 ---  Scanning binaries for linking errors   

After every install or upgrade, MacPorts scans all installed ports for errors.

 ---  Found 17 broken file(s), matching files to ports

17 ports with errors were found during the scan. MacPorts will now try to 
rebuild them.

 Warning: No port eggdbus found in the index; can't rebuild
 Warning: No port gst-plugins-base found in the index; can't rebuild
 Warning: No port gstreamer found in the index; can't rebuild

These 3 ports that you have installed were not found in the ports collection. 
In fact they were deleted from the collection some time ago. I don't remember 
what happened to eggdbus. The gstreamer and gst-plugins ports were split into 
ports for version 0.10.x and 1.x. You can uninstall these ports.

 ---  Found 2 broken port(s), determining rebuild order
 ---  Rebuilding in order
  nmap @5.51 
  wget @1.13.4 +ssl

These 2 installed ports seem to be broken.

 ---  Configuring libpcap
 Error: org.macports.configure for port libpcap returned: configure failure: 
 command execution failed
 Please see the log file for port libpcap for details:
 
 /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_libpcap/libpcap/main.log

The configure phase failed. The log file might tell us why.


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

Re: Macports stopped working after xcode 4.6 upgrade

2013-02-22 Thread Rainer Müller 
On 2013-02-21 09:42, Harald Hanche-Olsen wrote:
 [Lawrence Velázquez lar...@macports.org (2013-02-21 06:31:44 UTC)]
 
 Very annoying. I've actually filed a Radar about this.

 http://openradar.appspot.com/radar?id=2620402
 
 Good.
 
 (Should this be in the FAQ?)

 Considering that we don't recommend using /etc/paths or /etc/paths.d 
 anywhere, I'm not sure it needs to be.
 
 The reason would be to inform people who know about these, or discover them, 
 may want to use them in the way I suggested. But if it doesn't satisfy the F 
 in FAQ, then perhaps it should not be included. Tha balancing act between 
 supplying too little information and too much is always tricky.

Besides the FAQ [1], we also have the ProblemHotlist [2]. It's not
frequently asked and also not a hot problem, so maybe we should have
another list of common problems? Or maybe just decide for one of the
existing wiki pages and add it there...

I would appreciate to have a place in the wiki to point to for topics
like this (Why isn't MacPorts doing/using XYZ?).

Rainer

[1] https://trac.macports.org/wiki/FAQ
[2] https://trac.macports.org/wiki/ProblemHotlist
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Macports stopped working after xcode 4.6 upgrade

2013-02-22 Thread Ryan Schmidt 

On Feb 22, 2013, at 12:37, Rainer Müller rai...@macports.org wrote:

 On 2013-02-21 09:42, Harald Hanche-Olsen wrote:
 [Lawrence Velázquez lar...@macports.org (2013-02-21 06:31:44 UTC)]
 
 Very annoying. I've actually filed a Radar about this.
 
 http://openradar.appspot.com/radar?id=2620402
 
 Good.
 
 (Should this be in the FAQ?)
 
 Considering that we don't recommend using /etc/paths or /etc/paths.d 
 anywhere, I'm not sure it needs to be.
 
 The reason would be to inform people who know about these, or discover them, 
 may want to use them in the way I suggested. But if it doesn't satisfy the F 
 in FAQ, then perhaps it should not be included. Tha balancing act between 
 supplying too little information and too much is always tricky.
 
 Besides the FAQ [1], we also have the ProblemHotlist [2]. It's not
 frequently asked and also not a hot problem, so maybe we should have
 another list of common problems?

We already have far too many lists of problems; we should be working on 
consolidating them, not making new ones.


 Or maybe just decide for one of the
 existing wiki pages and add it there...

I'd be in favor of that. The more-frequently-asked questions would go at nearer 
to the top of the page.


 I would appreciate to have a place in the wiki to point to for topics
 like this (Why isn't MacPorts doing/using XYZ?).

We can also just create individual pages in the wiki to point people to.

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

Re: Macports stopped working after xcode 4.6 upgrade

2013-02-21 Thread Harald Hanche-Olsen 
[Lawrence Velázquez lar...@macports.org (2013-02-21 06:31:44 UTC)]

 Very annoying. I've actually filed a Radar about this.
 
 http://openradar.appspot.com/radar?id=2620402

Good.

  (Should this be in the FAQ?)
 
 Considering that we don't recommend using /etc/paths or /etc/paths.d 
 anywhere, I'm not sure it needs to be.

The reason would be to inform people who know about these, or discover them, 
may want to use them in the way I suggested. But if it doesn't satisfy the F in 
FAQ, then perhaps it should not be included. Tha balancing act between 
supplying too little information and too much is always tricky.

– Harald
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Macports stopped working after xcode 4.6 upgrade

2013-02-20 Thread Harald Hanche-Olsen 
[Richard R. Cahilig chr05210...@gmail.com (2013-02-19 22:39:32 UTC)]

 Sorry about the typo.
 
 export PATH=/opt/local/bin:/opt/local/sbin:$PATH

Another way to do that is to put this in a file in /etc/paths.d/:

/opt/local/bin
/opt/local/sbin

- Harald
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Macports stopped working after xcode 4.6 upgrade

2013-02-20 Thread Lawrence Velázquez 
On Feb 20, 2013, at 3:22 AM, Harald Hanche-Olsen han...@math.ntnu.no wrote:

 [Richard R. Cahilig chr05210...@gmail.com (2013-02-19 22:39:32 UTC)]
 
 Sorry about the typo.
 
 export PATH=/opt/local/bin:/opt/local/sbin:$PATH
 
 Another way to do that is to put this in a file in /etc/paths.d/:
 
 /opt/local/bin
 /opt/local/sbin

These are not equivalent. Directory entries added via /etc/paths.d are tacked 
onto the *end* of the default PATH, while the quoted export statement adds 
them to the *beginning*. The latter is necessary if you want your shell to find 
MacPorts executables before system ones.

vq
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Macports stopped working after xcode 4.6 upgrade

2013-02-20 Thread Harald Hanche-Olsen 
[Lawrence Velázquez lar...@macports.org (2013-02-20 08:47:13 UTC)]

 On Feb 20, 2013, at 3:22 AM, Harald Hanche-Olsen han...@math.ntnu.no wrote:
 
  [Richard R. Cahilig chr05210...@gmail.com (2013-02-19 22:39:32 UTC)]
  
  export PATH=/opt/local/bin:/opt/local/sbin:$PATH
  
  Another way to do that is to put this in a file in /etc/paths.d/:
  
  /opt/local/bin
  /opt/local/sbin
 
 These are not equivalent. Directory entries added via /etc/paths.d are tacked 
 onto the *end* of the default PATH, while the quoted export statement adds 
 them to the *beginning*. The latter is necessary if you want your shell to 
 find MacPorts executables before system ones.

True. If that is what you want, you can tack the directories onto the front of 
/etc/paths instead. Not sure if either will survive a system upgrade, though. 
But on the other hand, it will work for all users on the machine.

- Harald
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Macports stopped working after xcode 4.6 upgrade

2013-02-20 Thread Lawrence Velázquez 
On Feb 20, 2013, at 4:09 AM, Harald Hanche-Olsen han...@math.ntnu.no wrote:

 True. If that is what you want, you can tack the directories onto the front 
 of /etc/paths instead. Not sure if either will survive a system upgrade, 
 though. But on the other hand, it will work for all users on the machine.

For the curious.

https://trac.macports.org/ticket/20524
https://trac.macports.org/ticket/24105
https://trac.macports.org/ticket/30458
https://trac.macports.org/ticket/36323

vq
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Macports stopped working after xcode 4.6 upgrade

2013-02-20 Thread Harald Hanche-Olsen 
[Lawrence Velázquez lar...@macports.org (2013-02-20 09:16:27 UTC)]

 On Feb 20, 2013, at 4:09 AM, Harald Hanche-Olsen han...@math.ntnu.no wrote:
 
  True. If that is what you want, you can tack the directories onto the front 
  of /etc/paths instead. Not sure if either will survive a system upgrade, 
  though. But on the other hand, it will work for all users on the machine.
 
 For the curious. […]

Argh. So that doesn't work either, then. path_helper starts with the current 
PATH, then append pathnames from /etc/paths and /etc/paths.d/* excepting, 
presumably, patnames that have already been included – so you can't prepend a 
pathname to PATH this way. Good to know. (Should this be in the FAQ?)

- Harald
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Macports stopped working after xcode 4.6 upgrade

2013-02-20 Thread Lawrence Velázquez 
On Feb 20, 2013, at 4:31 AM, Harald Hanche-Olsen han...@math.ntnu.no wrote:

 Argh. So that doesn't work either, then. path_helper starts with the current 
 PATH, then append pathnames from /etc/paths and /etc/paths.d/* excepting, 
 presumably, patnames that have already been included – so you can't prepend a 
 pathname to PATH this way. Good to know.

For all situations other than fresh login shells, path_helper is all sorts of 
irritating. For instance, say path_helper initially sets up this PATH.

PATH=foo:bar:baz

Hurrah. Then you prepend an entry yourself, in your .profile or whatever.

PATH=quux:foo:bar:baz

If you run path_helper again (e.g., you start an interactive non-login bash 
shell on OS X), it won't be satisfied that the 3 directories it wants to add 
are already there. Oh no, it has to make sure they're first in line.

PATH=foo:bar:baz:quux

Very annoying. I've actually filed a Radar about this.

http://openradar.appspot.com/radar?id=2620402

 (Should this be in the FAQ?)

Considering that we don't recommend using /etc/paths or /etc/paths.d anywhere, 
I'm not sure it needs to be.

vq
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Macports stopped working after xcode 4.6 upgrade

2013-02-19 Thread Richard R. Cahilig 
Hi,

The port command stopped working after I upraded my xcode and xcode command 
line tools to 4.6. I got the below error whenever I ran the port command.

 sh: port: command not found

Any ideas to fix it? I'm using OSX Mountain Lion and I don't know the version 
of Macports but I downloaded it in December last year. Any help would be 
greatly appreciated. Thanks.


Best Regards,

Richard R. Cahilig
chr05210...@gmail.com



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

Re: Macports stopped working after xcode 4.6 upgrade

2013-02-19 Thread Jeremy Lavergne 
 sh: port: command not found
 
 Any ideas to fix it? I'm using OSX Mountain Lion and I don't know the version 
 of Macports but I downloaded it in December last year. Any help would be 
 greatly appreciated. Thanks.

The error means `port` is no longer in your $PATH. You should be able to run 
`/opt/local/bin/port` in the meantime.

Here's how to fix $PATH (from macports.org/install.php):

You will need to manually adapt your shell's environment to work with MacPorts 
and your chosen installation prefix (the value passed to configure's --prefix 
flag, defaulting to /opt/local):

• Add ${prefix}/bin and ${prefix}/sbin to the start of your PATH 
environment variable so that MacPorts-installed programs take precedence over 
system-provided programs of the same name.
• If a standard MANPATH environment variable already exists (that is, 
one that doesn't contain any empty components), add the ${prefix}/share/man 
path to it so that MacPorts-installed man pages are found by your shell.
• For Tiger and earlier only, add an appropriate X11 DISPLAY 
environment variable to run X11-dependent programs, as Leopard takes care of 
this requirement on its own.



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

Re: Macports stopped working after xcode 4.6 upgrade

2013-02-19 Thread Richard R. Cahilig 
Hi Jeremy,

Thanks for your quick reply. Its working now. I didn't realized that.
I just added the below in my ~/.bash_profile

export PATH=/opt/local/bin:opt/local/sbin:$PATH  

Thanks.


Best Regards,

Richard R. Cahilig
chr05210...@gmail.com



On Feb 19, 2013, at 10:40 PM, Jeremy Lavergne jer...@lavergne.gotdns.org 
wrote:

 sh: port: command not found
 
 Any ideas to fix it? I'm using OSX Mountain Lion and I don't know the 
 version of Macports but I downloaded it in December last year. Any help 
 would be greatly appreciated. Thanks.
 
 The error means `port` is no longer in your $PATH. You should be able to run 
 `/opt/local/bin/port` in the meantime.
 
 Here's how to fix $PATH (from macports.org/install.php):
 
 You will need to manually adapt your shell's environment to work with 
 MacPorts and your chosen installation prefix (the value passed to configure's 
 --prefix flag, defaulting to /opt/local):
 
   • Add ${prefix}/bin and ${prefix}/sbin to the start of your PATH 
 environment variable so that MacPorts-installed programs take precedence over 
 system-provided programs of the same name.
   • If a standard MANPATH environment variable already exists (that is, 
 one that doesn't contain any empty components), add the ${prefix}/share/man 
 path to it so that MacPorts-installed man pages are found by your shell.
   • For Tiger and earlier only, add an appropriate X11 DISPLAY 
 environment variable to run X11-dependent programs, as Leopard takes care of 
 this requirement on its own.
 
 
 

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

Re: Macports stopped working after xcode 4.6 upgrade

2013-02-19 Thread Richard R. Cahilig 
Sorry about the typo.

export PATH=/opt/local/bin:/opt/local/sbin:$PATH


Best Regards,

Richard R. Cahilig
chr05210...@gmail.com



On Feb 19, 2013, at 11:32 PM, Richard R. Cahilig chr05210...@gmail.com wrote:

 Hi Jeremy,
 
 Thanks for your quick reply. Its working now. I didn't realized that.
 I just added the below in my ~/.bash_profile
 
 export PATH=/opt/local/bin:opt/local/sbin:$PATH  
 
 Thanks.
 
 
 Best Regards,
 
 Richard R. Cahilig
 chr05210...@gmail.com
 
 
 
 On Feb 19, 2013, at 10:40 PM, Jeremy Lavergne jer...@lavergne.gotdns.org 
 wrote:
 
 sh: port: command not found
 
 Any ideas to fix it? I'm using OSX Mountain Lion and I don't know the 
 version of Macports but I downloaded it in December last year. Any help 
 would be greatly appreciated. Thanks.
 
 The error means `port` is no longer in your $PATH. You should be able to run 
 `/opt/local/bin/port` in the meantime.
 
 Here's how to fix $PATH (from macports.org/install.php):
 
 You will need to manually adapt your shell's environment to work with 
 MacPorts and your chosen installation prefix (the value passed to 
 configure's --prefix flag, defaulting to /opt/local):
 
  • Add ${prefix}/bin and ${prefix}/sbin to the start of your PATH 
 environment variable so that MacPorts-installed programs take precedence 
 over system-provided programs of the same name.
  • If a standard MANPATH environment variable already exists (that is, 
 one that doesn't contain any empty components), add the ${prefix}/share/man 
 path to it so that MacPorts-installed man pages are found by your shell.
  • For Tiger and earlier only, add an appropriate X11 DISPLAY 
 environment variable to run X11-dependent programs, as Leopard takes care of 
 this requirement on its own.
 
 
 
 

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