Re: binutils problem? WAS [Re: static linking error: ELF binary type 0 not known. Exec format error. Binary file not executable.]
On Wed, Dec 15, 2010 at 06:58:50PM +0100, Tijl Coosemans wrote: On Monday 06 December 2010 16:16:30 Anton Shterenlikht wrote: On Mon, Dec 06, 2010 at 02:06:22PM +0100, Tijl Coosemans wrote: On Monday 29 November 2010 14:04:16 Anton Shterenlikht wrote: - Forwarded message from Marcel Moolenaar xcl...@mac.com - On Nov 10, 2010, at 5:32 AM, Anton Shterenlikht wrote: [ia64] ia64% file a.out a.out: ELF 64-bit LSB executable, IA-64, version 1 (SYSV), statically linked, not stripped [amd64] amd64% file a.out a.out: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically linked, for FreeBSD 9.0 (900023), not stripped The branding on ia64 is wrong. The executable is not marked as being a FreeBSD executable. It's declared as SYSV, whereas on amd64 it's properly declared as FreeBSD. This is a binutils problem. Anybody here can explain better what Marcel meant by binutils problem, and how to fix it? I've binutils-2.20.1_3 installed from devel/binutils. As a workaround you could manually brand the executable: brandelf -f 9 a.out this works fine. A fix has been committed to CURRENT, 8-STABLE and 7-STABLE. You should no longer have to brand executables manually. yes, just checked, many thanks. anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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: binutils problem? WAS [Re: static linking error: ELF binary type 0 not known. Exec format error. Binary file not executable.]
On Monday 06 December 2010 16:16:30 Anton Shterenlikht wrote: On Mon, Dec 06, 2010 at 02:06:22PM +0100, Tijl Coosemans wrote: On Monday 29 November 2010 14:04:16 Anton Shterenlikht wrote: - Forwarded message from Marcel Moolenaar xcl...@mac.com - On Nov 10, 2010, at 5:32 AM, Anton Shterenlikht wrote: [ia64] ia64% file a.out a.out: ELF 64-bit LSB executable, IA-64, version 1 (SYSV), statically linked, not stripped [amd64] amd64% file a.out a.out: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically linked, for FreeBSD 9.0 (900023), not stripped The branding on ia64 is wrong. The executable is not marked as being a FreeBSD executable. It's declared as SYSV, whereas on amd64 it's properly declared as FreeBSD. This is a binutils problem. Anybody here can explain better what Marcel meant by binutils problem, and how to fix it? I've binutils-2.20.1_3 installed from devel/binutils. As a workaround you could manually brand the executable: brandelf -f 9 a.out this works fine. A fix has been committed to CURRENT, 8-STABLE and 7-STABLE. You should no longer have to brand executables manually. signature.asc Description: This is a digitally signed message part.
Re: binutils problem? WAS [Re: static linking error: ELF binary type 0 not known. Exec format error. Binary file not executable.]
On Monday 29 November 2010 14:04:16 Anton Shterenlikht wrote: - Forwarded message from Marcel Moolenaar xcl...@mac.com - On Nov 10, 2010, at 5:32 AM, Anton Shterenlikht wrote: [ia64] ia64% file a.out a.out: ELF 64-bit LSB executable, IA-64, version 1 (SYSV), statically linked, not stripped [amd64] amd64% file a.out a.out: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically linked, for FreeBSD 9.0 (900023), not stripped The branding on ia64 is wrong. The executable is not marked as being a FreeBSD executable. It's declared as SYSV, whereas on amd64 it's properly declared as FreeBSD. This is a binutils problem. Anybody here can explain better what Marcel meant by binutils problem, and how to fix it? I've binutils-2.20.1_3 installed from devel/binutils. As a workaround you could manually brand the executable: brandelf -f 9 a.out signature.asc Description: This is a digitally signed message part.
Re: binutils problem? WAS [Re: static linking error: ELF binary type 0 not known. Exec format error. Binary file not executable.]
On Mon, Dec 06, 2010 at 02:06:22PM +0100, Tijl Coosemans wrote: On Monday 29 November 2010 14:04:16 Anton Shterenlikht wrote: - Forwarded message from Marcel Moolenaar xcl...@mac.com - On Nov 10, 2010, at 5:32 AM, Anton Shterenlikht wrote: [ia64] ia64% file a.out a.out: ELF 64-bit LSB executable, IA-64, version 1 (SYSV), statically linked, not stripped [amd64] amd64% file a.out a.out: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically linked, for FreeBSD 9.0 (900023), not stripped The branding on ia64 is wrong. The executable is not marked as being a FreeBSD executable. It's declared as SYSV, whereas on amd64 it's properly declared as FreeBSD. This is a binutils problem. Anybody here can explain better what Marcel meant by binutils problem, and how to fix it? I've binutils-2.20.1_3 installed from devel/binutils. As a workaround you could manually brand the executable: brandelf -f 9 a.out this works fine. many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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
binutils problem? WAS [Re: static linking error: ELF binary type 0 not known. Exec format error. Binary file not executable.]
- Forwarded message from Marcel Moolenaar xcl...@mac.com - On Nov 10, 2010, at 5:32 AM, Anton Shterenlikht wrote: [ia64] ia64% file a.out a.out: ELF 64-bit LSB executable, IA-64, version 1 (SYSV), statically linked, not stripped [amd64] amd64% file a.out a.out: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically linked, for FreeBSD 9.0 (900023), not stripped The branding on ia64 is wrong. The executable is not marked as being a FreeBSD executable. It's declared as SYSV, whereas on amd64 it's properly declared as FreeBSD. This is a binutils problem. FYI, -- Marcel Moolenaar xcl...@mac.com - End forwarded message - Anybody here can explain better what Marcel meant by binutils problem, and how to fix it? I've binutils-2.20.1_3 installed from devel/binutils. many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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
kldload: can't load /usr/local/modules/fuse.ko: Exec format error fusefs-ntfs-1.2531
Hi people, I can't use my maxtor basic 640gb external harddrive on Freebsd amd64 running 7.0 because when I try to load fusefs with this command, kldload /usr/local/modules/fuse.ko I get the following error: kldload: can't load /usr/local/modules/fuse.ko: Exec format error Adding fusefs_enable=YES to /etc/rc.conf and fuse_load=YES to /boot/loader.conf and rebooting doesn't help either, because then that error message is printed on the console. uname -a gives: FreeBSD zouk.telfort.nl 7.0-RELEASE-p6 FreeBSD 7.0-RELEASE-p6 #1: Thu Nov 27 13:42:17 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 pkg_info | grep fuse gives: fusefs-kmod-0.3.9.p1.20080208_4 Kernel module for fuse fusefs-libs-2.7.3 FUSE allows filesystem implementation in userspace fusefs-ntfs-1.2531 Mount NTFS partitions (read/write) and disk images Does anyone have a clue as to what is causing this behavior? I prefer to keep the external harddisk in ntfs format, although I could easily reformat it as ufs or ext3 because my whole system environment consists of bsd and linux. But I don't know if I will violate maxtor's guarantee. So I hope someone can help me with this. Brgds Dino ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kldload: can't load /usr/local/modules/fuse.ko: Exec format error fusefs-ntfs-1.253
On 12/3/08, Dino Vliet [EMAIL PROTECTED] wrote: Hi people, I can't use my maxtor basic 640gb external harddrive on Freebsd amd64 running 7.0 because when I try to load fusefs with this command, kldload /usr/local/modules/fuse.ko I get the following error: kldload: can't load /usr/local/modules/fuse.ko: Exec format error Adding fusefs_enable=YES to /etc/rc.conf and fuse_load=YES to /boot/loader.conf and rebooting doesn't help either, because then that error message is printed on the console. uname -a gives: FreeBSD zouk.telfort.nl 7.0-RELEASE-p6 FreeBSD 7.0-RELEASE-p6 #1: Thu Nov 27 13:42:17 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 pkg_info | grep fuse gives: fusefs-kmod-0.3.9.p1.20080208_4 Kernel module for fuse fusefs-libs-2.7.3 FUSE allows filesystem implementation in userspace fusefs-ntfs-1.2531 Mount NTFS partitions (read/write) and disk images Does anyone have a clue as to what is causing this behavior? How did you install the fusefs-kmod was it from a package or did you build it through the ports system? The most likely cause of this error is due to the fuse.ko module was not built against the same source as your kernel. Rebuild fusefs-kmod and that should resolve the problem. Scot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kldload: can't load /usr/local/modules/fuse.ko: Exec format error fusefs-ntfs-1.253
On 12/3/08, Scot Hetzel [EMAIL PROTECTED] wrote: On 12/3/08, Dino Vliet [EMAIL PROTECTED] wrote: Hi people, I can't use my maxtor basic 640gb external harddrive on Freebsd amd64 running 7.0 because when I try to load fusefs with this command, kldload /usr/local/modules/fuse.ko I get the following error: kldload: can't load /usr/local/modules/fuse.ko: Exec format error : Does anyone have a clue as to what is causing this behavior? How did you install the fusefs-kmod was it from a package or did you build it through the ports system? The most likely cause of this error is due to the fuse.ko module was not built against the same source as your kernel. Rebuild fusefs-kmod and that should resolve the problem. I usually see this problem after cvs updating the FreeBSD sources and then rebuilding a module, and trying to load that module. Rebuilding the kernel and all external modules should resolve the problem. Scot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kldload: can't load /usr/local/modules/fuse.ko: Exec format error fusefs-ntfs-1.2531
Dino Vliet wrote: Hi people, kldload: can't load /usr/local/modules/fuse.ko: Exec format error What does $file /usr/local/modules/fuse.ko say, and do you have Linux support built and enabled? Kevin Kinsey -- A failure will not appear until a unit has passed final inspection. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kldload: can't load /usr/local/modules/fuse.ko: Exec format error fusefs-ntfs-1.253
--- On Wed, 12/3/08, Scot Hetzel [EMAIL PROTECTED] wrote: From: Scot Hetzel [EMAIL PROTECTED] Subject: Re: kldload: can't load /usr/local/modules/fuse.ko: Exec format error fusefs-ntfs-1.253 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], freebsd-questions@freebsd.org, [EMAIL PROTECTED] Date: Wednesday, December 3, 2008, 12:17 PM On 12/3/08, Dino Vliet [EMAIL PROTECTED] wrote: Hi people, I can't use my maxtor basic 640gb external harddrive on Freebsd amd64 running 7.0 because when I try to load fusefs with this command, kldload /usr/local/modules/fuse.ko I get the following error: kldload: can't load /usr/local/modules/fuse.ko: Exec format error Adding fusefs_enable=YES to /etc/rc.conf and fuse_load=YES to /boot/loader.conf and rebooting doesn't help either, because then that error message is printed on the console. uname -a gives: FreeBSD zouk.telfort.nl 7.0-RELEASE-p6 FreeBSD 7.0-RELEASE-p6 #1: Thu Nov 27 13:42:17 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 pkg_info | grep fuse gives: fusefs-kmod-0.3.9.p1.20080208_4 Kernel module for fuse fusefs-libs-2.7.3 FUSE allows filesystem implementation in userspace fusefs-ntfs-1.2531 Mount NTFS partitions (read/write) and disk images Does anyone have a clue as to what is causing this behavior? How did you install the fusefs-kmod was it from a package or did you build it through the ports system? The most likely cause of this error is due to the fuse.ko module was not built against the same source as your kernel. Rebuild fusefs-kmod and that should resolve the problem. Scot Hi Scot, I installed it from ports. I think as a dependency on fusefs-ntfs? I will rebuild my system as I upgraded lately from 6.3 to 7, but I'm sure I just followed the handbook and did everything allright. Will post the results when I try this again afterwards. Brgds Dino ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kldload: can't load /usr/local/modules/fuse.ko: Exec format error fusefs-ntfs-1.2531
--- On Wed, 12/3/08, Kevin Kinsey [EMAIL PROTECTED] wrote: From: Kevin Kinsey [EMAIL PROTECTED] Subject: Re: kldload: can't load /usr/local/modules/fuse.ko: Exec format error fusefs-ntfs-1.2531 To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Date: Wednesday, December 3, 2008, 3:56 PM Dino Vliet wrote: Hi people, kldload: can't load /usr/local/modules/fuse.ko: Exec format error What does $file /usr/local/modules/fuse.ko say, and do you have Linux support built and enabled? Kevin Kinsey -- A failure will not appear until a unit has passed final inspection. *** Hi Kevin, That command gives the following result on my system: file /usr/local/modules/fuse.ko /usr/local/modules/fuse.ko: ELF 64-bit LSB relocatable, x86-64, version 1 (FreeBSD), not stripped I don't have linux support build and enabled. Is it necessary? Thanks Dino ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kldload: can't load /usr/local/modules/fuse.ko: Exec format error fusefs-ntfs-1.253 SOLVED
--- On Wed, 12/3/08, Scot Hetzel [EMAIL PROTECTED] wrote: From: Scot Hetzel [EMAIL PROTECTED] Subject: Re: kldload: can't load /usr/local/modules/fuse.ko: Exec format error fusefs-ntfs-1.253 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], freebsd-questions@freebsd.org, [EMAIL PROTECTED] Date: Wednesday, December 3, 2008, 12:17 PM On 12/3/08, Dino Vliet [EMAIL PROTECTED] wrote: Hi people, I can't use my maxtor basic 640gb external harddrive on Freebsd amd64 running 7.0 because when I try to load fusefs with this command, kldload /usr/local/modules/fuse.ko I get the following error: kldload: can't load /usr/local/modules/fuse.ko: Exec format error Adding fusefs_enable=YES to /etc/rc.conf and fuse_load=YES to /boot/loader.conf and rebooting doesn't help either, because then that error message is printed on the console. uname -a gives: FreeBSD zouk.telfort.nl 7.0-RELEASE-p6 FreeBSD 7.0-RELEASE-p6 #1: Thu Nov 27 13:42:17 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 pkg_info | grep fuse gives: fusefs-kmod-0.3.9.p1.20080208_4 Kernel module for fuse fusefs-libs-2.7.3 FUSE allows filesystem implementation in userspace fusefs-ntfs-1.2531 Mount NTFS partitions (read/write) and disk images Does anyone have a clue as to what is causing this behavior? How did you install the fusefs-kmod was it from a package or did you build it through the ports system? The most likely cause of this error is due to the fuse.ko module was not built against the same source as your kernel. Rebuild fusefs-kmod and that should resolve the problem. Scot Hi all, this did the trick, thanks! I rebuild my kernel and had to rebuild that port as well. Was sure I had done a portupgrade -fa before, but still it seemed I had to rebuild the port first. After this, I could start fusefs with the script in rc.d and after rebooting it recognized that option as well. Now I managed to mount my external disk with that as well, so everything is ok:-) Thanks again, Dino ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kldload: exec format error on newly built GENERIC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steve Franks wrote: | I just added a device driver source file to the appropriate location | and rebuilt: | | dystant# cd /usr/src | dystant# make buildkernel KERNCONF=GENERIC | ... | dystant# make installkernel KERNCONF=GENERIC | dystant# init 6 | ... | [EMAIL PROTECTED] /usr/home/steve]$ sudo kldload ucp | kldload: can't load ucp: Exec format error | | ??? What am I doing wrong? | You are using some 3rd party driver for freebsd. Just like you got new kernel, get new driver for it. wtf is ucp anyway? cba to check google :/ - -- Best regards, Bogdan Culibrk [EMAIL PROTECTED] http://default.co.yu/~bc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkfVowEACgkQo6C4vAhYtCAEYgCfXArpJL7ncCrDa2DcqCVdmiGt KD0An3RM+cmLore6XMxCrdsBytTTVMbX =x6yC -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kldload: exec format error on newly built GENERIC
I just added a device driver source file to the appropriate location and rebuilt: dystant# cd /usr/src dystant# make buildkernel KERNCONF=GENERIC ... dystant# make installkernel KERNCONF=GENERIC dystant# init 6 ... [EMAIL PROTECTED] /usr/home/steve]$ sudo kldload ucp kldload: can't load ucp: Exec format error ??? What am I doing wrong? Thanks, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
snd_hda on amd64 - exec format error
This is not a priority, but I'm suprised that both the downloaded (ariff?) and the built-from-source snd*.ko files give me a: kldload: can't load snd_hda: Exec format error When I try to load them...guess my kernel is out of date with the latest 6.2-stable source? Best, Steve 6.2 - amd64 aire# dmesg Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-RELEASE #0: Fri Jan 12 08:32:24 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) CPU 440 @ 2.00GHz (1995.01-MHz K8-class CPU) Origin = GenuineIntel Id = 0x10661 Stepping = 1 Features=0xafebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE Features2=0xe31dSSE3,RSVD2,MON,DS_CPL,TM2,b9,CX16,b14,b15 AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF real memory = 1064173568 (1014 MB) avail memory = 1015042048 (968 MB) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
can't load /boot/kernel/ng_fec.ko: Exec format error
Chuck Swiger wrote: You can do other things, such as using ng_fec to perform port trunking, or using IPFW or some other thing to manually force traffic out of the other interface, but it's unlikely to result in much benefit. Hello again I'm trying to use ng_fec but I have a problem to load it into the kernel see below the trace of the problem Thank you for any info mail2# cd /usr/src/sys/modules/netgraph/fec mail2# make Warning: Object directory not changed from original /usr/src/sys/modules/netgraph/fec @ - /usr/src/sys machine - /usr/src/sys/amd64/include : opt_inet.h : opt_inet6.h : opt_netgraph.h cc -O2 -fno-strict-aliasing -pipe -DINET -DINET6 -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/contrib/altq -I@/../include -I/usr/include -finline-limit=8000 -fno-common -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/modules/netgraph/fec/../../../netgraph/ng_fec.c ld -d -warn-common -r -d -o ng_fec.ko ng_fec.o : export_syms awk -f /usr/src/sys/modules/netgraph/fec/../../../conf/kmod_syms.awk ng_fec.ko export_syms | xargs -J% objcopy % ng_fec.ko objcopy --strip-debug ng_fec.ko mail2# make install install -o root -g wheel -m 555 ng_fec.ko /boot/kernel kldxref /boot/kernel mail2# kldload /boot/kernel/ng_fec.ko kldload: can't load /boot/kernel/ng_fec.ko: Exec format error ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Apache + PHP : Exec format error
I can't get the package WebCalendar-1.0.0 to work; I always get following error in /var/log/httpd-error.log (8)Exec format error: exec of '/usr/local/www/data-dist/WebCalendar/index.php' If I put #!/usr/local/bin/php at the beginning of the index.php it works, however I would like to use the apache module php4_module instead of php as CGI. I'm running 5.4-STABLE with the pkg apache-2.0.54_4 and php4-4.4.0 (Apache Module and CLI). The httpd.conf includes the line LoadModule php4_module libexec/apache2/libphp4.so. Any ideas? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Exec format error
Hello I recently installed the squidtimes package from ports at 5.4-R then I have such erreor message when launching it ... squidtimes: Exec format error. Binary file not executable. A bit strange as make and make install ran smoothly ... -- Cordialement/Regards Frank Bonnet ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Exec format error
Frank Bonnet [EMAIL PROTECTED] writes: Hello I recently installed the squidtimes package from ports at 5.4-R then I have such erreor message when launching it ... squidtimes: Exec format error. Binary file not executable. A bit strange as make and make install ran smoothly ... It's a port, but it installs a prebuilt binary. [Which is the same one as when the port was added, back in '98.] You will need a.out support in the kernel, which can be installed with a module, and probably some compatibility libraries. Good luck. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
exec format error
Hi, I am a newbie FreeBSD installer. I installed 5.2.1 without any problems. But commands like gzip do not work, i.e. terminate with: /usr/bin/gzip: Exec format error. Binary file not executable. Also when I try to install new packages via CD, I always get error: ELF interpreter /libexec/ld-elf.so.1*** not found. (note that the 3 '*' stand for three weird characters.) I checked that /libexec/ld-elf.so.1 already exists... Any idea ? Cheers, Alper _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: exec format error
On Tue, Apr 13, 2004 at 08:19:47AM +, Alper Yurdakul wrote: Hi, I am a newbie FreeBSD installer. I installed 5.2.1 without any problems. But commands like gzip do not work, i.e. terminate with: /usr/bin/gzip: Exec format error. Binary file not executable. Also when I try to install new packages via CD, I always get error: ELF interpreter /libexec/ld-elf.so.1*** not found. (note that the 3 '*' stand for three weird characters.) I checked that /libexec/ld-elf.so.1 already exists... Any idea ? Sounds like 5.2.1 did not, in fact, install without any problems :-) Those errors are very weird and indicate something is quite wrong on your system. Try reinstalling it (if you install from CD then make sure you verify the checksum first so you don't install from an image that was corrupted during download). Kris pgp0.pgp Description: PGP signature
Re: mount floppy/cdrom on diskless PC: vfsload: Exec format error
Rob wrote: Hi, I have a diskless PC with a floppy and CDrom drive. I can create a dos floppy without a problem, but the mount fails: # /usr/sbin/fdformat /dev/fd0.1440 Format 1440K floppy `/dev/fd0.1440'? (y/n): y Processing done. # /sbin/disklabel -B -r -w /dev/fd0 fd1440 # /sbin/newfs_msdos /dev/fd0 /dev/fd0: 2840 sectors in 355 FAT12 clusters (4096 bytes/cluster) bps=512 spc=8 res=1 nft=2 rde=512 sec=2880 mid=0xf0 spf=2 spt=18 hds=2 hid=0 # mount_msdos /dev/fd0c /mnt mount_msdos: vfsload(msdos): Exec format error Same problem occurs for a CDrom: # mount -t cd9660 /dev/acd0c /cdrom cd9660: vfsload(cd9660): Exec format error The diskless machine has: /modules/msdos.ko /modules/cd9660.ko Probably related to this are these lines in /var/log/messages: Mar 6 13:09:33 diskless //kernel: link_elf: symbol s_lock_init undefined Any ideas what's going wrong here? I'll answer my own question here: When I add two options to the KERNEL config file: options MSDOSFS options CD9660 and use that kernel for my diskless PC, I can mount floppy and CDrom. Strange, because usually this is not needed for casual mounts of these devices. Cheers, Rob. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount floppy/cdrom on diskless PC: vfsload: Exec format error
Hi, I have a diskless PC with a floppy and CDrom drive. I can create a dos floppy without a problem, but the mount fails: # /usr/sbin/fdformat /dev/fd0.1440 Format 1440K floppy `/dev/fd0.1440'? (y/n): y Processing done. # /sbin/disklabel -B -r -w /dev/fd0 fd1440 # /sbin/newfs_msdos /dev/fd0 /dev/fd0: 2840 sectors in 355 FAT12 clusters (4096 bytes/cluster) bps=512 spc=8 res=1 nft=2 rde=512 sec=2880 mid=0xf0 spf=2 spt=18 hds=2 hid=0 # mount_msdos /dev/fd0c /mnt mount_msdos: vfsload(msdos): Exec format error Same problem occurs for a CDrom: # mount -t cd9660 /dev/acd0c /cdrom cd9660: vfsload(cd9660): Exec format error The diskless machine has: /modules/msdos.ko /modules/cd9660.ko Probably related to this are these lines in /var/log/messages: Mar 6 13:09:33 diskless //kernel: link_elf: symbol s_lock_init undefined Any ideas what's going wrong here? Thanks, Rob. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
