Re: hypermail port problem - SOLVED!!!

[Brandon Allbery]

On Fri, Jan 23, 2015 at 4:09 PM, jerome schatten  wrote:

> The ticket on this can be removed with my apologies. MacPorts works best
> when you know what your doing


No, I'd argue this is still a bug; if it needs support files, then (a)
those should be installed and (b) it should know where to look for them.
Silently hanging because it can't find its support files, particularly if
it's not looking where they were installed, is a bug no matter how you
slice it.

-- 
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: hypermail port problem - SOLVED!!!

[jerome schatten]

Porters... I report SUCCESS (with a lot of help from y'all)

As soon as I moved the new hypermail binary to the src directory of the 
hypermail tree and executed as I used to do on the Linux system, it 
worked -- no problems at all.  I brought the entire hypermail tree over 
to the mac from the linux machine, with all the config and mail files, 
and it played beautifully.  It was Brian's comments about hypermail not 
having anything to chew on which triggered the idea of putting it back 
in the src directory of the hypermail tree.


I want to thank everyone who took the time to be patient with a 77 year 
old fool, who is trying to learn a few new tricks. I did learn to use 
MacPorts which was an adventure in itself.


The ticket on this can be removed with my apologies. MacPorts works best 
when you know what your doing .

Thanks again,
jerome

On 2015-01-23 11:14 AM, Brandon Allbery wrote:
On Fri, Jan 23, 2015 at 1:00 PM, jerome schatten > wrote:


I think it's somewhat different than 'waiting for a mailbox file'.
I'm very new to MacPorts, and had a bit of trouble figuring out
what I was doing. But it's starting to sink in.


Having dug up some docs, it does look like to work as a filter it 
needs the -i parameter so that's not it.


It occurs to me now that the binary that was generated needs to be
returned to its original environment surrounded by all the support
files that it needs to run.  I did not do that; I just executed
the binary, period, and so it sat -- what else could it do?


I would expect an error message in that case, not sitting there 
looking dumb.


Are you the same Brandon Allerby that did the original early work
on Jnos?


Mmm, I'd call that a slight misstatement (now, if you mean the Linux 
port thereof...), but yes. Been a few years though. >.>


--
brandon s allbery kf8nh sine nomine associates
allber...@gmail.com  
ballb...@sinenomine.net 

unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net


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

Re: hypermail port problem

[Lawrence Velázquez]

On Jan 23, 2015, at 3:28 AM, jerome schatten  wrote:

> I did, Ryan and I installed it again, It took about 10 minutes -- and it 
> returned Software Installed at the end of the process. But command line tools 
> as such does not seem to appear anywhere.  In the gui if you go to 
> Applications -> Xcode -> Preferences you will see command line tools at the 
> bottom That's the only reference to it that I can find. Maybe this is the 
> clue?
> I appreciate your help -- I'm not trying to be difficult!

As Ryan said, the absence of the CLT is probably not what's causing your 
difficulty.

For future reference, one telltale sign that the CLT are installed is the 
presence of /usr/include. One reason (I'm sure there are others) that some 
build systems need the CLT is that they insist on looking for headers in 
/usr/include and fail if that directory doesn't exist.

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

Re: hypermail port problem

[Brandon Allbery]

On Fri, Jan 23, 2015 at 1:00 PM, jerome schatten  wrote:

> I think it's somewhat different than 'waiting for a mailbox file'. I'm
> very new to MacPorts, and had a bit of trouble figuring out what I was
> doing. But it's starting to sink in.
>

Having dug up some docs, it does look like to work as a filter it needs the
-i parameter so that's not it.

It occurs to me now that the binary that was generated needs to be returned
> to its original environment surrounded by all the support files that it
> needs to run.  I did not do that; I just executed the binary, period, and
> so it sat -- what else could it do?
>

I would expect an error message in that case, not sitting there looking
dumb.


> Are you the same Brandon Allerby that did the original early work on Jnos?
>

Mmm, I'd call that a slight misstatement (now, if you mean the Linux port
thereof...), but yes. Been a few years though. >.>

-- 
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: hypermail port problem

[jerome schatten]

Thanks for your comments Brandon...

I think it's somewhat different than 'waiting for a mailbox file'. I'm 
very new to MacPorts, and had a bit of trouble figuring out what I was 
doing. But it's starting to sink in.


It occurs to me now that the binary that was generated needs to be 
returned to its original environment surrounded by all the support files 
that it needs to run.  I did not do that; I just executed the binary, 
period, and so it sat -- what else could it do?


So, I'll get back to this later today.

Are you the same Brandon Allerby that did the original early work on Jnos?
Best,
jerome ve7ass
Vancouver


On 2015-01-23 6:31 AM, Brandon Allbery wrote:
On Fri, Jan 23, 2015 at 1:31 AM, jerome schatten > wrote:


If it's not a problem, then at this point, I should be able to
launch the hypermail binary with a './hypermail' and it should
run. But it doesn't. The cursor simply moves to the next line and
it sits there. No error messages, nothing.


Looks to me like hypermail converts mbox to HTML? So it's waiting for 
an mbox... on stdin, like any good filter. stdin being your terminal.


--
brandon s allbery kf8nh sine nomine associates
allber...@gmail.com  
ballb...@sinenomine.net 

unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net


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

Re: hypermail port problem

[Brandon Allbery]

On Fri, Jan 23, 2015 at 1:31 AM, jerome schatten  wrote:

> If it's not a problem, then at this point, I should be able to launch the
> hypermail binary with a './hypermail' and it should run. But it doesn't.
> The cursor simply moves to the next line and it sits there. No error
> messages, nothing.


Looks to me like hypermail converts mbox to HTML? So it's waiting for an
mbox... on stdin, like any good filter. stdin being your terminal.

-- 
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: hypermail port problem

[Ryan Schmidt]

On Jan 23, 2015, at 2:28 AM, jerome schatten wrote:

> I did, Ryan and I installed it again, It took about 10 minutes -- and it 
> returned Software Installed at the end of the process. But command line tools 
> as such does not seem to appear anywhere. In the gui if you go to 
> Applications -> Xcode -> Preferences you will see command line tools at the 
> bottom That's the only reference to it that I can find. Maybe this is the 
> clue?
> I appreciate your help -- I'm not trying to be difficult!

Great, then it sounds like it's been successfully installed.


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

Re: hypermail port problem

[jerome schatten]

I did, Ryan and I installed it again, It took about 10 minutes -- and it 
returned Software Installed at the end of the process. But command line 
tools as such does not seem to appear anywhere.  In the gui if you go to 
Applications -> Xcode -> Preferences you will see command line tools at 
the bottom That's the only reference to it that I can find. Maybe this 
is the clue?

I appreciate your help -- I'm not trying to be difficult!
Jerome
On 2015-01-23 12:16 AM, Ryan Schmidt wrote:

On Jan 23, 2015, at 1:56 AM, jerome schatten wrote:


Looks to me that the command line tools were installed -- are not the compilers 
part of command line tools? Maybe they're not in the expected place in Yosemite?


Last login: Thu Jan 22 23:41:26 on ttys001
jeromes-Mac-mini:~ jeromeschatten$ gcc --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
--with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk/usr/include/c++/4.2.1
Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn)
Target: x86_64-apple-darwin14.0.0
Thread model: posix
jeromes-Mac-mini:~ jeromeschatten$

Yosemite includes shims (such as /usr/bin/gcc) that in turn call the 
corresponding program in the Xcode bundle, if present. However, if I remember 
correctly, there are still situations where the shims are insufficient and the 
real Xcode command line tools package is required. Please install the Xcode 
command line tools package to avoid certain problems in the future (although it 
will not help with the hypermail problem you're currently experiencing).






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

Re: hypermail port problem

[Ryan Schmidt]

On Jan 23, 2015, at 1:56 AM, jerome schatten wrote:

> Looks to me that the command line tools were installed -- are not the 
> compilers part of command line tools? Maybe they're not in the expected place 
> in Yosemite?
> 
> 
> Last login: Thu Jan 22 23:41:26 on ttys001
> jeromes-Mac-mini:~ jeromeschatten$ gcc --version
> Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
> --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk/usr/include/c++/4.2.1
> Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn)
> Target: x86_64-apple-darwin14.0.0
> Thread model: posix
> jeromes-Mac-mini:~ jeromeschatten$

Yosemite includes shims (such as /usr/bin/gcc) that in turn call the 
corresponding program in the Xcode bundle, if present. However, if I remember 
correctly, there are still situations where the shims are insufficient and the 
real Xcode command line tools package is required. Please install the Xcode 
command line tools package to avoid certain problems in the future (although it 
will not help with the hypermail problem you're currently experiencing).



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

Re: hypermail port problem

[jerome schatten]

Looks to me that the command line tools were installed -- are not the 
compilers part of command line tools? Maybe they're not in the expected 
place in Yosemite?



Last login: Thu Jan 22 23:41:26 on ttys001
jeromes-Mac-mini:~ jeromeschatten$ gcc --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
--with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk/usr/include/c++/4.2.1

Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn)
Target: x86_64-apple-darwin14.0.0
Thread model: posix
jeromes-Mac-mini:~ jeromeschatten$

j.

On 2015-01-22 11:23 PM, Ryan Schmidt wrote:

On Jan 23, 2015, at 12:31 AM, jerome schatten wrote:


*S*ystem: MacMini -- late 2014 - Yosemite 10.10.1; Xcode installed.

I've installed macports 2.3.3 with no problems; I've installed port hypermail 
with no 'apparent' problem. I've followed the MacPorts Guide every step of the 
way.

My first question is this: The install of the hypermail port gives:

jeromes-Mac-mini:bin jeromeschatten$ sudo port install hypermail

Warning: The Xcode Command Line Tools don't appear to be installed; most ports 
will likely fail to build.
Warning: Install them by running `xcode-select --install'.
--->  Fetching archive for hypermail
--->  Attempting to fetch hypermail-2.3.0_1.darwin_14.x86_64.tbz2 from 
http://packages.macports.org/hypermail
--->  Attempting to fetch hypermail-2.3.0_1.darwin_14.x86_64.tbz2.rmd160 from 
http://packages.macports.org/hypermail
--->  Installing hypermail @2.3.0_1
--->  Activating hypermail @2.3.0_1
--->  Cleaning hypermail
--->  Updating database of binaries
--->  Scanning binaries for linking errors
--->  No broken files found.


But Xcode IS installed and the tools work as I've used them elsewhere. Is this 
a or is this not a problem?

Yes, MacPorts requires the Xcode command line tools, and Xcode. These are two 
separate installations, as of OS X 10.7 Lion.



If it's not a problem, then at this point, I should be able to launch the 
hypermail binary with a './hypermail' and it should run. But it doesn't. The 
cursor simply moves to the next line and it sits there. No error messages, 
nothing.

I looked at the hypermail and xcode process with top and it reports:
PID   COMMAND  %CPU  TIME #TH  #WQ  #PORT MEMPURG CMPR PGRP
[...]
1435  hypermail   0.0   00:00.001015 604K   0B 0B   
1435

1404  Xcode0.0   00:02.2681249 66M72K   0B  
 1404

So, it doesn't look like hypermail is doing much and Xcode is indeed there.

Xcode does not need to be running to use MacPorts, it just needs to be 
installed, as do the separate Xcode command line tools.

You didn't get an error while installing hypermail, so I would not suspect 
absence of the Xcode command line tools to have been a problem in this 
particular case. But you should install them to prevent future problems with 
other ports.





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

Re: hypermail port problem

[Ryan Schmidt]

On Jan 23, 2015, at 12:31 AM, jerome schatten wrote:

> *S*ystem: MacMini -- late 2014 - Yosemite 10.10.1; Xcode installed.
> 
> I've installed macports 2.3.3 with no problems; I've installed port hypermail 
> with no 'apparent' problem. I've followed the MacPorts Guide every step of 
> the way.
> 
> My first question is this: The install of the hypermail port gives:
> 
> jeromes-Mac-mini:bin jeromeschatten$ sudo port install hypermail
> 
> Warning: The Xcode Command Line Tools don't appear to be installed; most 
> ports will likely fail to build.
> Warning: Install them by running `xcode-select --install'.
> --->  Fetching archive for hypermail
> --->  Attempting to fetch hypermail-2.3.0_1.darwin_14.x86_64.tbz2 from 
> http://packages.macports.org/hypermail
> --->  Attempting to fetch hypermail-2.3.0_1.darwin_14.x86_64.tbz2.rmd160 from 
> http://packages.macports.org/hypermail
> --->  Installing hypermail @2.3.0_1
> --->  Activating hypermail @2.3.0_1
> --->  Cleaning hypermail
> --->  Updating database of binaries
> --->  Scanning binaries for linking errors
> --->  No broken files found.
> 
> 
> But Xcode IS installed and the tools work as I've used them elsewhere. Is 
> this a or is this not a problem?

Yes, MacPorts requires the Xcode command line tools, and Xcode. These are two 
separate installations, as of OS X 10.7 Lion.


> If it's not a problem, then at this point, I should be able to launch the 
> hypermail binary with a './hypermail' and it should run. But it doesn't. The 
> cursor simply moves to the next line and it sits there. No error messages, 
> nothing.
> 
> I looked at the hypermail and xcode process with top and it reports:
> PID   COMMAND  %CPU  TIME #TH  #WQ  #PORT MEMPURG CMPR PGRP
> [...]
> 1435  hypermail   0.0   00:00.001015 604K   0B 0B 
>   1435
> 
> 1404  Xcode0.0   00:02.2681249 66M72K   
> 0B   1404
> 
> So, it doesn't look like hypermail is doing much and Xcode is indeed there.

Xcode does not need to be running to use MacPorts, it just needs to be 
installed, as do the separate Xcode command line tools.

You didn't get an error while installing hypermail, so I would not suspect 
absence of the Xcode command line tools to have been a problem in this 
particular case. But you should install them to prevent future problems with 
other ports.


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

Re: hypermail port problem

[Lawrence Velázquez]

On Jan 23, 2015, at 1:31 AM, jerome schatten  wrote:

> *S*ystem: MacMini -- late 2014 - Yosemite 10.10.1; Xcode installed.
> 
> I've installed macports 2.3.3 with no problems; I've installed port hypermail 
> with no 'apparent' problem. I've followed the MacPorts Guide every step of 
> the way.

For others' benefit, OP already opened a ticket about this:

https://trac.macports.org/ticket/46655

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