Re: make installworld fails because /usr/include/c++/v1/__tuple is a file

[Dimitry Andric]

On 13 Dec 2023, at 19:07, John Baldwin  wrote:
> 
> On 12/10/23 8:43 AM, Dimitry Andric wrote:
>> On 10 Dec 2023, at 15:11, Herbert J. Skuhra  wrote:
>>> 
>>> On Sun, Dec 10, 2023 at 01:22:38PM +, John F Carr wrote:
 On arm64 running CURRENT from two weeks ago I updated to
 
  c711af772782 Bump __FreeBSD_version for llvm 17.0.6 merge
 
 and built and installed from source.  make installworld failed:
 
  install: target directory `/usr/include/c++/v1/__tuple/' does not exist
 
 That pathname is a file:
 
  -r--r--r--  1 root wheel 20512 Feb 15  2023 /usr/include/c++/v1/__tuple
 
 Early in make output is
 
  mtree -deU -i -f /usr/src/etc/mtree/BSD.include.dist -p /usr/include
  ./c++/v1/__algorithm/pstl_backends missing (created)
  [...]
  ./c++/v1/__tuple missing (not created: File exists)
 
 Should I remove the file and try again, or is there a more elegant fix?
 
 The word "tuple" does not appear in UPDATING.
>>> 
>>> 'make delete-old' should have removed this file.
>>> 
>>> bdd1243df58e6 (Dimitry Andric  2023-04-14 23:41:27 +0200   965)
>>> OLD_FILES+=usr/include/c++/v1/__tuple
>> Ah yes, that's it. The file was removed during the upgrade from libc++
>> 15.0 to 16.0, while its contents was split into a subdirectory named
>> __tuple_dir. In libc++ 17.0.0 they renamed this subdirectory back to
>> just __tuple.
>> This means that apparently people are not running "make delete-old"
>> after installations. Please don't forget that. :)
> 
> Well, but if you have an old system with LLVM 15 that you upgrade directly
> to LLVM 17 you will hit this even if you ran delete-old after your last
> upgrading that used LLVM 15.  We might need something to cope with this
> during the install target for libc++ in particular where this has occurred
> multiple times historically.

I have now added a workaround for this scenario, which is apparently
more common than I thought:

https://cgit.freebsd.org/src/commit/?id=ca217224f17229570f40227893353ca10ae1dda1

-Dimitry

Re: make installworld fails because /usr/include/c++/v1/__tuple is a file

[John Baldwin]

On 12/10/23 8:43 AM, Dimitry Andric wrote:

On 10 Dec 2023, at 15:11, Herbert J. Skuhra  wrote:


On Sun, Dec 10, 2023 at 01:22:38PM +, John F Carr wrote:

On arm64 running CURRENT from two weeks ago I updated to

  c711af772782 Bump __FreeBSD_version for llvm 17.0.6 merge

and built and installed from source.  make installworld failed:

  install: target directory `/usr/include/c++/v1/__tuple/' does not exist

That pathname is a file:

  -r--r--r--  1 root wheel 20512 Feb 15  2023 /usr/include/c++/v1/__tuple

Early in make output is

  mtree -deU -i -f /usr/src/etc/mtree/BSD.include.dist -p /usr/include
  ./c++/v1/__algorithm/pstl_backends missing (created)
  [...]
  ./c++/v1/__tuple missing (not created: File exists)

Should I remove the file and try again, or is there a more elegant fix?

The word "tuple" does not appear in UPDATING.


'make delete-old' should have removed this file.

bdd1243df58e6 (Dimitry Andric  2023-04-14 23:41:27 +0200   965)
OLD_FILES+=usr/include/c++/v1/__tuple


Ah yes, that's it. The file was removed during the upgrade from libc++
15.0 to 16.0, while its contents was split into a subdirectory named
__tuple_dir. In libc++ 17.0.0 they renamed this subdirectory back to
just __tuple.

This means that apparently people are not running "make delete-old"
after installations. Please don't forget that. :)


Well, but if you have an old system with LLVM 15 that you upgrade directly
to LLVM 17 you will hit this even if you ran delete-old after your last
upgrading that used LLVM 15.  We might need something to cope with this
during the install target for libc++ in particular where this has occurred
multiple times historically.

--
John Baldwin

Re: make installworld fails because /usr/include/c++/v1/__tuple is a file

[Dimitry Andric]

On 10 Dec 2023, at 15:11, Herbert J. Skuhra  wrote:
> 
> On Sun, Dec 10, 2023 at 01:22:38PM +, John F Carr wrote:
>> On arm64 running CURRENT from two weeks ago I updated to
>> 
>>  c711af772782 Bump __FreeBSD_version for llvm 17.0.6 merge
>> 
>> and built and installed from source.  make installworld failed:
>> 
>>  install: target directory `/usr/include/c++/v1/__tuple/' does not exist
>> 
>> That pathname is a file:
>> 
>>  -r--r--r--  1 root wheel 20512 Feb 15  2023 /usr/include/c++/v1/__tuple
>> 
>> Early in make output is
>> 
>>  mtree -deU -i -f /usr/src/etc/mtree/BSD.include.dist -p /usr/include
>>  ./c++/v1/__algorithm/pstl_backends missing (created)
>>  [...]
>>  ./c++/v1/__tuple missing (not created: File exists)
>> 
>> Should I remove the file and try again, or is there a more elegant fix?
>> 
>> The word "tuple" does not appear in UPDATING.
> 
> 'make delete-old' should have removed this file.
> 
> bdd1243df58e6 (Dimitry Andric  2023-04-14 23:41:27 +0200   965)
> OLD_FILES+=usr/include/c++/v1/__tuple

Ah yes, that's it. The file was removed during the upgrade from libc++
15.0 to 16.0, while its contents was split into a subdirectory named
__tuple_dir. In libc++ 17.0.0 they renamed this subdirectory back to
just __tuple.

This means that apparently people are not running "make delete-old"
after installations. Please don't forget that. :)

-Dimitry



signature.asc
Description: Message signed with OpenPGP

Re: make installworld fails because /usr/include/c++/v1/__tuple is a file

[Herbert J. Skuhra]

On Sun, Dec 10, 2023 at 01:22:38PM +, John F Carr wrote:
> On arm64 running CURRENT from two weeks ago I updated to
> 
>   c711af772782 Bump __FreeBSD_version for llvm 17.0.6 merge
> 
> and built and installed from source.  make installworld failed:
> 
>   install: target directory `/usr/include/c++/v1/__tuple/' does not exist
> 
> That pathname is a file:
> 
>   -r--r--r--  1 root wheel 20512 Feb 15  2023 /usr/include/c++/v1/__tuple
> 
> Early in make output is
> 
>   mtree -deU -i -f /usr/src/etc/mtree/BSD.include.dist -p /usr/include
>   ./c++/v1/__algorithm/pstl_backends missing (created)
>   [...]
>   ./c++/v1/__tuple missing (not created: File exists)
> 
> Should I remove the file and try again, or is there a more elegant fix?
> 
> The word "tuple" does not appear in UPDATING.

'make delete-old' should have removed this file.

bdd1243df58e6 (Dimitry Andric  2023-04-14 23:41:27 +0200   965)
OLD_FILES+=usr/include/c++/v1/__tuple

-- 
Herbert

make installworld fails because /usr/include/c++/v1/__tuple is a file

[John F Carr]

On arm64 running CURRENT from two weeks ago I updated to

  c711af772782 Bump __FreeBSD_version for llvm 17.0.6 merge

and built and installed from source.  make installworld failed:

  install: target directory `/usr/include/c++/v1/__tuple/' does not exist

That pathname is a file:

  -r--r--r--  1 root wheel 20512 Feb 15  2023 /usr/include/c++/v1/__tuple

Early in make output is

  mtree -deU -i -f /usr/src/etc/mtree/BSD.include.dist -p /usr/include
  ./c++/v1/__algorithm/pstl_backends missing (created)
  [...]
  ./c++/v1/__tuple missing (not created: File exists)

Should I remove the file and try again, or is there a more elegant fix?

The word "tuple" does not appear in UPDATING.

"make installworld" fails for main-n265819-af5e348c61da

[David Wolfskill]

This is for an in-place source update; machine is currently running:

freebeast(15.0-C)[15] uname -aUK
FreeBSD freebeast.catwhisker.org 15.0-CURRENT FreeBSD 15.0-CURRENT #427 
main-n265811-38ecc80b2a4e: Sun Oct  8 17:42:28 UTC 2023 
r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC 
amd64 151 151


Sources were updated to main-n265819-af5e348c61da.

Excerpt from the build typescript:

...
>>> Installing everything started on Mon Oct  9 11:26:45 UTC 2023
make[3]: "/common/S4/obj/usr/src/amd64.amd64/toolchain-metadata.mk" line 1: 
Using cached toolchain metadata from build at freebeast.catwhisker.org on Mon 
Oct  9 10:49:37 UTC 2023
...
install  -o root -g wheel -m 444 rk_grf.4.gz  /usr/share/man/man4/
install  -o root -g wheel -m 444 rk_i2c.4.gz  /usr/share/man/man4/
install  -o root -g wheel -m 444 rk_pinctrl.4.gz  /usr/share/man/man4/
rm -f /usr/share/man/man4/aarch64/armv8crypto.4 
/usr/share/man/man4/aarch64/armv8crypto.4.gz;  install -l h -o root -g wheel -m 
444  /usr/share/man/man4/armv8crypto.4.gz 
/usr/share/man/man4/aarch64/armv8crypto.4.gz
install: link /usr/share/man/man4/armv8crypto.4.gz -> 
/usr/share/man/man4/aarch64/armv8crypto.4.gz: No such file or directory
*** Error code 71

Stop.
make[7]: stopped in /usr/src/share/man/man4/man4.aarch64
*** Error code 1


So... a couple of things:
* This is an amd64 machine, building native.  I didn't specify anything
  with respect to aarch64, and have nothing about aarch64 mentioned in
  /etc/*.conf.

* While my build procedure is based on the information in src/UPDATING, I
  took the liberty (over a decade ago) to augment those instructions
  with a couple of additional steps just prior to issuing "make
  installworld":
  * One of those is to move /usr/include aside;
  * The other is to just completely remove /usr/share/man (recursively).

  In each case, this is not because I don't want the hierarchy in
  question; rather, it is because I want to be sure there is nothing
  extraneous in either.  "make hierarchy" has (in the past) been
  invoked by "make installworld" and everything has been fine.

  Prior to the above-described failure, I had an earlier one:

...
>> etcupdate -p OK
Mon Oct  9 11:10:29 UTC 2023
>> /usr/include.old removed
Mon Oct  9 11:10:29 UTC 2023
>> /usr/include moved aside
Mon Oct  9 11:10:29 UTC 2023
>> /usr/share/man removed
Mon Oct  9 11:10:29 UTC 2023
make[1]: "/common/S4/obj/usr/src/amd64.amd64/toolchain-metadata.mk" line 1: 
Using cached toolchain metadata from build at freebeast.catwhisker.org on Mon 
Oct  9 10:49:37 UTC 2023
--
>>> Install check world
--
...
installing DIRS CONFSDIR
install  -d -m 0755 -o root  -g wheel  /etc
installing DIRS NLSDIR
install  -d -m 0755 -o root  -g wheel  /usr/share/nls
install  -o root -g wheel -m 444 btree.3.gz  /usr/share/man/man3/
install: /usr/share/man/man3/: No such file or directory
*** Error code 71

Stop.
make[5]: stopped in /usr/src/lib/libc
*** Error code 1


I checked src/Makefile.inc1; it was last updated by:
| commit 1a18383a52bc373e316d224cef1298debf6f7e25
| Author: Pierre Pronchery 
| Date:   Fri Sep 15 17:14:16 2023 +0200
| 
| libcrypto: link engines and the legacy provider to libcrypto

Since I didn't see anything obvious that might have caused the observed
failure, I tweaked my procedure so that after removing /usr/share/man,
it then issued:

mkdir -p /usr/share/man/man{1,2,3{,lua},4,5,6,7,8,9}

Which appears to have got me through the initial issue.

I mention this in case there's a chance it might possibly be relevant.


Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
"I am not a member of any organized political party — I am a Democrat."
 - Will Rogers  (Huh.  Wonder what he'd say given recent events)

See https://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: head -r351056 self-hosted amd64 installworld fails with: "don't know how to make _testsDATA_FILESINS1_data/md5test-in. Stop"

[Simon J. Gerraty]

Cy Schubert  wrote:
> > installworld is failing with:
> >
> > ===> lib/libc/tests/hash (install)
> > install  -o root  -g wheel -m 555  hash_test  
> > /usr/tests/lib/libc/hash/hash_t
> > est
> > make[7]: don't know how to make _testsDATA_FILESINS1_data/md5test-in. Stop

Sorry about that.  Looks like more extensive fix is needed.

> Revert r351055 and installworld complete for now.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: head -r351056 self-hosted amd64 installworld fails with: "don't know how to make _testsDATA_FILESINS1_data/md5test-in. Stop"

[Cy Schubert]

In message <10aa93aa-4fd7-47af-bfd1-994ac5a8c...@yahoo.com>, Mark 
Millard write
s:
> While the buildworld buildkernel seemed to go okay, and so did installkernel,
> installworld is failing with:
>
> ===> lib/libc/tests/hash (install)
> install  -o root  -g wheel -m 555  hash_test  /usr/tests/lib/libc/hash/hash_t
> est
> make[7]: don't know how to make _testsDATA_FILESINS1_data/md5test-in. Stop
>
> make[7]: stopped in /usr/src/lib/libc/tests/hash
> *** Error code 2
>
> The original context was -r350364 .

Revert r351055 and installworld complete for now.


-- 
Cheers,
Cy Schubert 
FreeBSD UNIX: Web:  http://www.FreeBSD.org

The need of the many outweighs the greed of the few.


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

head -r351056 self-hosted amd64 installworld fails with: "don't know how to make _testsDATA_FILESINS1_data/md5test-in. Stop"

[Mark Millard]

While the buildworld buildkernel seemed to go okay, and so did installkernel,
installworld is failing with:

===> lib/libc/tests/hash (install)
install  -o root  -g wheel -m 555  hash_test  /usr/tests/lib/libc/hash/hash_test
make[7]: don't know how to make _testsDATA_FILESINS1_data/md5test-in. Stop

make[7]: stopped in /usr/src/lib/libc/tests/hash
*** Error code 2

The original context was -r350364 .


===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

-CURRENT "installworld" fails if not upgrading (e.g. building via Crochet)

[Karl Denninger]

svn updated this morning

Attempting to build 12 via Crochet fails with an error about the "ntpd"
user being missing during install.

Setting "-DDB_FROM_SRC" allows the install to complete.

I'm not sure where it's getting the base check from since this is a new
build into "empty" media (not an upgrade) -- should the "DB_FROM_SRC" be
detected on its own or is this just a Crochet screwball thing?

-- 
Karl Denninger
k...@denninger.net 
/The Market Ticker/
/[S/MIME encrypted email preferred]/


smime.p7s
Description: S/MIME Cryptographic Signature

Re: make installworld fails on install: process-control: No such file or directory

[Alan Somers]

Still works for me with a clean build.  Is it still failing for you?

On Tue, Jun 26, 2018 at 3:08 PM, Alan Somers  wrote:

> It works for me (though I didn't do a clean build).  Can you please svn up
> and try again?  I'll do a clean build in the meantime.
>
>
> On Tue, Jun 26, 2018 at 2:54 PM, Lars Schotte  wrote:
>
>> make installworld fails on install: process-control: No such file or
>> directory somewhere around Revision: 335679 of ^/head.
>>
>> --
>>  Lars Schotte
>>  Mudroňova 13
>> 92101 Piešťany
>> ___
>> freebsd-current@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org
>> "
>>
>
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: make installworld fails on install: process-control: No such file or directory

[Alan Somers]

It works for me (though I didn't do a clean build).  Can you please svn up
and try again?  I'll do a clean build in the meantime.

On Tue, Jun 26, 2018 at 2:54 PM, Lars Schotte  wrote:

> make installworld fails on install: process-control: No such file or
> directory somewhere around Revision: 335679 of ^/head.
>
> --
>  Lars Schotte
>  Mudroňova 13
> 92101 Piešťany
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

make installworld fails on install: process-control: No such file or directory

[Lars Schotte]

make installworld fails on install: process-control: No such file or
directory somewhere around Revision: 335679 of ^/head.

-- 
 Lars Schotte
 Mudroňova 13
92101 Piešťany
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: installworld fails on missing tzsetup when WITHOUT_DIALOG is set

[Baptiste Daroussin]

On Sun, Oct 23, 2016 at 11:41:23AM +0300, Guy Yur wrote:
> On Sat, Oct 22, 2016 at 7:23 PM, Baptiste Daroussin  wrote:
> > On Sat, Oct 22, 2016 at 06:51:28PM +0300, Guy Yur wrote:
> >> Hi,
> >> ...
> >
> > My proposal is a bit different: build tzsetup without dialog support :)
> >
> > https://reviews.freebsd.org/D8325
> >
> > Best regards,
> > Bapt
> 
> Thanks.

FYI it is in

Best regards,
Bapt


signature.asc
Description: PGP signature

Re: installworld fails on missing tzsetup when WITHOUT_DIALOG is set

[Guy Yur]

On Sat, Oct 22, 2016 at 7:23 PM, Baptiste Daroussin  wrote:
> On Sat, Oct 22, 2016 at 06:51:28PM +0300, Guy Yur wrote:
>> Hi,
>> ...
>
> My proposal is a bit different: build tzsetup without dialog support :)
>
> https://reviews.freebsd.org/D8325
>
> Best regards,
> Bapt

Thanks.

Guy
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: installworld fails on missing tzsetup when WITHOUT_DIALOG is set

[Baptiste Daroussin]

On Sat, Oct 22, 2016 at 06:51:28PM +0300, Guy Yur wrote:
> Hi,
> 
> installworld fails on missing tzsetup when src.conf has WITHOUT_DIALOG=
> and delete-old was previously run to remove tzsetup from the system.
> 
> mkdir -p /tmp/install.8gNIwAFV
> progs=$(for prog in [ awk cap_mkdb cat chflags chmod chown cmp cp
> date echo egrep find grep id install   ln make mkdir mtree mv pwd_mkdb
>  rm sed services_mkdb sh strip sysctl test true uname wc zic tzsetup
> makewhatis; do  if progpath=`which $prog`; then  echo $progpath;  else
>  echo "Required tool $prog not found in PATH." >&2;  exit 1;  fi;
> done);  libs=$(ldd -f "%o %p\n" -f "%o %p\n" $progs 2>/dev/null | sort
> -u |  while read line; do  set -- $line;  if [ "$2 $3" != "not found"
> ]; then  echo $2;  else  echo "Required library $1 not found." >&2;
> exit 1;  fi;  done);  cp $libs $progs /tmp/install.8gNIwAFV
> Required tool tzsetup not found in PATH.
> *** Error code 1
> 
> tzsetup is used in share/zoneinfo/Makefile when ${DESTDIR}/var/db/zoneinfo
> exists and some other conditions.
> 
> In my case, I don't have /var/db/zoneinfo since I manually created a symlink
> from /usr/share/zoneinfo/... to /etc/localtime instead of using tzsetup.
> 
> A possible fix is to add a WITHOUT_TZSETUP knob and not use
> tzsetup when the knob is enabled.
> 
> https://github.com/guyyur/freebsd-src_patches/blob/master/without_tzsetup_knob.patch
> (patch doesn't include regenerating src.conf.5)
> 
> Thanks,
> Guy
> ___

My proposal is a bit different: build tzsetup without dialog support :)

https://reviews.freebsd.org/D8325

Best regards,
Bapt


signature.asc
Description: PGP signature

installworld fails on missing tzsetup when WITHOUT_DIALOG is set

[Guy Yur]

Hi,

installworld fails on missing tzsetup when src.conf has WITHOUT_DIALOG=
and delete-old was previously run to remove tzsetup from the system.

mkdir -p /tmp/install.8gNIwAFV
progs=$(for prog in [ awk cap_mkdb cat chflags chmod chown cmp cp
date echo egrep find grep id install   ln make mkdir mtree mv pwd_mkdb
 rm sed services_mkdb sh strip sysctl test true uname wc zic tzsetup
makewhatis; do  if progpath=`which $prog`; then  echo $progpath;  else
 echo "Required tool $prog not found in PATH." >&2;  exit 1;  fi;
done);  libs=$(ldd -f "%o %p\n" -f "%o %p\n" $progs 2>/dev/null | sort
-u |  while read line; do  set -- $line;  if [ "$2 $3" != "not found"
]; then  echo $2;  else  echo "Required library $1 not found." >&2;
exit 1;  fi;  done);  cp $libs $progs /tmp/install.8gNIwAFV
Required tool tzsetup not found in PATH.
*** Error code 1

tzsetup is used in share/zoneinfo/Makefile when ${DESTDIR}/var/db/zoneinfo
exists and some other conditions.

In my case, I don't have /var/db/zoneinfo since I manually created a symlink
from /usr/share/zoneinfo/... to /etc/localtime instead of using tzsetup.

A possible fix is to add a WITHOUT_TZSETUP knob and not use
tzsetup when the knob is enabled.

https://github.com/guyyur/freebsd-src_patches/blob/master/without_tzsetup_knob.patch
(patch doesn't include regenerating src.conf.5)

Thanks,
Guy
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Installworld fails when /usr/bin and /usr/sbin are different FS / how to use symlinks in installworld?

[Alexander Leidinger]

Quoting Alexander Leidinger  (from Sat, 03  
Sep 2016 08:24:49 +0200):


Quoting Bryan Drewery  (from Fri, 2 Sep 2016  
15:51:56 -0700):



The error message is obvious, it tries to create a hardlink which is off
course not possible when src and dest of the link are on different FS.

My goal of an easy procedure (installworld into target datasets) doesn't
work like this off course. Do we have an easy way of telling
installworld to create symlinks instead of hardlinks, or alternatively a
way to tell to copy instead of doing a hardlink if the install hits the
cross-device case?


Maybe falling back to symlink could be done.


A copy-in-cross-fs-case would be the best solution, this way you  
don't need to care about having the right path (DESTDIR comes into  
the game here) specified on the comman line.


I just checked, this 9.6k file the only case were a hardlink would be  
done outside the dataset. Changing LINKS to SYMLINKS for chown would  
be the most easy solution. This would work in the usual use cases (and  
surely in the normal FreeBSD use), but it would fail in the edge case  
were someone is using relative-path based execution of chgrp in a  
shifted-away location without using chroot and expecting it will use  
chown from the shifted-away location.


Is this an use-case which we care about, or should we just change  
LINKS to SYMLINKS?


Without the need to support DESTDIR, the install-argument "-l m"  
(hardlink if same FS, symlink if cross-FS) would have been a less  
intrusive option for this. Unfortunately there is no linkoption "c"  
for copy-if-cross-FS (and I rather modify the Makefile locally than to  
spend time to implement such an option for just this one case).


Bye,
Alexander.

--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org  : PGP 0x8F31830F9F2772BF


pgpx1v7JsLjAs.pgp
Description: Digitale PGP-Signatur

Re: Installworld fails when /usr/bin and /usr/sbin are different FS / how to use symlinks in installworld?

[Alexander Leidinger]

Quoting Bryan Drewery  (from Fri, 2 Sep 2016  
15:51:56 -0700):



The error message is obvious, it tries to create a hardlink which is off
course not possible when src and dest of the link are on different FS.

My goal of an easy procedure (installworld into target datasets) doesn't
work like this off course. Do we have an easy way of telling
installworld to create symlinks instead of hardlinks, or alternatively a
way to tell to copy instead of doing a hardlink if the install hits the
cross-device case?


Maybe falling back to symlink could be done.


A copy-in-cross-fs-case would be the best solution, this way you don't  
need to care about having the right path (DESTDIR comes into the game  
here) specified on the comman line.



Couldn't you just make a usr-bin dataset and have usr-bin/bin and
usr-bin/sbin and symlink or nullfs-mount them in though?  I too go crazy
with datasets, but this seems a bit too much.


iocage is doing read-only zfs-clones of the datasets from the basejail  
location to the real jail location. I was hoping for a solution where  
I don't have to hack the inner workings of iocage. Additionally "copy  
in case of cross-fs case" looks like a useful feature in general.


My current (idea for a) workaround is "make -i installworld" and to  
copy the which failed. This is not clean, but looks less intrusive  
than introducing a new way (null-mounts) in iocage.


Bye,
Alexander.

--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org  : PGP 0x8F31830F9F2772BF


pgpKmTdOAhJAX.pgp
Description: Digitale PGP-Signatur

Re: Installworld fails when /usr/bin and /usr/sbin are different FS / how to use symlinks in installworld?

[Bryan Drewery]

On 9/2/2016 3:25 PM, Alexander Leidinger wrote:
> Hi,
> 
> background info:
>  - iocage (jail management) uses official release tarballs
>  - I want to install a jail from a specific src I compiled withour
> creating release tarballs (-> faster time to market), so I want to
> convince iocage to use what I provide via installworld
>  - jails of type "basejail" (jails read-only-share the base system) in
> iocage are handled via seperate zfs datasets for each directory
>  - as such /usr/bin and /usr/sbin are different datasets
> 
> I got this error in installworld:
> ---snip---
> ===> usr.sbin/chkgrp (install)
> install  -s -o root -g wheel -m 555   chkgrp
> /iocage/base/12.0-r305149M/root/usr/sbin/chkgrp
> install  -o root -g wheel -m 444  chkgrp.debug
> /iocage/base/12.0-r305149M/root/usr/lib/debug/usr/sbin/chkgrp.debug
> install  -o root -g wheel -m 444 chkgrp.8.gz 
> /iocage/base/12.0-r305149M/root/usr/share/man/man8/
> ===> usr.sbin/chown (install)
> install  -s -o root -g wheel -m 555   chown
> /iocage/base/12.0-r305149M/root/usr/sbin/chown
> install  -o root -g wheel -m 444  chown.debug
> /iocage/base/12.0-r305149M/root/usr/lib/debug/usr/sbin/chown.debug
> install  -o root -g wheel -m 444 chgrp.1.gz 
> /iocage/base/12.0-r305149M/root/usr/share/man/man1/
> install  -o root -g wheel -m 444 chown.8.gz 
> /iocage/base/12.0-r305149M/root/usr/share/man/man8/
> ===> usr.sbin/chown/tests (install)
> install  -o root  -g wheel -m 555  chown-f_test 
> /iocage/base/12.0-r305149M/root/usr/tests/usr.sbin/chown/chown-f_test
> install  -o root  -g wheel -m 444  Kyuafile 
> /iocage/base/12.0-r305149M/root/usr/tests/usr.sbin/chown/Kyuafile
> /usr/bin/chgrp -> /usr/sbin/chown
> install: link /iocage/base/12.0-r305149M/root/usr/sbin/chown ->
> /iocage/base/12.0-r305149M/root/usr/bin/chgrp: Cross-device link
> *** Error code 71
> 
> Stop.
> make[5]: stopped in /usr/src/usr.sbin/chown
> *** Error code 1
> 
> Stop.
> ---snip---
> 
> The error message is obvious, it tries to create a hardlink which is off
> course not possible when src and dest of the link are on different FS.
> 
> My goal of an easy procedure (installworld into target datasets) doesn't
> work like this off course. Do we have an easy way of telling
> installworld to create symlinks instead of hardlinks, or alternatively a
> way to tell to copy instead of doing a hardlink if the install hits the
> cross-device case?

Maybe falling back to symlink could be done.

Couldn't you just make a usr-bin dataset and have usr-bin/bin and
usr-bin/sbin and symlink or nullfs-mount them in though?  I too go crazy
with datasets, but this seems a bit too much.


-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

Installworld fails when /usr/bin and /usr/sbin are different FS / how to use symlinks in installworld?

[Alexander Leidinger]

Hi,

background info:
 - iocage (jail management) uses official release tarballs
 - I want to install a jail from a specific src I compiled withour  
creating release tarballs (-> faster time to market), so I want to  
convince iocage to use what I provide via installworld
 - jails of type "basejail" (jails read-only-share the base system)  
in iocage are handled via seperate zfs datasets for each directory

 - as such /usr/bin and /usr/sbin are different datasets

I got this error in installworld:
---snip---
===> usr.sbin/chkgrp (install)
install  -s -o root -g wheel -m 555   chkgrp  
/iocage/base/12.0-r305149M/root/usr/sbin/chkgrp
install  -o root -g wheel -m 444  chkgrp.debug  
/iocage/base/12.0-r305149M/root/usr/lib/debug/usr/sbin/chkgrp.debug
install  -o root -g wheel -m 444 chkgrp.8.gz   
/iocage/base/12.0-r305149M/root/usr/share/man/man8/

===> usr.sbin/chown (install)
install  -s -o root -g wheel -m 555   chown  
/iocage/base/12.0-r305149M/root/usr/sbin/chown
install  -o root -g wheel -m 444  chown.debug  
/iocage/base/12.0-r305149M/root/usr/lib/debug/usr/sbin/chown.debug
install  -o root -g wheel -m 444 chgrp.1.gz   
/iocage/base/12.0-r305149M/root/usr/share/man/man1/
install  -o root -g wheel -m 444 chown.8.gz   
/iocage/base/12.0-r305149M/root/usr/share/man/man8/

===> usr.sbin/chown/tests (install)
install  -o root  -g wheel -m 555  chown-f_test   
/iocage/base/12.0-r305149M/root/usr/tests/usr.sbin/chown/chown-f_test
install  -o root  -g wheel -m 444  Kyuafile   
/iocage/base/12.0-r305149M/root/usr/tests/usr.sbin/chown/Kyuafile

/usr/bin/chgrp -> /usr/sbin/chown
install: link /iocage/base/12.0-r305149M/root/usr/sbin/chown ->  
/iocage/base/12.0-r305149M/root/usr/bin/chgrp: Cross-device link

*** Error code 71

Stop.
make[5]: stopped in /usr/src/usr.sbin/chown
*** Error code 1

Stop.
---snip---

The error message is obvious, it tries to create a hardlink which is  
off course not possible when src and dest of the link are on different  
FS.


My goal of an easy procedure (installworld into target datasets)  
doesn't work like this off course. Do we have an easy way of telling  
installworld to create symlinks instead of hardlinks, or alternatively  
a way to tell to copy instead of doing a hardlink if the install hits  
the cross-device case?


Bye,
Alexander.

--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org  : PGP 0x8F31830F9F2772BF


pgpBlT2MUqRFA.pgp
Description: Digitale PGP-Signatur

Re: Installworld fails with TMPDIR pointing to NFS mounted directory

[Tom Vijlbrief]

Op di 12 jan. 2016 om 18:08 schreef NGie Cooper :

>
> > On Jan 12, 2016, at 08:42, Tom Vijlbrief  wrote:
> >
> > If have this issue with 11-CURRENT on my raspberry 1 and 2, but I do not
> > think it is raspberry related or even 11-CURRENT related.
> >
> > export TMPDIR=/media/usbdisk/tmp
> >
> > make installword MAKEOBJDIRPREFIX=/media/swan/obj
>
> Hi Tom,
> MAKEOBJDIRPREFIX should always be set via the environment, not the
> command line, e.g.
>
> export MAKEOBJDIRPREFIX=/media/swan/obj
> make installworld
>
> Cheers,
> -NGie


I think I actually did the export and not as I typed in my mail,
the export is in my shell history :-)

I also added:

rpc_lockd_enable="YES"

to my /etc/rc.conf and rebooted (rpc.lockd is now running) as Bryan
suggested, but I don't think that it is needed if the only client accessing
the NFS tmp dir is the local client?

[root@rpibsd /media/swan/src]# env | grep swan
TMPDIR=/media/swan/tmp
PWD=/media/swan/src
MAKEOBJDIRPREFIX=/media/swan/obj

make installworld DESTDIR=/d/root11

Same result:

===> etc/sendmail (install)
cd /media/swan/src/etc/../share/man; make makedb
makewhatis /d/root11/usr/share/man
makewhatis /d/root11/usr/share/openssl/man
rm: /media/swan/tmp/install.sy3BjziY/locale/en_US.UTF-8: Directory not empty
rm: /media/swan/tmp/install.sy3BjziY/locale: Directory not empty
rm: /media/swan/tmp/install.sy3BjziY: Directory not empty
*** Error code 1

Stop.
make[1]: stopped in /media/swan/src
*** Error code 1

Stop.
make: stopped in /media/swan/src
[root@rpibsd /media/swan/src]#
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Installworld fails with TMPDIR pointing to NFS mounted directory

[Garrett Cooper]

> On Jan 12, 2016, at 11:21, Tom Vijlbrief  wrote:
> 
> 
> Op di 12 jan. 2016 om 18:08 schreef NGie Cooper :
>> 
>> > On Jan 12, 2016, at 08:42, Tom Vijlbrief  wrote:
>> >
>> > If have this issue with 11-CURRENT on my raspberry 1 and 2, but I do not
>> > think it is raspberry related or even 11-CURRENT related.
>> >
>> > export TMPDIR=/media/usbdisk/tmp
>> >
>> > make installword MAKEOBJDIRPREFIX=/media/swan/obj
>> 
>> Hi Tom,
>> MAKEOBJDIRPREFIX should always be set via the environment, not the 
>> command line, e.g.
>> 
>> export MAKEOBJDIRPREFIX=/media/swan/obj
>> make installworld
>> 
>> Cheers,
>> -NGie
> 
> I think I actually did the export and not as I typed in my mail,
> the export is in my shell history :-)
> 
> I also added:
> 
> rpc_lockd_enable="YES"
> 
> to my /etc/rc.conf and rebooted (rpc.lockd is now running) as Bryan 
> suggested, but I don't think that it is needed if the only client accessing 
> the NFS tmp dir is the local client?
> 
> [root@rpibsd /media/swan/src]# env | grep swan
> TMPDIR=/media/swan/tmp
> PWD=/media/swan/src
> MAKEOBJDIRPREFIX=/media/swan/obj
> 
> make installworld DESTDIR=/d/root11
> 
> Same result:
> 
> ===> etc/sendmail (install)
> cd /media/swan/src/etc/../share/man; make makedb
> makewhatis /d/root11/usr/share/man
> makewhatis /d/root11/usr/share/openssl/man
> rm: /media/swan/tmp/install.sy3BjziY/locale/en_US.UTF-8: Directory not empty
> rm: /media/swan/tmp/install.sy3BjziY/locale: Directory not empty
> rm: /media/swan/tmp/install.sy3BjziY: Directory not empty
> *** Error code 1
> 
> Stop.
> make[1]: stopped in /media/swan/src
> *** Error code 1
> 
> Stop.
> make: stopped in /media/swan/src
> [root@rpibsd /media/swan/src]# 

The NFS "directory not empty" issue has been a common annoyance for me for 
several years. It's not just you... It deserves a bug though.
Thanks!
-NGie
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Installworld fails with TMPDIR pointing to NFS mounted directory

[Sergey Kandaurov]

On 12 January 2016 at 19:42, Tom Vijlbrief  wrote:
> [..]
> export TMPDIR=/media/swan/tmp
>
> The NFS server exports /media/swan which has a src/ obj/ and tmp/
> subdirectory.
> src/ has the sources, obj/ is filled correctly by makeworld.
> The tmp dir has the correct permissions. The installworld runs till the
> end, except for the last cleanup action which fails:
>
> ===> etc/sendmail (install)
> cd /media/swan/src/etc/../share/man; make makedb
> makewhatis /d/root11/usr/share/man
> makewhatis /d/root11/usr/share/openssl/man
> rm: /media/swan/tmp/install.xrgbPMy8/locale/en_US.UTF-8: Directory not empty
> rm: /media/swan/tmp/install.xrgbPMy8/locale: Directory not empty
> rm: /media/swan/tmp/install.xrgbPMy8: Directory not empty
> *** Error code 1

Search for NFS "sillyrename".

-- 
wbr,
pluknet
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Installworld fails with TMPDIR pointing to NFS mounted directory

[Tom Vijlbrief]

https://lists.freebsd.org/pipermail/freebsd-current/2010-September/019820.html
Op 12 jan. 2016 20:39 schreef "Garrett Cooper" :

>
> On Jan 12, 2016, at 11:21, Tom Vijlbrief  wrote:
>
>
> Op di 12 jan. 2016 om 18:08 schreef NGie Cooper :
>
>>
>> > On Jan 12, 2016, at 08:42, Tom Vijlbrief  wrote:
>> >
>> > If have this issue with 11-CURRENT on my raspberry 1 and 2, but I do not
>> > think it is raspberry related or even 11-CURRENT related.
>> >
>> > export TMPDIR=/media/usbdisk/tmp
>> >
>> > make installword MAKEOBJDIRPREFIX=/media/swan/obj
>>
>> Hi Tom,
>> MAKEOBJDIRPREFIX should always be set via the environment, not
>> the command line, e.g.
>>
>> export MAKEOBJDIRPREFIX=/media/swan/obj
>> make installworld
>>
>> Cheers,
>> -NGie
>
>
> I think I actually did the export and not as I typed in my mail,
> the export is in my shell history :-)
>
> I also added:
>
> rpc_lockd_enable="YES"
>
> to my /etc/rc.conf and rebooted (rpc.lockd is now running) as Bryan
> suggested, but I don't think that it is needed if the only client accessing
> the NFS tmp dir is the local client?
>
> [root@rpibsd /media/swan/src]# env | grep swan
> TMPDIR=/media/swan/tmp
> PWD=/media/swan/src
> MAKEOBJDIRPREFIX=/media/swan/obj
>
> make installworld DESTDIR=/d/root11
>
> Same result:
>
> ===> etc/sendmail (install)
> cd /media/swan/src/etc/../share/man; make makedb
> makewhatis /d/root11/usr/share/man
> makewhatis /d/root11/usr/share/openssl/man
> rm: /media/swan/tmp/install.sy3BjziY/locale/en_US.UTF-8: Directory not
> empty
> rm: /media/swan/tmp/install.sy3BjziY/locale: Directory not empty
> rm: /media/swan/tmp/install.sy3BjziY: Directory not empty
> *** Error code 1
>
> Stop.
> make[1]: stopped in /media/swan/src
> *** Error code 1
>
> Stop.
> make: stopped in /media/swan/src
> [root@rpibsd /media/swan/src]#
>
>
> The NFS "directory not empty" issue has been a common annoyance for me for
> several years. It's not just you... It deserves a bug though.
> Thanks!
> -NGie
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Installworld fails with TMPDIR pointing to NFS mounted directory

[NGie Cooper]

> On Jan 12, 2016, at 08:42, Tom Vijlbrief  wrote:
> 
> If have this issue with 11-CURRENT on my raspberry 1 and 2, but I do not
> think it is raspberry related or even 11-CURRENT related.
> 
> export TMPDIR=/media/usbdisk/tmp
> 
> make installword MAKEOBJDIRPREFIX=/media/swan/obj

Hi Tom,
MAKEOBJDIRPREFIX should always be set via the environment, not the 
command line, e.g.

export MAKEOBJDIRPREFIX=/media/swan/obj
make installworld

Cheers,
-NGie
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Installworld fails with TMPDIR pointing to NFS mounted directory

[Bryan Drewery]

On 1/12/16 8:42 AM, Tom Vijlbrief wrote:
> If have this issue with 11-CURRENT on my raspberry 1 and 2, but I do not
> think it is raspberry related or even 11-CURRENT related.
> 
> export TMPDIR=/media/usbdisk/tmp
> 
> make installword MAKEOBJDIRPREFIX=/media/swan/obj
> 
> Works as expected but fails cleaning up when TMPDIR points to an NFS
> mounted directory:
> 
> export TMPDIR=/media/swan/tmp
> 
> The NFS server exports /media/swan which has a src/ obj/ and tmp/
> subdirectory.
> src/ has the sources, obj/ is filled correctly by makeworld.
> The tmp dir has the correct permissions. The installworld runs till the
> end, except for the last cleanup action which fails:
> 
> ===> etc/sendmail (install)
> cd /media/swan/src/etc/../share/man; make makedb
> makewhatis /d/root11/usr/share/man
> makewhatis /d/root11/usr/share/openssl/man
> rm: /media/swan/tmp/install.xrgbPMy8/locale/en_US.UTF-8: Directory not empty
> rm: /media/swan/tmp/install.xrgbPMy8/locale: Directory not empty
> rm: /media/swan/tmp/install.xrgbPMy8: Directory not empty
> *** Error code 1

Well, it's not really a build or installworld problem. Are you running
the proper NFS daemons for lock/rpc?

> 
> Stop.
> make[1]: stopped in /media/swan/src
> *** Error code 1
> 
> Stop.
> make: stopped in /media/swan/src
> 
> On some runs just a single error message that complains about:
> /media/swan/tmp/install.xyz
> not being empty, but an "ls" shows no files and an "rmdir /media/swan/tmp/
> install.xyz" succeeds!
> In the example above  "/media/swan/tmp/install.xrgbPMy8/locale/en_US.UTF-8"
> IS empty!
> 
> It is as if a removed file remains visible for the client for a while.
> 
> The NFS server is running Ubuntu 15.10, NFSv3 is used, no other clients
> access the NFS tmp directory,
> no error messages on the client or server dmesg.
> 
> /etc/exports on the server:
> 
> /export/all/bsd
> 192.168.0.0/24(rw,no_root_squash,nohide,insecure,no_subtree_check,async)
> 
> The systems have completed many build/install world/kernel cycles using
> this NFS mount and are rock solid.
> 
> Any hints would be appreciated.
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 


-- 
Regards,
Bryan Drewery
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Installworld fails with TMPDIR pointing to NFS mounted directory

[Tom Vijlbrief]

If have this issue with 11-CURRENT on my raspberry 1 and 2, but I do not
think it is raspberry related or even 11-CURRENT related.

export TMPDIR=/media/usbdisk/tmp

make installword MAKEOBJDIRPREFIX=/media/swan/obj

Works as expected but fails cleaning up when TMPDIR points to an NFS
mounted directory:

export TMPDIR=/media/swan/tmp

The NFS server exports /media/swan which has a src/ obj/ and tmp/
subdirectory.
src/ has the sources, obj/ is filled correctly by makeworld.
The tmp dir has the correct permissions. The installworld runs till the
end, except for the last cleanup action which fails:

===> etc/sendmail (install)
cd /media/swan/src/etc/../share/man; make makedb
makewhatis /d/root11/usr/share/man
makewhatis /d/root11/usr/share/openssl/man
rm: /media/swan/tmp/install.xrgbPMy8/locale/en_US.UTF-8: Directory not empty
rm: /media/swan/tmp/install.xrgbPMy8/locale: Directory not empty
rm: /media/swan/tmp/install.xrgbPMy8: Directory not empty
*** Error code 1

Stop.
make[1]: stopped in /media/swan/src
*** Error code 1

Stop.
make: stopped in /media/swan/src

On some runs just a single error message that complains about:
/media/swan/tmp/install.xyz
not being empty, but an "ls" shows no files and an "rmdir /media/swan/tmp/
install.xyz" succeeds!
In the example above  "/media/swan/tmp/install.xrgbPMy8/locale/en_US.UTF-8"
IS empty!

It is as if a removed file remains visible for the client for a while.

The NFS server is running Ubuntu 15.10, NFSv3 is used, no other clients
access the NFS tmp directory,
no error messages on the client or server dmesg.

/etc/exports on the server:

/export/all/bsd
192.168.0.0/24(rw,no_root_squash,nohide,insecure,no_subtree_check,async)

The systems have completed many build/install world/kernel cycles using
this NFS mount and are rock solid.

Any hints would be appreciated.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

CURRENT installworld fails: LC_CTYPE: No such file or directory

[O. Hartmann]

The recent CURRENT starts dropping "make installworld" since two days ago, now 
at
revision 290923, with the error shown below.

Regards,

oh


[...]
===> share/ctypedef (install)
install -o root  -g wheel -m 444
be_BY.CP1131.LC_CTYPE  /usr/share/locale/be_BY.CP1131/LC_CTYPE install -o root  
-g wheel
-m 444  ca_IT.ISO8859-1.LC_CTYPE  /usr/share/locale/ca_IT.ISO8859-1/LC_CTYPE
install: /usr/share/locale/ca_IT.ISO8859-1/LC_CTYPE: No such file or directory 
*** Error
code 71


pgp9Yrfg5trvP.pgp
Description: OpenPGP digital signature

Re: Make installworld fails on file not found (Error code 71)

[Thomas Mueller]

> > It looks like a problem with WITHOUT_MANCOMPRESS.

> > I am looking into it.


> A fix is now committed. It has been broken since June.

> Regards,
> Bryan Drewery

Thanks for the fix, computer is now busy with NetBSD update from 6.99.44 (16 
months old) to 7.99.21 for both amd64 and i386, but I intend to get back to the 
FreeBSD update after that is done.

I checked /etc/src.conf and found
WITHOUT_MANCOMPRESS=yes
WITHOUT_DOCCOMPRESS=yes

I looked in other directions for the problem and would have just been wasting 
time and computer energy.

Compressed man pages can be a nuisance, and not really necessary or helpful 
with today's big hard drives and USB sticks.

Good I was able to expose a bug of four months' standing.

UPDATE: buildworld succeeded, but installworld crashed to the debugger prompt:
  Fatal trap 12: page fault while in kernel mode

Reboot attempt, both with custom kernel and GENERIB, failed:

/libc/libc.so.7: version FBSD_1.3 required by /bin/sh not defined

GENERIB is kernel config derived from GENERIC but with some outdated devices 
unlikely to be found on a modern computer system removed, and some wireless 
drivers including rsu added.

So now that FreeBSD installation is not bootable.  I ran
fsck_ffs -y /dev/dk9 
from NetBSD 7.99.21 (current) i386, /dev/dk9 being NetBSD's version of the 
FreeBSD partition name.

I can say "make installworld" likely failed because, after interrupted 
(crashed) installworld, userland was out of sync.

I have another FreeBSD partition, 10.1-STABLE amd64, dating to January 29, 
2015, could boot into that and try to update both that (10.2-STABLE) and the 
messed-up FreeBSD-current installation (with HEAD/current).

MicroNet Fantom external hard drives, 1 TB to 5 TB, USB 3.0 and eSATA, look 
attractive now, back up a whole OS installation, eSATA figures to work better 
than USB 3.0: better for FreeBSD and NetBSD, and better recognition at boot 
time by motherboard/BIOS/UEFI.

Tom

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Make installworld fails on file not found (Error code 71)

[Thomas Mueller]

> > It looks like a problem with WITHOUT_MANCOMPRESS.

> > I am looking into it.


> A fix is now committed. It has been broken since June.

> Regards,
> Bryan Drewery

Thanks for the fix, computer is now busy with NetBSD update from 6.99.44 (16 
months old) to 7.99.21 for both amd64 and i386, but I intend to get back to the 
FreeBSD update after that is done.

I checked /etc/src.conf and found
WITHOUT_MANCOMPRESS=yes
WITHOUT_DOCCOMPRESS=yes

I looked in other directions for the problem and would have just been wasting 
time and computer energy.

Compressed man pages can be a nuisance, and not really necessary or helpful 
with today's big hard drives and USB sticks.

Good I was able to expose a bug of four months' standing.

Tom

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Make installworld fails on file not found (Error code 71)

[Thomas Mueller]

I was trying to test the new i915 graphics driver but got stuck in building and 
installing the userland:

/usr/share/man/man2/mknodat.2 -> /usr/share/man/man2/mknod.2
/usr/share/man/man2/munlock.2 -> /usr/share/man/man2/mlock.2
/usr/share/man/man2/munlockall.2 -> /usr/share/man/man2/mlockall.2
/usr/share/man/man2/modfnext.2 -> /usr/share/man/man2/modnext.2
/usr/share/man/man2/nmount.2 -> /usr/share/man/man2/mount.2
/usr/share/man/man2/unmount.2 -> /usr/share/man/man2/mount.2
/usr/share/man/man2/mq_timedreceive.2 -> /usr/share/man/man2/mq_receive.2
/usr/share/man/man2/mq_timedsend.2 -> /usr/share/man/man2/mq_send.2
/usr/share/man/man2/ntp_gettime.2 -> /usr/share/man/man2/ntp_adjtime.2
/usr/share/man/man2/numa_setaffinity.2 -> /usr/share/man/man2/numa_getaffinity.2
install: link /usr/share/man/man2/numa_getaffinity.2 -> 
/usr/share/man/man2/numa_setaffinity.2: No such file or directory
*** Error code 71

Stop.
make[5]: stopped in /usr/src/lib/libc
*** Error code 1

Stop.
make[4]: stopped in /usr/src/lib
*** Error code 1

Stop.
make[3]: stopped in /usr/src
*** Error code 1


I tried svn-updating, building and installing again, the last time was after 
running "make cleandir" twice from /usr/src, then "make clean".

But I find the host system has no file

install: link /usr/share/man/man2/numa_getaffinity.2 -> 
/usr/share/man/man2/numa_setaffinity.2: No such file or directory

either regular or compressed; last userland update was April 27, 2015.

So I can't figure what I'm doing wrong, that any further attempt to update 
FreeBSD-current is a stab in the dark until I get a better clue.

either regular or compressed.

So I can't figure what I'm doing wrong.

Tom

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Make installworld fails on file not found (Error code 71)

[Oliver Pinter]

On Tue, Oct 20, 2015 at 10:07 AM, Thomas Mueller
 wrote:
> I was trying to test the new i915 graphics driver but got stuck in building 
> and installing the userland:
>
> /usr/share/man/man2/mknodat.2 -> /usr/share/man/man2/mknod.2
> /usr/share/man/man2/munlock.2 -> /usr/share/man/man2/mlock.2
> /usr/share/man/man2/munlockall.2 -> /usr/share/man/man2/mlockall.2
> /usr/share/man/man2/modfnext.2 -> /usr/share/man/man2/modnext.2
> /usr/share/man/man2/nmount.2 -> /usr/share/man/man2/mount.2
> /usr/share/man/man2/unmount.2 -> /usr/share/man/man2/mount.2
> /usr/share/man/man2/mq_timedreceive.2 -> /usr/share/man/man2/mq_receive.2
> /usr/share/man/man2/mq_timedsend.2 -> /usr/share/man/man2/mq_send.2
> /usr/share/man/man2/ntp_gettime.2 -> /usr/share/man/man2/ntp_adjtime.2
> /usr/share/man/man2/numa_setaffinity.2 -> 
> /usr/share/man/man2/numa_getaffinity.2
> install: link /usr/share/man/man2/numa_getaffinity.2 -> 
> /usr/share/man/man2/numa_setaffinity.2: No such file or directory
> *** Error code 71
>
> Stop.
> make[5]: stopped in /usr/src/lib/libc
> *** Error code 1
>
> Stop.
> make[4]: stopped in /usr/src/lib
> *** Error code 1
>
> Stop.
> make[3]: stopped in /usr/src
> *** Error code 1
>
> Stop.
> make[2]: stopped in /usr/src
> *** Error code 1
>
> Stop.
> make[1]: stopped in /usr/src
> *** Error code 1
>
> Stop.
> make: stopped in /usr/src
>
>
> Now I have a new kernel on a userland dating to last April 27.
>
> I got this same result with "make installworld" also on previous attempt just 
> a day previous.
>
> Do I need to clean out old build directory tree?  Build runs cleandir 
> automatically, but do I need more, like rm -R /usr/obj/* ?
>
> If this happened in NetBSD, I would use -r with build.sh which gets rid of 
> outdated stuff in build directories, and will get a chance to try this as I 
> try to update a system last built 14 months ago.
>
> What do I need to do in FreeBSD?

If you like to test the i915kms driver from "binary source", you could
fine them in our (HardenedBSD) ISOs:
http://jenkins.hardenedbsd.org/builds/HardenedBSD-i915kms-amd64-LATEST/ISO-IMAGES/

>
> Tom
>
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Make installworld fails on file not found (Error code 71)

[Bryan Drewery]

On 10/22/15 12:05 AM, Thomas Mueller wrote:
> I was trying to test the new i915 graphics driver but got stuck in building 
> and installing the userland:
> 
> /usr/share/man/man2/mknodat.2 -> /usr/share/man/man2/mknod.2
> /usr/share/man/man2/munlock.2 -> /usr/share/man/man2/mlock.2
> /usr/share/man/man2/munlockall.2 -> /usr/share/man/man2/mlockall.2
> /usr/share/man/man2/modfnext.2 -> /usr/share/man/man2/modnext.2
> /usr/share/man/man2/nmount.2 -> /usr/share/man/man2/mount.2
> /usr/share/man/man2/unmount.2 -> /usr/share/man/man2/mount.2
> /usr/share/man/man2/mq_timedreceive.2 -> /usr/share/man/man2/mq_receive.2
> /usr/share/man/man2/mq_timedsend.2 -> /usr/share/man/man2/mq_send.2
> /usr/share/man/man2/ntp_gettime.2 -> /usr/share/man/man2/ntp_adjtime.2
> /usr/share/man/man2/numa_setaffinity.2 -> 
> /usr/share/man/man2/numa_getaffinity.2
> install: link /usr/share/man/man2/numa_getaffinity.2 -> 
> /usr/share/man/man2/numa_setaffinity.2: No such file or directory
> *** Error code 71

It looks like a problem with WITHOUT_MANCOMPRESS.

I am looking into it.

-- 
Regards,
Bryan Drewery
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Make installworld fails on file not found (Error code 71)

[Bryan Drewery]

On 10/22/15 2:31 PM, Bryan Drewery wrote:
> On 10/22/15 12:05 AM, Thomas Mueller wrote:
>> I was trying to test the new i915 graphics driver but got stuck in building 
>> and installing the userland:
>>
>> /usr/share/man/man2/mknodat.2 -> /usr/share/man/man2/mknod.2
>> /usr/share/man/man2/munlock.2 -> /usr/share/man/man2/mlock.2
>> /usr/share/man/man2/munlockall.2 -> /usr/share/man/man2/mlockall.2
>> /usr/share/man/man2/modfnext.2 -> /usr/share/man/man2/modnext.2
>> /usr/share/man/man2/nmount.2 -> /usr/share/man/man2/mount.2
>> /usr/share/man/man2/unmount.2 -> /usr/share/man/man2/mount.2
>> /usr/share/man/man2/mq_timedreceive.2 -> /usr/share/man/man2/mq_receive.2
>> /usr/share/man/man2/mq_timedsend.2 -> /usr/share/man/man2/mq_send.2
>> /usr/share/man/man2/ntp_gettime.2 -> /usr/share/man/man2/ntp_adjtime.2
>> /usr/share/man/man2/numa_setaffinity.2 -> 
>> /usr/share/man/man2/numa_getaffinity.2
>> install: link /usr/share/man/man2/numa_getaffinity.2 -> 
>> /usr/share/man/man2/numa_setaffinity.2: No such file or directory
>> *** Error code 71
> 
> It looks like a problem with WITHOUT_MANCOMPRESS.
> 
> I am looking into it.
> 

A fix is now committed. It has been broken since June.

-- 
Regards,
Bryan Drewery
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Make installworld fails on file not found (Error code 71)

[Sergey Kandaurov]

On 20 October 2015 at 11:07, Thomas Mueller  wrote:
> I was trying to test the new i915 graphics driver but got stuck in building 
> and installing the userland:
>
> /usr/share/man/man2/mknodat.2 -> /usr/share/man/man2/mknod.2
> /usr/share/man/man2/munlock.2 -> /usr/share/man/man2/mlock.2
> /usr/share/man/man2/munlockall.2 -> /usr/share/man/man2/mlockall.2
> /usr/share/man/man2/modfnext.2 -> /usr/share/man/man2/modnext.2
> /usr/share/man/man2/nmount.2 -> /usr/share/man/man2/mount.2
> /usr/share/man/man2/unmount.2 -> /usr/share/man/man2/mount.2
> /usr/share/man/man2/mq_timedreceive.2 -> /usr/share/man/man2/mq_receive.2
> /usr/share/man/man2/mq_timedsend.2 -> /usr/share/man/man2/mq_send.2
> /usr/share/man/man2/ntp_gettime.2 -> /usr/share/man/man2/ntp_adjtime.2
> /usr/share/man/man2/numa_setaffinity.2 -> 
> /usr/share/man/man2/numa_getaffinity.2
> install: link /usr/share/man/man2/numa_getaffinity.2 -> 
> /usr/share/man/man2/numa_setaffinity.2: No such file or directory
> *** Error code 71
>

This looks like if you would try to installworld on newer sources and older
objs without doing buildworld first to get in sync.

-- 
wbr,
pluknet
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Make installworld fails on file not found (Error code 71)

[Thomas Mueller]

I was trying to test the new i915 graphics driver but got stuck in building and 
installing the userland:

/usr/share/man/man2/mknodat.2 -> /usr/share/man/man2/mknod.2
/usr/share/man/man2/munlock.2 -> /usr/share/man/man2/mlock.2
/usr/share/man/man2/munlockall.2 -> /usr/share/man/man2/mlockall.2
/usr/share/man/man2/modfnext.2 -> /usr/share/man/man2/modnext.2
/usr/share/man/man2/nmount.2 -> /usr/share/man/man2/mount.2
/usr/share/man/man2/unmount.2 -> /usr/share/man/man2/mount.2
/usr/share/man/man2/mq_timedreceive.2 -> /usr/share/man/man2/mq_receive.2
/usr/share/man/man2/mq_timedsend.2 -> /usr/share/man/man2/mq_send.2
/usr/share/man/man2/ntp_gettime.2 -> /usr/share/man/man2/ntp_adjtime.2
/usr/share/man/man2/numa_setaffinity.2 -> /usr/share/man/man2/numa_getaffinity.2
install: link /usr/share/man/man2/numa_getaffinity.2 -> 
/usr/share/man/man2/numa_setaffinity.2: No such file or directory
*** Error code 71

Stop.
make[5]: stopped in /usr/src/lib/libc
*** Error code 1

Stop.
make[4]: stopped in /usr/src/lib
*** Error code 1

Stop.
make[3]: stopped in /usr/src
*** Error code 1

Stop.
make[2]: stopped in /usr/src
*** Error code 1

Stop.
make[1]: stopped in /usr/src
*** Error code 1

Stop.
make: stopped in /usr/src


Now I have a new kernel on a userland dating to last April 27.

I got this same result with "make installworld" also on previous attempt just a 
day previous.

Do I need to clean out old build directory tree?  Build runs cleandir 
automatically, but do I need more, like rm -R /usr/obj/* ?

If this happened in NetBSD, I would use -r with build.sh which gets rid of 
outdated stuff in build directories, and will get a chance to try this as I try 
to update a system last built 14 months ago.

What do I need to do in FreeBSD?

Tom

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Make installworld fails on file not found (Error code 71)

[Thomas Mueller]

from Jeffrey Bouquet:

> I'd installworld in single user mode...  sorry for no backstory. Worked here.

Sure, I used single user mode, as advised in UPDATING file.

from Sergey Kandauro:

> This looks like if you would try to installworld on newer sources and older
> objs without doing buildworld first to get in sync.

I ran "make buildworld" successfully, and "make kernel" before rebooting into 
single-user mode, mergemaster -Fp and make installworld.

Tom

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: installworld fails

[Ryan Stone]

On Tue, Jan 22, 2013 at 1:24 AM, Jason Evans jas...@freebsd.org wrote:

 On Jan 21, 2013, at 10:13 PM, AN a...@neu.net wrote:
  FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #29 r245766: Tue Jan 22
 00:49:02 EST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL  amd64
 
  Is anyone seeing this?
 
  install -l s usr/src/sys /sys
  install: /sys/sys: Directory not empty
  *** [distrib-dirs] Error code 71

 Yes.  I haven't tracked down the cause, but doing 'rm /sys' prior to
 installworld is an effective workaround.

 Jason


 CC'ing Brooks, who I believe made this change.

It looks as though install is using the semantics of ln -s /usr/src/sys
/sys instead of ln -fs.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

r245791: make installworld fails

[O. Hartmann]

A make installworld fails since today on FreeBSD 10.0-CURRENT/amd64.
FreeBSD 10.0-CURRENT #0 r245455: Tue Jan 15 11:31:21 CET 2013

See error message below.


Regards,

Oliver


[...]

mkdir -p /tmp/install.qSk73yBh
progs=$(for prog in [ awk cap_mkdb cat chflags chmod chown  date echo
egrep find grep install-info  ln lockf make mkdir mtree mv pwd_mkdb rm
sed sh sysctl  test true uname wc zic tzsetup; do  if progpath=`which
$prog`; then  echo $progpath;  else  echo Required tool $prog not found
in PATH. 2;  exit 1;  fi;  done);  libs=$(ldd -f %o %p\n -f %o
%p\n $progs 2/dev/null | sort -u |  while read line; do  set -- $line;
 if [ $2 $3 != not found ]; then  echo $2;  else  echo Required
library $1 not found. 2;  exit 1;  fi;  done);  cp $libs $progs
/tmp/install.qSk73yBh
cp -R ${PATH_LOCALE:-/usr/share/locale} /tmp/install.qSk73yBh/locale
cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=amd64 MACHINE=amd64
CPUTYPE=native GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin
GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font
GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac
PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/tmp/install.qSk73yBh
 LD_LIBRARY_PATH=/tmp/install.qSk73yBh
PATH_LOCALE=/tmp/install.qSk73yBh/locale
/usr/obj/usr/src/make.amd64/make -f Makefile.inc1
__MAKE_SHELL=/tmp/install.qSk73yBh/sh reinstall;
MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=amd64 MACHINE=amd64
CPUTYPE=native GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin
GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font
GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac
PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/tmp/install.qSk73yBh
 LD_LIBRARY_PATH=/tmp/install.qSk73yBh
PATH_LOCALE=/tmp/install.qSk73yBh/locale rm -rf /tmp/install.qSk73yBh
--
 Making hierarchy
--
cd /usr/src; /usr/obj/usr/src/make.amd64/make -f Makefile.inc1
LOCAL_MTREE= hierarchy
cd /usr/src/etc; /usr/obj/usr/src/make.amd64/make LOCAL_MTREE= distrib-dirs
mtree -deU -f /usr/src/etc/mtree/BSD.root.dist -p /
mtree -deU -f /usr/src/etc/mtree/BSD.var.dist -p /var
cache changed
permissions expected 0750 found 0755 modified
tmp/vi.recover changed
user expected 0 found 2001 modified
./run/named missing (created)
./run/ppp missing (created)
./run/wpa_supplicant missing (created)
mtree -deU -f /usr/src/etc/mtree/BSD.usr.dist -p /usr
mtree -deU -f /usr/src/etc/mtree/BSD.include.dist -p /usr/include
mtree -deU -f /usr/src/etc/mtree/BIND.include.dist -p /usr/include
mtree -deU -f /usr/src/etc/mtree/BIND.chroot.dist -p /var/named
mtree -deU -f /usr/src/etc/mtree/BSD.groff.dist -p /usr
mtree -deU -f /usr/src/etc/mtree/BSD.sendmail.dist -p /
install -l s usr/src/sys /sys
install: /sys/sys: Directory not empty



signature.asc
Description: OpenPGP digital signature

Re: installworld fails

[Brooks Davis]

On Tue, Jan 22, 2013 at 08:49:12AM -0500, Ryan Stone wrote:
 On Tue, Jan 22, 2013 at 1:24 AM, Jason Evans jas...@freebsd.org wrote:
 
  On Jan 21, 2013, at 10:13 PM, AN a...@neu.net wrote:
   FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #29 r245766: Tue Jan 22
  00:49:02 EST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL  amd64
  
   Is anyone seeing this?
  
   install -l s usr/src/sys /sys
   install: /sys/sys: Directory not empty
   *** [distrib-dirs] Error code 71
 
  Yes.  I haven't tracked down the cause, but doing 'rm /sys' prior to
  installworld is an effective workaround.
 
  Jason
 
 
  CC'ing Brooks, who I believe made this change.
 
 It looks as though install is using the semantics of ln -s /usr/src/sys
 /sys instead of ln -fs.

Sorry about this breakage I'm testing a fix now.  The problem is
actually that install implemented the behavior of ln -sf and not ln -sfh.

-- Brooks
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: r245791: make installworld fails

[O. Hartmann]

Grmpf ... obviously, I should look first into the list, then post. it
has been discovered by others recently ...

On 01/22/13 16:45, O. Hartmann wrote:
 A make installworld fails since today on FreeBSD 10.0-CURRENT/amd64.
 FreeBSD 10.0-CURRENT #0 r245455: Tue Jan 15 11:31:21 CET 2013
 
 See error message below.
 
 
 Regards,
 
 Oliver
 
 
 [...]
 
 mkdir -p /tmp/install.qSk73yBh
 progs=$(for prog in [ awk cap_mkdb cat chflags chmod chown  date echo
 egrep find grep install-info  ln lockf make mkdir mtree mv pwd_mkdb rm
 sed sh sysctl  test true uname wc zic tzsetup; do  if progpath=`which
 $prog`; then  echo $progpath;  else  echo Required tool $prog not found
 in PATH. 2;  exit 1;  fi;  done);  libs=$(ldd -f %o %p\n -f %o
 %p\n $progs 2/dev/null | sort -u |  while read line; do  set -- $line;
  if [ $2 $3 != not found ]; then  echo $2;  else  echo Required
 library $1 not found. 2;  exit 1;  fi;  done);  cp $libs $progs
 /tmp/install.qSk73yBh
 cp -R ${PATH_LOCALE:-/usr/share/locale} /tmp/install.qSk73yBh/locale
 cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=amd64 MACHINE=amd64
 CPUTYPE=native GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin
 GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font
 GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac
 PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/tmp/install.qSk73yBh
  LD_LIBRARY_PATH=/tmp/install.qSk73yBh
 PATH_LOCALE=/tmp/install.qSk73yBh/locale
 /usr/obj/usr/src/make.amd64/make -f Makefile.inc1
 __MAKE_SHELL=/tmp/install.qSk73yBh/sh reinstall;
 MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=amd64 MACHINE=amd64
 CPUTYPE=native GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin
 GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font
 GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac
 PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/tmp/install.qSk73yBh
  LD_LIBRARY_PATH=/tmp/install.qSk73yBh
 PATH_LOCALE=/tmp/install.qSk73yBh/locale rm -rf /tmp/install.qSk73yBh
 --
 Making hierarchy
 --
 cd /usr/src; /usr/obj/usr/src/make.amd64/make -f Makefile.inc1
 LOCAL_MTREE= hierarchy
 cd /usr/src/etc; /usr/obj/usr/src/make.amd64/make LOCAL_MTREE= distrib-dirs
 mtree -deU -f /usr/src/etc/mtree/BSD.root.dist -p /
 mtree -deU -f /usr/src/etc/mtree/BSD.var.dist -p /var
 cache changed
 permissions expected 0750 found 0755 modified
 tmp/vi.recover changed
 user expected 0 found 2001 modified
 ./run/named missing (created)
 ./run/ppp missing (created)
 ./run/wpa_supplicant missing (created)
 mtree -deU -f /usr/src/etc/mtree/BSD.usr.dist -p /usr
 mtree -deU -f /usr/src/etc/mtree/BSD.include.dist -p /usr/include
 mtree -deU -f /usr/src/etc/mtree/BIND.include.dist -p /usr/include
 mtree -deU -f /usr/src/etc/mtree/BIND.chroot.dist -p /var/named
 mtree -deU -f /usr/src/etc/mtree/BSD.groff.dist -p /usr
 mtree -deU -f /usr/src/etc/mtree/BSD.sendmail.dist -p /
 install -l s usr/src/sys /sys
 install: /sys/sys: Directory not empty



signature.asc
Description: OpenPGP digital signature

Re: installworld fails

[Brooks Davis]

On Tue, Jan 22, 2013 at 10:02:39AM -0600, Brooks Davis wrote:
 On Tue, Jan 22, 2013 at 08:49:12AM -0500, Ryan Stone wrote:
  On Tue, Jan 22, 2013 at 1:24 AM, Jason Evans jas...@freebsd.org wrote:
  
   On Jan 21, 2013, at 10:13 PM, AN a...@neu.net wrote:
FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #29 r245766: Tue Jan 22
   00:49:02 EST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL  amd64
   
Is anyone seeing this?
   
install -l s usr/src/sys /sys
install: /sys/sys: Directory not empty
*** [distrib-dirs] Error code 71
  
   Yes.  I haven't tracked down the cause, but doing 'rm /sys' prior to
   installworld is an effective workaround.
  
   Jason
  
  
   CC'ing Brooks, who I believe made this change.
  
  It looks as though install is using the semantics of ln -s /usr/src/sys
  /sys instead of ln -fs.
 
 Sorry about this breakage I'm testing a fix now.  The problem is
 actually that install implemented the behavior of ln -sf and not ln -sfh.

Should be fixed with r245793.  Sorry for the breakage.

-- Brooks


pgpdB2wRh588S.pgp
Description: PGP signature

installworld fails

[AN]

FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #29 r245766: Tue Jan 22 
00:49:02 EST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL  amd64


Is anyone seeing this?

install -l s usr/src/sys /sys
install: /sys/sys: Directory not empty
*** [distrib-dirs] Error code 71

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: installworld fails

[Jason Evans]

On Jan 21, 2013, at 10:13 PM, AN a...@neu.net wrote:
 FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #29 r245766: Tue Jan 22 
 00:49:02 EST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL  amd64
 
 Is anyone seeing this?
 
 install -l s usr/src/sys /sys
 install: /sys/sys: Directory not empty
 *** [distrib-dirs] Error code 71

Yes.  I haven't tracked down the cause, but doing 'rm /sys' prior to 
installworld is an effective workaround.

Jason
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: make installworld fails

[matt]

On 05/03/12 20:49, Tim Kientzle wrote:

On May 3, 2012, at 1:34 PM, AN wrote:


Thu May  3 16:25:27 EDT 2012

FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #13 r234872: Tue May  1 
13:09:55 EDT 2012 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL  amd64

# svn up
Updated to revision 234981

I did build world/kernel, after booting into single user mode and trying make 
installworld I get the following error:

/usr/src/Makefile Line:219 check date and time

I have seen this failure before, previously I was able to open the make file 
and comment out the date and time check, but this time the file seems 
corrupted, I am not able to open the file in vi.

What causes this check to fail?  Is there any way to detect this possibility 
before rebboting to single user?

Try looking very critically at the system date and time:
  $ date

This check is comparing the system time to the timestamps of
the files on disks to try to detect whether your system clock
is correct.  Since the 'make' program relies on comparing timestamps,
you can get very strange results if your system clock is not consistent.

You can use the date utility to set the system clock to
the approximately correct time (it doesn't need to be very
exact).  If you have networking, you can use ntpdate pool.ntp.org
to set the clock from the network.

Tim

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Did you run adjkerntz -i before mounting disks in single user?

Matt
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

make installworld fails

[AN]

Thu May  3 16:25:27 EDT 2012

FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #13 r234872: Tue May  1 
13:09:55 EDT 2012 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL  amd64


# svn up
Updated to revision 234981

I did build world/kernel, after booting into single user mode and trying 
make installworld I get the following error:


/usr/src/Makefile Line:219 check date and time

I have seen this failure before, previously I was able to open the make 
file and comment out the date and time check, but this time the file seems 
corrupted, I am not able to open the file in vi.


What causes this check to fail?  Is there any way to detect this 
possibility before rebboting to single user?


# cat /etc/make.conf
OVERRIDE_LINUX_BASE_PORT=f10
QT4_OPTIONS= QGTKSTYLE
WITH_OPENSSL_PORT=yes
# added by use.perl 2012-04-04 01:11:13
PERL_VERSION=5.14.2
MALLOC_PRODUCTION=yes

Using system compiler, _not_ Clang.

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: make installworld fails

[Tim Kientzle]

On May 3, 2012, at 1:34 PM, AN wrote:

 Thu May  3 16:25:27 EDT 2012
 
 FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #13 r234872: Tue May  1 
 13:09:55 EDT 2012 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL  amd64
 
 # svn up
 Updated to revision 234981
 
 I did build world/kernel, after booting into single user mode and trying make 
 installworld I get the following error:
 
 /usr/src/Makefile Line:219 check date and time
 
 I have seen this failure before, previously I was able to open the make file 
 and comment out the date and time check, but this time the file seems 
 corrupted, I am not able to open the file in vi.
 
 What causes this check to fail?  Is there any way to detect this possibility 
 before rebboting to single user?

Try looking very critically at the system date and time:
 $ date

This check is comparing the system time to the timestamps of
the files on disks to try to detect whether your system clock
is correct.  Since the 'make' program relies on comparing timestamps,
you can get very strange results if your system clock is not consistent.

You can use the date utility to set the system clock to
the approximately correct time (it doesn't need to be very
exact).  If you have networking, you can use ntpdate pool.ntp.org
to set the clock from the network.

Tim

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: make installworld fails on releng9

[Benjamin Kaduk]

On Sat, 29 Oct 2011, Chuck Burns wrote:


On Saturday, October 29, 2011 1:13:58 AM Benjamin Kaduk wrote:


Are you running installworld in single-user mode?
What is the value of kern.securelevel?

-Ben Kaduk


Yes, I was running in single-user mode, and kern.securelevel was never
modified, and is currently showing as -1

Also, I am running zfs root, if that makes a difference


Hmm, ZFS root is indeed potentially interesting.  Marco, are you also on 
ZFS root?


Have you run a ZFS scrub recently?  (That being about the limit of my ZFS 
knowledge, unfortunately.)


It's pretty puzzling why only this handful of immutable files would 
trigger an issue, though.


-Ben Kaduk
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: make installworld fails on releng9

[Chuck Burns]

On Saturday, October 29, 2011 1:13:58 AM Benjamin Kaduk wrote:
 
 Are you running installworld in single-user mode?
 What is the value of kern.securelevel?
 
 -Ben Kaduk

Yes, I was running in single-user mode, and kern.securelevel was never 
modified, and is currently showing as -1

Also, I am running zfs root, if that makes a difference

-- 
Chuck Burns

We have the right as individuals to give away as much of our own money as we 
please in charity; but as members of Congress we have no right to appropriate 
a dollar of the public money. - Davy Crockett
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: make installworld fails on releng9

[Anton Shterenlikht]

On Fri, Oct 28, 2011 at 05:59:57AM +0200, Marco Steinbach wrote:
 
 
 On Thu, 27 Oct 2011, Chuck Burns wrote:
 
 I had some issues while running make installworld after I sync'd to the 
 latest
 releng9, on my RC1 install.
 
 Now, it appears to failed, while trying to create some links,
 chfn
 chsh
 ypchpass
 ypchfn
 ypchsh.
 
 These are supposed to be hardlinked to /usr/bin/chpass, except that, since 
 the
 other files already exist, and are immutable, make installworld was unable 
 to
 do anything, so I wound up removing the immutable flag on these files and 
 re-
 running make installworld.
 
 I didn't see any mention of this little.. issue, in UPDATING, or in the -
 current mailing list (yes, I know, 9.0 is no longer technically, current, 
 but
 since it isn't released yet, I figure it's close enough)
 
 I'm seeing this on head (226827, amd64), also.

Just updated to 9.0-RC1 #2 r226827 sparc64,
didn't see any problems.

-- 
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-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: make installworld fails on releng9

[Benjamin Kaduk]

On Thu, 27 Oct 2011, Chuck Burns wrote:


I had some issues while running make installworld after I sync'd to the latest
releng9, on my RC1 install.

Now, it appears to failed, while trying to create some links,
chfn
chsh
ypchpass
ypchfn
ypchsh.

These are supposed to be hardlinked to /usr/bin/chpass, except that, since the
other files already exist, and are immutable, make installworld was unable to
do anything, so I wound up removing the immutable flag on these files and re-
running make installworld.


Are you running installworld in single-user mode?
What is the value of kern.securelevel?

-Ben Kaduk
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

make installworld fails on releng9

[Chuck Burns]

I had some issues while running make installworld after I sync'd to the latest 
releng9, on my RC1 install.

Now, it appears to failed, while trying to create some links,
chfn
chsh
ypchpass
ypchfn
ypchsh.

These are supposed to be hardlinked to /usr/bin/chpass, except that, since the 
other files already exist, and are immutable, make installworld was unable to 
do anything, so I wound up removing the immutable flag on these files and re-
running make installworld.

I didn't see any mention of this little.. issue, in UPDATING, or in the -
current mailing list (yes, I know, 9.0 is no longer technically, current, but 
since it isn't released yet, I figure it's close enough)

 --
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: make installworld fails on releng9

[Marco Steinbach]

On Thu, 27 Oct 2011, Chuck Burns wrote:


I had some issues while running make installworld after I sync'd to the latest
releng9, on my RC1 install.

Now, it appears to failed, while trying to create some links,
chfn
chsh
ypchpass
ypchfn
ypchsh.

These are supposed to be hardlinked to /usr/bin/chpass, except that, since the
other files already exist, and are immutable, make installworld was unable to
do anything, so I wound up removing the immutable flag on these files and re-
running make installworld.

I didn't see any mention of this little.. issue, in UPDATING, or in the -
current mailing list (yes, I know, 9.0 is no longer technically, current, but
since it isn't released yet, I figure it's close enough)


I'm seeing this on head (226827, amd64), also.

MfG CoCo

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

make installworld fails

[AN]

Trying to installworld on 9-current AMD64, and it fails with:

install -o root -g wheel -m 444 
/usr/src/share/info/../../contrib/tzdata//zone.tab /usr/share/zoneinfo/
Updating /etc/localtime
tzsetup: illegal option -- r
usage:tzsetup [-ns]
***Error code 1

Stop in /usr/src/share/zoneinfo.

(above was transcribed from console)

Anyone else seeing this?  Is there a fix

Csup from last night.

Tia
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: make installworld fails

[Benjamin Kaduk]

On Tue, 16 Nov 2010, AN wrote:



Trying to installworld on 9-current AMD64, and it fails with:

install -o root -g wheel -m 444 
/usr/src/share/info/../../contrib/tzdata//zone.tab /usr/share/zoneinfo/

Updating /etc/localtime
tzsetup: illegal option -- r
usage:tzsetup [-ns]
***Error code 1

Stop in /usr/src/share/zoneinfo.

(above was transcribed from console)

Anyone else seeing this?  Is there a fix

Csup from last night.


We have seen similar tzsetup errors in installworld in the past.  Is your 
build environment unusual in any way (cross-building, DESTDIR set, etc.)?


-Ben Kaduk
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: make installworld fails

[AN]

On Tue, 16 Nov 2010, Benjamin Kaduk wrote:


On Tue, 16 Nov 2010, AN wrote:



Trying to installworld on 9-current AMD64, and it fails with:

install -o root -g wheel -m 444 
/usr/src/share/info/../../contrib/tzdata//zone.tab /usr/share/zoneinfo/

Updating /etc/localtime
tzsetup: illegal option -- r
usage:tzsetup [-ns]
***Error code 1

Stop in /usr/src/share/zoneinfo.

(above was transcribed from console)

Anyone else seeing this?  Is there a fix

Csup from last night.


We have seen similar tzsetup errors in installworld in the past.  Is your 
build environment unusual in any way (cross-building, DESTDIR set, etc.)?


-Ben Kaduk




Nothing unusual, standard plain install.  I used an image from 
http://pub.allbsd.org/FreeBSD-snapshots/ downloaded about 2 or 3 days ago.


Used standard procedure:

csup
make buildworld
make buildkernel
make install kernel
make installworld (single user mode)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: make installworld fails

[Benjamin Kaduk]

On Tue, 16 Nov 2010, AN wrote:




On Tue, 16 Nov 2010, Benjamin Kaduk wrote:


On Tue, 16 Nov 2010, AN wrote:



Trying to installworld on 9-current AMD64, and it fails with:

install -o root -g wheel -m 444 
/usr/src/share/info/../../contrib/tzdata//zone.tab /usr/share/zoneinfo/

Updating /etc/localtime
tzsetup: illegal option -- r
usage:tzsetup [-ns]
***Error code 1

Stop in /usr/src/share/zoneinfo.

(above was transcribed from console)

Anyone else seeing this?  Is there a fix

Csup from last night.


We have seen similar tzsetup errors in installworld in the past.  Is your 
build environment unusual in any way (cross-building, DESTDIR set, etc.)?


-Ben Kaduk




Nothing unusual, standard plain install.  I used an image from 
http://pub.allbsd.org/FreeBSD-snapshots/ downloaded about 2 or 3 days ago.


Used standard procedure:

csup


Hmm, what server do you csup from?
My tzsetup has this usage:
usage: tzsetup [-nrs] [zoneinfo file]

The one quoted above looks to be rather old.

-Ben Kaduk
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: make installworld fails

[Garrett Cooper]

On Tue, Nov 16, 2010 at 10:39 AM, AN a...@neu.net wrote:


 On Tue, 16 Nov 2010, Benjamin Kaduk wrote:

 On Tue, 16 Nov 2010, AN wrote:


 Trying to installworld on 9-current AMD64, and it fails with:

 install -o root -g wheel -m 444
 /usr/src/share/info/../../contrib/tzdata//zone.tab /usr/share/zoneinfo/
 Updating /etc/localtime
 tzsetup: illegal option -- r
 usage:tzsetup [-ns]
 ***Error code 1

 Stop in /usr/src/share/zoneinfo.

 (above was transcribed from console)

 Anyone else seeing this?  Is there a fix

 Csup from last night.

 We have seen similar tzsetup errors in installworld in the past.  Is your
 build environment unusual in any way (cross-building, DESTDIR set, etc.)?

 -Ben Kaduk



 Nothing unusual, standard plain install.  I used an image from
 http://pub.allbsd.org/FreeBSD-snapshots/ downloaded about 2 or 3 days ago.

 Used standard procedure:

 csup
 make buildworld
 make buildkernel
 make install kernel
 make installworld (single user mode)

(CCing edwin@)

There might be a handful of other apps that don't work when upgrading
from major version to major version (config; the way to work around
this particular issue is to execute:

cd /usr/src
make -C usr.sbin/tzsetup all install

This should be fixed in the share/zoneinfo Makefile (but might be
tricky with cross-builds); producing an UPDATING entry to document the
breakage might be good enough.

Thanks,
-Garrett
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: make installworld fails

[AN]

On Tue, 16 Nov 2010, Garrett Cooper wrote:


On Tue, Nov 16, 2010 at 10:39 AM, AN a...@neu.net wrote:



On Tue, 16 Nov 2010, Benjamin Kaduk wrote:


On Tue, 16 Nov 2010, AN wrote:



Trying to installworld on 9-current AMD64, and it fails with:

install -o root -g wheel -m 444
/usr/src/share/info/../../contrib/tzdata//zone.tab /usr/share/zoneinfo/
Updating /etc/localtime
tzsetup: illegal option -- r
usage:tzsetup [-ns]
***Error code 1

Stop in /usr/src/share/zoneinfo.

(above was transcribed from console)

Anyone else seeing this?  Is there a fix

Csup from last night.


We have seen similar tzsetup errors in installworld in the past.  Is your
build environment unusual in any way (cross-building, DESTDIR set, etc.)?

-Ben Kaduk




Nothing unusual, standard plain install.  I used an image from
http://pub.allbsd.org/FreeBSD-snapshots/ downloaded about 2 or 3 days ago.

Used standard procedure:

csup
make buildworld
make buildkernel
make install kernel
make installworld (single user mode)


(CCing edwin@)

There might be a handful of other apps that don't work when upgrading
from major version to major version (config; the way to work around
this particular issue is to execute:

cd /usr/src
make -C usr.sbin/tzsetup all install

This should be fixed in the share/zoneinfo Makefile (but might be
tricky with cross-builds); producing an UPDATING entry to document the
breakage might be good enough.

Thanks,
-Garrett




Hi Garrett:

After executing:
cd /usr/src
make -C usr.sbin/tzsetup all install

make installworld completed sucessfully

Machine is back, and seems to be fine.  Thanks for your fast and helpful 
reply.



___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: make installworld fails

[Benjamin Kaduk]

On Tue, 16 Nov 2010, Garrett Cooper wrote:

There might be a handful of other apps that don't work when upgrading 
from major version to major version (config; the way to work around this 



I thought we only supported major version upgrades by first upgrading from 
RELENG_X_Y to RELENG_X and then to RELENG_{X+1}_Z, but I didn't find 
documentation for that in a quick check.




This should be fixed in the share/zoneinfo Makefile (but might be
tricky with cross-builds); producing an UPDATING entry to document the
breakage might be good enough.


I had actually thought we fixed it a year ago when I ran into issues with 
r198351, but my memory is a bit hazy on what actually happened.


-Ben Kaduk
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

make installworld fails; tzsetup missing -C option

[Pieter de Goeje]

I'm trying to do a remote upgrade of a machine by mounting
it's root filesystem on /mnt using nfs. The build machine
runs a recent 8-STABLE. The target runs 9-CURRENT.

make installworld fails with:

install -o root -g wheel -m 444  
/data/FreeBSD/FreeBSD-current/src/share/zoneinfo/../../contrib/tzdata//zone.tab 
/mnt/usr/share/zoneinfo/
Updating /etc/localtime
tzsetup: illegal option -- C
usage: tzsetup [-ns]
*** Error code 1

Build script does the equivalent of this:
$ mount target:/ /mnt
$ cd /FreeBSD/FreeBSD-current/src
$ make -j4 buildworld  make -j4 buildkernel
$ setenv DESTDIR /mnt
$ make installkernel
$ setenv NO_FSCHG 1
$ make installworld

uname on the build machine:
FreeBSD 8.1-STABLE #1: Tue Aug 10 13:09:59 CEST 2010

- Pieter
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: make installworld fails; tzsetup missing -C option

[Gary Jennejohn]

On Tue, 24 Aug 2010 12:41:37 +0200
Pieter de Goeje pie...@degoeje.nl wrote:

 I'm trying to do a remote upgrade of a machine by mounting
 it's root filesystem on /mnt using nfs. The build machine
 runs a recent 8-STABLE. The target runs 9-CURRENT.
 
 make installworld fails with:
 
 install -o root -g wheel -m 444  
 /data/FreeBSD/FreeBSD-current/src/share/zoneinfo/../../contrib/tzdata//zone.tab
  /mnt/usr/share/zoneinfo/
 Updating /etc/localtime
 tzsetup: illegal option -- C
 usage: tzsetup [-ns]
 *** Error code 1
 
 Build script does the equivalent of this:
 $ mount target:/ /mnt
 $ cd /FreeBSD/FreeBSD-current/src
 $ make -j4 buildworld  make -j4 buildkernel
 $ setenv DESTDIR /mnt
 $ make installkernel
 $ setenv NO_FSCHG 1
 $ make installworld
 
 uname on the build machine:
 FreeBSD 8.1-STABLE #1: Tue Aug 10 13:09:59 CEST 2010
 

You're trying to install 9-CURRENT using 8.1-STABLE binaries, which just
won't work in this (tzsetup) case.

The -C flag is only set when DESTDIR is set, which might be considered
a bug since it prevents cross-compiling and cross-installation using
different versions of FreeBSD, like in your case.

But I'm not so sure that support for this is guaranteed when going from
an older version to a newer version.

I suppose you could try a) editing share/zoneinfo/Makefile and deleting
the optC code or b) pointing PATH at DESTDIR, if it's already populated.

--
Gary Jennejohn
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: make installworld fails; tzsetup missing -C option

[Pieter de Goeje]

On Tuesday 24 August 2010 17:53:07 Gary Jennejohn wrote:
 On Tue, 24 Aug 2010 12:41:37 +0200

 Pieter de Goeje pie...@degoeje.nl wrote:
  I'm trying to do a remote upgrade of a machine by mounting
  it's root filesystem on /mnt using nfs. The build machine
  runs a recent 8-STABLE. The target runs 9-CURRENT.
 
  make installworld fails with:
 
  install -o root -g wheel -m 444 
  /data/FreeBSD/FreeBSD-current/src/share/zoneinfo/../../contrib/tzdata//zo
 ne.tab /mnt/usr/share/zoneinfo/ Updating /etc/localtime
  tzsetup: illegal option -- C
  usage: tzsetup [-ns]
  *** Error code 1
 
  Build script does the equivalent of this:
  $ mount target:/ /mnt
  $ cd /FreeBSD/FreeBSD-current/src
  $ make -j4 buildworld  make -j4 buildkernel
  $ setenv DESTDIR /mnt
  $ make installkernel
  $ setenv NO_FSCHG 1
  $ make installworld
 
  uname on the build machine:
  FreeBSD 8.1-STABLE #1: Tue Aug 10 13:09:59 CEST 2010

 You're trying to install 9-CURRENT using 8.1-STABLE binaries, which just
 won't work in this (tzsetup) case.

 The -C flag is only set when DESTDIR is set, which might be considered
 a bug since it prevents cross-compiling and cross-installation using
 different versions of FreeBSD, like in your case.

 But I'm not so sure that support for this is guaranteed when going from
 an older version to a newer version.
It's a bit of an edge case I agree. A working cross installation is desirable 
if for example you want to upgrade a machine in place, but have a fallback 
mechanism by installing everyting on a separate root filesystem first.

 I suppose you could try a) editing share/zoneinfo/Makefile and deleting
 the optC code or b) pointing PATH at DESTDIR, if it's already populated.

As I'm not cross compiling, I simply used the tzetup it built to complete the 
install. I temporarily replaced the 8-STABLE version with the 9-CURRENT 
version on the build box.

I wonder if tzsetup should be a bootstrap tool...

-- 
Pieter de Goeje
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

make installworld fails on 5.1 REL

[Christophe Zwecker]

hi,

im moving from beta1 to 5.1 release, I build a new kernel, booted. rm 
-rf /usr/obj did make buildworld, and when I do make installworld I get 
this:

Running test variables
PASS: Test variables detected no regression, output matches.
Running test targets
PASS: Test targets detected no regression.
Running test sysvmatch
PASS: Test sysvmatch detected no regression.
Running test lhs_expn
PASS: Test lhs_expn detected no regression.
Running test notdef
PASS: Test notdef detected no regression.
Running test modifiers
PASS: Test modifiers detected no regression.
Running test funny_targets
PASS: Test funny_targets detected no regression.
Checking to see if your booted kernel is fresh enough..
/usr/obj/usr/src/bin/sh/sh -c  'echo Testing installed kernel for new 
sigaction(2) syscall'
Testing installed kernel for new sigaction(2) syscall
Seems ok..
mkdir -p /tmp/install.XG0p8Esu
for prog in [ awk cap_mkdb cat chflags chmod chown  date echo egrep find 
grep  ln make mkdir mtree mv pwd_mkdb rm sed sh sysctl  test true uname 
wc zic; do  cp `which $prog` /tmp/install.XG0p8Esu;  done
cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj  MACHINE_ARCH=i386  MACHINE=i386 
 CPUTYPE=  GROFF_BIN_PATH=/usr/obj/usr/src/i386/legacy/usr/bin 
GROFF_FONT_PATH=/usr/obj/usr/src/i386/legacy/usr/share/groff_font 
GROFF_TMAC_PATH=/usr/obj/usr/src/i386/legacy/usr/share/tmac 
PATH=/usr/obj/usr/src/i386/legacy/usr/sbin:/usr/obj/usr/src/i386/legacy/usr/bin:/usr/obj/usr/src/i386/legacy/usr/games:/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/tmp/install.XG0p8Esu 
make -f Makefile.inc1 reinstall
make: Permission denied
*** Error code 126

Stop in /usr/src.
*** Error code 1
Stop in /usr/src.

whats wrong here ?

thx for help!

Christophe
--
Christophe Zwecker mail: [EMAIL PROTECTED]
Hamburg, Germanyfon: +49 179 3994867
http://www.zwecker.de
Who is General Failure ?  And why is he reading my disk ??

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: make installworld fails on 5.1 REL

[Steve Kargl]

On Fri, Jun 13, 2003 at 02:56:35AM +0200, Christophe Zwecker wrote:
 hi,
 
 im moving from beta1 to 5.1 release, I build a new kernel, booted. rm 
 -rf /usr/obj did make buildworld, and when I do make installworld I get 

AFAIK, this isn't one of the documented methods for
upgrading a system.  Oh well.

 GROFF_TMAC_PATH=/usr/obj/usr/src/i386/legacy/usr/share/tmac 
 PATH=/usr/obj/usr/src/i386/legacy/usr/sbin:/usr/obj/usr/src/i386/legacy/usr/bin:/usr/obj/usr/src/i386/legacy/usr/games:/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/tmp/install.XG0p8Esu
  
 make -f Makefile.inc1 reinstall
 make: Permission denied
 *** Error code 126
 

What is the security level for the system?

-- 
Steve
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: make installworld fails on 5.1 REL

[Christophe Zwecker]

David Wolfskill wrote:
kern_securelevel_enable set (in /etc/rc.conf)?

Peace,
david
its set to NO.

should it be YES ?

cu

Christophe

--
Christophe Zwecker mail: [EMAIL PROTECTED]
Hamburg, Germanyfon: +49 179 3994867
http://www.zwecker.de
Who is General Failure ?  And why is he reading my disk ??

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Installworld fails building Current from 4.7-R

[Richard Cotrina]

Hello :

I am getting an strange error when trying to install current ( make
installworld ). I cvsup-ed it in my 4.7- Release box, and I sompiling the
sources and the kernel without any error messages :

# make -j4 buildworld
# make buildkernel
# make installkernel
# reboot

All the above finished without problems. After rebooting, I tried to do :

# make installworld

and after a while, it finished with the following error :

== usr.bin/chpass
[ ! -e /usr/bin/chpass ] || chflags noschg /usr/bin/chpass || true
*** Signal 12

Stop in /usr/src/usr.bin/chpass.
*** Error Code 1

And the console gave me this message :

/kernel pid 21078 (sh),uid 0 : exited on signal 12 ( core dumped )

Does anyone have any ideas about what I did it wrong or it is missing ?

Thanks in advance for your help

Richard Cotrina


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

Re: Installworld fails building Current from 4.7-R

[Craig Rodrigues]

Hi,

Did you see the instructions in /usr/src/Makefile and /usr/src/UPDATING?

This is from /usr/src/Makefile:

# For individuals wanting to upgrade their sources (even if only a
# delta of a few days):
#
# 1.  `cd /usr/src'   (or to the directory containing your source tree).
# 2.  `make buildworld'
# 3.  `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC).
# 4.  `make installkernel KERNCONF=YOUR_KERNEL_HERE'   (default is GENERIC).
# 5.  `reboot'(in single user mode: boot -s from the loader prompt).
# 6.  `mergemaster -p'
# 7.  `make installworld'
# 8.  `mergemaster'
# 9.  `reboot'
#
# See src/UPDATING `COMMON ITEMS' for more complete information.
#

-- 
Craig Rodrigues
http://www.gis.net/~craigr
[EMAIL PROTECTED]

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

Re: Installworld fails building Current from 4.7-R

[Richard Cotrina]

Yes, I did. However make installworld fails as I said.

- Original Message -
From: Craig Rodrigues [EMAIL PROTECTED]
To: Richard Cotrina [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, October 24, 2002 5:02 PM
Subject: Re: Installworld fails building Current from 4.7-R


 Hi,

 Did you see the instructions in /usr/src/Makefile and /usr/src/UPDATING?

 This is from /usr/src/Makefile:

 # For individuals wanting to upgrade their sources (even if only a
 # delta of a few days):
 #
 # 1.  `cd /usr/src'   (or to the directory containing your source
tree).
 # 2.  `make buildworld'
 # 3.  `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is
GENERIC).
 # 4.  `make installkernel KERNCONF=YOUR_KERNEL_HERE'   (default is
GENERIC).
 # 5.  `reboot'(in single user mode: boot -s from the loader
prompt).
 # 6.  `mergemaster -p'
 # 7.  `make installworld'
 # 8.  `mergemaster'
 # 9.  `reboot'
 #
 # See src/UPDATING `COMMON ITEMS' for more complete information.
 #

 --
 Craig Rodrigues
 http://www.gis.net/~craigr
 [EMAIL PROTECTED]

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



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

Re: Installworld fails building Current from 4.7-R

[Mike Hunter]

On Thu, 24 Oct 2002, Richard Cotrina wrote:

 Yes, I did. However make installworld fails as I said.

I ran into the same problem going from 4.6 to 5.0-CURRENT.

We used truss to see that sh was making funny calls, and concluded that
we'd need to run from the kernel to get it working.  We installed the
new kernel and were able to complete the install.

Definitely not knowledgeable enough to be posting to freebsd-current,

Mike Hunter


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

Re: Installworld fails building Current from 4.7-R

[Nate Lawson]

On Thu, 24 Oct 2002, Mike Hunter wrote:
 On Thu, 24 Oct 2002, Richard Cotrina wrote:
 
  Yes, I did. However make installworld fails as I said.
 
 I ran into the same problem going from 4.6 to 5.0-CURRENT.
 
 We used truss to see that sh was making funny calls, and concluded that
 we'd need to run from the kernel to get it working.  We installed the
 new kernel and were able to complete the install.
 
 Definitely not knowledgeable enough to be posting to freebsd-current,
 
 Mike Hunter

That's why there is a reboot between installing the new kernel and doing
installworld.  You need to run the new kernel to have the ABI match.

-Nate


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

Re: Installworld fails building Current from 4.7-R

[Nate Lawson]

[Redirected to current@ with sender's approval]

On Thu, 24 Oct 2002, Mike Hunter wrote:
 On Thu, 24 Oct 2002, Nate Lawson wrote:
 
  That's why there is a reboot between installing the new kernel and doing
  installworld.  You need to run the new kernel to have the ABI match.
 
 From my understanding of what was written earlier today (and what the guy
 who was helping me said) the boot loader is not updated during that first
 reboot, and therefore the old kernel is booted on that reboot.
 5.0-current moves the default location of the kernel IIRC.
 
 I'm pretty sure that I followed the UPDATING directions to the letter.
 
 Mike

I've run into the same problem in the past but manually selected the new
kernel.  Should we add the explicit step that you need to load
/boot/kernel/kernel when upgrading?  Or has that been fixed?

-Nate


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

Re: Installworld fails building Current from 4.7-R

[The Gupta Age]

|
|I've run into the same problem in the past but manually selected the new
|kernel.  Should we add the explicit step that you need to load
|/boot/kernel/kernel when upgrading?  Or has that been fixed?
|
|-Nate

I have posted atleast twice on current to add this
info to UPDATING. guess it still hasnt been done.


Saurabh Gupta


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

make installworld fails

[Mathieu Arnold]

Hi

Doing a make make installworld fails on a 5_0-CURRENT from this morning
fails in :
gnu/lib/libreadline/history
rlhistory.3: doc/history.3
cp ${.ALLSRC} ${.TARGET}

no cp in $PATH...

then :
usr.sbin/ppp
.8.m4.8:
m4 ${M4FLAGS} ${.IMPSRC} ${.TARGET}

no m4 in PATH...

and then :
secure/usr.bin/openssl
.pod.1: 
pod2man ${.IMPSRC}  ${.TARGET}
no pod2man in PATH...

-- 
Mathieu Arnold

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

make buildworld works... make installworld fails!

[Raul Zighelboim]

Hello there;

This happened to me on the last 3 'current' days:

=== lib/libcrypt
install -c -o root -g wheel -m 444   libscrypt.a /usr/lib
install -c -o root -g wheel -m 444   libscrypt_p.a /usr/lib
install -c -s -o root -g wheel -m 444   -fschg  libscrypt.so.2 /usr/lib
/usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags"
*** Error code 1

Stop in /usr/src/lib/libcrypt.
*** Error code 1

but:
root@rodia pwd
/usr/src/lib/libcrypt
root@rodia make install
install -c -o root -g wheel -m 444   libscrypt.a /usr/lib
install -c -o root -g wheel -m 444   libscrypt_p.a /usr/lib
install -c -s -o root -g wheel -m 444 libscrypt.so.2 /usr/lib
ln -sf libscrypt.so.2 /usr/lib/libscrypt.so
install -c -o root -g wheel -m 444 crypt.3.gz  /usr/share/man/man3

works.



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

Re: make buildworld works... make installworld fails!

[Mike Tancsa]

At 08:26 AM 2/7/00 -0600, you wrote:
Hello there;

This happened to me on the last 3 'current' days:


Have a look through the past few days archives of freebsd-current for a
discussion as to why this has been happening, and the various work arounds,
as well as have a read through the UPDATING text file.

---Mike

Mike Tancsa,  tel +1 519 651 3400
Network Administrator,[EMAIL PROTECTED]
Sentex Communications www.sentex.net
Cambridge, Ontario Canada


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

Re: make buildworld works... make installworld fails!

[Patrick M. Hausen]

Hi!

 This happened to me on the last 3 'current' days:
 
 === lib/libcrypt
 install -c -o root -g wheel -m 444   libscrypt.a /usr/lib
 install -c -o root -g wheel -m 444   libscrypt_p.a /usr/lib
 install -c -s -o root -g wheel -m 444   -fschg  libscrypt.so.2 /usr/lib
 /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags"
 *** Error code 1
 
 Stop in /usr/src/lib/libcrypt.
 *** Error code 1

Metoo :)

I solved it the "Ken Thompson way" - when in doubt use brute force ;-)

# make buildworld
# make -k installworld
# make installworld

No errors with the last one.
Somewhere this was suggested for updating a 3.x system to -current, too.

Regards,
Patrick


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

Re: installworld fails with setresuid.2.gz

[Sheldon Hearn]

On Tue, 18 Jan 2000 13:46:36 +0900, Munehiro Matsuda wrote:

 /usr/share/man/man2/setresgid.2.gz - /usr/share/man/man2/setresuid.2.gz
 ln: /usr/share/man/man2/setresuid.2.gz: No such file or directory
 *** Error code 1

My fault.  It's fixed in rev 1.75 of src/lib/libc/sys/Makefile.inc .

Sorry for the inconvenience. :-(

Ciao,
Sheldon.


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

installworld fails with setresuid.2.gz

[Munehiro Matsuda]

Hi all,

Installworld fails with following error.
It's -current as of Jan 18 03:15 JST-9 (CTM:src-cur.4185.gz).

/usr/share/man/man2/setresgid.2.gz - /usr/share/man/man2/setresuid.2.gz
ln: /usr/share/man/man2/setresuid.2.gz: No such file or directory
*** Error code 1

Stop in /usr/src/lib/libc.
*** Error code 1

Stop in /usr/src/lib.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.


It seems that setresuid.2 entry is missing for 'MAN2+=' in rev 1.72 of
/usr/src/lib/libc/sys/Makefile.inc.

 Thank you,
  Haro

=--
   _ _Munehiro (haro) Matsuda
 -|- /_\  |_|_|   Office of Business Planning  Developement, Kubota Corp.
 /|\ |_|  |_|_|   1-3 Nihonbashi-Muromachi 3-Chome
  Chuo-ku Tokyo 103, Japan
  Tel: +81-3-3245-3318  Fax: +81-3-32454-3315
  Email: [EMAIL PROTECTED]


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