I can't install xorg

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

I can't install xorg

Daniel
Command mport install xorg doesn;t work and ports have not dependecies. Help me
Reply | Threaded
Open this post in threaded view
|

Re: I can't install xorg

Nyan
Have same problem.

mport - don't see any packages.
mport search - don't give any result
midnightbsd-desktop port also does not exist and it fails to install on initial startup.
Reply | Threaded
Open this post in threaded view
|

Re: I can't install xorg

Krush206
In reply to this post by Daniel
Same issue here too. On latest MBSD version, 1.1
Reply | Threaded
Open this post in threaded view
|

Re: I can't install xorg

rafaelfonseca
In reply to this post by Daniel
I'm a new MidnightBSD user and also tried to install the X.org, but the package was not found.

Just returns this error message:

# mport install xorg
mport: Package xorg not found int the index.


I recently installed MidnightBSD 1.1.

Reply | Threaded
Open this post in threaded view
|

Re: I can't install xorg

Krush206
In reply to this post by Daniel
Installing xorg from the ports returns a compilation error

Reply | Threaded
Open this post in threaded view
|

Re: I can't install xorg

rafaelfonseca
In reply to this post by Daniel
I tried to follow the manual build tutorial disponibilized in MidnightBSD documentation but ocurred an error too:

# cd /usr/mports/x11/xorg; make install clean

error
Reply | Threaded
Open this post in threaded view
|

Re: I can't install xorg

disgruntledtester
In reply to this post by Daniel
I've got to say this is poor form. I tried this OS (but version 1.0) back in October 2018 and the same thing occurred.

I was just experimenting to see how it was but I can't like you all, get past mport errors.

I'm sorry, but I'm done with this. Good luck to the developers, but I'm not trying this again.
Reply | Threaded
Open this post in threaded view
|

Re: I can't install xorg

rafaelfonseca
I've tried the 1.0 too in last year and had the same feeling that you. And with this new release I though that probably was working, but seems still the same problem/error.