It is on my list of things to look into next week.
Glen
Sent from my phone.
Please excuse my brevity and/or typos.
> On Aug 20, 2021, at 4:10 PM, Alan Somers wrote:
>
>
>> On Thu, Jul 29, 2021 at 12:43 PM Emmanuel Vadot
>> wrote:
>> On Thu, 29 Jul 2021 00:13:54 +
>> Glen Barber wrote:
On Thu, Jul 29, 2021 at 12:43 PM Emmanuel Vadot
wrote:
> On Thu, 29 Jul 2021 00:13:54 +
> Glen Barber wrote:
>
> > On Wed, Jul 28, 2021 at 06:00:28PM -0600, Alan Somers wrote:
> > > On Wed, Jul 28, 2021 at 5:52 PM Miroslav Lachman <000.f...@quip.cz>
> wrote:
> > >
> > > > On 28/07/2021
On Thu, 29 Jul 2021 00:13:54 +
Glen Barber wrote:
> On Wed, Jul 28, 2021 at 06:00:28PM -0600, Alan Somers wrote:
> > On Wed, Jul 28, 2021 at 5:52 PM Miroslav Lachman <000.f...@quip.cz> wrote:
> >
> > > On 28/07/2021 20:46, Juraj Lutter wrote:
> > > >
> > > >
> > > >> On 28 Jul 2021, at
On 2021-07-28 10:11, Alan Somers wrote:
Is it possible to build multiple different kernels and include them all in
a release image? release.conf says so. But from experiment, what I see is
that:
* release.sh does pass both kernels in the KERNCONF variable to "make
buildkernel"
* "make
On Wed, Jul 28, 2021 at 06:00:28PM -0600, Alan Somers wrote:
> On Wed, Jul 28, 2021 at 5:52 PM Miroslav Lachman <000.f...@quip.cz> wrote:
>
> > On 28/07/2021 20:46, Juraj Lutter wrote:
> > >
> > >
> > >> On 28 Jul 2021, at 20:37, Glen Barber wrote:
> > >>
> > >> On Wed, Jul 28, 2021 at
On Wed, Jul 28, 2021 at 5:52 PM Miroslav Lachman <000.f...@quip.cz> wrote:
> On 28/07/2021 20:46, Juraj Lutter wrote:
> >
> >
> >> On 28 Jul 2021, at 20:37, Glen Barber wrote:
> >>
> >> On Wed, Jul 28, 2021 at 12:05:25PM -0600, Alan Somers wrote:
> >>> On Wed, Jul 28, 2021 at 11:57 AM Glen
On 28/07/2021 20:46, Juraj Lutter wrote:
On 28 Jul 2021, at 20:37, Glen Barber wrote:
On Wed, Jul 28, 2021 at 12:05:25PM -0600, Alan Somers wrote:
On Wed, Jul 28, 2021 at 11:57 AM Glen Barber wrote:
Just on a hunch, could you try with adding INSTALLKERNEL="${KERNEL}" to
your
On Wed, Jul 28, 2021 at 08:46:19PM +0200, Juraj Lutter wrote:
>
>
> > On 28 Jul 2021, at 20:37, Glen Barber wrote:
> >
> > On Wed, Jul 28, 2021 at 12:05:25PM -0600, Alan Somers wrote:
> >> On Wed, Jul 28, 2021 at 11:57 AM Glen Barber wrote:
> >>> Just on a hunch, could you try with adding
> On 28 Jul 2021, at 20:37, Glen Barber wrote:
>
> On Wed, Jul 28, 2021 at 12:05:25PM -0600, Alan Somers wrote:
>> On Wed, Jul 28, 2021 at 11:57 AM Glen Barber wrote:
>>> Just on a hunch, could you try with adding INSTALLKERNEL="${KERNEL}" to
>>> your release.conf?
>>>
>>> I now seem to
On Wed, Jul 28, 2021 at 12:05:25PM -0600, Alan Somers wrote:
> On Wed, Jul 28, 2021 at 11:57 AM Glen Barber wrote:
> > Just on a hunch, could you try with adding INSTALLKERNEL="${KERNEL}" to
> > your release.conf?
> >
> > I now seem to recall some weirdness with this, but the exact details
> >
gt; > provide a way to specify that.
> > > > > >
> > > > > > So is the "multiple kernels in release.conf" feature
> unfinished? If
> > > > so,
> > > > > > does anybody have a good idea about the best way to finish it?
&
so,
> > > > > does anybody have a good idea about the best way to finish it?
> > > > >
> > > > >
> > > https://github.com/freebsd/freebsd-src/blob/7045b1603bdf054145dd958a4acc17b410fb62a0/release/release.conf.sample#L32
> > > > >
> >
t; > > >
> > > > So is the "multiple kernels in release.conf" feature unfinished? If
> > so,
> > > > does anybody have a good idea about the best way to finish it?
> > > >
> > > >
> > https://github.com/freebsd/freebsd-src/blob/704
to finish it?
> > >
> > >
> https://github.com/freebsd/freebsd-src/blob/7045b1603bdf054145dd958a4acc17b410fb62a0/release/release.conf.sample#L32
> > >
> >
> > Last I was aware, based on a patch sent to me privately, I believe, it
> > should work.
> >
> > Let me take a look.
> >
>
> Oh, wait. Are you using 'make release' or release/release.sh?
>
> Glen
>
I'm using release.sh. I thought that was just a wrapper for "make
release".
is the "multiple kernels in release.conf" feature unfinished? If so,
> > does anybody have a good idea about the best way to finish it?
> >
> > https://github.com/freebsd/freebsd-src/blob/7045b1603bdf054145dd958a4acc17b410fb62a0/release/release.conf.sample#L32
>
On Wed, Jul 28, 2021 at 11:11:48AM -0600, Alan Somers wrote:
> Is it possible to build multiple different kernels and include them all in
> a release image? release.conf says so. But from experiment, what I see is
> that:
>
> * release.sh does pass both kernels in the KERNCONF variable to "make
Is it possible to build multiple different kernels and include them all in
a release image? release.conf says so. But from experiment, what I see is
that:
* release.sh does pass both kernels in the KERNCONF variable to "make
buildkernel"
* "make buildkernel" dutifully builds both
* BUT, "make
Any ideas what broke this?
--
>>> Kernel build for GENERIC completed on Tue Feb 9 20:48:05 UTC 2021
--
>>> Kernel(s) GENERIC built in 465 seconds, ncpu: 8, make -j8
On 30/01/2021 17:23, tech-lists wrote:
Hi,
I'm trying to make release with -current on a rpi4b/8GB. Basically, I
have a working rpi4B/8GB with a no-debug kernel running -current.
However, release(7) says a lot about svn and nothing about git.
What's the method with git?
thanks,
Correct me
Hi,
I'm trying to make release with -current on a rpi4b/8GB. Basically, I
have a working rpi4B/8GB with a no-debug kernel running -current.
However, release(7) says a lot about svn and nothing about git.
What's the method with git?
thanks,
--
J.
signature.asc
Description: PGP signature
I'm sure I did this yesterday without a failure; any hints as to what
broke/how to fix it?
imb
===> tests/sys/cddl/zfs/tests/threadsappend (all)
===> tests/sys/cddl/zfs/tests/truncate (all)
===> usr.sbin/amd/libamu (all)
===> usr.sbin/audit (all)
===>
( $(( $(sysctl -n hw.ncpu) + 1 )) / 2 ))"
>
> without any noticable effect - make release always build release fully, no
> matter wether there has been new sources checked out or not. It takes a lot of
> time compiling llvm/clang. Using 11-stable on a NanoBSD installation,
&g
is
11-STABLE.
In release.conf, I tried setting
## Set to use world- and kernel-specific make(1) flags.
WORLD_FLAGS="-DNO_CLEAN -j $(sysctl -n hw.ncpu)"
KERNEL_FLAGS="-DNO_CLEAN -j $(( $(( $(sysctl -n hw.ncpu) + 1 )) / 2 ))"
without any noticable effect - make release always
We use jenkins to build, test and release 11.0-CURRENT using jenkin's uid:gid.
Everything works well up to "install -o root -g wheel" in "make release".
Anyone know what the use case is for requiring release to be built as root?
Roger
___
On Fri, Sep 13, 2013 at 11:21:43AM +0900, Lundberg, Johannes wrote:
Trying to create a custom install image which has been successful before
but suddenly fails during make release/memstick.
Procedure
1) cd /usr/src
2) make buildworld
3) make buildkernel
4) cd release
5) make release
Hi
Trying to create a custom install image which has been successful before
but suddenly fails during make release/memstick.
Procedure
1) cd /usr/src
2) make buildworld
3) make buildkernel
4) cd release
5) make release
and I get the error
...
gencat be_BY.UTF-8.cat /usr/src/lib/libc/nls
at 11:21:43AM +0900, Lundberg, Johannes wrote:
Trying to create a custom install image which has been successful before
but suddenly fails during make release/memstick.
Procedure
1) cd /usr/src
2) make buildworld
3) make buildkernel
4) cd release
5) make release
and I get
On Fri, Sep 13, 2013 at 11:30:44AM +0900, Lundberg, Johannes wrote:
# sysctl -n kern.osreldate
145
The system is 10.0. I used it before to build custom distribution.
What I've done since last time is basically removing /usr/src and grabbing
a new one from head.
Recent changes in head/
Is this perhaps related to the 20130905 post in UPDATING, regarding the
Capsicum framework?
--
Johannes Lundberg
Project leader and lead developer of Mirama OS (previously Viking OS)
BRILLIANTSERVICE CO., LTD.
My blog http://brilliantobjc.blogspot.com
Mirama homepage
Oh.. Thanks a lot!
But please tell me, how can I upgrade the build environment? Do I have to
rebuild world and kernel on the host system?
--
Johannes Lundberg
Project leader and lead developer of Mirama OS (previously Viking OS)
BRILLIANTSERVICE CO., LTD.
My blog
Yes, the buildworld/buildkernel.
Glen
On Fri, Sep 13, 2013 at 11:37:38AM +0900, Lundberg, Johannes wrote:
Oh.. Thanks a lot!
But please tell me, how can I upgrade the build environment? Do I have to
rebuild world and kernel on the host system?
--
Johannes Lundberg
Project leader and
In part, yes.
Glen
On Fri, Sep 13, 2013 at 11:41:54AM +0900, Lundberg, Johannes wrote:
Is this perhaps related to the 20130905 post in UPDATING, regarding the
Capsicum framework?
--
Johannes Lundberg
Project leader and lead developer of Mirama OS (previously Viking OS)
BRILLIANTSERVICE
Alexander Pyhalov a...@rsu.ru wrote:
Hello.
On 07/28/2012 00:09, Glen Barber wrote:
Hello,
On Fri, Jul 27, 2012 at 09:35:13AM +0400, Alexander Pyhalov wrote:
Hello.
I've tried to do make cdrom on recent 10-current (svn revision
238763)
and got after day of work:
[...]
Could you please
Hi,
On Fri, Jul 27, 2012 at 09:35:13AM +0400, Alexander Pyhalov wrote:
Hello.
I've tried to do make cdrom on recent 10-current (svn revision 238763)
and got after day of work:
[...]
It seems, it continued to add files to some archive recursively... Is it
a bug or maybe I just can't cook it
On Fri, Jul 27, 2012 at 7:26 AM, Oliver Brandmueller o...@e-gitt.net wrote:
Hi,
On Fri, Jul 27, 2012 at 09:35:13AM +0400, Alexander Pyhalov wrote:
Hello.
I've tried to do make cdrom on recent 10-current (svn revision 238763)
and got after day of work:
[...]
It seems, it continued to add
On Fri, Jul 27, 2012 at 8:37 AM, Garrett Cooper yaneg...@gmail.com wrote:
On Fri, Jul 27, 2012 at 7:26 AM, Oliver Brandmueller o...@e-gitt.net wrote:
Hi,
On Fri, Jul 27, 2012 at 09:35:13AM +0400, Alexander Pyhalov wrote:
Hello.
I've tried to do make cdrom on recent 10-current (svn revision
Hello,
On Fri, Jul 27, 2012 at 09:35:13AM +0400, Alexander Pyhalov wrote:
Hello.
I've tried to do make cdrom on recent 10-current (svn revision 238763)
and got after day of work:
[...]
Could you please retry the cdrom build with NOSRC=yes set?
If this does not succeed, could you please
Hello.
I've tried to do make cdrom on recent 10-current (svn revision 238763)
and got after day of work:
a
Ive noticed trying a make release on CURRENT that it appears to be
looping deeper and deeper,
does this appear normal to anyone else???
a
usr/src/release/dist/usr/src/release/dist/usr/src/release/dist/usr/src/sys/dev/malo/if_malohal.h
a
usr/src/release/dist/usr/src/release/dist/usr/src/release
Attempting to run: make release resulted in 'looping' until a kernel compile
directory
sys/amd64/compile/* was removed.
Maybe I missed something in the docs.
-kim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
On Fri, Jun 24, 2011 at 8:47 AM, Kim Culhan w8hd...@gmail.com wrote:
Attempting to run: make release resulted in 'looping' until a kernel compile
directory
sys/amd64/compile/* was removed.
Maybe I missed something in the docs.
-kim
___
freebsd
Try to build a cdrom from most recent CURRENT/amd64 sources.
Issuing the follwing command fails the build process looping recursively
and indefinitely within the source folder /usr/src/release:
make release cdrom CHROOTDIR=/unused/release/9.0/ SVNROOT/usr/src
BUILDNAME=9.0-CURRENT
On 06/18/11 05:15, Hartmann, O. wrote:
Try to build a cdrom from most recent CURRENT/amd64 sources.
Issuing the follwing command fails the build process looping
recursively and indefinitely within the source folder /usr/src/release:
make release cdrom CHROOTDIR=/unused/release/9.0/ SVNROOT
On 06/18/11 17:35, Nathan Whitehorn wrote:
On 06/18/11 05:15, Hartmann, O. wrote:
Try to build a cdrom from most recent CURRENT/amd64 sources.
Issuing the follwing command fails the build process looping
recursively and indefinitely within the source folder /usr/src/release:
make release
I am trying to make a release with the following arguments:
make release CHROOTDIR=/usr/home/current BUILDNAME=9-CURRENT
EXTSRCDIR=/usr/src NOPORTS=YES MAKE_ISOS=YES
however /usr/home/current is being ignored completely and everything ends up
in /usr/obj/usr/src. Am I doing something wrong
On 12/04/2011, at 17:02, George Kontostanos wrote:
I am trying to make a release with the following arguments:
make release CHROOTDIR=/usr/home/current BUILDNAME=9-CURRENT
EXTSRCDIR=/usr/src NOPORTS=YES MAKE_ISOS=YES
however /usr/home/current is being ignored completely and everything
On 04/12/11 10:02, George Kontostanos wrote:
I am trying to make a release with the following arguments:
make release CHROOTDIR=/usr/home/current BUILDNAME=9-CURRENT
EXTSRCDIR=/usr/src NOPORTS=YES MAKE_ISOS=YES
however /usr/home/current is being ignored completely and everything ends up
sh generate-release.sh head /local3/release
On Tue, Apr 12, 2011 at 6:14 PM, Nathan Whitehorn nwhiteh...@freebsd.orgwrote:
On 04/12/11 10:02, George Kontostanos wrote:
I am trying to make a release with the following arguments:
make release CHROOTDIR=/usr/home/current BUILDNAME=9-CURRENT
On 26/03/2011, at 18:42, O. Hartmann wrote:
Yes, I tried and I ran into the same problems. But I didn't run into problems
lately, the problem resists for me now for approx. three weeks or so and I
reported this in questions@ once.
Try 'make obj' before 'make release' - that fixed it for me
On 26.03.2011 05:32, Daniel O'Connor wrote:
Has anyone done one recently?
I note there aren't any snapshots for this month, so perhaps I'm not alone.
I tried this :-
RELNAME=9.0
BUILDNAME=${RELNAME}-GENESIS
make release CHROOTDIR=/tmp/${RELNAME}-release BUILDNAME=$BUILDNAME
HTTP_PROXY=http
' before 'make release' - that fixed it for me.
Thanks for reporting this! I just modified src/release/Makefile so that
'make release' causes the obj target to be run first, so this shouldn't
happen anymore.
-Nathan
___
freebsd-current@freebsd.org
Has anyone done one recently?
I note there aren't any snapshots for this month, so perhaps I'm not alone.
I tried this :-
RELNAME=9.0
BUILDNAME=${RELNAME}-GENESIS
make release CHROOTDIR=/tmp/${RELNAME}-release BUILDNAME=$BUILDNAME
HTTP_PROXY=http://proxy:3128 FTP_PROXY=http://proxy:3128
On 26/03/2011, at 15:02, Daniel O'Connor wrote:
!
[adding a mailing list per your suggestion]
I think you are misunderstanding the issue here.
This is not a ghostscript issue and the maintainer of ghostscript
isn't the right person to look at it. The same issue can appear with
other ports used by make release, such as perl. In fact, there isn't
any
On 5/22/2010 8:25 PM, Rob Farmer wrote:
make release is still broken on amd64 as of svn 208373 (2010-05-21
04:52:49 -0500)
That patch seems unrelated?
What needs done is
/src/release/$ARCH/boot_crunch.conf files need the relevant libraries
added to the libs section. I haven't tested
On Sun, May 23, 2010 at 11:02 PM, James R. Van Artsdalen
james-freebsd-curr...@jrv.org wrote:
On 5/22/2010 8:25 PM, Rob Farmer wrote:
make release is still broken on amd64 as of svn 208373 (2010-05-21
04:52:49 -0500)
That patch seems unrelated?
What needs done is
/src/release/$ARCH
On 5/18/2010 2:34 AM, jhell wrote:
On Mon, May 17, 2010 at 10:35 PM, Rob Farmer
rfar...@predatorlabs.net wrote:
make release is broken on current. Seems to be related to the lzma
import. This is on i386:
cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo
test.lo
On Sat, May 22, 2010 at 8:09 AM, James R. Van Artsdalen
james-freebsd-curr...@jrv.org wrote:
On 5/18/2010 2:34 AM, jhell wrote:
On Mon, May 17, 2010 at 10:35 PM, Rob Farmer
rfar...@predatorlabs.net wrote:
make release is broken on current. Seems to be related to the lzma
import
On 5/18/2010 1:39 AM, Garrett Cooper wrote:
On Mon, May 17, 2010 at 10:35 PM, Rob Farmer rfar...@predatorlabs.net wrote:
Hi,
make release is broken on current. Seems to be related to the lzma
import. This is on i386:
cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo
Rob Farmer wrote:
Hi,
make release is broken on current. Seems to be related to the lzma
import. This is on i386:
..
: undefined reference to `lzma_end'
/usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x567):
In function `xz_filter_read
Hi,
make release is broken on current. Seems to be related to the lzma
import. This is on i386:
cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo
test.lo camcontrol.lo dhclient.lo fsck_ffs.lo ifconfig.lo mount_nfs.lo
newfs.lo route.lo rtsol.lo tunefs.lo cpio.lo find.lo
On Mon, May 17, 2010 at 10:35 PM, Rob Farmer rfar...@predatorlabs.net wrote:
Hi,
make release is broken on current. Seems to be related to the lzma
import. This is on i386:
cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo
test.lo camcontrol.lo dhclient.lo fsck_ffs.lo
thanks alot for your reply...
but, after patched my FreeBSD with your patch, i still get errors
root pwd
/home/fajri/data/usr/src/release
root patch genesis-patch-ae
root make release CHROOTDIR=/home/fajri/data/root BUILDNAME=FAJRI
CVSROOT=/home/fajri/data/usr RELEASETAG
email.
root pwd
/home/fajri/data/usr/src/release
root patch genesis-patch-ae
root make release CHROOTDIR=/home/fajri/data/root BUILDNAME=FAJRI
CVSROOT=/home/fajri/data/usr RELEASETAG=RELENG_4_8_RELEASE
cd /home/fajri/data/root/usr rm -rf src cvs -R -d
/home/fajri/data/usr co -P
fajri more stable-supfile|grep release
*default release=cvs tag=RELENG_4
==
# make release CHROOTDIR=/home/fajri/data/root BUILDNAME=FAJRI
CVSROOT=/home/fajri/data/usr RELEASETAG=RELENG_4
if [ -f /etc/resolv.conf ]; then cp -p /etc/resolv.conf
On Tuesday 21 October 2003 16:31, Anthony Fajri wrote:
fajri more stable-supfile|grep release
*default release=cvs tag=RELENG_4
You aren't syncing the repo with cvsup so the check out in make release
doesn't work.
Either apply the patch I attached and add CPNOTCVS= to your make release
On Tue, Oct 21, 2003 at 04:51:22PM +0930, Daniel O'Connor wrote:
[...]
Either apply the patch I attached and add CPNOTCVS= to your make release
options, or check out the repository.
In HEAD, a similar functionality is already provided through the
use of the EXTSRCDIR variable. JFYI.
Cheers
On Tue, Oct 21, 2003 at 04:51:22PM +0930, Daniel O'Connor wrote:
[...]
Either apply the patch I attached and add CPNOTCVS= to your make
release options, or check out the repository.
In HEAD, a similar functionality is already provided through the
use of the EXTSRCDIR variable. JFYI.
Ahh
Hi,
when doing my first make release I noticed it stopped somewhere and
hung :(
74830 p2 D+ 0:01.12 cpio -dump /mnt
The host is i386 and TARGET ist sparc64 just to confuse.
The base system runs a HEAD world/kernel from mid july.
The above cpio must be from src/release/sparc64
Folks,
I've noted that the following inconsistency exists in make release. If
there is a install.cfg file in /usr/src/release when executing make
release (the file which if exists is placed into the root of mfs and
customises behaviour of sysinstall), /usr/src/release/install.cfg takes
How can the values for BIGBOOT image can be changed so if there is source
patch for the system like ssp make release won;t fail when buidling release.9
stage ?
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
On 14-Aug-2003 NIkolay Kalev wrote:
How can the values for BIGBOOT image can be changed so if there is source
patch for the system like ssp make release won;t fail when buidling release.9
stage ?
Use a local patch via LOCAL_PATCHES.
--
John Baldwin [EMAIL PROTECTED]http
Hi,
I'm currently down to this patch to allow a make release to complete
for -current:
===
RCS file: /home/ncvs/src/release/Makefile,v
retrieving revision 1.801
diff -u -r1.801 Makefile
--- Makefile26 Jul 2003 06:47:40 -
On Tue, Jul 29, 2003 at 06:30:54AM -0400, John wrote:
Hi,
I'm currently down to this patch to allow a make release to complete
for -current:
[...]
Try setting the KERNEL_FLAGS=-DNO_WERROR instead.
without it, the following causes BOOTMFS to abort:
cc -c -Os -pipe -Wall
calls the command above. I'm currently in the middle of the
make release and will see if this is reproduceable.
# chroot /vol/vol0/work/5-current-chrootdir /bin/sh
# env
A few things not needed that are inherited from my normal
account, but nothing that should have a negative
On Tue, 29 Jul 2003, Ruslan Ermilov wrote:
...
Forget what I've said about NO_WERROR, it (unfortunately) only
applies to the userland.
Still, running make rerelease KERNEL_FLAGS=WERROR= gets the
release done.
I wondered why I get it, and similarly my nigthly buildkernel
completed without
On Wed, Jul 30, 2003 at 06:14:17AM +1000, Bruce Evans wrote:
On Tue, 29 Jul 2003, Ruslan Ermilov wrote:
...
Forget what I've said about NO_WERROR, it (unfortunately) only
applies to the userland.
Still, running make rerelease KERNEL_FLAGS=WERROR= gets the
release done.
I
In the last episode (Jul 29), Ruslan Ermilov said:
Hm, I always thought that -O2 and -Os are just useful aliases that in
effect only turn a few dozens of -f optimization flags, and that
switching some of them off later is allowed. I.e., -Os
-fno-strict-aliasing should work.
That does work,
On Tue, 29 Jul 2003, Ruslan Ermilov wrote:
On Wed, Jul 30, 2003 at 06:14:17AM +1000, Bruce Evans wrote:
On Tue, 29 Jul 2003, Ruslan Ermilov wrote:
...
Forget what I've said about NO_WERROR, it (unfortunately) only
applies to the userland.
Still, running make rerelease
On Tue, Jul 22, 2003 at 02:26:34PM -0400, John Baldwin wrote:
On 22-Jul-2003 Ruslan Ermilov wrote:
Hi!
As many of you probably know, recent telnet commit broke snapshot
building. Since I needed a working make release to go on with
my task on floppy-less make release (for AMD64, etc
release to go on with
my task on floppy-less make release (for AMD64, etc.), I had to
just fix it. Attached is the patch. It also fixes another issue
with this telnet commit: it ensures that crypto telnet[d] do not
end up in the base distribution.
Why not simply enable 'NO_FLOPPIES
On Tue, Jul 22, 2003 at 03:07:01PM -0400, John Baldwin wrote:
Are you eliminating the mfsroot?
Yes.
Ugh.
How does sysinstall work with this change? You do realize that we
mount the MFS as /, then mount the disk under /mnt, chroot to /mnt,
then mount the CD in /dist in the chroot
On Tue, Jul 22, 2003 at 07:42:33PM +0300, Ruslan Ermilov wrote:
Hi!
As many of you probably know, recent telnet commit broke snapshot
building. Since I needed a working make release to go on with
my task on floppy-less make release (for AMD64, etc.), I had to
just fix it. Attached
probably know, recent telnet commit broke snapshot
building. Since I needed a working make release to go on with
my task on floppy-less make release (for AMD64, etc.), I had to
just fix it. Attached is the patch. It also fixes another issue
with this telnet commit: it ensures that crypto
On Wed, Jul 23, 2003 at 11:33:50AM +0100, Mark Murray wrote:
Hi
Please do not commit this.
Please stop repeating this endlessly. This patch is only
for those who need a working make release urgently, like
me. You made it clear that you're working on a better fix.
--
Ruslan Ermilov
Hi!
As many of you probably know, recent telnet commit broke snapshot
building. Since I needed a working make release to go on with
my task on floppy-less make release (for AMD64, etc.), I had to
just fix it. Attached is the patch. It also fixes another issue
with this telnet commit
: inline
Content-Transfer-Encoding: quoted-printable
Hi!
As many of you probably know, recent telnet commit broke snapshot
building. Since I needed a working make release to go on with
my task on floppy-less make release (for AMD64, etc.), I had to
just fix it. Attached is the patch. It also
On 22-Jul-2003 Ruslan Ermilov wrote:
Hi!
As many of you probably know, recent telnet commit broke snapshot
building. Since I needed a working make release to go on with
my task on floppy-less make release (for AMD64, etc.), I had to
just fix it. Attached is the patch. It also fixes
On Tue, Jul 22, 2003 at 02:26:34PM -0400, John Baldwin wrote:
On 22-Jul-2003 Ruslan Ermilov wrote:
Hi!
As many of you probably know, recent telnet commit broke snapshot
building. Since I needed a working make release to go on with
my task on floppy-less make release (for AMD64, etc
On 22-Jul-2003 Ruslan Ermilov wrote:
On Tue, Jul 22, 2003 at 02:26:34PM -0400, John Baldwin wrote:
On 22-Jul-2003 Ruslan Ermilov wrote:
Hi!
As many of you probably know, recent telnet commit broke snapshot
building. Since I needed a working make release to go on with
my task
building. Since I needed a working make release to go on with
my task on floppy-less make release (for AMD64, etc.), I had to
just fix it. Attached is the patch. It also fixes another issue
with this telnet commit: it ensures that crypto telnet[d] do not
end up in the base distribution
telnet commit broke snapshot
building. Since I needed a working make release to go on with
my task on floppy-less make release (for AMD64, etc.), I had to
just fix it. Attached is the patch. It also fixes another issue
with this telnet commit: it ensures that crypto telnet[d] do
On Tue, Jul 22, 2003 at 03:07:01PM -0400, John Baldwin wrote:
Why not simply enable 'NO_FLOPPIES' on the arch's that don't want
floppies?
Are you eliminating the mfsroot?
Yes.
Ugh.
Yes, after looking into this a bit deeper, I must agree that
preserving the mfsroot is much
On Sun, Jul 20, 2003 at 02:44:23PM +0300, Ruslan Ermilov wrote:
A few days ago I've noticed such messages in CURRENT buildlog (on 4.7
box, building without -jsomething) :
cc -Os -pipe -c chown_stub.c
ld -dc -r -o chown.lo chown_stub.o /usr/obj//usr/src/usr.sbin/chown/chown.o
On Mon, Jul 21, 2003 at 02:13:45PM +0300, Andrey Elperin wrote:
On Sun, Jul 20, 2003 at 02:44:23PM +0300, Ruslan Ermilov wrote:
A few days ago I've noticed such messages in CURRENT buildlog (on 4.7
box, building without -jsomething) :
cc -Os -pipe -c chown_stub.c
ld -dc -r -o
On Mon, Jul 21, 2003 at 06:08:43PM +0300, Ruslan Ermilov wrote:
On Mon, Jul 21, 2003 at 02:13:45PM +0300, Andrey Elperin wrote:
On Sun, Jul 20, 2003 at 02:44:23PM +0300, Ruslan Ermilov wrote:
A few days ago I've noticed such messages in CURRENT buildlog (on 4.7
box, building without
Just got the following from a 'make release BUILDNAME=5.1-CURRENT
CHROOTDIR=/usr/release CVSROOT=/usr/ncvs NOPORTS= NODOC= . My
world was up to date to within a day. The full log is at
http://people.freebsd.org/~scottl/current-release-i386.log.gz. Note
that while this is an SMP machine, -j
On Sun, Jul 20, 2003 at 02:18:42AM -0600, Scott Long wrote:
Just got the following from a 'make release BUILDNAME=5.1-CURRENT
CHROOTDIR=/usr/release CVSROOT=/usr/ncvs NOPORTS= NODOC= . My
world was up to date to within a day. The full log is at
http://people.freebsd.org/~scottl/current
Hi,
A few days ago I've noticed such messages in CURRENT buildlog (on 4.7
box, building without -jsomething) :
cc -Os -pipe -c chown_stub.c
ld -dc -r -o chown.lo chown_stub.o /usr/obj//usr/src/usr.sbin/chown/chown.o
crunchide -k _crunched_chown_stub chown.lo
echo int
On Sun, Jul 20, 2003 at 02:04:28PM +0300, Andrey Elperin wrote:
Hi,
A few days ago I've noticed such messages in CURRENT buildlog (on 4.7
box, building without -jsomething) :
cc -Os -pipe -c chown_stub.c
ld -dc -r -o chown.lo chown_stub.o /usr/obj//usr/src/usr.sbin/chown/chown.o
1 - 100 of 436 matches
Mail list logo
