Alex wrote:
The glibc you have might just do fine. Just make a symlink from the one
you want to the one you have and try!
Jim Stapleton wrote:
The problem is I don't already have one, though there is a reply to my
other post that I'll be looking at in a few minutes, maybe something
will be
The problem is I don't already have one, though there is a reply to my
other post that I'll be looking at in a few minutes, maybe something
will be there. I updated the locate db, and tried to locate "glibc",
but I only found documentation, and a few bin (not lib) compat files
that look like they
Jim Stapleton wrote:
found it; uname -a, I fixed that line, now I just need to figure out
how to get the appropriate libs (glibc) into my compat dir... it isn't
in any of the linux compat ports.
Good stuff.
The glibc you have might just do fine. Just make a symlink from the one
you want to
found it; uname -a, I fixed that line, now I just need to figure out
how to get the appropriate libs (glibc) into my compat dir... it isn't
in any of the linux compat ports.
-Jim Stapleton
On 6/19/06, Alex Zbyslaw <[EMAIL PROTECTED]> wrote:
Jim Stapleton wrote:
> OK, that was easier than expec
Jim Stapleton wrote:
OK, that was easier than expected. These blobs appeared around
everything "linux", but don't look horribly useful. I'll check later
to see if I can find anything else. is there anything I should be
looking for aside from linux?
What you want to find is the error message yo
Ahh, it is, in fact, a binary sh.
The binary compatability looks pretty thourough, and it seems most of
the details in the compatability section for most apps seem to involve
making them check for BSD instead of linux, and ensuring they run in
compatability mode,
I'll run ktrace tonight. thanks.
OK, that was easier than expected. These blobs appeared around
everything "linux", but don't look horribly useful. I'll check later
to see if I can find anything else. is there anything I should be
looking for aside from linux?
$ wc -l kdumped
11413 kdumped
7851 rm RET fcntl 0
7851
Jim Stapleton wrote:
I don't know how to find out, except that the app is the Crossover
Office demo installer. I'd like to try to find a way to trick it into
running in the linux compatability mode of FreeBSD if I can.
So is there source code? Or is it some dumb binary rpm?
You could try run
"Jim Stapleton" <[EMAIL PROTECTED]> wrote:
> Basically, I have an application that doesn't want to run in FreeBSD,
> though it may still run given the compatability layer. I was wondering
> if there was some way to make the OS respond when it ran the
> application, that it was linux and not BSD.
On Sun, Jun 18, 2006 at 10:13:03PM +0100, Alex Zbyslaw wrote:
> That really rather depends on *how* the app is asking. If you can tell
> us that, we can almost certainly tell you how to fool it.
>
> Of course, if you have the source code, it should be easy as you can
> just comment out the test
I don't know how to find out, except that the app is the Crossover
Office demo installer. I'd like to try to find a way to trick it into
running in the linux compatability mode of FreeBSD if I can.
On 6/18/06, Alex Zbyslaw <[EMAIL PROTECTED]> wrote:
Jim Stapleton wrote:
> Basically, I have an a
Jim Stapleton wrote:
Basically, I have an application that doesn't want to run in FreeBSD,
though it may still run given the compatability layer. I was wondering
if there was some way to make the OS respond when it ran the
application, that it was linux and not BSD.
i.e.
==
Basically, I have an application that doesn't want to run in FreeBSD,
though it may still run given the compatability layer. I was wondering
if there was some way to make the OS respond when it ran the
application, that it was linux and not BSD.
i.e.
$ ./
13 matches
Mail list logo