Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Actually the creators of NEdit had no idea what packages will be required 5-10 years later on a fresh new OS
Well, what could be said is that the developers assembling "openSUSE_Leap_42.2/editors.repo" did not test the provided NEDIT binary sufficiently. Anyway, they managed to compile an NEDIT 64 bits binary that starts in the SUSE42.2 environment where it then finds all required run time "shared libraries" (*.so). And where almost everything is working, just with a minor but fatal flaw causing the cursor symbol not to be erased when the cursor moves on.
As it seems very difficult to compile NEDIT with the Sourceforge makefile in the SUSE42.2 environment maybe "norobro" or "ondoho" who already have compiled an executable binary (64 bits) running correctly on their systems (that presumable are not SUSE42.2!) could send me their binaries! I would for this set up a temporary email adress where the binaries could be sent as email-attachment!
I would then test the binary in my SUSE42.2 environment and report the result here!
stamcose, if the nedit package included in your suse repos fails, i think it is something that you should indeed report.
but you have to find the proper channels.
i suggest posting on their forums, politely, and do not claim you found a bug if you cannot prove it.
maybe ask someone to take you through the process of making a bug report.
i have taken a look at nedit and it seems to be a pretty powerful piece of software, at least for its time.
and for our time it's just incredibly lightweight and relatively feature-rich.
yet, i urge you to consider using a different editor.
maybe geany?
Thank you very much, ondoho, for the directory you sent! But the executable working in your environment does not immediately fit into the SUSE42.2 environment!
First attempt:
Code:
mats@linux-ze70:~/nedit> ./nedit &
[1] 5158
./nedit: error while loading shared libraries: libXm.so.2: cannot open shared object file: No such file or directory
[1]+ Exit 127 ./nedit
mats@linux-ze70:~/nedit> ./nedit
./nedit: Symbol `_XmStrings' has different size in shared object, consider re-linking
Segmentation fault (core dumped)
What works fine in your environment is no good in the SUSE42.2 environment! Which distribution are you using!
I already registered by Sourceforge where there is a "bug report" service. I hope Scott Tringali himself will be informed! Obviously the "bug" is in the SUSE42.2 repo, not in the 10 year old source that has been working perfectly in earlier SUSE releases!
Pending the fix of NEDIT I am using KWRITE which is a perfectly acceptable editor although I miss some features of NEDIT that I got accustomed to!
no, it is still not a bug. you have different libraries (=different versions) which make the binary useless. The best would be to build NEdit for yourself or specify your system exactly.
I guess there are a number of "shared libraries" and possibly other "dependencies" that have to added. That is what YAST is supposed to do for the user using information supplied in the repo! Unfortunately the X11 "dependencies" added/linked by YAST appears to no more be fully compatible with NEDIT.
no, that is not true again, yast will add/install only runtime dependencies, but this time you want to build it and build dependencies are not handled that way.
There is no dependency handling (by yast) for files compiled from sources.
Anyway, if it was a bug you need to report it and in that report you need to specify your system exactly (just to be able to reproduce it).
if opensuse packaged a version that does not work on the current opensuse, what is that? not a bug, but certainly something that shouldbe reported, no?
samcose, you need to learn how to compile things with dependencies.
the problems and confusion you experience are not specific to nedit.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.