> When I ran `startx` on the next boot, the server shutdown > because the VESA driver's ABI was at a different version than Xorg's. > So I tried update that driver but I ran into some other issues. I > could describe those issues, but I'm feeling like that isn't the > root issue.
I am not currently running GoboLinux but I remember ABI-related problems and xorg-server not starting. What I usually do is to make sure that LLVM is up to date; and cmake; then I compile meson ( http://www.linuxfromscratch.org/lfs/view/systemd/chapter06/meson.html ) (even though the URL includes systemd, meson works perfectly well without systemd of course; I only have this "bookmarked" as link, LFS/BLFS instructions can be super-helpful). After meson I tend to compile the xorg-libs (libx11, libice, libsm, libxcb - all available on the same URL where the xorg-server is), then I compile the xorg-server. Here you have to be a bit careful in that I have had problems in the past; e. g. wayland related parts aren't that good; I tend to do things such as --disable-xwayland-eglstream and similar to xorg-server. This serves me better than enabling these snippets. By the way, from my own experience it is quite hard to break a GoboLinux system because you should always have the older versions in the respective directory under /Programs/ so you can just re-symlink that. :) To your problem like this: Requested 'xproto >= 7.0.31' but version of Xproto is 7.0.29 Requested 'randrproto >= 1.6.0' but version of RandrProto is 1.5.0 Requested 'presentproto >= 1.1' but version of PresentProto is 1.0 I think if you install https://www.x.org/releases/individual/proto/xorgproto-2018.4.tar.bz2 then this should be fine. That has all the .pc files as far as I can see for the protos: scrnsaverproto.pc, trapproto.pc, videoproto.pc and so forth. I also recommend to you to keep information in a text file - this may help you at a later time a LOT. I started noting down how to resolve some problems within the yaml-files that I use to compile/install programs from source; a bit like the LFS/BLFS project but more tuned towards the problems I encounter. I also used to autogenerate something similar to LFS/BLFS - will try to see to do so and then make this available somewhere again. PS: The mailing interface confuses me too a bit. I see your emails but I don't see the other email that came first in 2019 altogether, so I could not hit on "reply" (I sent a mail to the email listed though). I find mailing lists pretty confusing altogether in general. On Sat, Jan 5, 2019 at 6:52 PM Philip White <philipwh...@cedarville.edu> wrote: > I realized that digest mode is not what I want for a mailing list, since I > cannot reply to emails individually. > > Anyway, my attempt to build i3 has been sidetracked because I ran > > InstallPackage Xorg-Server > > which broke X. When I ran `startx` on the next boot, the server shutdown > because the VESA driver's ABI was at a different version than Xorg's. So I > tried update that driver but I ran into some other issues. I could describe > those issues, but I'm feeling like that isn't the root issue. > > I would expect this is an issue other people have run into, since nearly > everyone uses Xorg, and people generally keep their systems up to the > latest version. > > While looking for a solution, I noticed the UpdateXorgRecipe script. I ran > it, and it made a bunch of local recipes, but as far as I can tell, it > didn't actually compile anything. Thus, I tried to run `Compile > Xorg-Server` to compile the newly generated recipes. I got the dependency > issues: > > Requested 'xproto >= 7.0.31' but version of Xproto is 7.0.29 > Requested 'randrproto >= 1.6.0' but version of RandrProto is 1.5.0 > Requested 'presentproto >= 1.1' but version of PresentProto is 1.0 > > Has anybody encountered this error before? Also, is there any > documentation for what UpdateXorgRecipe does? > > Last question, how do I search these mailing list archives? The link on > the website points to > http://search.gmane.org/search.php?group=gmane.linux.distributions.gobo.general, > which does not work. > > Thanks, > Philip > _______________________________________________ > gobolinux-users mailing list > gobolinux-users@lists.gobolinux.org > http://lists.gobolinux.org/mailman/listinfo/gobolinux-users >
_______________________________________________ gobolinux-users mailing list gobolinux-users@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-users
