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

From: Marcin Jessa (lists_at_yazzy.org)
Date: 06/06/05

  • Next message: Søren Schmidt: "Re: 'atacontrol cap' not working under recent CURRENT?"
    Date: Mon, 6 Jun 2005 22:34:43 +0200
    To: Doug White <dwhite@gumbysoft.com>
    
    

    Hi Doug.

    On Mon, 6 Jun 2005 13:12:15 -0700 (PDT)
    Doug White <dwhite@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...
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


  • Next message: Søren Schmidt: "Re: 'atacontrol cap' not working under recent CURRENT?"

    Relevant Pages

    • Re: make installworld fails
      ... It is sometimes necessary to reboot with the new kernel to have ... 'make installworld' work correctly (and the recommended procedure is to ... (e.g. every FreeBSD command crashes when run with the old kernel, ...
      (freebsd-questions)
    • panic: mi_switch: kse state?
      ... hrs. US/Pacific. ... I had done the usual buildworld, kernel, installworld, mergemaster, ... Locked vnodes ...
      (freebsd-current)
    • Error on installworld from 5.2.1 to 5.3-p1
      ... I rebooted the machine and enter in single mode with kernel 5.2.1 ... When I execute the installworld, ... /dev/null -V MAKEOBJDIRPREFIX dummy" returned non-zero status ... *** Error code 1 ...
      (freebsd-stable)
    • Re: upgrading
      ... Matthew Seaman hit a keyboard in the following places: ... > This method has the effect that you're still running the same kernel, ... Doing an installworld before you've verified that the kernel is ... you don't want to mount NFS mounts and the like. ...
      (freebsd-stable)
    • Re: error when doing make installworld
      ... "Doing a make installworld before finding out if ... How am I able to find out if the new kernel will ... kernel will boot will bite ... *** Error code 1 ...
      (freebsd-questions)