Any spare mac hardware (for MacPorts meeting) lying around?

2018-02-19 Thread Mojca Miklavec 
Hi,

>From 10th to 14th March we'll be meeting at the 2nd MacPorts Meeting
in Slovenia.

https://trac.macports.org/wiki/Meetings/MacPortsMeeting2018

During the last meeting we borrowed two older Mac Pros (box format,
pretty old, but with quite some cores and speed) which we used for
heavily testing the buildbot setup that we were playing with.

In case any user has some spare old hardware that could be borrowed
for the duration of the meeting, either physically (ideally without
shipping/transport costs exceeding the price of hardware :) or by
providing remote login with sudo rights, please let us know.

(Donations to help cover the meeting cost, i.e. reduce the fee are of
course also welcome :)

Thank you,
Mojca

Re: Fail to install git from macports ("can't find file to patch" error)

2018-02-19 Thread Ryan Schmidt 

On Feb 19, 2018, at 13:37, Qianqian Fang wrote:

> I don't know what was changed recently, the built-in git command from Xcode 
> stopped working with the following error
> 
> fangq@jinwy:~/space/git/Project/autobuild/mcx$ git pull
> dyld: lazy symbol binding failed: Symbol not found: _iconv_open
>   Referenced from: 
> /Library/Developer/CommandLineTools/usr/libexec/git-core/git
>   Expected in: /opt/local/lib/libiconv.2.dylib
> 
> dyld: Symbol not found: _iconv_open
>   Referenced from: 
> /Library/Developer/CommandLineTools/usr/libexec/git-core/git
>   Expected in: /opt/local/lib/libiconv.2.dylib
> 
> error: fetch died of signal 6

Nothing of Apple's (such as 
/Library/Developer/CommandLineTools/usr/libexec/git-core/git) should be 
referencing anything of MacPorts's (such as /opt/local/lib/libiconv.2.dylib). 
The only reason that might happen is if you set DYLD_LIBRARY_PATH. So don't set 
that.

> I can only fix this if I put /usr/lib in the front of DYLD_LIBRARY_PATH, but 
> this breaks tons of other command.

You should not need to set DYLD_LIBRARY_PATH at all. Why do you think you need 
to?


> So, I decided to install a git from macports, however, this attempt failed 
> with the following error:
> 
> fangq@jinwy:~/space/git/Project/autobuild/mcx$ sudo port install git
> Warning: xcodebuild exists but failed to execute
> Warning: Xcode does not appear to be installed; most ports will likely fail 
> to build.
> --->  Computing dependencies for git
> --->  Applying patches to git
> Error: Failed to patch git: command execution failed
> Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_git/git/main.log
>  for details.
> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
> Error: Processing of port git failed
> look at the main.log file, I found the error message attached at the end.
> 
> My macport version is 2.4.2, OS is Sierra, already ran port selfupdate. 
> I have an old version of xcode (7.3) in order to compile cuda code, but I 
> don't think it was the issue.

I agree that an old Xcode would not cause a patch failure, but note that macOS 
Sierra requires Xcode 8 or 9.


> can someone let me know how to fix this? alternative approaches, such as 
> portable git binaries are also welcome, thanks a lot!
> Qianqian
> 
> 
> :debug:main Executing org.macports.main (git)
> :debug:main dropping privileges: euid changed to 502, egid changed to 505.
> :debug:main Skipping completed org.macports.archivefetch (git)
> :debug:main Privilege de-escalation not attempted as not running as root.
> :debug:main Skipping completed org.macports.fetch (git)
> :debug:main Privilege de-escalation not attempted as not running as root.
> :debug:main Skipping completed org.macports.checksum (git)
> :debug:main Privilege de-escalation not attempted as not running as root.
> :debug:main Skipping completed org.macports.extract (git)
> :debug:main Privilege de-escalation not attempted as not running as root.

The "Skipping" lines show us that this was not a clean attempt so no 
conclusions can be reached from it. "sudo port clean git" and try again.

Fail to install git from macports ("can't find file to patch" error)

2018-02-19 Thread Qianqian Fang 

hi everyone,

I don't know what was changed recently, the built-in git command from 
Xcode stopped working with the following error


   *|fangq@jinwy:~/space/git/Project/autobuild/mcx$ git pull|*|
   ||dyld: lazy symbol binding failed: Symbol not found: _iconv_open||
   ||  Referenced from:
   /Library/Developer/CommandLineTools/usr/libexec/git-core/git||
   ||  Expected in: /opt/local/lib/libiconv.2.dylib||
   ||
   ||dyld: Symbol not found: _iconv_open||
   ||  Referenced from:
   /Library/Developer/CommandLineTools/usr/libexec/git-core/git||
   ||  Expected in: /opt/local/lib/libiconv.2.dylib||
   ||
   ||error: fetch died of signal 6|

I can only fix this if I put /usr/lib in the front of DYLD_LIBRARY_PATH, 
but this breaks tons of other command. So, I decided to install a git 
from macports, however, this attempt failed with the following error:


   *|fangq@jinwy:~/space/git/Project/autobuild/mcx$ sudo port install
   git|*|
   ||Warning: xcodebuild exists but failed to execute||
   ||Warning: Xcode does not appear to be installed; most ports will
   likely fail to build.||
   ||--->  Computing dependencies for git||
   ||--->  Applying patches to git||
   ||Error: Failed to patch git: command execution failed||
   ||Error: See
   
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_git/git/main.log
   for details.||
   ||Error: Follow https://guide.macports.org/#project.tickets to
   report a bug.||
   ||Error: Processing of port git failed|

look at the main.log file, I found the error message attached at the end.

My macport version is 2.4.2, OS is Sierra, already ran port selfupdate.

I have an old version of xcode (7.3) in order to compile cuda code, but 
I don't think it was the issue.


can someone let me know how to fix this? alternative approaches, such as 
portable git binaries are also welcome, thanks a lot!


Qianqian



|:debug:main Executing org.macports.main (git)|||
|||:debug:main dropping privileges: euid changed to 502, egid changed to 
505.|||

|||:debug:main Skipping completed org.macports.archivefetch (git)|||
|||:debug:main Privilege de-escalation not attempted as not running as 
root.|||

|||:debug:main Skipping completed org.macports.fetch (git)|||
|||:debug:main Privilege de-escalation not attempted as not running as 
root.|||

|||:debug:main Skipping completed org.macports.checksum (git)|||
|||:debug:main Privilege de-escalation not attempted as not running as 
root.|||

|||:debug:main Skipping completed org.macports.extract (git)|||
|||:debug:main Privilege de-escalation not attempted as not running as 
root.|||

|||:debug:patch patch phase started at Mon Feb 19 14:27:42 EST 2018|||
|||:debug:patch Executing org.macports.patch (git)|||
|||:notice:patch --->  Applying patches to git|||
|||:info:patch --->  Applying patch-Makefile.diff|||
|||:debug:patch Environment: |||
|||:debug:patch CC_PRINT_OPTIONS='YES'|||
|||:debug:patch 
CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_git/git/work/.CC_PRINT_OPTIONS'|||

|||:debug:patch CPATH='/opt/local/include'|||
|||:debug:patch LIBRARY_PATH='/opt/local/lib'|||
|||:debug:patch MACOSX_DEPLOYMENT_TARGET='10.12'|||
|||:info:patch Executing:  cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_git/git/work/git-2.16.2" 
&& /usr/bin/patch -p1 < 
'/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/git/files/patch-Makefile.diff'|||
|||:debug:patch system:  cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_git/git/work/git-2.16.2" 
&& /usr/bin/patch -p1 < 
'/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/git/files/patch-Makefile.diff'|||

|||:info:patch can't find file to patch at input line 3|||
|||:info:patch Perhaps you used the wrong -p or --strip option?|||
|||:info:patch The text leading up to this was:|||
|||:info:patch --|||
|||:info:patch |--- a/Makefile.orig|||
|||:info:patch |+++ b/Makefile|||
|||:info:patch --|||
|||:info:patch File to patch: |||
|||:info:patch Skip this patch? [y] |||
|||:info:patch Skipping patch.|||
|||:info:patch 2 out of 2 hunks ignored|||
|||:info:patch Command failed:  cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_git/git/work/git-2.16.2" 
&& /usr/bin/patch -p1 < 
'/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/git/files/patch-Makefile.diff'|||

|||:info:patch Exit code: 1|||
|||:error:patch Failed to patch git: command execution failed|||
|||:debug:patch Error code: CHILDSTATUS 81845 1|||
|||:debug:patch Backtrace: command execution failed|||
|||:debug:patch while executing|||
|||:debug:patch "system {*}$notty {*}$nice

Re: Problem opening x-window over an ssh connection

2018-02-19 Thread Gustavo Seabra 
Well,

Just in case anyone runs into the same problem in the future, mine was solved 
by adding the line:

127.0.0.1   localhost.localdomain

to /etc/hosts.

Thanks,
—
Gustavo Seabra.



> Em 16 de fev de 2018, à(s) 16:15, Ken Cunningham 
>  escreveu:
> 
> This happens recurrently to me, usually after significant updates. 
> 
> The last time was some months ago, so I forget exactly what I did, but it 
> involved the location of xauth and the ssh config on the target machine, if I 
> recall correctly.
> 
> So that's where I would start to google, (and will, the next time I have this 
> issue).
> 
> I hope this helps.
> 
> Ken
> 
> 
> On 2018-02-16, at 10:33 AM, Gustavo Seabra wrote:
> 
>> Hi all,
>> 
>> I understand this may not be a real Macports problem, but I suspect someone 
>> here may know the solution. I have googled a bit about this, but the 
>> solutions I found do not really apply to that problem. Here it is:
>> 
>> I have 3 machines:
>> 
>> A: My Mac
>> B: A Unix machine that serves as firewall to other computers
>> C: The computer I want to access.
>> 
>> SO, If I do:
>> 
>> A]$ ssh -Y B
>> B]$ echo $DISPLAY
>> localhost:10.0
>> B]$ xmgrace
>> 
>> I get a nice window from xmgrace, as expected.
>> 
>> However, If I try to open xmgrace from C using B as a jump, I get:
>> 
>> A]$ ssh -Y B
>> B]$ echo $DISPLAY
>> localhost:10.0
>> B]$ ssh -Y C
>> C]$ echo $DISPLAY
>> localhost:10.0
>> C]$ xmgrace
>> Can't open display
>> Failed initializing GUI, exiting
>> C]$
>> 
>> I suspect there’s something ill-configured in C, but don’t know what could 
>> it be or where to look. Could someone there please help me here?
>> 
>> Thanks,
>> —
>> Gustavo Seabra.
>> 
>> 
>> 
>