search

OSGeo / homebrew-osgeo4mac

Mac homebrew tap for maintaining a stable work environment for the OSGeo.org geospatial toolset
https://git.io/fhh3X
BSD 3-Clause "New" or "Revised" License
364 stars 112 forks source link

grace no longer working #1406

Closed JD-UIUC closed 3 years ago

JD-UIUC commented 3 years ago

Please answers the following

I've...

Describe the bug

After installing latest home-brew, some features of grace (xmgrace) are no longer working correctly

When grace is invoked from the command line, I now get the following messages, which were not present before: Warning: locale not supported by Xlib, locale set to C Warning: X locale modifiers not supported, using default This is not a major issue. The following is the issue:

A plot window opens, but when I select "Axis" from the "Plot" drop-down menu, it hangs. Other menu options work!

To Reproduce

  1. Invoke xmgrace
  2. In window, choose "Plot -> Axis properties"
  3. Hangs with the "watch" icon

Expected behavior

Should get a dialog box to set axis properties (title, ticks, etc)

Screenshots

Additional context

I am running MacOS Mojave 10.14.6 on a Mid-2010 12-core Mac Pro. I cannot upgrade to later OS because this machine is not supported.

I tried brew reinstall -s openmotif grace

During the grace compile, I get the following message: Warning: Calling ENV.O1 is deprecated! There is no replacement. Please report this issue to the homebrew/core tap (not Homebrew/brew or Homebrew/core): /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/grace.rb:36

brew doctor output: 

Warning: Some installed kegs have no formulae!
This means they were either deleted or installed with `brew diy`.
You should find replacements for the following formulae:
  ecj
  python@2

Warning: You have the following deprecated, cask taps tapped:
  caskroom/cask
Untap them with `brew untap`.

Logs

I can't do this. When I run brew gist-logs grace, I get an error that a newer version of command line tools exists. But it does exist for my installation of Mojave. I can't update to later OS because my machine is no longer supported. It's a Mid-2010 Mac Pro.

tanmoy1989 commented 3 years ago

Did you solve the problem? I am having the same problem.

JD-UIUC commented 3 years ago

Hello Tanmoy,

I didn’t know that anyone had even seen my post!

Not exactly solved it. I went back to the previous version of XQuartz (2.7.11) and an earlier version of homebrew (2.5.6-82-g6d8978e). I don’t know that it’s necessary to go back that far, but that’s what I had available on my backups. At least it works. Probably can’t update anything though.

I just got a new MacBook Air with the Apple M1 chip. Supposedly homebrew 3.0 works on that chipset, but I haven’t tried it yet. I have the same versions of XQuartz and homebrew installed there, ported from my old laptop. Grace works, but brew crashes. I think I’ll wait a while before trying to update.

Jon

On Mar 7, 2021, at 9:21 PM, Tanmoy Chakraborty notifications@github.com<mailto:notifications@github.com> wrote:

Did you solve the problem? I am having the same problem.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/OSGeo/homebrew-osgeo4mac/issues/1406*issuecomment-792471444__;Iw!!DZ3fjg!swDN9BmRhSaHSEv9RTpKd-KAfKge6SkxEbqvGeVDZgkOXwRGRws8GpOqqWurGds_uQ$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABWB5SUNS3CNEHE5GMK366LTCRNGNANCNFSM4VP6Z6KA__;!!DZ3fjg!swDN9BmRhSaHSEv9RTpKd-KAfKge6SkxEbqvGeVDZgkOXwRGRws8GpOqqWutWeV8vQ$.

tanmoy1989 commented 3 years ago

Hi Jon,

Thanks for your reply. This is really strange that just 'Axis Properties' does not work and it seems that no one (except us) has faced this problem. I am using Homebrew 3.0.4 and XQuartz (2.7.11). Anyway, please let me know if you find other solutions apart from downgrading homebrew.

Tanmoy

JD-UIUC commented 3 years ago

I agree that it’s strange. Which version of MacOS are you running? The machine where I have this problem is running 10.14.6. Haven’t explored the others yet that are running later versions.

Also, could you try replacing the whole tree for grace under /usr/local/Cellar from backups you made before upgrading homebrew? Who knows - might be worth a try.

On Mar 7, 2021, at 9:49 PM, Tanmoy Chakraborty notifications@github.com<mailto:notifications@github.com> wrote:

Hi Jon,

Thanks for your reply. This is really strange that just 'Axis Properties' does not work and it seems that no one (except us) has faced this problem. I am using Homebrew 3.0.4 and XQuartz (2.7.11). Anyway, please let me know if you find other solutions apart from downgrading homebrew.

Tanmoy

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/OSGeo/homebrew-osgeo4mac/issues/1406*issuecomment-792484102__;Iw!!DZ3fjg!uCLP6q1xP6QA7Yktq13-R0KTkVMdrkx7eGvM3gD2Lc_3SkJB-83J5_bH4YVp8v2Bgw$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABWB5SUB7ODF42UZXFAZDBTTCRQNBANCNFSM4VP6Z6KA__;!!DZ3fjg!uCLP6q1xP6QA7Yktq13-R0KTkVMdrkx7eGvM3gD2Lc_3SkJB-83J5_bH4YXRcf1aNQ$.

tanmoy1989 commented 3 years ago

Ok, strangely enough, I found a workaround! After I click on the 'Axis Properties', I just wait 40-50 seconds and miraculously the 'clock' sign goes away and xmgrace starts working normally. So, everytime I open xmgrace from the terminal, I just need to give that much time to clock sign goes away - it's strange again, and need a permanent solution but at least it works for me for now.

Coming back to your query, I am using macOS Big Sur version 11.2.2 in MacBook Pro (late 2013) machine.

Tanmoy

JD-UIUC commented 3 years ago

Strange!! Something is timing out somewhere I guess.

Patience is rewarded!

On Mar 8, 2021, at 11:44 AM, Tanmoy Chakraborty notifications@github.com<mailto:notifications@github.com> wrote:

Ok, strangely enough, I found a workaround! After I click on the 'Axis Properties', I just wait 40-50 seconds and miraculously the 'clock' sign goes away and xmgrace starts working normally. So, everytime I open xmgrace from the terminal, I just need to give that much time to clock sign goes away - it's strange again, and need a permanent solution but at least it works for me for now.

Coming back to your query, I am using macOS Big Sur version 11.2.2 in MacBook Pro (late 2013) machine.

Tanmoy

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/OSGeo/homebrew-osgeo4mac/issues/1406*issuecomment-793024105__;Iw!!DZ3fjg!oMAriHdz1nG_cuowRpi3vVx143I7NoB69VopWemYtzWXzVzC-13PJzAARCQWGdQUKw$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABWB5SSUPXWWSSLJEVSVDOLTCUSK5ANCNFSM4VP6Z6KA__;!!DZ3fjg!oMAriHdz1nG_cuowRpi3vVx143I7NoB69VopWemYtzWXzVzC-13PJzAARCQ69NnY1A$.

JD-UIUC commented 3 years ago

I installed homebrew 3.0.4 on my new (2020) MacBook Air, and installed grace. Similar result as you - click on the “Axis Properties” and after a delay, the menu pops up. It takes about 10 to appear seconds on this machine.

Thanks for finding a work-around!

On Mar 8, 2021, at 11:44 AM, Tanmoy Chakraborty notifications@github.com<mailto:notifications@github.com> wrote:

Ok, strangely enough, I found a workaround! After I click on the 'Axis Properties', I just wait 40-50 seconds and miraculously the 'clock' sign goes away and xmgrace starts working normally. So, everytime I open xmgrace from the terminal, I just need to give that much time to clock sign goes away - it's strange again, and need a permanent solution but at least it works for me for now.

Coming back to your query, I am using macOS Big Sur version 11.2.2 in MacBook Pro (late 2013) machine.

Tanmoy

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/OSGeo/homebrew-osgeo4mac/issues/1406*issuecomment-793024105__;Iw!!DZ3fjg!oMAriHdz1nG_cuowRpi3vVx143I7NoB69VopWemYtzWXzVzC-13PJzAARCQWGdQUKw$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABWB5SSUPXWWSSLJEVSVDOLTCUSK5ANCNFSM4VP6Z6KA__;!!DZ3fjg!oMAriHdz1nG_cuowRpi3vVx143I7NoB69VopWemYtzWXzVzC-13PJzAARCQ69NnY1A$.

tanmoy1989 commented 3 years ago

Glad to hear that it's working for you as well. However, I still hope someone reads our conversation and comes up with the 'real' solution. Otherwise, we just hope that the problem goes away with the future OS, homebrew.. upgraded versions.

piskuliche commented 3 years ago

Hi everyone -

Sorry to jump into an old thread, but I wanted to see if either of you have come up with a better fix for this since you last posted? I'm still having the issue where the axis properties window take a long time to pop up.

JD-UIUC commented 3 years ago

Nope. I’ve learned to get used to it.

Jon

Sent from my iPhone

On Apr 30, 2021, at 11:41 AM, Zeke A. Piskulich @.***> wrote:



Hi everyone -

Sorry to jump into an old thread, but I wanted to see if either of you have come up with a better fix for this since you last posted? I'm still having the issue where the axis properties window take a long time to pop up.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/OSGeo/homebrew-osgeo4mac/issues/1406*issuecomment-830288231__;Iw!!DZ3fjg!pk73UyQo2uUuYIquufzrm_CGNGn1y8wYPLwc96P3KT00XxLRKvcdv_NQCUFLWO5WRw$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABWB5SWKLG7SDIBMG27E2KTTLL2WXANCNFSM4VP6Z6KA__;!!DZ3fjg!pk73UyQo2uUuYIquufzrm_CGNGn1y8wYPLwc96P3KT00XxLRKvcdv_NQCUFhl5vzYg$.

Agnese-rosc commented 3 years ago

Hi everyone, sorry to bother you on this conversation but I've a similar issue. I'm using a MacBook Pro with Catalina (10.15.7) and I've problems running xmgrace. In particularly when I run xmgrace this error pop up:

Warning: locale not supported by Xlib, locale set to C Warning: X locale modifiers not supported, using default

and I'm not able to plot two set on data together. Moreover from the graphical interface I'm not able to open new file... Anyone have a solution?

I tried to reinstall grace with brew, but nothing has changed.

JD-UIUC commented 3 years ago

I use xmgrace on a Mac Pro running 10.14.6 (last version that runs on that machine) and on a MacBook Air running 11.3.1. On both systems I am running the previous version XQuartz, 2.7.11. If I recall correctly, there were some problems with xmgrace on XQuartz 2.8.x. I haven’t upgraded XQuartz to see if there are any problems now.

I get the same warning messages about the locale, and haven’t been able to resolve them. They do not seem to have any effect on the performance of xmgrace.

I do not have any of the other problems that you describe. The only one that remains is the weird time delay on opening the axis menu for the first time.

I’d suggest checking the version of Xquartz, and possibly downgrading to 2.7 if you’re running 2.8.

Hope that helps.

Agnese-rosc commented 3 years ago

Thank you very much for the answer! I'll try what you suggest and I hope it will work!

piskuliche commented 3 years ago

As a comment on this - I am running on Xquartz 2.8.1 and I am not having the problems you describe (just the normal ones of the locale issue + slow axis command). I did have an issue for a bit where if I resized the grace window it crashed, but it fixed itself on restarting my computer. I'm also on 10.15.7 like you.

stale[bot] commented 3 years ago

This issue or pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want to keep the issue open, please comment or update the info here. Thank you for your contributions.

stale[bot] commented 3 years ago

This issue or pull request has been automatically closed because it has not had recent activity. Thank you for your contributions.

rocco-martinazzo commented 2 years ago

Sorry for getting back to this issue. It looks like nobody fixed it, isn't? Rather annoiying, I tried different options, reinstalled xmgrace, xquartz, etc. to no avail. Here is my setting

BigSur 11.15.2 xquartz 2.8.1 Grace-5.1.25 GUI toolkit: @(#)Motif Version 2.3.8

I even failed to remove the warnings

Warning: locale not supported by Xlib, locale set to C Warning: X locale modifiers not supported, using default

At least, I managed to make grace opening xquartz when launched (not obvious at the beginning..)

JD-UIUC commented 2 years ago

Nothing new to report. The issue remains the same: Everything works as expected, except the “Axis properties” menu takes a very long time to load. It works fine after it loads for the first time.

I’ve just sort of gotten used to it. It takes about 10-12 seconds on my Mi-chip Macbook Air.

rocco-martinazzo commented 2 years ago

I finally fixed the issue by recompiling grace from the source code. Here are the steps that I followed (cd to your preferred dir for compiling the code, this is a slightly modified version of the instructions that you can find at http://www.phy.ohio.edu/~hadizade/blog_files/XmGrace_Mac.html)

You should find a perfectly working version of xmgrace on /DIR/grace/bin/xmgrace

This is the version of my C compiler (I run gcc but it is actually clang): Apple clang version 12.0.5 One might probably fix the problem of the optimization level of the compiler by using true gcc, however in my tests I ran into troubles with the motif test above.

Hope that it helps

JD-UIUC commented 2 years ago

Thanks. I tried this, and so far have not been able to get it to work.

On my old Mac Pro (2010), the latest OS I can run is Mojave. I got it to compile, but the executable fails to run, giving the error:

[xcb] Extra reply data still left in queue [xcb] This is most likely caused by a broken X extension library Assertion failed: (!xcb_xlib_extra_reply_data_left), function _XReply, file xcb_io.c, line 665

On my new MacBook Air (M1 chip), the compile fails complaining about not being able to find compatible X11 libraries for arm64 architecture.

On Sep 14, 2021, at 3:26 AM, Rocco Martinazzo @.**@.>> wrote:

I finally fixed the issue by recompiling grace from the source code. Here are the steps that I followed (cd to your preferred dir for compiling the code, this is a slightly modified version of the instructions that you can find at http://www.phy.ohio.edu/~hadizade/blog_files/XmGrace_Mac.htmlhttps://urldefense.com/v3/__http://www.phy.ohio.edu/*hadizade/blog_files/XmGrace_Mac.html__;fg!!DZ3fjg!vbihM_8Rr4dnHPG7cBqrdFF7AvIjWn7GaIoEUbRgekhQBz8p1Dig8tZ5x-to_e8x0g$)

You should find a perfectly working version of xmgrace on /DIR/grace/bin/xmgrace

This is the version of my C compiler (I run gcc but it is actually clang): Apple clang version 12.0.5 One might probably fix the problem of the optimization level of the compiler by using true gcc, however in my tests I ran into troubles with the motif test above.

Hope that it helps

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/OSGeo/homebrew-osgeo4mac/issues/1406*issuecomment-919021933__;Iw!!DZ3fjg!vbihM_8Rr4dnHPG7cBqrdFF7AvIjWn7GaIoEUbRgekhQBz8p1Dig8tZ5x-vunCuq7Q$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABWB5SUNNBVB5SJZB4MXNALUB4PMJANCNFSM4VP6Z6KA__;!!DZ3fjg!vbihM_8Rr4dnHPG7cBqrdFF7AvIjWn7GaIoEUbRgekhQBz8p1Dig8tZ5x-vBrY6pqA$. Triage notifications on the go with GitHub Mobile for iOShttps://urldefense.com/v3/__https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!DZ3fjg!vbihM_8Rr4dnHPG7cBqrdFF7AvIjWn7GaIoEUbRgekhQBz8p1Dig8tZ5x-tC4zymGA$ or Androidhttps://urldefense.com/v3/__https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign*3Dnotification-email*26utm_medium*3Demail*26utm_source*3Dgithub__;JSUlJSU!!DZ3fjg!vbihM_8Rr4dnHPG7cBqrdFF7AvIjWn7GaIoEUbRgekhQBz8p1Dig8tZ5x-twRP3e5A$.

CarlosM-M commented 2 years ago

Thanks Rocco for posting this. I have tried to reinstall Xmgrace following your instructions but configure failed, not finding Motif "configure: error: M*tif has not been found", a typical error while configuring Xmgrace. However, I do have Motif installed and have checked that its location is correct.

Any ideas?

I am on a MacBook Pro (Intel) up-to-date with: Big Sur 11.5.2 Homebrew 3.2.12 openMotif 2.3.8_1 Xquartz 2.8.1

I finally fixed the issue by recompiling grace from the source code. Here are the steps that I followed (cd to your preferred dir for compiling the code, this is a slightly modified version of the instructions that you can find at http://www.phy.ohio.edu/~hadizade/blog_files/XmGrace_Mac.html)

  • wget ftp://ftp.fu-berlin.de/unix/graphics/grace/src/grace5/grace-5.1.25.tar.gz
  • tar xzvf grace-5.1.25.tar.gz
  • modify configure to remove a (harmless) compiler option that generate warnings & (importantly) skip the useless motif test which otherwise procudes an error, 4266c4266: CFLAGS="$CFLAGS -fno-strength-reduce" --> # CFLAGS="$CFLAGS -fno-strength-reduce" 9554a9555 #include 9559c9560 XmRegisterConverters(); --> / XmRegisterConverters(); /
  • ./configure -prefix=/DIR --x-includes=/usr/X11/include --x-libraries=/usr/X11/lib --with-motif-library=-lXm --with-extra-incpath=/usr/local/Cellar/openmotif/2.3.8_1/include/:/usr/local/Cellar/fftw/3.3.9_1/include/ --with-extra-ldpath=/usr/local/Cellar/openmotif/2.3.8_1/lib/:/usr/local/Cellar/fftw/3.3.9_1/lib/
  • modfy Make.conf to lower optimization level of the C compiler, i.e. set CFLAGS to: CFLAGS0=-O1 -fno-common -Wall -Wpointer-arith -Wnested-externs
  • make
  • sudo make install

You should find a perfectly working version of xmgrace on /DIR/grace/bin/xmgrace

This is the version of my C compiler (I run gcc but it is actually clang): Apple clang version 12.0.5 One might probably fix the problem of the optimization level of the compiler by using true gcc, however in my tests I ran into troubles with the motif test above.

Hope that it helps

rocco-martinazzo commented 2 years ago

Hi Carlos, did you edit the configure file to make the motif test dummy (i.e. by commenting the call to XmRegisterConverters)? It is useless but fails because of a call to an intrinsic function, apparently no longer supported by the C compiler. Furthermore, check where the motif library is installed

$ brew list openmotif

and modify the confiure command accordingly. If not yet working, it may be due to the fact that you are using true gcc (which, for reasons obscure to me, produce the same error despite the patch to configure). In that case enforce the use of clang by adding --with-cc=clang to the configure command.

PS Taka a look at the config.log file, right above the motif error. It should give some hint on the root of the problem.

Thanks Rocco for posting this. I have tried to reinstall Xmgrace following your instructions but configure failed, not finding Motif "configure: error: M*tif has not been found", a typical error while configuring Xmgrace. However, I do have Motif installed and have checked that its location is correct.

Any ideas?

I am on a MacBook Pro (Intel) up-to-date with: Big Sur 11.5.2 Homebrew 3.2.12 openMotif 2.3.8_1 Xquartz 2.8.1

I finally fixed the issue by recompiling grace from the source code. Here are the steps that I followed (cd to your preferred dir for compiling the code, this is a slightly modified version of the instructions that you can find at http://www.phy.ohio.edu/~hadizade/blog_files/XmGrace_Mac.html)

  • wget ftp://ftp.fu-berlin.de/unix/graphics/grace/src/grace5/grace-5.1.25.tar.gz
  • tar xzvf grace-5.1.25.tar.gz
  • modify configure to remove a (harmless) compiler option that generate warnings & (importantly) skip the useless motif test which otherwise procudes an error, 4266c4266: CFLAGS="$CFLAGS -fno-strength-reduce" --> # CFLAGS="$CFLAGS -fno-strength-reduce" 9554a9555 #include 9559c9560 XmRegisterConverters(); --> / XmRegisterConverters(); /
  • ./configure -prefix=/DIR --x-includes=/usr/X11/include --x-libraries=/usr/X11/lib --with-motif-library=-lXm --with-extra-incpath=/usr/local/Cellar/openmotif/2.3.8_1/include/:/usr/local/Cellar/fftw/3.3.9_1/include/ --with-extra-ldpath=/usr/local/Cellar/openmotif/2.3.8_1/lib/:/usr/local/Cellar/fftw/3.3.9_1/lib/
  • modfy Make.conf to lower optimization level of the C compiler, i.e. set CFLAGS to: CFLAGS0=-O1 -fno-common -Wall -Wpointer-arith -Wnested-externs
  • make
  • sudo make install

You should find a perfectly working version of xmgrace on /DIR/grace/bin/xmgrace This is the version of my C compiler (I run gcc but it is actually clang): Apple clang version 12.0.5 One might probably fix the problem of the optimization level of the compiler by using true gcc, however in my tests I ran into troubles with the motif test above. Hope that it helps

JD-UIUC commented 2 years ago

Still no success for me. I made sure to use the clang compiler. On the machine with the M1 chip, the compiler fails to link because the arch comes back arm64 and the linker fails.

On my Intel/Mojave machine, I get it to compile, but when I try to run it, I get the error: Error: Couldn't find per display information

xterms and other X-apps open without any issue.

Jon

On Sep 15, 2021, at 11:13 AM, Rocco Martinazzo @.**@.>> wrote:

Hi Carlos, did you edit the configure file to make the motif test dummy (i.e. by commenting the call to XmRegisterConverters)? It is useless but fails because of a call to an intrinsic function, apparently no longer supported by the C compiler. Furthermore, check where the motif library is installed

$ brew list openmotif

and modify the confiure command accordingly. If not yet working, it may be due to the fact that you are using true gcc (which, for reasons obscure to me, produce the same error despite the patch to configure). In that case enforce the use of clang by adding --with-cc=clang to the configure command.

PS Taka a look at the config.log file, right above the motif error. It should give some hint on the root of the problem.

Thanks Rocco for posting this. I have tried to reinstall Xmgrace following your instructions but configure failed, not finding Motif "configure: error: M*tif has not been found", a typical error while configuring Xmgrace. However, I do have Motif installed and have checked that its location is correct.

Any ideas?

I am on a MacBook Pro (Intel) up-to-date with: Big Sur 11.5.2 Homebrew 3.2.12 openMotif 2.3.8_1 Xquartz 2.8.1

I finally fixed the issue by recompiling grace from the source code. Here are the steps that I followed (cd to your preferred dir for compiling the code, this is a slightly modified version of the instructions that you can find at http://www.phy.ohio.edu/~hadizade/blog_files/XmGrace_Mac.htmlhttps://urldefense.com/v3/__http://www.phy.ohio.edu/*hadizade/blog_files/XmGrace_Mac.html__;fg!!DZ3fjg!vESbI7Npvtd7zfQ6ajOGGDQevUQMh43i7_YcfdFpZ6etUJP_sBFwl4YQfUIuThd9GA$)

You should find a perfectly working version of xmgrace on /DIR/grace/bin/xmgrace This is the version of my C compiler (I run gcc but it is actually clang): Apple clang version 12.0.5 One might probably fix the problem of the optimization level of the compiler by using true gcc, however in my tests I ran into troubles with the motif test above. Hope that it helps

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/OSGeo/homebrew-osgeo4mac/issues/1406*issuecomment-920262281__;Iw!!DZ3fjg!vESbI7Npvtd7zfQ6ajOGGDQevUQMh43i7_YcfdFpZ6etUJP_sBFwl4YQfUIowEeBxw$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABWB5STNBTDHECE54X634ODUCDO3FANCNFSM4VP6Z6KA__;!!DZ3fjg!vESbI7Npvtd7zfQ6ajOGGDQevUQMh43i7_YcfdFpZ6etUJP_sBFwl4YQfUIU2W5XfQ$. Triage notifications on the go with GitHub Mobile for iOShttps://urldefense.com/v3/__https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!DZ3fjg!vESbI7Npvtd7zfQ6ajOGGDQevUQMh43i7_YcfdFpZ6etUJP_sBFwl4YQfUJ_CKv-rw$ or Androidhttps://urldefense.com/v3/__https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign*3Dnotification-email*26utm_medium*3Demail*26utm_source*3Dgithub__;JSUlJSU!!DZ3fjg!vESbI7Npvtd7zfQ6ajOGGDQevUQMh43i7_YcfdFpZ6etUJP_sBFwl4YQfUJOMQ_Fqg$.

rocco-martinazzo commented 2 years ago

Is DISPLAY environmental variable correctly set? One should also be able to configure Xquartz for running xmgrace (IApplications menu), but I'd first suggest a reboot

Still no success for me. I made sure to use the clang compiler. On the machine with the M1 chip, the compiler fails to link because the arch comes back arm64 and the linker fails. On my Intel/Mojave machine, I get it to compile, but when I try to run it, I get the error: Error: Couldn't find per display information xterms and other X-apps open without any issue. Jon On Sep 15, 2021, at 11:13 AM,

JD-UIUC commented 2 years ago

That was the first thing I checked:

echo $DISPLAY /private/tmp/com.apple.launchd.CnAY0nBtcO/org.xquartz:0

That file exists and its permissions are srw-rw-rw. All other X apps work, including the homebrew version of xmgrace. It just has that flaky Axis Properties issue.

I also tried setting DISPLAY to :0 , :0.0 , and localhost:0.0 None of those had any effect, same error.

I also rebooted the machine. No joy.

And finally, I tried adding xmgrace to the XQuartz Application list. No help.

On Sep 15, 2021, at 3:06 PM, Rocco Martinazzo @.**@.>> wrote:

Is DISPLAY environmental variable correctly set? One should also be able to configure Xquartz for running xmgrace (IApplications menu), but I'd first suggest a reboot

Still no success for me. I made sure to use the clang compiler. On the machine with the M1 chip, the compiler fails to link because the arch comes back arm64 and the linker fails. On my Intel/Mojave machine, I get it to compile, but when I try to run it, I get the error: Error: Couldn't find per display information xterms and other X-apps open without any issue. Jon On Sep 15, 2021, at 11:13 AM,

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/OSGeo/homebrew-osgeo4mac/issues/1406*issuecomment-920415388__;Iw!!DZ3fjg!qD-BE7at8BGntD0OCXtDInUcRujy4hCc9iylCpYM1NRd3vxjlbpV9uzdUxs0BvcQag$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABWB5SRWIIXX3GE6YOGFC73UCEKFDANCNFSM4VP6Z6KA__;!!DZ3fjg!qD-BE7at8BGntD0OCXtDInUcRujy4hCc9iylCpYM1NRd3vxjlbpV9uzdUxvG-0LfBQ$. Triage notifications on the go with GitHub Mobile for iOShttps://urldefense.com/v3/__https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!DZ3fjg!qD-BE7at8BGntD0OCXtDInUcRujy4hCc9iylCpYM1NRd3vxjlbpV9uzdUxtV6tYjWQ$ or Androidhttps://urldefense.com/v3/__https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign*3Dnotification-email*26utm_medium*3Demail*26utm_source*3Dgithub__;JSUlJSU!!DZ3fjg!qD-BE7at8BGntD0OCXtDInUcRujy4hCc9iylCpYM1NRd3vxjlbpV9uzdUxtXGMggzA$.

rocco-martinazzo commented 2 years ago

Don't really know..I remember to have had the same problem with the brew installation of grace, and fixed it by reinstalling it along with openmotif

brew reinstall -s openmotif grace

That fixed the display problem but left the axis problem. On top of this, I re-compiled grace from source. I do not know whether it can help, it looks like a kind of alchemy at this point..

JD-UIUC commented 2 years ago

I looked into this a bit further. The reason that Mtif is not found is that libXm is not included in XQuartz. So there is no libXm. in /usr/X11/lib. The only way to get the compile to complete is to use the libXm in openmotif, and the version of libXm in homebrew has the axis issue.

So Rocco - are you using XQuartz? What is the source of your libXm?

On Sep 16, 2021, at 12:15 AM, Rocco Martinazzo @.**@.>> wrote:

Don't really know..I remember to have had the same problem with the brew installation of grace, and fixed it by reinstalling it along with openmotif

brew reinstall -s openmotif grace

That fixed the display problem but left the axis problem. On top of this, I re-compiled grace from source. I do not know whether it can help, it looks like a kind of alchemy at this point..

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/OSGeo/homebrew-osgeo4mac/issues/1406*issuecomment-920639896__;Iw!!DZ3fjg!pV0lfoSGqRpVwa6aOChHzdj74nkgu8qRpiro1D8x73OjMbhtb5RAnJBt0NVsBwMwcw$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABWB5SSASHVMTNLMKKB2WSDUCGKRNANCNFSM4VP6Z6KA__;!!DZ3fjg!pV0lfoSGqRpVwa6aOChHzdj74nkgu8qRpiro1D8x73OjMbhtb5RAnJBt0NXelRAP_w$. Triage notifications on the go with GitHub Mobile for iOShttps://urldefense.com/v3/__https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!DZ3fjg!pV0lfoSGqRpVwa6aOChHzdj74nkgu8qRpiro1D8x73OjMbhtb5RAnJBt0NV1pwaByQ$ or Androidhttps://urldefense.com/v3/__https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign*3Dnotification-email*26utm_medium*3Demail*26utm_source*3Dgithub__;JSUlJSU!!DZ3fjg!pV0lfoSGqRpVwa6aOChHzdj74nkgu8qRpiro1D8x73OjMbhtb5RAnJBt0NUUcBZ1Vg$.

rocco-martinazzo commented 2 years ago

That's correct, libXm is part of the Motif suite of libraries and may come from several packages ("openmotif" is one example, another is "lesstif"). As I said, I have (re)installed openmotif with brew, and used it when compiling grace from source, so I am not sure that this is the root of the problem. You might try "lessitf", but notice that it conflicts with openmotif so you probably need to uninstall the latter.

Please check the options to configure in my example,

--with-motif-library=-lXm --with-extra-incpath=/usr/local/Cellar/openmotif/2.3.8_1/include --with-extra-ldpath=/usr/local/Cellar/openmotif/2.3.8_1/lib

The libraries (include files) should be localed under lib (include) of the openmotif keg (you should find both the static and dynamic version of the Xm library). If they are present there is no reason for not finding them when compiling grace, but please remember to skip the motif test at the configuration time -- as I described in the first post --since it fails with an error which is actually a compiler issue.

I looked into this a bit further. The reason that Mtif is not found is that libXm is not included in XQuartz. So there is no libXm. in /usr/X11/lib. The only way to get the compile to complete is to use the libXm in openmotif, and the version of libXm in homebrew has the axis issue. So Rocco - are you using XQuartz? What is the source of your libXm?

JD-UIUC commented 2 years ago

I did try linking with lesstif (after uninstalling open motif). Different failure mode. Homebrew says lesstif is deprecated.

The XmRegister line is commented out as you said.

I think that you’re right - it’s alchemy at this point.

On Sep 16, 2021, at 11:00 AM, Rocco Martinazzo @.**@.>> wrote:

That's correct, libXm is part of the Motif suite of libraries and may come from several packages ("openmotif" is one example, another is "lesstif"). As I said, I have (re)installed openmotif with brew, and used it when compiling grace from source, so I am not sure that this is the root of the problem. You might try "lessitf", but notice that it conflicts with openmotif so you probably need to uninstall the latter.

Please check the options to configure in my example,

--with-motif-library=-lXm --with-extra-incpath=/usr/local/Cellar/openmotif/2.3.8_1/include --with-extra-ldpath=/usr/local/Cellar/openmotif/2.3.8_1/lib

The libraries (include files) should be localed under lib (include) of the openmotif keg (you should find both the static and dynamic version of the Xm library). If they are present there is no reason for not finding them when compiling grace, but please remember to skip the motif test at the configuration time -- as I described in the first post --since it fails with an error which is actually a compiler issue.

I looked into this a bit further. The reason that Mtif is not found is that libXm is not included in XQuartz. So there is no libXm. in /usr/X11/lib. The only way to get the compile to complete is to use the libXm in openmotif, and the version of libXm in homebrew has the axis issue. So Rocco - are you using XQuartz? What is the source of your libXm?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/OSGeo/homebrew-osgeo4mac/issues/1406*issuecomment-921115186__;Iw!!DZ3fjg!t3K_l4b0zN225ox2jS9y6IcxuGQX_8rwwebDPtCYU4r5WlRBB5AdQfxZpQLAdmrNcw$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABWB5STV6ALRBIQYSPOUQMDUCIWDPANCNFSM4VP6Z6KA__;!!DZ3fjg!t3K_l4b0zN225ox2jS9y6IcxuGQX_8rwwebDPtCYU4r5WlRBB5AdQfxZpQIM1P69tw$. Triage notifications on the go with GitHub Mobile for iOShttps://urldefense.com/v3/__https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!DZ3fjg!t3K_l4b0zN225ox2jS9y6IcxuGQX_8rwwebDPtCYU4r5WlRBB5AdQfxZpQLcWPKLYg$ or Androidhttps://urldefense.com/v3/__https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign*3Dnotification-email*26utm_medium*3Demail*26utm_source*3Dgithub__;JSUlJSU!!DZ3fjg!t3K_l4b0zN225ox2jS9y6IcxuGQX_8rwwebDPtCYU4r5WlRBB5AdQfxZpQJaJ-A9eQ$.

CarlosM-M commented 2 years ago

Sorry for my slow reply. Yes Rocco I did followed your instructions. First I checked my Motif libraries ( I have the same 2.3.8_1 version) and indeed, I have commented the XmRegisterConverters test line. Configuration file was already using clang. Still I added the compilation option --with-cc=clang and got the same result: configure: error: M*tif has not been found.

Also, libraries and include files are all in their right place.

Looking at config.log the error occurs at the same instance of the Motif test:

include <Xm/XmAll.h>

  int main(void) {
    int vlibn, vincn;
    vincn = XmVersion;
    /* XmRegisterConverters(); */
    vlibn = xmUseVersion;
    if (vincn < 1002) {
      exit(1);
    }
    if (vincn != vlibn) {
      exit(2);
    }
    exit(0);
  }

Could it be XmVersion string under homebrew does not return the correct version > 1.2?

I have tried other modifications to configure code without success.

athomps commented 2 years ago

I have the Axis properties problem. It hangs for about 50 secs each time, which is very frustrating. My set up is:

Catalina 10.15.7 Homebrew 3.2.13 openMotif 2.3.8_1 Xquartz 2.8.1 Grace 5.1.25_3

After reading this long thread, I tried: brew reinstall -s openmotif grace

It still stalls for 50 secs.

athomps commented 2 years ago

It it possible that compiling an earlier version of Grace or OpenMotif might help?

rocco-martinazzo commented 2 years ago

Dear Carlos, try to make the test dummy by editing the configuration file. Whether the test fails or not is set right below the XmRegisterConverters test line,

if ac_fn_c_try_run "$LINENO"; then : acx_cv_motif="yes" else acx_cv_motif="no" fi

Just set acx_cv_motif always "yes". In this way it won't complain anymore about the motif libraries and you should be able to compile the code. I have no guarantee at this point, though, that the excetuable will show up in Xqaurtz (see discussion above) and work smoothly.

Sorry for my slow reply. Yes Rocco I did followed your instructions. First I checked my Motif libraries ( I have the same 2.3.8_1 version) and indeed, I have commented the XmRegisterConverters test line. Configuration file was already using clang. Still I added the compilation option --with-cc=clang and got the same result: configure: error: M*tif has not been found.

Also, libraries and include files are all in their right place.

Looking at config.log the error occurs at the same instance of the Motif test:

include <Xm/XmAll.h>

int main(void) { int vlibn, vincn; vincn = XmVersion; / XmRegisterConverters(); / vlibn = xmUseVersion; if (vincn < 1002) { exit(1); } if (vincn != vlibn) { exit(2); } exit(0); }

Could it be XmVersion string under homebrew does not return the correct version > 1.2?

I have tried other modifications to configure code without success.

rocco-martinazzo commented 2 years ago

Yes, the problem must be in the pre-compiled version available in the homebrew repository. You should re-compile grace from source, upon patching the configuration file to skip the motif test (as indicated above) since otherwise it produces an error (and you do not need such test since you do have the motif libraries installed, they came along with grace when you imported the formula from homebrew).

I have the Axis properties problem. It hangs for about 50 secs each time, which is very frustrating. My set up is:

Catalina 10.15.7 Homebrew 3.2.13 openMotif 2.3.8_1 Xquartz 2.8.1 Grace 5.1.25_3

After reading this long thread, I tried: brew reinstall -s openmotif grace

It still stalls for 50 secs.

CarlosM-M commented 2 years ago

Dear Rocco, thanks.

I forced acx_cv_motif="yes" in configure as you suggested and indeed I could produce the Make.conf. I got xmgrace installed locally by following the rest of your instructions.

Running the compiled version the problem with the axis properties persisted. Moreover, other things like recalling the window made my X system to crash.

The solution to this seems to be sensitive to the platform in use,,, thus complex.

Dear Carlos, try to make the test dummy by editing the configuration file. Whether the test fails or not is set right below the XmRegisterConverters test line,

if ac_fn_c_try_run "$LINENO"; then : acx_cv_motif="yes" else acx_cv_motif="no" fi

Just set acx_cv_motif always "yes". In this way it won't complain anymore about the motif libraries and you should be able to compile the code. I have no guarantee at this point, though, that the excetuable will show up in Xqaurtz (see discussion above) and work smoothly.

Sorry for my slow reply. Yes Rocco I did followed your instructions. First I checked my Motif libraries ( I have the same 2.3.8_1 version) and indeed, I have commented the XmRegisterConverters test line. Configuration file was already using clang. Still I added the compilation option --with-cc=clang and got the same result: configure: error: M*tif has not been found. Also, libraries and include files are all in their right place. Looking at config.log the error occurs at the same instance of the Motif test:

include <Xm/XmAll.h>

int main(void) { int vlibn, vincn; vincn = XmVersion; / XmRegisterConverters(); / vlibn = xmUseVersion; if (vincn < 1002) { exit(1); } if (vincn != vlibn) { exit(2); } exit(0); } Could it be XmVersion string under homebrew does not return the correct version > 1.2? I have tried other modifications to configure code without success.

athomps commented 2 years ago

Since you can now reproduce the problem with source code, you could try to isolate the point where it is hanging, and eliminate it in the source code.

rocco-martinazzo commented 2 years ago

This is the set of shared libraries my executabe is linked to (use otools -L path/exectuable)

/usr/local/opt/openmotif/lib/libXm.4.dylib (compatibility version 5.0.0, current version 5.4.0) /opt/X11/lib/libXpm.4.dylib (compatibility version 16.0.0, current version 16.0.0) /usr/local/opt/libxp/lib/libXp.6.dylib (compatibility version 9.0.0, current version 9.0.0) /opt/X11/lib/libXmu.6.dylib (compatibility version 9.0.0, current version 9.0.0) /opt/X11/lib/libXt.6.dylib (compatibility version 7.0.0, current version 7.0.0) /opt/X11/lib/libXext.6.dylib (compatibility version 11.0.0, current version 11.0.0) /opt/X11/lib/libX11.6.dylib (compatibility version 11.0.0, current version 11.0.0) /opt/X11/lib/libSM.6.dylib (compatibility version 7.0.0, current version 7.1.0) /opt/X11/lib/libICE.6.dylib (compatibility version 10.0.0, current version 10.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1292.100.5)

what about yours? What you say looks rather weird becuase (if I remember correcltly) we share precisely the same configuration..!

Running the compiled version the problem with the axis properties persisted. Moreover, other things like recalling the window made my X system to crash.

The solution to this seems to be sensitive to the platform in use,,, thus complex.