NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: skirmishing w/ emulation



On 07/19/15 09:40, William A. Mahaffey III wrote:
On 07/18/15 14:54, Eric Haszlakiewicz wrote:
On July 18, 2015 11:38:06 AM EDT, "William A. Mahaffey III" <wam%hiwaay.net@localhost> wrote:
[wam@4256EE1, ~, 10:32:08am] 240 % file bin/VectorExe.AMD64.new
bin/VectorExe.AMD64.new: ELF 64-bit LSB executable, x86-64, version 1
(SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9,
stripped
[wam@4256EE1, ~, 10:32:12am] 241 % rehash
[wam@4256EE1, ~, 10:32:16am] 242 % VectorExe.AMD64.new
VectorExe.AMD64.new: Command not found.
[wam@4256EE1, ~, 10:32:19am] 243 % bin/VectorExe.AMD64.new
bin/VectorExe.AMD64.new: Command not found.
In this last particular case you probably need "./bin/VectorExe.AMD64.new", but the previous one should have worked since you have it in your path. To rule out any issues with that I recommend using an absolute path.

The file VectorExe... was compiled & statically linked for compiler
libraries (not runtime stuff) on a CentOS 5 VM (kernel 2.6.18 EL) on
Your "file" command says "dynamically linked", which means you need to make sure you've got linux libraries installed. There's pkgsrc packages for this, so try:

pkgin install suse

Which should install a whole slew of packages. Once you do that you can try "/emul/linux/bin/ls" and see if at least that works before running your binary.

Eric



Thanks for the reply. I figured out that the 'command not found' was probably 'ld.so' about 30 sec. after I hit return. I notice compatibility packages for both suse-10 & suse-12. I actually think I need the suse-10, rather than 12, unless suse-12 is backwards compatible w/ suse-10, would you have any info on that ? The handbook is mum, & reflects installing suse-10 compatibility stuff. TIA & have a good one.


Update: I went ahead & did a 'pkgin install suse_base-10 suse_compat-10' & it installed those packages no sweat. Post install, it said something about putting an entry in my fstab file mounting procfs as /emul/linux/proc. I already have a procfs in my fstab file for NetBSD, I presume. Did it mean an entry in /emul/linux/etc/fstab ? If so, the message out of the install process is off-base. Please advise & have a good one.

--

	William A. Mahaffey III

 ----------------------------------------------------------------------

	"The M1 Garand is without doubt the finest implement of war
	 ever devised by man."
                           -- Gen. George S. Patton Jr.



Home | Main Index | Thread Index | Old Index