Terminal problems after ports update

classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Terminal problems after ports update

Dave Horsfall
Every Monday I update Macports, but this time I'm starting to see some
weird problems.  Firefox (the latest) was misbehaving in a way that took a
reboot to fix; can't be more explicit than that but I do recall that it
wouldn't restart properly, and when I killed it it wouldn't start from the
task bar.

Then I find that Gnuplot isn't quite working; whenever I use "^P" to
scroll back through the command history a newline is not taken, but a
shell escape shows the TTY modes are correct; however, things like "reset"
give the message "can't initialize terminal type xterm-256color (error
-1)" even though Gnuplot reports it as "aqua".

However, things like VI work OK, so it doesn't look like a TTY mode bug.

Anyone else having these problems following a recent update?

MacBook runs 10.12.4, Firefox is 53.0.2 (64-bit), Gnuplot is 5.0.6.

--
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Now fixed: Re: Terminal problems after ports update

Dave Horsfall
Well well...  After this morning's "port upgrade outdated" ritual, I see
that the ncurses library was updated.  Suspicious, I tried "rogue" (which
I recalled was failing as well, in hindsight) and it worked, and so did
Gnuplot!  Therefor it was a bug in the ncurses library introduced after
some other modification.

I was baffled because VI was working (which doesn't use curses), so I
guess Gnuplot uses it indirectly via "readline" or something.

Perhaps "rogue" should be included as part of the ncurses test suite :-)  
It was written for it, after all, and believe me it gets hammered.

--
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Now fixed: Re: Terminal problems after ports update

William H. Magill-3

> On May 14, 2017, at 5:57 PM, Dave Horsfall <[hidden email]> wrote:
>
> Well well...  After this morning's "port upgrade outdated" ritual, I see
> that the ncurses library was updated.  Suspicious, I tried "rogue" (which
> I recalled was failing as well, in hindsight) and it worked, and so did
> Gnuplot!  Therefor it was a bug in the ncurses library introduced after
> some other modification.
>
> I was baffled because VI was working (which doesn't use curses), so I
> guess Gnuplot uses it indirectly via "readline" or something.
>
> Perhaps "rogue" should be included as part of the ncurses test suite :-)  
> It was written for it, after all, and believe me it gets hammered.
>
> --
> Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."


Oh dear!!! I haven’t thought about Rogue for man years.

However, it appears that the install of Rogue still fails.
I just ran:

> sudo port selfupdate
--->  Updating MacPorts base sources using rsync
MacPorts base version 2.4.1 installed,
MacPorts base version 2.4.1 downloaded.
--->  Updating the ports tree
--->  MacPorts base is already the latest version

The ports tree has been updated. To upgrade your installed ports, you should run
  port upgrade outdated
You haven't run 'sudo port reclaim' in two weeks. It's recommended you run this regularly to reclaim disk space. Would you like to run it now? [Y/n]: Y
--->  Checking for inactive ports
Found no inactive ports.
--->  Building list of distfiles still in use
--->  Searching for unused distfiles                    
No unused files found.
[/Users/magill] magill
 > sudo port upgrade outdated
--->  Fetching archive for ncurses
 . . .
All updated as expected, so I decided to try to install Rogue for the first time.

> sudo port install rogue
--->  Computing dependencies for rogue
--->  Fetching archive for rogue
--->  Attempting to fetch rogue-5.4.4_3.darwin_16.x86_64.tbz2 from https://packages.macports.org/rogue
--->  Attempting to fetch rogue-5.4.4_3.darwin_16.x86_64.tbz2 from http://lil.fr.packages.macports.org/rogue
--->  Attempting to fetch rogue-5.4.4_3.darwin_16.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/rogue
--->  Fetching distfiles for rogue
--->  Attempting to fetch rogue5.4.4-src.tar.gz from https://distfiles.macports.org/rogue
--->  Verifying checksums for rogue
--->  Extracting rogue
--->  Configuring rogue
--->  Building rogue
Error: Failed to build rogue: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_rogue/rogue/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port rogue failed
———————

:info:build mdport.c:264:17: error: incomplete definition of type 'struct term'
:info:build     if (cur_term->type.Strings == NULL)
:info:build         ~~~~~~~~^
:info:build /opt/local/include/term.h:710:16: note: forward declaration of 'struct term'
:info:build typedef struct term TERMINAL;
————————

Sierra 10.12.4
Xcode 8.3.2
Ticket #54171
==============
Will have to play around to attach the log file — the Trac oprtion does NOT see /opt



T.T.F.N.
William H. Magill

# iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.12
# Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.12

[hidden email]
[hidden email]
[hidden email]










Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Trac does not see /opt for attaching files

William H. Magill-3
I know that Apple has changed things, so I don’t know if this is a bug or a WAI (works as intended).

When you file a Trac ticket and attempt to attach a log file — the “choose” option does NOT show /opt.

Obviously, easily worked around by copying the /opt file to a user directory.

If this is WAI, there should probably be some sort of reference to this fact in the Ticket guide.


T.T.F.N.
William H. Magill

# iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.12
# Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.12

[hidden email]
[hidden email]
[hidden email]










Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Trac does not see /opt for attaching files

Ryan Schmidt-24
Works as intended. The Finder and the file choosing dialogs do not show hidden directories, and we do indeed mark /opt as hidden.

In the Finder, you can press Command-Shift-G, then type /opt to get there. You can do that in file choosing dialogs too, or just start typing /opt.

If we don't mention this in the guide where we talk about attaching files to tickets, that would indeed be a good idea.

> On May 14, 2017, at 18:52, William H. Magill <[hidden email]> wrote:
>
> I know that Apple has changed things, so I don’t know if this is a bug or a WAI (works as intended).
>
> When you file a Trac ticket and attempt to attach a log file — the “choose” option does NOT show /opt.
>
> Obviously, easily worked around by copying the /opt file to a user directory.
>
> If this is WAI, there should probably be some sort of reference to this fact in the Ticket guide.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Now fixed: Re: Terminal problems after ports update

Dave Horsfall
In reply to this post by William H. Magill-3
On Sun, 14 May 2017, William H. Magill wrote:

> :info:build mdport.c:264:17: error: incomplete definition of type 'struct term'
> :info:build     if (cur_term->type.Strings == NULL)
> :info:build         ~~~~~~~~^
> :info:build /opt/local/include/term.h:710:16: note: forward declaration of 'struct term'
> :info:build typedef struct term TERMINAL;
> ————————
>
> Sierra 10.12.4
> Xcode 8.3.2
> Ticket #54171
> ==============
> Will have to play around to attach the log file — the Trac oprtion does NOT see /opt
Hmmm...  Then it would've been broken some time after:

ozzie:~ dave$ ls -ltc /opt/local/bin/rogue
-rwxr-sr-x  1 root  games  158420 Oct 10  2016 /opt/local/bin/rogue

In the meantime, I'm trying to get Rog-O-Matic to compile (I did see it
win the Amulet of Yendor many years ago.)

--
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Trac does not see /opt for attaching files

Joshua Root-8
In reply to this post by William H. Magill-3
William H. Magill wrote:
> I know that Apple has changed things, so I don’t know if this is a bug or a WAI (works as intended).
>
> When you file a Trac ticket and attempt to attach a log file — the “choose” option does NOT show /opt.
>
> Obviously, easily worked around by copying the /opt file to a user directory.
>
> If this is WAI, there should probably be some sort of reference to this fact in the Ticket guide.

You can hit cmd-shift-. to show hidden files and folders in open/save
dialogs.

- Josh
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Trac does not see /opt for attaching files

Dave Horsfall
On Tue, 16 May 2017, Joshua Root wrote:

> You can hit cmd-shift-. to show hidden files and folders in open/save
> dialogs.

The question is of course why is /opt hidden in the first place?  This
smacks of the M$ "you don't need to know this" attitude.

--
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Trac does not see /opt for attaching files

Ryan Schmidt-24

> On May 15, 2017, at 12:03, Dave Horsfall <[hidden email]> wrote:
>
> On Tue, 16 May 2017, Joshua Root wrote:
>
>> You can hit cmd-shift-. to show hidden files and folders in open/save
>> dialogs.
>
> The question is of course why is /opt hidden in the first place?  This
> smacks of the M$ "you don't need to know this" attitude.

I thought we were hiding it, but it's not hidden on my systems and I can't find anywhere in the Makefile or postflight script where it's being hidden, so I must've imagined it.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Trac does not see /opt for attaching files

Lenore Horner-2

> On May 15, 2017, at 13:56, Ryan Schmidt <[hidden email]> wrote:
>
>
>> On May 15, 2017, at 12:03, Dave Horsfall <[hidden email]> wrote:
>>
>> On Tue, 16 May 2017, Joshua Root wrote:
>>
>>> You can hit cmd-shift-. to show hidden files and folders in open/save
>>> dialogs.
>>
>> The question is of course why is /opt hidden in the first place?  This
>> smacks of the M$ "you don't need to know this" attitude.
>
> I thought we were hiding it, but it's not hidden on my systems and I can't find anywhere in the Makefile or postflight script where it's being hidden, so I must've imagined it.
>
/opt (and other things like files beginning with . /Library) are hidden by the OS by default but it’s pretty easy to find instructions on how to turn the hiding off or make a script to toggle hiding.  My guess is Ryan turned the hiding off entirely on his system.  

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Trac does not see /opt for attaching files

Ryan Schmidt-24

> On May 15, 2017, at 14:53, Lenore Horner <[hidden email]> wrote:
>
>
>> On May 15, 2017, at 13:56, Ryan Schmidt <[hidden email]> wrote:
>>
>>
>>> On May 15, 2017, at 12:03, Dave Horsfall <[hidden email]> wrote:
>>>
>>> On Tue, 16 May 2017, Joshua Root wrote:
>>>
>>>> You can hit cmd-shift-. to show hidden files and folders in open/save
>>>> dialogs.
>>>
>>> The question is of course why is /opt hidden in the first place?  This
>>> smacks of the M$ "you don't need to know this" attitude.
>>
>> I thought we were hiding it, but it's not hidden on my systems and I can't find anywhere in the Makefile or postflight script where it's being hidden, so I must've imagined it.
>>
> /opt (and other things like files beginning with . /Library) are hidden by the OS by default but it’s pretty easy to find instructions on how to turn the hiding off or make a script to toggle hiding.  My guess is Ryan turned the hiding off entirely on his system.  
>

/opt is visible on all the systems I've checked, even those that are not configured to show invisible items.

The OS does not have any idea what /opt is or that it should be hidden, unless someone told it to be that way. Apple for example told /Library to be that way as of Lion. I thought we made /opt hidden, but I can't find any evidence of that now.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Trac does not see /opt for attaching files

Lenore Horner-2

On May 15, 2017, at 18:48, Ryan Schmidt <[hidden email]> wrote:


On May 15, 2017, at 14:53, Lenore Horner <[hidden email]> wrote:


On May 15, 2017, at 13:56, Ryan Schmidt <[hidden email]> wrote:


On May 15, 2017, at 12:03, Dave Horsfall <[hidden email]> wrote:

On Tue, 16 May 2017, Joshua Root wrote:

You can hit cmd-shift-. to show hidden files and folders in open/save
dialogs.

The question is of course why is /opt hidden in the first place?  This
smacks of the M$ "you don't need to know this" attitude.

I thought we were hiding it, but it's not hidden on my systems and I can't find anywhere in the Makefile or postflight script where it's being hidden, so I must've imagined it.

/opt (and other things like files beginning with . /Library) are hidden by the OS by default but it’s pretty easy to find instructions on how to turn the hiding off or make a script to toggle hiding.  My guess is Ryan turned the hiding off entirely on his system.  


/opt is visible on all the systems I've checked, even those that are not configured to show invisible items.

The OS does not have any idea what /opt is or that it should be hidden, unless someone told it to be that way. Apple for example told /Library to be that way as of Lion. I thought we made /opt hidden, but I can't find any evidence of that now.

/opt is not visible on my system (I usually us cmd-shift-G) even though files I have set the hidden flag for are currently showing in my save dialog box (but not things starting with .). The only directories visible at that level are /Applications /Library /System /Users.  However, ~/Library is hidden. 

Info at https://developer.apple.com/library/content/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/FileSystemOverview/FileSystemOverview.html sounds to me like MacOS may hide /opt by default even if doesn’t start with a /opt directory.  It’s not really clear.



Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Trac does not see /opt for attaching files

William H. Magill-3

> On May 15, 2017, at 7:57 PM, Lenore Horner <[hidden email]> wrote:
>
>
>> On May 15, 2017, at 18:48, Ryan Schmidt <[hidden email]> wrote:
>>
>>
>>> On May 15, 2017, at 14:53, Lenore Horner <[hidden email]> wrote:
>>>
>>>
>>>> On May 15, 2017, at 13:56, Ryan Schmidt <[hidden email]> wrote:
>>>>
>>>>
>>>>> On May 15, 2017, at 12:03, Dave Horsfall <[hidden email]> wrote:
>>>>>
>>>>> On Tue, 16 May 2017, Joshua Root wrote:
>>>>>
>>>>>> You can hit cmd-shift-. to show hidden files and folders in open/save
>>>>>> dialogs.
>>>>>
>>>>> The question is of course why is /opt hidden in the first place?  This
>>>>> smacks of the M$ "you don't need to know this" attitude.
>>>>
>>>> I thought we were hiding it, but it's not hidden on my systems and I can't find anywhere in the Makefile or postflight script where it's being hidden, so I must've imagined it.
>>>>
>>> /opt (and other things like files beginning with . /Library) are hidden by the OS by default but it’s pretty easy to find instructions on how to turn the hiding off or make a script to toggle hiding.  My guess is Ryan turned the hiding off entirely on his system.  
>>>
>>
>> /opt is visible on all the systems I've checked, even those that are not configured to show invisible items.
>>
>> The OS does not have any idea what /opt is or that it should be hidden, unless someone told it to be that way. Apple for example told /Library to be that way as of Lion. I thought we made /opt hidden, but I can't find any evidence of that now.
>>
> /opt is not visible on my system (I usually us cmd-shift-G) even though files I have set the hidden flag for are currently showing in my save dialog box (but not things starting with .). The only directories visible at that level are /Applications /Library /System /Users.  However, ~/Library is hidden.
>
> Info at https://developer.apple.com/library/content/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/FileSystemOverview/FileSystemOverview.html sounds to me like MacOS may hide /opt by default even if doesn’t start with a /opt directory.  It’s not really clear.
>

I believe that /opt and certain other root directories are normally hidden unless you “show hidden files”  (also “dot” files).

This command is apparently still correct:  defaults write com.apple.finder AppleShowAllFiles TRUE;killall Finder

                defaults read com.apple.finder AppleShowAllFiles

On my iMac the Finder displays all hidden files.  
However, that does NOT have any effect on the selection display from within Safari (i.e. in Trac when trying to append a file to a ticket.)


T.T.F.N.
William H. Magill
# iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.12
# Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.12

[hidden email]
[hidden email]
[hidden email]








Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Trac does not see /opt for attaching files

Al Varnell
In reply to this post by Ryan Schmidt-24
/opt has been installed as a hidden directory by every macOS/OS X installer from day 1.

Sent from my iPhone

-Al-
--
Al Varnell
Mountain View, CA

On May 15, 2017, at 3:48 PM, Ryan Schmidt wrote:
> The OS does not have any idea what /opt is or that it should be hidden, unless someone told it to be that way.

smime.p7s (3K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Trac does not see /opt for attaching files

Ryan Schmidt-24

On May 15, 2017, at 20:18, Al Varnell wrote:

> /opt has been installed as a hidden directory by every macOS/OS X installer from day 1.

I guess /opt is a standard UNIX directory, and macOS does install other UNIX directories like /private and /usr as hidden, so it makes sense.

Nevertheless, it's not hidden on my machines. I've installed MacPorts from source on most if not all of my machines, so if the hiding is happening in the Installer, that would explain why I don't see it on systems where I didn't use Installer. Maybe we should modify our Makefiles to install /opt as hidden, to match the behavior of Installer.


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Trac does not see /opt for attaching files

Dave Horsfall
On Mon, 15 May 2017, Ryan Schmidt wrote:

> I guess /opt is a standard UNIX directory, and macOS does install other
> UNIX directories like /private and /usr as hidden, so it makes sense.

A semi-standard; it was first used on Solaris as I recall to install
non-base-but-supported software (such as the Sun C compiler), and truly
local stuff went into /usr/local.

FreeBSD (and probably others) don't use /opt, but /usr/local.

Penguin/OS seems to ram everything into /usr/bin...

--
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
Loading...