On 28-Jan-00 Marcel Moolenaar wrote:
>> On 28-Jan-00 Jeroen Ruigrok van der Werven wrote:
>> > ===> bin/pwd
>> > install -c -s -o root -g wheel -m 555   pwd /bin
>> > install -c -o root -g wheel -m 444 pwd.1.gz  /usr/share/man/man1
>> > ===> bin/rcp
>> > install -c -s -o root -g wheel -m 4555  -fschg rcp /bin
>> > /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags"
>> > *** Error code 1
>> >
>> > Stop in /usr/src/bin/rcp.
>> > *** Error code 1
> [snip]
>> This is indicative of a larger problem with installworld.  The short
>> version is that we need install tools just like we have build tools now.
>> The long version is this:
> [snip]
>> It would seem from Asmodai's breakage that installworld assumes that it
>> is ok to use the existing binaries on the system in /bin /usr/bin, etc.
> [snip]
>> We need statically built install tools just like we have build tools.
> [snip]
>> Comments, suggestions?
> [snip]
> 
> I already have patches (somewhere :-) that solve this problem. I choose not
> to apply these before the release. I will fix installworld after the
> release. For now, you can use the buildkernel and installkernel targets
> (after a buildworld) to solve the (possibly complex) dependencies between
> kernel, modules and world.

This isn't related to the kernel though, it is a dependency within the world
between libraries and binaries.  Do you have those patches somewhere where I
can look at them.  I want to start testing them, because it _may_ (I'm only
saying "may" right now) be better to fix this before 4.0 so that we don't have
4 million using cvsup to upgrade to 4.0 (despite all the warnings about 4.0
being only for early adopters) and then running into this and flooding
-questions.  I'd like to prevent a FAQ rather than create one, if you know
what I mean.

> FYI,
> 
> marcel

-- 

John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to