Re: libexec/ld-elf.so.1: Undefined symbol "__stdoutp" referenced from COPY relocation in /bin/sh

From: Marcin Jessa <lists_at_yazzy.org>
Date: Mon, 6 Jun 2005 22:34:43 +0200
Hi Doug.

On Mon, 6 Jun 2005 13:12:15 -0700 (PDT)
Doug White <dwhite_at_gumbysoft.com> wrote:

> On Mon, 6 Jun 2005, Marcin Jessa wrote:
> 
> > I forgot to mention I am upgrading from 5.4-RELEASE to 6.0 The world and
> > kernel compiled fine but the new installed by make installworld binaries
> > make the make installworld process to fail.
> 
> Oops... didn't follow the instructions in src/UPDATING, did you? :) You
> need to install the new kernel and reboot before installing the binaries.

That's exactly what I did. Built new world, built and installed new kernel, rebooted in single user mode, ran mergemaster -p and then make installworld. That's when the error kicked in.

 
> > As you can see in this case, install fails first.
> > I can copy install from 5.4 and then make installworld starts to complain about other binaries.
> > When I copy over the entire /bin and /sbin from 5.4 I can use the userland applications again just fine (they give the same errors when I try to run the freshly installed ones).
> > I also tried to copy over binaries from a snapshot CD (ISO downloaded from ftp2.jp.freebsd.org) but I still get the same error with those...
> > I am stucked having no idea what may be wrong here...
> 
> Your best bet is to reinstall 5.4-R over the broken system. This should
> get enough working again to reattempt the upgrade.  Just mount the
> filesystems in sysinstall and don't newfs them.


I tried that too. I have a working system running back on 5.4. I booted to livecd and copied over all the bins and libs.
Btw, the 6.0 kernel seems to be running fine with 5.4 bins as well.
Anyway, when I try to install new 6.0 world doing the same stuff all over again, the error occurs.
I also tried to run with 6.0 binaries from CURRENT snapshot but then I get the same error booting my box. 
It immidiately falls to single user mode and /bin/sh cannot be executed becouse of that error.
As I said, I am stucked and I have no idea why that happens...
Received on Mon Jun 06 2005 - 18:34:46 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:35 UTC