Re: vim nox11 pkg problem - BSD

This is a discussion on Re: vim nox11 pkg problem - BSD ; Nutso OpenBSD User Dave writes: > Pkg_adding vim no-x11 fails because of no expat. > I think expat is in the x11 files, but I am trying to > put together an OpenBSD system with no x11 dependencies. extract libexpat* ...

+ Reply to Thread
Results 1 to 9 of 9

Thread: Re: vim nox11 pkg problem

  1. Re: vim nox11 pkg problem

    Nutso OpenBSD User Dave writes:

    > Pkg_adding vim no-x11 fails because of no expat.
    > I think expat is in the x11 files, but I am trying to
    > put together an OpenBSD system with no x11 dependencies.


    extract libexpat* from the x11 tarball and move the files to /usr/lib.

    This is a one-time workaround as expat has been moved to /usr/lib
    in -current.

    -r--r--r-- 1 root bin 480324 Oct 30 13:58 /usr/lib/libexpat.a
    -r--r--r-- 1 root bin 271834 Oct 30 13:58 /usr/lib/libexpat.so.9.0
    -r--r--r-- 1 root bin 494022 Oct 30 13:58 /usr/lib/libexpat_p.a
    -r--r--r-- 1 root bin 378354 Oct 30 13:58 /usr/lib/libexpat_pic.a

    // marc

  2. Re: vim nox11 pkg problem

    Marco S Hyman wrote:
    > Nutso OpenBSD User Dave writes:
    >
    >> Pkg_adding vim no-x11 fails because of no expat.
    >> I think expat is in the x11 files, but I am trying to
    >> put together an OpenBSD system with no x11 dependencies.

    >
    > extract libexpat* from the x11 tarball and move the files to /usr/lib.
    >
    > This is a one-time workaround as expat has been moved to /usr/lib
    > in -current.
    >
    > -r--r--r-- 1 root bin 480324 Oct 30 13:58 /usr/lib/libexpat.a
    > -r--r--r-- 1 root bin 271834 Oct 30 13:58 /usr/lib/libexpat.so.9.0
    > -r--r--r-- 1 root bin 494022 Oct 30 13:58 /usr/lib/libexpat_p.a
    > -r--r--r-- 1 root bin 378354 Oct 30 13:58 /usr/lib/libexpat_pic.a
    >
    > // marc

    I had been thinking about doing something like this.
    I built and installed expat myself but the package installs still fail
    for lack of expat. What is the difference between extracting libexpat
    from the x11 tarball and building and installing expat from source?

  3. Re: vim nox11 pkg problem

    Nutso OpenBSD User Dave wrote:
    > Marco S Hyman wrote:
    >> Nutso OpenBSD User Dave writes:
    >>
    >>> Pkg_adding vim no-x11 fails because of no expat.
    >>> I think expat is in the x11 files, but I am trying to
    >>> put together an OpenBSD system with no x11 dependencies.

    >>
    >> extract libexpat* from the x11 tarball and move the files to /usr/lib.
    >>
    >> This is a one-time workaround as expat has been moved to /usr/lib
    >> in -current.
    >>
    >> -r--r--r-- 1 root bin 480324 Oct 30 13:58 /usr/lib/libexpat.a
    >> -r--r--r-- 1 root bin 271834 Oct 30 13:58 /usr/lib/libexpat.so.9.0
    >> -r--r--r-- 1 root bin 494022 Oct 30 13:58 /usr/lib/libexpat_p.a
    >> -r--r--r-- 1 root bin 378354 Oct 30 13:58 /usr/lib/libexpat_pic.a
    >>
    >> // marc

    > I had been thinking about doing something like this.
    > I built and installed expat myself but the package installs still fail
    > for lack of expat. What is the difference between extracting libexpat
    > from the x11 tarball and building and installing expat from source?


    Thinking about this I think the answer is where the library is installed.
    The expat libs from the x11 tarball go in to /usr/lib.
    The expat lib I installed went into /usr/local/lib.

  4. Re: vim nox11 pkg problem

    Nutso OpenBSD User Dave writes:

    > > I had been thinking about doing something like this.
    > > I built and installed expat myself but the package installs still fail
    > > for lack of expat. What is the difference between extracting libexpat
    > > from the x11 tarball and building and installing expat from source?

    >
    > Thinking about this I think the answer is where the library is installed.
    > The expat libs from the x11 tarball go in to /usr/lib.
    > The expat lib I installed went into /usr/local/lib.


    Oh, packages.... You might have to put the libe in /usr/X11R6/lib
    for proper package operation. Not sure.

    // marc

  5. Re: vim nox11 pkg problem

    In article ,
    Marco S Hyman wrote:
    >Nutso OpenBSD User Dave writes:
    >
    >> > I had been thinking about doing something like this.
    >> > I built and installed expat myself but the package installs still fail
    >> > for lack of expat. What is the difference between extracting libexpat
    >> > from the x11 tarball and building and installing expat from source?

    >>
    >> Thinking about this I think the answer is where the library is installed.
    >> The expat libs from the x11 tarball go in to /usr/lib.
    >> The expat lib I installed went into /usr/local/lib.

    >
    >Oh, packages.... You might have to put the libe in /usr/X11R6/lib
    >for proper package operation. Not sure.
    >
    >// marc


    Probably shouldn't matter, unless some stuff did a libtool ****up and
    hardcoded the rpath to /usr/X11R6...

  6. Re: vim nox11 pkg problem

    In article ,
    Nutso OpenBSD User Dave wrote:
    >I had been thinking about doing something like this.
    >I built and installed expat myself but the package installs still fail
    >for lack of expat. What is the difference between extracting libexpat
    >from the x11 tarball and building and installing expat from source?


    Think a bit about what you're doing. Why is it an issue for you to
    install the expat that comes with X11 ? that way you don't have to
    compile anything.

    In any case, in OpenBSD, we tend to assume that people who compile stuff
    from source are smart enough to figure out these kinds of trivial issue,
    like, they're able to read cvs logs and figure things out, or read through
    archive and stuff like that (like, finding out the FAQ).

    Apparently, that's not your case, so stick to binaries, or make more efforts
    to learn things.

  7. Re: vim nox11 pkg problem

    Marc Espie wrote:
    > In article ,
    > Nutso OpenBSD User Dave wrote:
    >>I had been thinking about doing something like this.
    >>I built and installed expat myself but the package installs still fail
    >>for lack of expat. What is the difference between extracting libexpat
    >>from the x11 tarball and building and installing expat from source?

    >
    > Think a bit about what you're doing. Why is it an issue for you to
    > install the expat that comes with X11 ? that way you don't have to
    > compile anything.
    >
    > In any case, in OpenBSD, we tend to assume that people who compile stuff
    > from source are smart enough to figure out these kinds of trivial issue,
    > like, they're able to read cvs logs and figure things out, or read through
    > archive and stuff like that (like, finding out the FAQ).
    >
    > Apparently, that's not your case, so stick to binaries, or make more efforts
    > to learn things.


    Hi Mark!

    Glad to hear from you! Your current work with make -j looks interesting.
    I have stayed away from CVS as I currently have my hands full trying to
    figure out how my computer's bios is getting changed, but not by me.
    (All usb devices malfunction, dvd tray won't open, can't boot to bios,
    keyboard status lights always on.)
    I now have enough problems with the bios that I will probably have to
    replace the motherboard if I cannot fix them. Right now my best guess is
    that there is a security hole in X that allows a flash bios exploit.
    (keyboard lights are on for all virtual consoles of AMD computer, but
    work normally when the keyboard is attached to another computer).
    It will be interesting to see if X security on OpenBSD improves now that
    there is an OpenBSD-specific version of X.




  8. Re: vim nox11 pkg problem

    Oh, with your recent post name changes, I had not realized it was you...
    (though I should have, your madness is very characteristic).

    so you're still nuts, and paranoid, and think your installation got
    cracked, whereas it's incredibly more likely you're just incompetent
    and you set it up in such a way that it doesn't work.

    So, keep thinking people are out to get you, where Occam's razor would
    indicate all your problems come from your own misguided experiments.

    As far as I'm concerned, if you remember, I had given up on you.
    Your new address just means there's one extra address I need to add
    to my killfile.

    *PLONK*

  9. Re: vim nox11 pkg problem

    Marc Espie wrote:
    > Oh, with your recent post name changes, I had not realized it was you...
    > (though I should have, your madness is very characteristic).
    >
    > so you're still nuts, and paranoid, and think your installation got
    > cracked, whereas it's incredibly more likely you're just incompetent
    > and you set it up in such a way that it doesn't work.


    Ah, Mark, Mark, Mark.

    I had an NT computer flash bios altered about 12 years ago. Fortunately
    the fact that after all the ntfs drives were wiped out, the computer
    would not boot from the cdrom tipped me off to the possibility of a
    flash bios exploit. A quick call to Dell technical support
    helped me reflash the bios, after which the cdrom drive worked normally.
    That event was the one that got me to switch to OpenBSD.
    I suspect that something similar is going on now as a result of my having
    pissed off some unusually technically adept people with a politically
    incorrect opinion on a particularly sensitive subject.
    (8 known deaths connected with this subject so far).

    > So, keep thinking people are out to get you, where Occam's razor would
    > indicate all your problems come from your own misguided experiments.


    Speaking of Ockam's razor, have you thought about shaving off your beard?
    The beard looks fine, but I'd like to see your clean-shaven face.
    Maybe you could post an old picture of yourself.

    > As far as I'm concerned, if you remember, I had given up on you.
    > Your new address just means there's one extra address I need to add
    > to my killfile.
    >
    > *PLONK*

    I try to make it as easy as possible for people to kill my posts so
    they won't have apoplexy when they read the posts.

+ Reply to Thread