I bought myself an AMD64 for trying out FreeNX at home. Anyway i stepped through almost everything in bugs.gentoo.org to forums.gentoo.org... nothing really works. could anyone who got knowledge of making ebuilds please make some functional FreeNX packages? i got all over this weekend to try out that stuff.. i am almost about to give up gentoo64 and install it only for 32 bit... Reproducible: Always Steps to Reproduce: 1. emerge nxserver-freenx Actual Results: It stops at several points, depends on which ebuilds i try to use. 1.4.0 stops at some other package than 1.5.0. Expected Results: compile correctly
NOT a bugzilla product bug. File ebuild-related bugs under Gentoo Linux product as per instructions, please.
Hi, I can't answer this, as I'm a Gentoo/x86 user, not a Gentoo/amd64 user. I'll see if I can find anyone who can help. Best regards, Stu
I am interested in helping to get freenx to amd64 wfg Mario
According to these the nx libraries can't be compiled on amd64 (or at least not all of them): http://www.nomachine.com/ar/view.php?ar_id=AR02C00154 http://www.nomachine.com/ar/view.php?ar_id=AR06C00224 What about providing binary packages?
Well i finally got it running - half a year ago. Since i didn't have much time i forgot to take attention to this bug. I made a small tarball with all the libs and stuff. 4.8M Aug 25 13:57 NX.tar.bz2 If there is still interest in this Bug, i would apply the .tar.bz2. so.. is there? :)
I got the nx packages compile under amd64 when it try to connect nxagent segfaults. wfg Mario (In reply to comment #3) > I am interested in helping to get freenx to amd64 > > wfg > Mario >
Created attachment 80268 [details, diff] This patch adds some missing declarations in nxcomp
Created attachment 80269 [details, diff] This patch makes nx-x11 compile on amd64 (it also includes the nxcomp gcc4 patches) It makes nx compile on amd64 but on connect the nxagent segfaults. (still something to do)
*** Bug 119408 has been marked as a duplicate of this bug. ***
There is a nx-x11-bin ebuild in the overlay. It will be added to portage. This is for people on AMD64 archs. It should work correctly. All the ebuilds have been modified to accept it or the regular nx-x11. Since nx-x11 isn't keyworded AMD64, the bin should install automatically when you type emerge nxserver-freenx. :) Cheers.
I just installed nxserver-freenx on my amd64 System. It seems to work fine (as well as on my debian System since I never managed to get the multimedia extensions running) as well. I had some smaller problems when emerging: Just putting: =net-misc/nxclient-1.5.0-r4 ~amd64 =net-misc/nxssh-1.5.0-r2 ~amd64 =net-misc/nxcomp-1.5.0-r2 ~amd64 =net-misc/nxesd-1.5.0 ~amd64 =net-misc/nxserver-freenx-0.5.0.20060311-r1 ~amd64 =net-misc/nx-x11-1.5.0-r8 ~amd64 into /etc/portage/package.keywords was not enough. I always got this error: !!! All ebuilds that could satisfy "=net-misc/nx-x11-1.5*" have been masked. !!! One of the following masked packages is required to complete your request: - net-misc/nx-x11-1.5.0-r8 (masked by: missing keyword) For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. !!! (dependency required by "net-misc/nxserver-freenx-0.5.0.20060311-r1" [ebuild]) So I installed it using: ACCEPT_KEYWORDS="~amd64" emerge -v nxserver-freenx and added =dev-lang/tcl-8.4.12 ~amd64 =dev-lang/tk-8.4.12 ~amd64 =dev-tcltk/expect-5.43.0 ~amd64 To my /etc/portage/package.keywords. After that I ran /usr/NX/bin/nxsetup For now I did not find any problems. I tested it with an nxclient on debian, on Windows and with the Gentoo nxclient. btw. is there a way to disable Shadows/Translucency for remote sessions only? Cheers ...
(In reply to comment #11) > I just installed nxserver-freenx on my amd64 System. It seems to work fine (as > well as on my debian System since I never managed to get the multimedia > extensions running) as well. > > I had some smaller problems when emerging: > Just putting: > =net-misc/nxclient-1.5.0-r4 ~amd64 > =net-misc/nxssh-1.5.0-r2 ~amd64 > =net-misc/nxcomp-1.5.0-r2 ~amd64 > =net-misc/nxesd-1.5.0 ~amd64 > =net-misc/nxserver-freenx-0.5.0.20060311-r1 ~amd64 > =net-misc/nx-x11-1.5.0-r8 ~amd64 > into /etc/portage/package.keywords was not enough. > > I always got this error: > !!! All ebuilds that could satisfy "=net-misc/nx-x11-1.5*" have been masked. > !!! One of the following masked packages is required to complete your request: > - net-misc/nx-x11-1.5.0-r8 (masked by: missing keyword) > > For more information, see MASKED PACKAGES section in the emerge man page or > refer to the Gentoo Handbook. > !!! (dependency required by "net-misc/nxserver-freenx-0.5.0.20060311-r1" > [ebuild]) These files are package masked. You need to add them to /etc/portage/package.unmask. ;)
> These files are package masked. You need to add them to > /etc/portage/package.unmask. ;) Hi, that sounds reasonable to some extend, but I mentioned how I solved that "Problem" already. btw.: I added "=net-misc/nx-x11-1.5.0-r8" to my /etc/portage/package.unmask before I emerged net-misc/nxserver-freenx-0.5.0.20060311-r1 and still got that error; by now net-misc/nx-x11 is not installed on my System at all. Instead a package called "net-misc/nx-x11-bin" is used - that might be the reason why it actually works that nice! Since there is NX version 2 out now I already tried nxclient-2.0.0-89 on my amd64 nxserver and I have still now reason to complain. Best Regards Ramin PS: =net-misc/nx-x11-1.5.0-r8 is not package masked anymore - it is only keywords (~amd64) masked.
(In reply to comment #13) > > These files are package masked. You need to add them to > > /etc/portage/package.unmask. ;) > > Hi, > > that sounds reasonable to some extend, but I mentioned how I solved that > "Problem" already. > btw.: I added "=net-misc/nx-x11-1.5.0-r8" to my /etc/portage/package.unmask > before I emerged net-misc/nxserver-freenx-0.5.0.20060311-r1 and still got that > error; by now net-misc/nx-x11 is not installed on my System at all. Instead a > package called "net-misc/nx-x11-bin" is used - that might be the reason why it > actually works that nice! > > Since there is NX version 2 out now I already tried nxclient-2.0.0-89 on my > amd64 nxserver and I have still now reason to complain. > > Best Regards > Ramin > > PS: =net-misc/nx-x11-1.5.0-r8 is not package masked anymore - it is only > keywords (~amd64) masked. > Well, one of the main reasons that there is an issue with AMD64 processors is that NoMachine is not officially supporting them. Thus, installation on a AMD64 machine is not supported upstream, which means that most bugs pertaining to AMD64 cannot be reported upstream. The only support they give is when you install their precompiled binaries in a 64 bit environment. Now that NX 2.0.0 is released and so is nxnode, that means there is much better support for AMD64. However, compiling may still prove problematic.
I have a suggestion, but I'm not really sure how to do it. I tried all of the suggestions that I could find in the forums and I cannot get freenx to function properly on 64 bit Gentoo. I also tried using the nx-x11-bin package. My post in the forums is here, so you can see what all I've tried: http://forums.gentoo.org/viewtopic-t-477659-highlight-freenx.html It has almost 200 views and no one seems to know how to make it work, so I thought I would ask people more knowledgable than me. My apologies if I'm abusing the "bugs" system. So what if you made 32 bit precompiled packages for each nx package that you needed on a 32bit box and "emerged" them on a 64 bit machine. Shouldn't portage's quickpkg feature do this? I have never used this... Please let me know, as I would be willing to help do this, or try something new perhaps that I'm missing to begin with. I would also be willing to write up a quick how-to on it, if I ever figure it out.
*** Bug 156542 has been marked as a duplicate of this bug. ***
portage now has ~amd64 KEYWORD for nxclient-2.1.0-r1, nx-2.1.0 and nxserver-frenx-0.6.0, so we can finally close this one :)
