Re: Linux Compatability

2009-03-20 Thread rasz

Paul B. Mahol wrote:

On 3/18/09, rasz raszo...@gmail.com wrote:
  

hi
i have 2 distinct questions, and first is, i installed a linux app
(binaries) and it failed
when run complaining that it needs a CPU with SSE instuctions enabled.
does anyone know what this is and related too?



For example, mplayer check for SSSE3 but it will fail even if your CPU
supports it because gcc that ships with freebsd (4.2.1) doesnt know about
SSSE3.

I dont know what's happening in your SSE case.
  
vaguely my first thoughts were that the app makes some checks for SSE 
but in the wrong place freebsd-wise.


i thought i'd try mailing the developers now, see if they have some insight.

thanks
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Linux Compatability

2009-03-19 Thread Paul B. Mahol
On 3/18/09, rasz raszo...@gmail.com wrote:
 hi
 i have 2 distinct questions, and first is, i installed a linux app
 (binaries) and it failed
 when run complaining that it needs a CPU with SSE instuctions enabled.
 does anyone know what this is and related too?

For example, mplayer check for SSSE3 but it will fail even if your CPU
supports it because gcc that ships with freebsd (4.2.1) doesnt know about
SSSE3.

I dont know what's happening in your SSE case.


-- 
Paul
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Linux Compatability

2009-03-18 Thread rasz

hi
i have 2 distinct questions, and first is, i installed a linux app 
(binaries) and it failed

when run complaining that it needs a CPU with SSE instuctions enabled.
does anyone know what this is and related too?
i am running 7.2-prerelease i386 with linux_base-fc4. the only setting i 
have is fallback_elf_brand=3 (no osrelease)

has anyone ever come across this?

2nd question, is the freebsd base (usr/src) documented anywhere, as to 
the programs it entirely contains? i thought developers handbook, but 
all i found is description of the directories in usr/src/ (unless i 
missed it elsewhere). besides that, is there any kind of database app in 
the base system no matter how compact/basic? if not, what would be the 
*closest* in ports?


thanks in advance for any info
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Linux Compatability

2009-03-18 Thread Ricardo Jesus

rasz wrote:

hi
i have 2 distinct questions, and first is, i installed a linux app 
(binaries) and it failed

when run complaining that it needs a CPU with SSE instuctions enabled.
does anyone know what this is and related too?
i am running 7.2-prerelease i386 with linux_base-fc4. the only setting i 
have is fallback_elf_brand=3 (no osrelease)

has anyone ever come across this?

2nd question, is the freebsd base (usr/src) documented anywhere, as to 
the programs it entirely contains? i thought developers handbook, but 
all i found is description of the directories in usr/src/ (unless i 
missed it elsewhere). besides that, is there any kind of database app in 
the base system no matter how compact/basic? if not, what would be the 
*closest* in ports?


thanks in advance for any info
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
freebsd-questions-unsubscr...@freebsd.org



Regarding the 2nd question...

As /usr/src contains the source of building the userland and kernel, if 
you can always man something that is interesting.


You can also do a man hier, but it will present a description of each 
directory content like the Developers Handbook (although more verbose).


There are also the Makefile and the actual source.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Linux Compatability

2009-03-18 Thread Wojciech Puchar

and it failed
when run complaining that it needs a CPU with SSE instuctions enabled.
does anyone know what this is and related too?


are you CPU SSE capable? if so, probably this app checks capabilities 
through /proc


add this to /etc/fstab
linprocfs   /compat/linux/proc  linprocfs   rw  0   0

and mount /compat/linux/proc

2nd question, is the freebsd base (usr/src) documented anywhere, as to the 
programs it entirely contains?


exactly those what gets installed :)
it contains sources of whole FreeBSD system (excluding ports).

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Linux Compatability

2009-03-18 Thread Frank Shute
On Wed, Mar 18, 2009 at 06:14:59PM +0100, rasz wrote:

 hi
 i have 2 distinct questions, and first is, i installed a linux app 
 (binaries) and it failed
 when run complaining that it needs a CPU with SSE instuctions enabled.
 does anyone know what this is and related too?

SSE is an Intel extension to the original x86 instruction set. You can
tell whether your CPU has got it by looking at dmesg(8). E.g mine has
it (and most modern processors do):

CPU: Intel(R) Core(TM)2 Duo CPU E6550  @ 2.33GHz (2333.34-MHz K8-class CPU)
  Origin = GenuineIntel  Id = 0x6fb  Stepping = 11
  
Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
  Features2=0xe3fdSSE3,RSVD2,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM
  AMD Features=0x20100800SYSCALL,NX,LM
  AMD Features2=0x1LAHF


 i am running 7.2-prerelease i386 with linux_base-fc4. the only setting i 
 have is fallback_elf_brand=3 (no osrelease)
 has anyone ever come across this?

Did you install your Linux app via ports? If not, then your mileage
with regards getting it going may vary.

 
 2nd question, is the freebsd base (usr/src) documented anywhere, as to 
 the programs it entirely contains? i thought developers handbook, but 
 all i found is description of the directories in usr/src/ (unless i 
 missed it elsewhere). besides that, is there any kind of database app in 
 the base system no matter how compact/basic? if not, what would be the 
 *closest* in ports?

You can grovel through /bin  /usr/bin to see what programs base installed.

I guess you're looking for an SQL database so you could give
databases/sqlite34 in ports a look but it's a bit difficult to
recommend anything without knowing your needs.

 
 thanks in advance for any info

Regards,

-- 

 Frank 


 Contact info: http://www.shute.org.uk/misc/contact.html 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Linux Compatability

2009-03-18 Thread Adam Vande More

rasz wrote:

hi
i have 2 distinct questions, and first is, i installed a linux app 
(binaries) and it failed

when run complaining that it needs a CPU with SSE instuctions enabled.
does anyone know what this is and related too?
i am running 7.2-prerelease i386 with linux_base-fc4. the only setting 
i have is fallback_elf_brand=3 (no osrelease)

has anyone ever come across this?

2nd question, is the freebsd base (usr/src) documented anywhere, as to 
the programs it entirely contains? i thought developers handbook, but 
all i found is description of the directories in usr/src/ (unless i 
missed it elsewhere). besides that, is there any kind of database app 
in the base system no matter how compact/basic? if not, what would be 
the *closest* in ports?


thanks in advance for any info
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
freebsd-questions-unsubscr...@freebsd.org


berkley db, sqlite, qdbm are in ports if you need more of a filesystems 
type db.  Nothing exists in the base system AFAIK.


--
Adam Vandemore
Systems Administrator
IMED Mobility
(605) 498-1610

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Linux Compatability

2009-03-18 Thread Maca Cassar
On Wed, Mar 18, 2009 at 6:52 PM, Adam Vande More a...@imedmobility.comwrote:

 rasz wrote:

 hi
 i have 2 distinct questions, and first is, i installed a linux app
 (binaries) and it failed
 when run complaining that it needs a CPU with SSE instuctions enabled.
 does anyone know what this is and related too?
 i am running 7.2-prerelease i386 with linux_base-fc4. the only setting i
 have is fallback_elf_brand=3 (no osrelease)
 has anyone ever come across this?

 2nd question, is the freebsd base (usr/src) documented anywhere, as to the
 programs it entirely contains? i thought developers handbook, but all i
 found is description of the directories in usr/src/ (unless i missed it
 elsewhere). besides that, is there any kind of database app in the base
 system no matter how compact/basic? if not, what would be the *closest* in
 ports?

 thanks in advance for any info
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to 
 freebsd-questions-unsubscr...@freebsd.org

  berkley db, sqlite, qdbm are in ports if you need more of a filesystems
 type db.  Nothing exists in the base system AFAIK.



thanks all for replies, but for the base system stuff i was trying to figure
out things ike what's under
/usr/src/sys/dev/ for instance, and say under dev/sound there is usb, pcm,
etc.
If i man usb i am guessing that only refers to main usb stuff. i got the
impression though that everything under sys/dev/ is likely kernel modules
and man sound was more appropriate, but no info there.

with the linux app, i have an SSE capable  CPU and linproc mounted , even
SSE2 i'm sure, and have  been running  some linux  apps no problem ,
including  ut2004-demo  from ports and even the full linux version if that
is relevant.

the app is not in ports, i just downloaded the installer and edited the
install script to go from /usr/local/bin to /compat/linux/usr/bin. I thought
at this point it was either not finding some libs or something similar but
have no clue as to what.

is there any hope for this to work? and should i be using the rpm installer
? rpm make any difference ?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: linux compatability question

2007-01-03 Thread Jim Stapleton

Thank you, I had to use a different linux library (linux-dri I think),
but it ended up working.

-Jim Stapleton

On 12/27/06, Boris Samorodov [EMAIL PROTECTED] wrote:

On Wed, 27 Dec 2006 14:02:39 -0500 Jim Stapleton wrote:

 I'm not sure what to do at this point, I'm trying to run a linux app
 (binary) that requires libGLU.so.1, and it's an x86 binary.

It requires a linux library.

 When I first ran it, it complained that the file libGLU.so.1 could not
 be found (it was in my /usr/X11R6/lib directory. I made a simlink with

And that is a FreeBSD one.

 that name to that file to /compat/linux/usr/X11R6/lib and now get this
 error:

 ./partiview: error while loading shared libraries: /lib/libGLU.so.1:
 ELF file OS ABI invalid

Yes, the linux app tries to load a FreeBSD library.

 This is on an i950 based notebook (integrated intel graphics), using
 the i810 and vga drivers in X. FreeBSD 6.1,  X is either 6.8 or 6.9

 Any suggestions?

Remove your simlink and install graphics/linux-libGLU.


WBR
--
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone  Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


linux compatability question

2006-12-27 Thread Jim Stapleton

I'm not sure what to do at this point, I'm trying to run a linux app
(binary) that requires libGLU.so.1, and it's an x86 binary.

When I first ran it, it complained that the file libGLU.so.1 could not
be found (it was in my /usr/X11R6/lib directory. I made a simlink with
that name to that file to /compat/linux/usr/X11R6/lib and now get this
error:

./partiview: error while loading shared libraries: /lib/libGLU.so.1:
ELF file OS ABI invalid

This is on an i950 based notebook (integrated intel graphics), using
the i810 and vga drivers in X. FreeBSD 6.1,  X is either 6.8 or 6.9

Any suggestions?
Thanks,
-Jim Stpleton
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: linux compatability question

2006-12-27 Thread Boris Samorodov
On Wed, 27 Dec 2006 14:02:39 -0500 Jim Stapleton wrote:

 I'm not sure what to do at this point, I'm trying to run a linux app
 (binary) that requires libGLU.so.1, and it's an x86 binary.

It requires a linux library.

 When I first ran it, it complained that the file libGLU.so.1 could not
 be found (it was in my /usr/X11R6/lib directory. I made a simlink with

And that is a FreeBSD one.

 that name to that file to /compat/linux/usr/X11R6/lib and now get this
 error:

 ./partiview: error while loading shared libraries: /lib/libGLU.so.1:
 ELF file OS ABI invalid

Yes, the linux app tries to load a FreeBSD library.

 This is on an i950 based notebook (integrated intel graphics), using
 the i810 and vga drivers in X. FreeBSD 6.1,  X is either 6.8 or 6.9

 Any suggestions?

Remove your simlink and install graphics/linux-libGLU.


WBR
-- 
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone  Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Linux Compatability and RPM

2003-06-26 Thread Schimcek, Derrick
when i try and install this arcserv rpm under linux compatablility mode it
gives me 0 bit files for all the asagent files.
i am running freebsd 5.0
and i have installed this same package on redhat linux 6.1 and 6.2 and it
works correctly
does anyone have an idea what i am doing wrong? 





SAMBA# ls
asagent.deb asagent.rpm uagent.deb  uagent.rpm
SAMBA# /compat/linux/bin/rpm -ivh asagent.rpm
Preparing...###
[100%]
   1:asagent###
[100%]
ln: creating symbolic link `/usr/bin/asagent' to `/usr/CYEagent/asagent':
File exists
ln: `/usr/CYEagent/asagent': File exists
chown: getting attributes of `/usr/bin/asagent': No such file or directory
chgrp: getting attributes of `/usr/bin/asagent': No such file or directory
sed: /usr/CYEagent/nls/asagent.C: No such file or directory
sed: /usr/CYEagent/nls/asagent.de: No such file or directory
sed: /usr/CYEagent/nls/asagent.fr: No such file or directory
sed: /usr/CYEagent/nls/asagent.ja_euc: No such file or directory
sed: /usr/CYEagent/nls/asagent.ja_sjis: No such file or directory
SAMBA#

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


linux compatability

2002-12-28 Thread Adam K Kirchhoff

Hey folks,

I'm noticing some odd behaviour with the linux compatability
recently.  I have this small gnome app called gnome-run.  It links against
a number of gnome libraries that I've copied from my linux partition over
to /compat/linux and put in the appropriate directories.

The problem is, when executing this app, the linker seems to try
and load the libaudiofile.so.0 file from my FreeBSD installation instead
of my /compat/linux installation.  When running gnome-run it only does
this for that one library (though other apps have shown this to be a
problem with other libraries such as libgmodule-2.0.so.0,
libglib-2.0.so.0, and libgobject-2.0.so.0)

This is what happens when I try to launch gnome-run from an
xterm:

[ adamk@sorrow ~ ]$ gnome-run
gnome-run: error while loading shared libraries:
/usr/local/lib/libaudiofile.so.0: ELF file OS ABI invalid

Well, of course the OS ABI is invalid.  The libaudiofile library
it's trying to load is for FreeBSD, not Linux.  But, if I move the
libaudiofile.so.0 file from /usr/local/lib to /usr/local/lib/old, and
try to launch gnome-run, everything works fine.  So, if the FreeBSD
version of the library isn't present, it then looks for the Linux version.

Any ideas what's going on or how to fix this?

Adam


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability

2002-12-28 Thread Mikko Työläjärvi
On Sat, 28 Dec 2002, Adam K Kirchhoff wrote:

 Hey folks,

   I'm noticing some odd behaviour with the linux compatability
 recently.  I have this small gnome app called gnome-run.  It links against
 a number of gnome libraries that I've copied from my linux partition over
 to /compat/linux and put in the appropriate directories.

   The problem is, when executing this app, the linker seems to try
 and load the libaudiofile.so.0 file from my FreeBSD installation instead
 of my /compat/linux installation.  When running gnome-run it only does
 this for that one library (though other apps have shown this to be a
 problem with other libraries such as libgmodule-2.0.so.0,
 libglib-2.0.so.0, and libgobject-2.0.so.0)

   This is what happens when I try to launch gnome-run from an
 xterm:

 [ adamk@sorrow ~ ]$ gnome-run
 gnome-run: error while loading shared libraries:
 /usr/local/lib/libaudiofile.so.0: ELF file OS ABI invalid

   Well, of course the OS ABI is invalid.  The libaudiofile library
 it's trying to load is for FreeBSD, not Linux.  But, if I move the
 libaudiofile.so.0 file from /usr/local/lib to /usr/local/lib/old, and
 try to launch gnome-run, everything works fine.  So, if the FreeBSD
 version of the library isn't present, it then looks for the Linux version.

   Any ideas what's going on or how to fix this?

Run /compat/linux/sbin/ldconfig.  That should update the path cache
of the (linux) dynamic linker.  I assume the permissions on the libs
already are reasonable.

   $.02,
   /Mikko


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability

2002-12-28 Thread Adam K Kirchhoff

On Sat, 28 Dec 2002, [ISO-8859-1] Mikko Työläjärvi wrote:

 On Sat, 28 Dec 2002, Adam K Kirchhoff wrote:

  Hey folks,
 
  I'm noticing some odd behaviour with the linux compatability
  recently.  I have this small gnome app called gnome-run.  It links against
  a number of gnome libraries that I've copied from my linux partition over
  to /compat/linux and put in the appropriate directories.
 
  The problem is, when executing this app, the linker seems to try
  and load the libaudiofile.so.0 file from my FreeBSD installation instead
  of my /compat/linux installation.  When running gnome-run it only does
  this for that one library (though other apps have shown this to be a
  problem with other libraries such as libgmodule-2.0.so.0,
  libglib-2.0.so.0, and libgobject-2.0.so.0)
 
  This is what happens when I try to launch gnome-run from an
  xterm:
 
  [ adamk@sorrow ~ ]$ gnome-run
  gnome-run: error while loading shared libraries:
  /usr/local/lib/libaudiofile.so.0: ELF file OS ABI invalid
 
  Well, of course the OS ABI is invalid.  The libaudiofile library
  it's trying to load is for FreeBSD, not Linux.  But, if I move the
  libaudiofile.so.0 file from /usr/local/lib to /usr/local/lib/old, and
  try to launch gnome-run, everything works fine.  So, if the FreeBSD
  version of the library isn't present, it then looks for the Linux version.
 
  Any ideas what's going on or how to fix this?

 Run /compat/linux/sbin/ldconfig.  That should update the path cache
 of the (linux) dynamic linker.

Didn't help :-(

 I assume the permissions on the libs already are reasonable.

[ adamk@sorrow ~ ]$ ls -l /compat/linux/usr/lib/libaudiofile.so.0*
lrwxr-xr-x  1 root  wheel  21 Dec 28 14:33
/compat/linux/usr/lib/libaudiofile.so.0 - libaudiofile.so.0.0.2
-rwxr-xr-x  1 root  wheel  158396 Dec 28 14:33
/compat/linux/usr/lib/libaudiofile.so.0.0.2

Solved it!

It's LD_LIBRARY_PATH.  If you have the same FreeBSD library in your
LD_LIBRARY_PATH, it tries to use that library instead of the linux one :-)

Mikko, thanks for your help.  It was your tip on permissions that got me
to try the app as root.  When I saw that they worked as root, I realized
it had to be something in my environment.

Adam


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: Linux Compatability and compiling linux program - problem with...

2002-10-16 Thread John Mills

Hello -

On Tue, 15 Oct 2002, joe wrote:

 I am atrying to compile a linux program under FreeBSD 4.7-STABLE.  I 
 have installed linux_base but seem to be missing a number of files, 
 specifically header files.  

DISCLAIMER - this is from a FreeBSD newbie.

If the program is not Linux-specific (or specific to linux-only
libraries), you might try using generic sources and running 'configure',
then compiling instead of building from Linux sources.

The negative is that the app would not be automagically managed - you
would have to know it was there, look for upgrades, etc.

The missing headers are things I would expect in the Linux kernel sources,
if that gives you any leads.

 SoI obviously don't have the header files... Do I need to install the 
 entire linux src?

There may be a port of just the headers. That should be enough of the
sources to compile. You would need suitable a suitable intermediate
library to link, which takes you beyond my knowledge here. (That point may
actually have passed a few paragraphs ago. 8+P)

 - John Mills


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Linux Compatability and compiling linux program - problem with...

2002-10-15 Thread joe


I am atrying to compile a linux program under FreeBSD 4.7-STABLE.  I 
have installed linux_base but seem to be missing a number of files, 
specifically header files.  

Here's a portion of the errors when making the program (by the way, it's 
cdparanoia.  I am following the lead of a discussion this last week 
suggesting the atapicam kernel driver will allow cdparanoia to 
work...So I managed to get rebuild the kernel with the driver. Next 
step is to build the application)

In file included from scan_devices.c:18:
low_interface.h:28: linux/major.h: No such file or directory
low_interface.h:29: linux/version.h: No such file or directory
low_interface.h:45: scsi/sg.h: No such file or directory
low_interface.h:46: scsi/scsi.h: No such file or directory
low_interface.h:48: linux/cdrom.h: No such file or directory
low_interface.h:49: linux/major.h: No such file or directory
In file included from scan_devices.c:20:
utils.h:1: endian.h: No such file or directory

SoI obviously don't have the header files... Do I need to install the 
entire linux src? I am stuck at this point.  Is there a port which 
provides this source?


-- 

Joe
-
We have been silent witnesses of evil deeds...
Will our inward power of resistance 
be strong enough for us to find our way back?
   - Dietrich Bonhoeffer

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken

2002-07-25 Thread Jud

7/25/2002 12:49:49 AM, Dan Nelson [EMAIL PROTECTED] 
wrote:

In the last episode (Jul 24), Eric Dedrick said:
 Okay, we got it.  I had to run linux_base-6 and *not* any type of
 linux_base (7.1) whatsoever.
 
 Since it would appear that running linux_base-6 and linux_base(7.1) 
are
 mutually exclusive (after all, they run non-compatable versions of 
glibc),
 here's a question:  I have some software I can't upgrade 
(proprietary)
 that requires linux_base-6.  If I install linux software from the ports,
 is it going to require linux_base 7.1?

You should be able to install both ports at once.
 
 Here was the hangup:  In order to install linux_base-6, svr4.ko had to 
be
 unloaded from the kernel.  Once linux_base-6 was installed, svr4.ko 
could
 be loaded again and things still worked just fine.  At least that's what I
 think the solution was.
 
 At any rate, I can run my linux binaries now, though I am still 
somewhat
 dis-satisfied.  Why do things break under 7.1 and not 6?

Dunno. It looks like all your linux binaries got branded to the wrong
type (svr4 instead of Linux), so the svr4 layer grabbed them first if
it was loaded.  Try this:

find /compat/linux -type f -perm +a+x -ls | xargs brandelf -t Linux

, which should rebrand all the Linux binaries to Linux.  It shouldn't
be necessary though.

-- 
   Dan Nelson
   [EMAIL PROTECTED]


I changed from 6 to 7.1 when -STABLE did using portupgrade, and 
managed not to break anything in the system, including Opera and 
Acrobat5.  Don't know whether it was just dumb luck, but as a general 
cure for running two versions of any port, especially linux_base, I tend 
to favor it.

Jud



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken

2002-07-25 Thread Eric Dedrick

 Just to clarify, I mean that using portupgrade will
 (hopefully, and in my experience, almost always) take
 care of your dependencies during the upgrade process,
 thus saving you from the IMO less preferable
 alternative of running more than one version of a
 port.

 Have you tried portupgrade with linux_base (after a
 backup of the old linux_base port skeleton and
 installation of the new one) to see whether Maple
 is happy?

Yup.  portupgrading eliminates ld-linux.so.1, required by maple.  Thanks
for the suggestion, though.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken

2002-07-25 Thread Dan Nelson

In the last episode (Jul 25), Eric Dedrick said:
  Just to clarify, I mean that using portupgrade will (hopefully, and
  in my experience, almost always) take care of your dependencies
  during the upgrade process, thus saving you from the IMO less
  preferable alternative of running more than one version of a port.
 
  Have you tried portupgrade with linux_base (after a backup of the
  old linux_base port skeleton and installation of the new one) to
  see whether Maple is happy?
 
 Yup.  portupgrading eliminates ld-linux.so.1, required by maple. 
 Thanks for the suggestion, though.

Hm.  It shouldn't, since linux_base and linux_base-6 are different
ports.  Unless you had the RH6 version of linux_base, then installed
linux_base-6, then upgraded linux_base to the RH7 version.  The upgrade
of linux_base would have effectively wiped out the linux_base-6
install.

-- 
Dan Nelson
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken?

2002-07-24 Thread Adam Weinberger

i'm going to have to ask that anybody else who knows please step in
here...

to know where it's dying, i'd need to see a kernel trace, isolating the
system call that it's b0rking on.

have you changed any other options in your kernel?

-Adam


is it still complaining that it cannot load the so.2?
 (07.23.2002 @ 2237 PST): Eric Dedrick said, in 2.3K: 
 Okay, I just installed linux_base 7.1 from the ports and linux
 compatability is still broken (everything is failing with bad system
 call signal 12).  linux.ko is loaded, compatability mode enabled.  What
 do you suggest now?
 
 On Tue, 23 Jul 2002, Adam Weinberger wrote:
 
  you have to uninstall the old version of linux_base that you have. if
  you don't know how to do that, you can always:
 
  install /usr/ports/sysutils/portupgrade
 
  then, do:
  portupgrade -o emulators/linux_base linux_base-\*
 
  that should take care of that.
 
  -Adam
 
 
   (07.23.2002 @ 2024 PST): Eric Dedrick said, in 1.4K: 
i hope you have a semi-recent ports tree, because you need
linux_base-7.1.
  
   installing linux_base 7.1 from the ports gives me the following error.
   Advice?  Thanks.
  
   ---
  
   (several screen fulls of the same type of stuff)...
   file /usr/share/zoneinfo/right/US/Eastern from install of
   glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
   file /usr/share/zoneinfo/right/US/Hawaii from install of
   glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
   file /usr/share/zoneinfo/right/US/Indiana-Starke from install of
   glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
   file /usr/share/zoneinfo/right/US/Michigan from install of
   glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
   file /usr/share/zoneinfo/right/US/Mountain from install of
   glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
   file /usr/share/zoneinfo/right/US/Pacific from install of
   glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
   file /usr/share/zoneinfo/right/W-SU from install of glibc-common-2.2.2-10
   conflicts with file from package glibc-2.1.2-11
   file /usr/bin/catchsegv from install of glibc-common-2.2.2-10 conflicts
   with file from package glibc-2.1.2-11
   *** Error code 1
  
   Stop in /usr/ports/emulators/linux_base.
  
  
  
  
   To Unsubscribe: send mail to [EMAIL PROTECTED]
   with unsubscribe freebsd-questions in the body of the message
  
   end of Re: linux compatability broken? from Eric Dedrick 
 
 
  --
  Oh good, my dog found the chainsaw.
  -Lilo, Lilo  Stitch
  Adam Weinberger
  [EMAIL PROTECTED]
  http://vectors.cx
 
 
 end of Re: linux compatability broken? from Eric Dedrick 


--
Oh good, my dog found the chainsaw.
-Lilo, Lilo  Stitch
Adam Weinberger
[EMAIL PROTECTED]
http://vectors.cx


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken?

2002-07-24 Thread Eric Dedrick

Yup.  See the new attachements.  Again, thank you so much for the help.

On Wed, 24 Jul 2002, Dan Nelson wrote:

 In the last episode (Jul 24), Eric Dedrick said:
   i'm going to have to ask that anybody else who knows please step in
   here...
  
   to know where it's dying, i'd need to see a kernel trace, isolating the
   system call that it's b0rking on.
 
  I've attached a couple.  Thanks.

 Try running ktrace -i program, then kdump -m128.  All you traced here
 is the shell script, and the trace of opera itself is the more
 interesting one.  Also maybe install the linux_kdump port, and run that
 instead of regular kdump.   The trace of the Linux binary will be more
 readable that way.


 --
   Dan Nelson
   [EMAIL PROTECTED]



settimeofday(0xbfbff364,0x0,0x0) ERR#9 'Bad file descriptor'
open(‰ÆƒÄƒþÿ„Ä,0x286ae113,00)   ERR#22 'Invalid argument'
read(0x286a9657,0x16,0xbfbff4f4) ERR#9 'Bad file descriptor'
close(22)ERR#9 'Bad file descriptor'
SIGNAL 12
SIGNAL 12
Process stopped because of:  16
process exit, rval = 140


 11590 ktrace   RET   ktrace 0
 11590 ktrace   CALL  execve(0xbfbff8be,0xbfbff7d4,0xbfbff7dc)
 11590 ktrace   NAMI  /usr/local/opera/lib/opera/5.05_tp1/opera-static
 11590 ktrace   NAMI  /compat/svr4/lib/ld-linux.so.2
 11590 opera-static RET   execve 0
 11590 opera-static CALL  settimeofday(0xbfbff364,0,0)
 11590 opera-static RET   settimeofday -1 errno 9 Bad file descriptor
 11590 opera-static CALL  open(0x286a963a,0x286ae113,0)
 11590 opera-static RET   open -1 errno 22 Invalid argument
 11590 opera-static CALL  read(0x286a9657,0x16,0xbfbff4f4)
 11590 opera-static RET   read -1 errno 9 Bad file descriptor
 11590 opera-static CALL  close(0x16)
 11590 opera-static RET   close -1 errno 9 Bad file descriptor
 11590 opera-static CALL  old.killpg
 11590 opera-static PSIG  SIGSYS SIG_DFL
 11590 opera-static NAMI  opera-static.core


settimeofday(0xbfbff378,0x0,0x0) ERR#9 'Bad file descriptor'
open(‰ÆƒÄƒþÿ„Ä,0x28099113,00)   ERR#22 'Invalid argument'
read(0x28094657,0x16,0xbfbff508) ERR#9 'Bad file descriptor'
close(22)ERR#9 'Bad file descriptor'
SIGNAL 12
SIGNAL 12
Process stopped because of:  16
process exit, rval = 140


 11596 ktrace   RET   ktrace 0
 11596 ktrace   CALL  execve(0xbfbff8ce,0xbfbff7e4,0xbfbff7ec)
 11596 ktrace   NAMI  /usr/local/mozilla/mozilla-bin
 11596 ktrace   NAMI  /compat/svr4/lib/ld-linux.so.2
 11596 mozilla-bin RET   execve 0
 11596 mozilla-bin CALL  settimeofday(0xbfbff378,0,0)
 11596 mozilla-bin RET   settimeofday -1 errno 9 Bad file descriptor
 11596 mozilla-bin CALL  open(0x2809463a,0x28099113,0)
 11596 mozilla-bin RET   open -1 errno 22 Invalid argument
 11596 mozilla-bin CALL  read(0x28094657,0x16,0xbfbff508)
 11596 mozilla-bin RET   read -1 errno 9 Bad file descriptor
 11596 mozilla-bin CALL  close(0x16)
 11596 mozilla-bin RET   close -1 errno 9 Bad file descriptor
 11596 mozilla-bin CALL  old.killpg
 11596 mozilla-bin PSIG  SIGSYS SIG_DFL
 11596 mozilla-bin NAMI  mozilla-bin.core



Re: linux compatability broken?

2002-07-24 Thread Adam Weinberger

ok. from /usr/src/sys/i386/linux/syscalls.master:
79  NOPROTO LINUX   { int settimeofday(struct timeval *tp, \
struct timezone *tzp); }

it's getting passed a memory address, and then 0. what timezone do you
have your system set to?

-Adam


 (07.24.2002 @ 1127 PST): Eric Dedrick said, in 5.2K: 
 Yup.  See the new attachements.  Again, thank you so much for the help.
 
 On Wed, 24 Jul 2002, Dan Nelson wrote:
 
  In the last episode (Jul 24), Eric Dedrick said:
i'm going to have to ask that anybody else who knows please step in
here...
   
to know where it's dying, i'd need to see a kernel trace, isolating the
system call that it's b0rking on.
  
   I've attached a couple.  Thanks.
 
  Try running ktrace -i program, then kdump -m128.  All you traced here
  is the shell script, and the trace of opera itself is the more
  interesting one.  Also maybe install the linux_kdump port, and run that
  instead of regular kdump.   The trace of the Linux binary will be more
  readable that way.
 
 
  --
  Dan Nelson
  [EMAIL PROTECTED]
 

 settimeofday(0xbfbff364,0x0,0x0)   ERR#9 'Bad file descriptor'
 open(‰ÆƒÄƒþÿ„Ä,0x286ae113,00) ERR#22 'Invalid argument'
 read(0x286a9657,0x16,0xbfbff4f4)   ERR#9 'Bad file descriptor'
 close(22)  ERR#9 'Bad file descriptor'
 SIGNAL 12
 SIGNAL 12
 Process stopped because of:  16
 process exit, rval = 140

  11590 ktrace   RET   ktrace 0
  11590 ktrace   CALL  execve(0xbfbff8be,0xbfbff7d4,0xbfbff7dc)
  11590 ktrace   NAMI  /usr/local/opera/lib/opera/5.05_tp1/opera-static
  11590 ktrace   NAMI  /compat/svr4/lib/ld-linux.so.2
  11590 opera-static RET   execve 0
  11590 opera-static CALL  settimeofday(0xbfbff364,0,0)
  11590 opera-static RET   settimeofday -1 errno 9 Bad file descriptor
  11590 opera-static CALL  open(0x286a963a,0x286ae113,0)
  11590 opera-static RET   open -1 errno 22 Invalid argument
  11590 opera-static CALL  read(0x286a9657,0x16,0xbfbff4f4)
  11590 opera-static RET   read -1 errno 9 Bad file descriptor
  11590 opera-static CALL  close(0x16)
  11590 opera-static RET   close -1 errno 9 Bad file descriptor
  11590 opera-static CALL  old.killpg
  11590 opera-static PSIG  SIGSYS SIG_DFL
  11590 opera-static NAMI  opera-static.core

 settimeofday(0xbfbff378,0x0,0x0)   ERR#9 'Bad file descriptor'
 open(‰ÆƒÄƒþÿ„Ä,0x28099113,00) ERR#22 'Invalid argument'
 read(0x28094657,0x16,0xbfbff508)   ERR#9 'Bad file descriptor'
 close(22)  ERR#9 'Bad file descriptor'
 SIGNAL 12
 SIGNAL 12
 Process stopped because of:  16
 process exit, rval = 140

  11596 ktrace   RET   ktrace 0
  11596 ktrace   CALL  execve(0xbfbff8ce,0xbfbff7e4,0xbfbff7ec)
  11596 ktrace   NAMI  /usr/local/mozilla/mozilla-bin
  11596 ktrace   NAMI  /compat/svr4/lib/ld-linux.so.2
  11596 mozilla-bin RET   execve 0
  11596 mozilla-bin CALL  settimeofday(0xbfbff378,0,0)
  11596 mozilla-bin RET   settimeofday -1 errno 9 Bad file descriptor
  11596 mozilla-bin CALL  open(0x2809463a,0x28099113,0)
  11596 mozilla-bin RET   open -1 errno 22 Invalid argument
  11596 mozilla-bin CALL  read(0x28094657,0x16,0xbfbff508)
  11596 mozilla-bin RET   read -1 errno 9 Bad file descriptor
  11596 mozilla-bin CALL  close(0x16)
  11596 mozilla-bin RET   close -1 errno 9 Bad file descriptor
  11596 mozilla-bin CALL  old.killpg
  11596 mozilla-bin PSIG  SIGSYS SIG_DFL
  11596 mozilla-bin NAMI  mozilla-bin.core

 end of Re: linux compatability broken? from Eric Dedrick 


--
Oh good, my dog found the chainsaw.
-Lilo, Lilo  Stitch
Adam Weinberger
[EMAIL PROTECTED]
http://vectors.cx


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken?

2002-07-24 Thread Adam Weinberger

oh wow i didn't notice that one.

run /compat/linux/sbin/ldconfig -p and see where it's looking for
ld-linux.so.2. the line should be something like:
ld-linux.so.2 (ELF) = /lib/ld-linux.so.2

but yeah, rebuild that kernel and modules!

-Adam


 (07.24.2002 @ 1143 PST): Dan Nelson said, in 0.5K: 
 In the last episode (Jul 24), Eric Dedrick said:
  Yup.  See the new attachements.  Again, thank you so much for the help.
 
  11590 ktrace   NAMI  /compat/svr4/lib/ld-linux.so.2
 
 Why does it think the binary is an svr4 binary?  That's why the
 syscalls still don't match and you get SIGSYS after a while.  Something
 sounds really out of sync.  Try rebuilding your kernel and modules, and
 make sure they install into the right places.
 
 -- 
   Dan Nelson
   [EMAIL PROTECTED]
 
 end of Re: linux compatability broken? from Dan Nelson 


--
Oh good, my dog found the chainsaw.
-Lilo, Lilo  Stitch
Adam Weinberger
[EMAIL PROTECTED]
http://vectors.cx


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken?

2002-07-24 Thread Eric Dedrick

 oh wow i didn't notice that one.

 run /compat/linux/sbin/ldconfig -p and see where it's looking for
 ld-linux.so.2. the line should be something like:
 ld-linux.so.2 (ELF) = /lib/ld-linux.so.2

 but yeah, rebuild that kernel and modules!

I've rebuilt them so many times figuring that was the problem that I'm
getting kind of sick of it.  Everything is fresh.  The whole kernel and OS
is what was on CVS stable as of about noon yesterday.  Unless there is a
patch or something that's not going to do any good.

$ /compat/linux/sbin/ldconfig -p
(other suff)...
ld-linux.so.2 (ELF) = /lib/ld-linux.so.2



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken?

2002-07-24 Thread Adam Weinberger

uhmm you can always kludge by ln -s /compat/linux /compat/svr4 ::)

just curious... do you have anything in /compat/svr4?

-Adam


 (07.24.2002 @ 1210 PST): Eric Dedrick said, in 0.6K: 
  oh wow i didn't notice that one.
 
  run /compat/linux/sbin/ldconfig -p and see where it's looking for
  ld-linux.so.2. the line should be something like:
  ld-linux.so.2 (ELF) = /lib/ld-linux.so.2
 
  but yeah, rebuild that kernel and modules!
 
 I've rebuilt them so many times figuring that was the problem that I'm
 getting kind of sick of it.  Everything is fresh.  The whole kernel and OS
 is what was on CVS stable as of about noon yesterday.  Unless there is a
 patch or something that's not going to do any good.
 
 $ /compat/linux/sbin/ldconfig -p
 (other suff)...
 ld-linux.so.2 (ELF) = /lib/ld-linux.so.2
 
 
 end of Re: linux compatability broken? from Eric Dedrick 


--
Oh good, my dog found the chainsaw.
-Lilo, Lilo  Stitch
Adam Weinberger
[EMAIL PROTECTED]
http://vectors.cx


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken?

2002-07-24 Thread Eric Dedrick

  11590 ktrace   NAMI  /compat/svr4/lib/ld-linux.so.2

 Why does it think the binary is an svr4 binary?  That's why the
 syscalls still don't match and you get SIGSYS after a while.  Something
 sounds really out of sync.

That's kind of what I thought.  I tried re-brandelf'ing my version of
netscape just to make sure it was doing linux and not svr4, and it just
complained about something else.  I also don't think that linux-netscape
is elf format.  I don't know that one can brand file types other than elf.
Besides, it worked fine before, the brand on these linux files is what it
should be I assume.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken?

2002-07-24 Thread Eric Dedrick

 uhmm you can always kludge by ln -s /compat/linux /compat/svr4 ::)

 just curious... do you have anything in /compat/svr4?

A symbolic link to /usr/compat/linux/lib.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken?

2002-07-24 Thread Eric Dedrick

 but then it's looking for /usr/compat/linux/lib/lib/ld-linux.so.2

 make /compat/svr4 - /compat/linux

No change.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken?

2002-07-24 Thread Dan Nelson

In the last episode (Jul 24), Eric Dedrick said:
  i'm going to have to ask that anybody else who knows please step in
  here...
 
  to know where it's dying, i'd need to see a kernel trace, isolating the
  system call that it's b0rking on.
 
 I've attached a couple.  Thanks.

Try running ktrace -i program, then kdump -m128.  All you traced here
is the shell script, and the trace of opera itself is the more
interesting one.  Also maybe install the linux_kdump port, and run that
instead of regular kdump.   The trace of the Linux binary will be more
readable that way.


-- 
Dan Nelson
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken?

2002-07-24 Thread Dan Nelson

In the last episode (Jul 24), Eric Dedrick said:
 Yup.  See the new attachements.  Again, thank you so much for the help.

 11590 ktrace   NAMI  /compat/svr4/lib/ld-linux.so.2

Why does it think the binary is an svr4 binary?  That's why the
syscalls still don't match and you get SIGSYS after a while.  Something
sounds really out of sync.  Try rebuilding your kernel and modules, and
make sure they install into the right places.

-- 
Dan Nelson
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken

2002-07-24 Thread Eric Dedrick

 If you don't load the svr4 module (and don't have options COMPAT_SVR4
 in your config file), it shouldn't look in /compat/svr4.  Try removing
 those and see what happens.

 Symlinking /compat/svr4 to /compat/linux won't do a thing, since the
 syscalls don't match.

I get:

$ opera
ELF interpreter /compat/svr4/lib/ld-linux.so.2 not found
[1]   11964 Abort trap


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken

2002-07-24 Thread Eric Dedrick

  $ opera
  ELF interpreter /compat/svr4/lib/ld-linux.so.2 not found
  [1]   11964 Abort trap

 Now that's really confusing.  Without the svr4 module loaded, the
 string /compat/svr4 should not exist anywhere in the kernel (it's
 defined in /sys/svr4/svr4_sysvec.c).  There is simply no way you should
 get that error message.  Are you _sure_ you're booting a rebuilt
 kernel?  Try rm -rf'ing the compile directory and build again.  What
 does 'uname -v' print?

I am totally sure that I have a new kernel.  I did it with the make world,
make buildkernel KERNCONF=xxx; make installkernel KERNCONF=xxx; make
installworld sequence followed by mergemaster to get the /etc files right.

Let's see

$ uname -v

FreeBSD 4.6-STABLE #4: Tue Jul 23 21:13:42 EST 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/DSL-146-127-2

That looks like a pretty recent kernel to me.

$ kldstat
Id Refs AddressSize Name
 15 0xc010 238690   kernel
 21 0xc0944000 2000 green_saver.ko
 31 0xc0947000 14000linux.ko
 41 0xc0974000 3000 streams.ko
 51 0xc0977000 11000svr4.ko

I've also unloaded the svr4.ko module and when I do that I get a whole new
realm of complaints.  Mostly a whole bunch of libraries that can't be
found.  Instead of
[1]   21021 Bad system call (core dumped)
we get
/usr/local/opera/lib/opera/5.05_tp1/opera-static: error while loading
shared libraries: libjpeg.so.62: cannot load shared object file: No such
file or directory

There are also a whole bunch of other libraries missing from
/compat/linux.  Some programs want ld-linux.so.1, and another wants
libdl.so.1.  None of these exist in /compat with the linux-7.1 install.

Still, the nature of the problems changed.  Maybe I can't run svr4 and
linux at the same time?  (I've only used svr4 compatability a couple times
anyway.)  A bug like that would explain some of the odd behaviour.  But
what should I do about the libraries missing from linux 7.1, like
ld-linux.so.1 and stuff?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken

2002-07-24 Thread Eric Dedrick

 Getting a bit better, but now it looks like it thinks the binary is a
 native BSD one instead of Linux.  If you run file
 /usr/local/opera/lib/opera/5.05_tp1/opera-static, what does it print?

$ file /usr/local/opera/lib/opera/5.05_tp1/opera-static
/usr/local/opera/lib/opera/5.05_tp1/opera-static: ELF 32-bit LSB
executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared
libs), stripped


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken

2002-07-24 Thread Dan Nelson

In the last episode (Jul 24), Eric Dedrick said:
  Getting a bit better, but now it looks like it thinks the binary is a
  native BSD one instead of Linux.  If you run file
  /usr/local/opera/lib/opera/5.05_tp1/opera-static, what does it print?
 
 $ file /usr/local/opera/lib/opera/5.05_tp1/opera-static
 /usr/local/opera/lib/opera/5.05_tp1/opera-static: ELF 32-bit LSB
 executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared
 libs), stripped

Try running brandelf -t Linux /usr/local/opera/lib/opera/5.05_tp1/opera-static
and see what happens, or sysctl kern.fallback_elf_brand=3

-- 
Dan Nelson
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken?

2002-07-23 Thread Roman Neuhauser

 Date: Tue, 23 Jul 2002 10:52:49 -0500 (EST)
 From: Eric Dedrick [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: linux compatability broken?
 
 I recently made a few kernel changes so I remade world.
 
 It would seem that linux compatability is now broken.  At first things
 were complaining about the fact that ld-linux.so.2 got moved.  After I
 made symbolic links things failed with a bad system call signal 12.
 
 Weren't all of my modules, including the compatibility ones, updated with
 make world?

barring a knob in (IIRC) /etc/make.conf, kernel modules are built
and installed during make buildkernel and make installkernel,
respectively

-- 
FreeBSD 4.6-STABLE
7:44PM up 7 days, 6:03, 8 users, load averages: 0.03, 0.02, 0.00

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken?

2002-07-23 Thread Eric Dedrick

  Date: Tue, 23 Jul 2002 10:52:49 -0500 (EST)
  From: Eric Dedrick [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Subject: linux compatability broken?
 
  I recently made a few kernel changes so I remade world.
 
  It would seem that linux compatability is now broken.  At first things
  were complaining about the fact that ld-linux.so.2 got moved.  After I
  made symbolic links things failed with a bad system call signal 12.
 
  Weren't all of my modules, including the compatibility ones, updated with
  make world?

 barring a knob in (IIRC) /etc/make.conf, kernel modules are built
 and installed during make buildkernel and make installkernel,
 respectively

Okay, so any guesses why my linux compatiability would break?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken?

2002-07-23 Thread Roman Neuhauser

 Date: Tue, 23 Jul 2002 16:35:38 -0500 (EST)
 From: Eric Dedrick [EMAIL PROTECTED]
 To: Roman Neuhauser [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Subject: Re: linux compatability broken?
 
   Date: Tue, 23 Jul 2002 10:52:49 -0500 (EST)
   From: Eric Dedrick [EMAIL PROTECTED]
   To: [EMAIL PROTECTED]
   Subject: linux compatability broken?
  
   I recently made a few kernel changes so I remade world.
  
   It would seem that linux compatability is now broken.  At first things
   were complaining about the fact that ld-linux.so.2 got moved.  After I
   made symbolic links things failed with a bad system call signal 12.
  
   Weren't all of my modules, including the compatibility ones, updated with
   make world?
 
  barring a knob in (IIRC) /etc/make.conf, kernel modules are built
  and installed during make buildkernel and make installkernel,
  respectively
 
 Okay, so any guesses why my linux compatiability would break?

no idea, really. i don't use any linux apps atm.

-- 
FreeBSD 4.6-STABLE
12:08AM up 7 days, 10:27, 7 users, load averages: 0.05, 0.10, 0.07

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken?

2002-07-23 Thread Eric Dedrick

 i hope you have a semi-recent ports tree, because you need
 linux_base-7.1.

installing linux_base 7.1 from the ports gives me the following error.
Advice?  Thanks.

---

(several screen fulls of the same type of stuff)...
file /usr/share/zoneinfo/right/US/Eastern from install of
glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
file /usr/share/zoneinfo/right/US/Hawaii from install of
glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
file /usr/share/zoneinfo/right/US/Indiana-Starke from install of
glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
file /usr/share/zoneinfo/right/US/Michigan from install of
glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
file /usr/share/zoneinfo/right/US/Mountain from install of
glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
file /usr/share/zoneinfo/right/US/Pacific from install of
glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
file /usr/share/zoneinfo/right/W-SU from install of glibc-common-2.2.2-10
conflicts with file from package glibc-2.1.2-11
file /usr/bin/catchsegv from install of glibc-common-2.2.2-10 conflicts
with file from package glibc-2.1.2-11
*** Error code 1

Stop in /usr/ports/emulators/linux_base.




To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken?

2002-07-23 Thread Adam Weinberger

you have to uninstall the old version of linux_base that you have. if
you don't know how to do that, you can always:

install /usr/ports/sysutils/portupgrade

then, do:
portupgrade -o emulators/linux_base linux_base-\*

that should take care of that.

-Adam


 (07.23.2002 @ 2024 PST): Eric Dedrick said, in 1.4K: 
  i hope you have a semi-recent ports tree, because you need
  linux_base-7.1.
 
 installing linux_base 7.1 from the ports gives me the following error.
 Advice?  Thanks.
 
 ---
 
 (several screen fulls of the same type of stuff)...
 file /usr/share/zoneinfo/right/US/Eastern from install of
 glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
 file /usr/share/zoneinfo/right/US/Hawaii from install of
 glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
 file /usr/share/zoneinfo/right/US/Indiana-Starke from install of
 glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
 file /usr/share/zoneinfo/right/US/Michigan from install of
 glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
 file /usr/share/zoneinfo/right/US/Mountain from install of
 glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
 file /usr/share/zoneinfo/right/US/Pacific from install of
 glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
 file /usr/share/zoneinfo/right/W-SU from install of glibc-common-2.2.2-10
 conflicts with file from package glibc-2.1.2-11
 file /usr/bin/catchsegv from install of glibc-common-2.2.2-10 conflicts
 with file from package glibc-2.1.2-11
 *** Error code 1
 
 Stop in /usr/ports/emulators/linux_base.
 
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message
 
 end of Re: linux compatability broken? from Eric Dedrick 


--
Oh good, my dog found the chainsaw.
-Lilo, Lilo  Stitch
Adam Weinberger
[EMAIL PROTECTED]
http://vectors.cx


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: linux compatability broken?

2002-07-23 Thread Eric Dedrick

Okay, I just installed linux_base 7.1 from the ports and linux
compatability is still broken (everything is failing with bad system
call signal 12).  linux.ko is loaded, compatability mode enabled.  What
do you suggest now?

On Tue, 23 Jul 2002, Adam Weinberger wrote:

 you have to uninstall the old version of linux_base that you have. if
 you don't know how to do that, you can always:

 install /usr/ports/sysutils/portupgrade

 then, do:
 portupgrade -o emulators/linux_base linux_base-\*

 that should take care of that.

 -Adam


  (07.23.2002 @ 2024 PST): Eric Dedrick said, in 1.4K: 
   i hope you have a semi-recent ports tree, because you need
   linux_base-7.1.
 
  installing linux_base 7.1 from the ports gives me the following error.
  Advice?  Thanks.
 
  ---
 
  (several screen fulls of the same type of stuff)...
  file /usr/share/zoneinfo/right/US/Eastern from install of
  glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
  file /usr/share/zoneinfo/right/US/Hawaii from install of
  glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
  file /usr/share/zoneinfo/right/US/Indiana-Starke from install of
  glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
  file /usr/share/zoneinfo/right/US/Michigan from install of
  glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
  file /usr/share/zoneinfo/right/US/Mountain from install of
  glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
  file /usr/share/zoneinfo/right/US/Pacific from install of
  glibc-common-2.2.2-10 conflicts with file from package glibc-2.1.2-11
  file /usr/share/zoneinfo/right/W-SU from install of glibc-common-2.2.2-10
  conflicts with file from package glibc-2.1.2-11
  file /usr/bin/catchsegv from install of glibc-common-2.2.2-10 conflicts
  with file from package glibc-2.1.2-11
  *** Error code 1
 
  Stop in /usr/ports/emulators/linux_base.
 
 
 
 
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with unsubscribe freebsd-questions in the body of the message
 
  end of Re: linux compatability broken? from Eric Dedrick 


 --
 Oh good, my dog found the chainsaw.
 -Lilo, Lilo  Stitch
 Adam Weinberger
 [EMAIL PROTECTED]
 http://vectors.cx



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message