Re: Help with Linux interpreter
In message <[EMAIL PROTECTED]> FUJISHIMA Satsuki writes: : Hmm, all that I can tell about the matter is described in the PR: : http://www.freebsd.org/cgi/query-pr.cgi?pr=18489 : : I'm not sure this is the case but it looks pretty similar for me. Hmmm. I took another look at this PR. It fixed my problem. I deinstalled linux_base (cause I F***ed it up somehow) and acroread4. I then updated the acroread4 port (which had Makefile 1.25 instead of Makefile 1.26 for reasons I still don't understand, but were likely pilot error on my part) and reinstalled both. It works for me now. fujishima-san, arigatou gozaimashita! Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Help with Linux interpreter
On Wednesday, 5 July 2000 at 0:17:46 +0900, FUJISHIMA Satsuki wrote:
> Hmm, all that I can tell about the matter is described in the PR:
> http://www.freebsd.org/cgi/query-pr.cgi?pr=18489
>
> I'm not sure this is the case but it looks pretty similar for me.
Hmm.
$ brandelf -t Linux acroread
$ hd acroread|head -1
7f 45 4c 46 01 01 01 03 46 72 65 65 42 53 44 00 |.ELFFreeBSD.|
On the other machine, I get:
$ hd acroread|head -1
7f 45 4c 46 01 01 01 03 4c 69 6e 75 78 00 00 00 |.ELFLinux...|
$ brandelf -t FreeBSD acroread
$ hd acroread|head -1
7f 45 4c 46 01 01 01 09 4c 69 6e 75 78 00 00 00 |.ELFLinux...|
Repeating this last brandelf invocation (-t FreeBSD) with ktrace, I see:
2586 brandelf NAMI "acroread"
2586 brandelf RET open 3
2586 brandelf CALL sigprocmask(0x1,0x28060040,0x28060050)
2586 brandelf RET sigprocmask 0
2586 brandelf CALL sigprocmask(0x3,0x28060050,0)
2586 brandelf RET sigprocmask 0
2586 brandelf CALL read(0x3,0xbfbfefe4,0x10)
2586 brandelf GIO fd 3 read 16 bytes
"\^?ELF\^A\^A\^A Linux\0\0\0"
2586 brandelf RET read 16/0x10
2586 brandelf CALL sigprocmask(0x1,0x28060040,0x28060050)
2586 brandelf RET sigprocmask 0
2586 brandelf CALL sigprocmask(0x3,0x28060050,0)
2586 brandelf RET sigprocmask 0
2586 brandelf CALL sigprocmask(0x1,0x28060040,0x28060050)
2586 brandelf RET sigprocmask 0
2586 brandelf CALL sigprocmask(0x3,0x28060050,0)
2586 brandelf RET sigprocmask 0
2586 brandelf CALL lseek(0x3,0,0,0,0)
2586 brandelf RET lseek 0
2586 brandelf CALL sigprocmask(0x1,0x28060040,0x28060050)
2586 brandelf RET sigprocmask 0
2586 brandelf CALL sigprocmask(0x3,0x28060050,0)
2586 brandelf RET sigprocmask 0
2586 brandelf CALL write(0x3,0xbfbfefe4,0x10)
2586 brandelf GIO fd 3 wrote 16 bytes
"\^?ELF\^A\^A\^A Linux\0\0\0"
2586 brandelf RET write 16/0x10
It looks as if brandelf is broke.
Greg
--
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Help with Linux interpreter
Hmm, all that I can tell about the matter is described in the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=18489 I'm not sure this is the case but it looks pretty similar for me. -- FUJISHIMA Satsuki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Help with Linux interpreter
On Monday, 3 July 2000 at 9:48:38 -0600, Warner Losh wrote: > In message <[EMAIL PROTECTED]> FUJISHIMA Satsuki writes: >> At Sun, 02 Jul 2000 22:10:15 -0600, >> Warner Losh <[EMAIL PROTECTED]> wrote: >>> In message <[EMAIL PROTECTED]> FUJISHIMA Satsuki writes: Please take a look into ports/18489. Workaround for i386 has been committed at 14th May but not for Alpha. I think you are on the Alpha plathome, or your ports tree is weirdly out of date. >>> >>> Everything is up to date. The kernel, my ports tree, userland. I >>> still get this problem after updating to today's kernel/userland. >>> Yes, ldconfig has been branded. ld.so has been branded. acroread >>> (the binary that acroread4 runs, verified). I've enabled linux in the >>> boot script (and verified that it runs). >> >> You don't answered my question: Is it Alpha plathome you are on? > > Sorry about that. I'm running on Intel. > >> print/acroread4 port has workaround for i386 but not for Alpha. see >> ports/18489 for details. >> >> Brand new kernel/userland is not a solusion. I successfully installed >> and ran acroread4 perfectly on 1st July i386 kernel/userland built >> from scratch. > > OK. Nothing changed in this area between July and July 2 when I > rebuilt > >>> ELF interpreter /lib/ld-linux.so.2 not found >>> Abort >> >> This seems `Linux binary branded to FreeBSD.' > > If it is, I can't figure out which one it is :-( FWIW, I'm getting exactly the same problem on one machine, but not on the other. Good machine: FreeBSD sydney.worldwide.lemis.com 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Sat Jun 10 17:46:50 CST 2000 [EMAIL PROTECTED]:/home/src/sys/compile/SYDNEY i386 Bad machine: FreeBSD wantadilla.lemis.com 5.0-CURRENT FreeBSD 5.0-CURRENT #3: Sat Jun 10 15:11:18 CST 2000 [EMAIL PROTECTED]:/src/FreeBSD/WANTADILLA/src/sys/compile/WANTADILLA i386 In each case, the sources were freshly cvsupped. I don't have time to look more deeply (since I can get things to work :-), but I was pretty sure that it used to work on wantadilla as well, and that I haven't changed anything in the interim. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Help with Linux interpreter
In message <[EMAIL PROTECTED]> FUJISHIMA Satsuki writes: : At Sun, 02 Jul 2000 22:10:15 -0600, : Warner Losh <[EMAIL PROTECTED]> wrote: : > In message <[EMAIL PROTECTED]> FUJISHIMA Satsuki writes: : > : Please take a look into ports/18489. : > : Workaround for i386 has been committed at 14th May but not for Alpha. : > : I think you are on the Alpha plathome, or your ports tree is weirdly : > : out of date. : > : > Everything is up to date. The kernel, my ports tree, userland. I : > still get this problem after updating to today's kernel/userland. : > Yes, ldconfig has been branded. ld.so has been branded. acroread : > (the binary that acroread4 runs, verified). I've enabled linux in the : > boot script (and verified that it runs). : : You don't answered my question: Is it Alpha plathome you are on? Sorry about that. I'm running on Intel. : print/acroread4 port has workaround for i386 but not for Alpha. see : ports/18489 for details. : : Brand new kernel/userland is not a solusion. I successfully installed : and ran acroread4 perfectly on 1st July i386 kernel/userland built : from scratch. OK. Nothing changed in this area between July and July 2 when I rebuilt : >ELF interpreter /lib/ld-linux.so.2 not found : >Abort : : This seems `Linux binary branded to FreeBSD.' If it is, I can't figure out which one it is :-( Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Help with Linux interpreter
At Sun, 02 Jul 2000 22:10:15 -0600, Warner Losh <[EMAIL PROTECTED]> wrote: > In message <[EMAIL PROTECTED]> FUJISHIMA Satsuki writes: > : Please take a look into ports/18489. > : Workaround for i386 has been committed at 14th May but not for Alpha. > : I think you are on the Alpha plathome, or your ports tree is weirdly > : out of date. > > Everything is up to date. The kernel, my ports tree, userland. I > still get this problem after updating to today's kernel/userland. > Yes, ldconfig has been branded. ld.so has been branded. acroread > (the binary that acroread4 runs, verified). I've enabled linux in the > boot script (and verified that it runs). You don't answered my question: Is it Alpha plathome you are on? print/acroread4 port has workaround for i386 but not for Alpha. see ports/18489 for details. Brand new kernel/userland is not a solusion. I successfully installed and ran acroread4 perfectly on 1st July i386 kernel/userland built from scratch. >ELF interpreter /lib/ld-linux.so.2 not found >Abort This seems `Linux binary branded to FreeBSD.' -- FUJISHIMA Satsuki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Help with Linux interpreter
In message <[EMAIL PROTECTED]> FUJISHIMA Satsuki writes: : Please take a look into ports/18489. : Workaround for i386 has been committed at 14th May but not for Alpha. : I think you are on the Alpha plathome, or your ports tree is weirdly : out of date. Everything is up to date. The kernel, my ports tree, userland. I still get this problem after updating to today's kernel/userland. Yes, ldconfig has been branded. ld.so has been branded. acroread (the binary that acroread4 runs, verified). I've enabled linux in the boot script (and verified that it runs). Any ideas about how I should go about debugging this? I need my acroread4 :-). Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Help with Linux interpreter
In message <[EMAIL PROTECTED]> Doug White writes: : > ELF interpreter /lib/ld-linux.so.2 not found : > Abort : : Did you brand acroread? Yes. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Help with Linux interpreter
On Sat, 1 Jul 2000, Warner Losh wrote: > > I was able to install the acroread4 port on my -current machine of a > week or two ago. I find when I try to run acroread4 I get the > following error: > > ELF interpreter /lib/ld-linux.so.2 not found > Abort Did you brand acroread? Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Help with Linux interpreter
At Sat, 01 Jul 2000 21:25:42 -0600, Warner Losh <[EMAIL PROTECTED]> wrote: > > > I was able to install the acroread4 port on my -current machine of a > week or two ago. I find when I try to run acroread4 I get the > following error: > > ELF interpreter /lib/ld-linux.so.2 not found > Abort Please take a look into ports/18489. Workaround for i386 has been committed at 14th May but not for Alpha. I think you are on the Alpha plathome, or your ports tree is weirdly out of date. -- FUJISHIMA Satsuki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
