REFIX=${.OBJDIR}/modules KMODDIR=${KODIR}
>
> modules:
> ! @mkdir -p ${.OBJDIR}/modules
> ! cd $S/modules && env ${MKMODULESENV} ${MAKE} obj all
>
> modules-depend:
> @mkdir -p ${.OBJDIR}/modules
> ! cd $S/modules && env ${MKM
d ../marcel; pwd
/xtra/marcel
pwd
/xtra/ncvs
*** Parallel case
gauss% make -f ~/mf -j2
cd ../marcel; pwd
/xtra/marcel
pwd
/xtra/marcel
...other than that... :-)
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
David O'Brien wrote:
>
> On Mon, Nov 13, 2000 at 01:19:38PM -0500, Marcel Moolenaar wrote:
> > I'll commit a fix with just semi-colons today for all architectures if
> > someone hasn't done that already by that time.
>
> Can you post a patch first. Ther
Marcel Moolenaar wrote:
>
> David O'Brien wrote:
> >
> > On Mon, Nov 13, 2000 at 07:51:11PM +0900, Makoto MATSUSHITA wrote:
> > > ! cd $S/modules && env ${MKMODULESENV} ${MAKE} obj all
> > > --- 310,322
> > > ! cd $S/mo
cd $S/modules && env ${MKMODULESENV} ${MAKE} all
>
> I can certainly commit this type of fix. The combined make invocation
> was an optimization someone recommended.
No you can't. $S expands to "../.." which only works for the first cd in
the -jX case. The seco
uot;../.." and -j runs a single shell, the first cd
will succeed, but not the second.
I simply copied the "construction" in the second and posted fix.
I'll commit a fix with just semi-colons today for all architectures if
someone hasn't done that already by that time.
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
-depend:
@mkdir -p ${.OBJDIR}/modules
- cd $S/modules && env ${MKMODULESENV} ${MAKE} obj depend
+ cd $S/modules && env ${MKMODULESENV} ${MAKE} obj $$ \
+ env ${MKMODULESENV} ${MAKE} depend
modules-clean:
cd $S/modules && env ${MKM
gt;
> I think i read some thing about this from the mailing list not long ago..
> however i can hardly remember anything or any solutions of fixing this
> problem. Can someone plz help me with this!
The problem has been resolved for some time now. Make sure you have the
latest sources whe
verted. Auto-generation needs more work than just
changing a makefile. I was under the impression that the Alpha port
worked, but it basicly is as broken as the i386 port was after my
"syncing".
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
T
t; Sync with Alpha:
> Do not use sysent.c, proto.h and syscall.h in source tree;
> use auto-generated versions.
>
> This happens when I build in sys/compile and when I build via
> 'make buildkernel'. With a fresh cvs updated source I get:
I reverted the commit.
--
ke a
case study).
If the precise ifdefs are too costly, the "not quite right" approach
will probably be preferable. I didn't want to implement the "not quite
right" fix as an interim solution, because interim somehow gets a more
permanent nature in these cases...
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
John Baldwin wrote:
>
> I already managed to test it locally here and commit the proper fix.
> It was an order of operations bug due to the fact that ! is
> evaluated before &.
Ok, thanks!
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (40
o this instead:
>
> if (dev->si_flags & SI_NAMED != 0)
>
> It could be an order of operations buglet.
Give me a couple of days to play with it...
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Akinori MUSHA wrote:
>
> At Thu, 2 Nov 2000 14:11:44 -0500 (EST),
> Andrew Gallatin wrote:
> > To clarify -- this is the native /bin/ls and NOT /compat/linux/bin/ls?
>
> Yes.
How is linux_ustat involved if the panic is caused by a native binary?
--
Marcel Moolenaar
m
or anybody can give pointers as to what needs to be
> done?
I'm not aware someone is working on it. It doesn't look like it needs
much work, but I don't know the details as I said. For pointers: mail
archives.
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
t
no.
> Are there similar problems for seriel devices?
Probably.
It's quite likely we don't support less frequently used or very
specialized ioctls. These are mostly implemented on a need-to-have basis
triggered by a can-be-done condition (what?)
Do you know what you need?
--
Marcel Mool
it as well. IIRC, it simply means that the bpf pseudo device needs
to be updated, but is otherwise harmless. I forgot the details, but it's
all in the mailinglist archives. Somewhere... :-)
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscrib
in the vfinddev() right after.
Right-o :-)
> It's still mightily bogus though...
Yes. A more dynamic solution needs to be used that creates mappings (and
dev_t values) on the fly.
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe:
quence S,
with S > 255 into S % 255. This is not very likely. Hmmm... the strange
assignment of NFS mounts might be a problem as well (warning: vague
recollections in combination with memory leaks of dated info and mental
cross-talk may make this statement slightly off :-)
--
Marcel Moolenaar
Andrew Gallatin wrote:
>
> Marcel Moolenaar writes:
> > Wesley Morgan wrote:
> > >
> > > Anyone having problems with the linuxulator the past couple days?
> >
> > Define "past couple of days". I have a working linuxulator made on Oct
&g
free are explained by the following two
statements:
lu.f_tfree = stat->f_bfree;
lu.f_tinode = stat->f_ffree;
In short: given the (u)dev_t, get the FS statistics and return the
number of free blocks and inodes of the FS on that device.
--
Marcel Moolenaar
m
Wesley Morgan wrote:
>
> Anyone having problems with the linuxulator the past couple days?
Define "past couple of days". I have a working linuxulator made on Oct
29, 12:25 PST.
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubs
Satoshi - Ports Wraith - Asami wrote:
>
> * From: Marcel Moolenaar <[EMAIL PROTECTED]>
>
> * The following 2 patches solve the problem when building XFree86-3.3.6
> * with only the VGA16 and SVGA servers. Building other servers may still
> * be broken.
>
&g
t;
The following 2 patches solve the problem when building XFree86-3.3.6
with only the VGA16 and SVGA servers. Building other servers may still
be broken.
The patches are relative to .../XFree86/work
FYI,
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
dif
#include
#elif defined(linux)
#if defined __STRICT_ANSI__
I'm going to build 3.3.6 anyway, because 4.0.1 coredumps on my new
notebook, so I'll try to make a patch as well. If someone can make a PR
out of this thread, then we're all happy; especially jmz.
--
Marcel Moolenaar
ma
to free some time for
this. It sounds important enough from what I understand from Gerald.
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
break;
Is their any harm in just keeping the -P flag as a no-op and optionally
remove it at some later time (for backward compatibility)?
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marcel Moolenaar wrote:
>
> Alexey Zelkin wrote:
> >
> > I am trying to realize "is requested locale physicaly present on this system"
> > or it's just an alias.
>
> Can you not revert the test: if the locale is present in the alias file,
> then
he
system?
Just a quick thought...
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
he same error.
> XFree86-3.3.6 and XFree86-contrib-3.3.6 both working just fine.
> ``xhost +'' did not resolve the problem.
Should be fixed already. Please re-cvsup.
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [
Sean-Paul Rees wrote:
>
> On Sun, Aug 27, 2000 at 05:24:07PM -0700, Marcel Moolenaar wrote:
> > "George W. Dinolt" wrote:
> > >
> > > I was wondering whether the setrlimit changes had something to do with
> > > this. This seems to be the major ch
rcel)
Can you track down which change caused the failure. I haven't
experienced any problems so far. I'll try running SO myself in the mean
time.
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
with &
Johan Karlsson wrote:
>
> Can you please have a look at some PRs which deals with some minor problem
> with the buldkernel/installkernel targets of Makefile.inc1 and the
> install-modules target of sys/conf/Makefile.${MACHINE}
I will. Thanks for the pointers,
--
Marcel Mool
make KERNEL=GENERIC install
> make: not found
> *** Error code 127
Make sure you have /usr/src/Makefile.inc1 rev 1.162 or up. The
installkernel was using the wrong buildcontext (ie IMAKEENV). IMAKEENV
was changed to have the very restricted path that broke the
installkernel target as you d
th /usr/bin != /usr.bin...
WORLDTMP is a place to *install* binaries we made during the build. We
don't install in /usr.bin or /usr.sbin; we install in /usr/bin and
/usr/sbin resp.
> Disgruntled and reverting back to making kernels the way they were intended,
So, what's broken the
.
It's fixed now (famous last words)...
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
e kernel will be called
'kernel' (again)! If you used the installkernel before and have modified
your /boot/loader.conf, make sure it's booting /kernel again.
HTH,
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail
snapshot.
Grrr...
Is there a clean way to fix this, other than reverting the -L
incompatibility?
Did we bump the libc version number when the strtofflags/fflagstostr
functions went in?
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send
nt is int (which is 32-bits for us) and
creates the call-site as such, but while compiling the function itself
it creates a 64-bit integral for that argument)...
HTH,
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROT
opy 'cp' in installworld as well. I didn't catch it
because it will probably only copy ld-elf.so if an existing version is
present (I tested with an empty DESTDIR).
I'll fix it.
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsu
LES=true == ...
To enable modules, remove or comment out the NO_MODULES line.
HTH,
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
SD, when on Windows it probably gets
> executed by default...
Netscape runs it as well. Seeing Netscape start java is a clear sign.
It's probably harmless in this case, but I didn't wait to find that out.
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408)
the daemon is down and the script doesn't know about
it, you have to remove pid files and whatnot to use the script again to
get the daemon running, right?
> I personally find the 'chkconfig' command to be
> very convenient to enable, disable, and list boot-time services, wi
David O'Brien wrote:
>
> On Tue, Jul 04, 2000 at 03:53:12PM -0700, Marcel Moolenaar wrote:
> > Good point. For the linuxulator this has been discussed before and
> > something in the line off...
> > ...came out of it.
>
> Even before you get an Alpha, woul
bles (= compat.linux.*) and where other emulators are
expected to have their variables.
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
gt; binutils first? It sure would be a MAJOR BUMMER if one needed to
> update binutils first...
The ability to do cross builds rules out the need to update binutils
first. I haven't done any cross-builds since, well, februari, so I'm not
at all up to date on that front; things may
ion.
You can however use a union and have a non-volatile object aliasing a
volatile object as in:
union u {
volatile int vi;
int nvi;
};
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
ew
headers are installed. Obsoleting header files can create as much
backward compatibility problems as obsoleting functions or options can.
It should have been dealt with accordingly...
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe:
t, Linux is linux_base and linux_devel from ports.
Do you see this on other filesystems as well?
BTW: How old are your linux_base and linux_devtools ports?
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "
n't think pam is a development tool, which makes linux_devtools the
wrong port. I also don't think we need pam in any other port if it's
needed in only one or two situations. Since the ports use rpms, you can
always, and are free, to install any additional rpms you want/need. It
actu
the feedback.
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
abase working. Oracle8i was fairly new at the time and I
wasn't going to waste any time tracing bugs that also existed on Linux.
My primary concern was the Linuxulator :-)
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EM
999Q2 I did an install of Oracle8i, which failed due to an installer
problem, IIRC. I only modified 1 script to overcome the shell execution
problem. You are using Blackdown JDK, are you?
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
assigned
during a buildworld for internal purposes. There's only a very limited
way (ie for a very limited set of tools) to specify during build where
they will end up and where they can expect data files. In all other
cases it is assumed that the programs are run from the normal place.
--
Ma
Andrzej Bialecki wrote:
> Is it possible to do an installworld not to / of existing system, but to,
> say, subdirs somewhere, which could be mountpoints for another disk?
Yes. Do something like:
make installworld DESTDIR=/where/ever/you/want/it/installed
HTH,
--
Marcel Moo
sysctls are on a
per jail basis. See jail(8)
FYI,
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
gent
enough to rush it in anyway...
The bottomline is known...
BTW: If a fix is easy, then that doesn't mean that it isn't potentially
dangerous :-)
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
again before I commit it. To speed things up, you are
of course welcome to be pro-active (damn, my work environment already
gets to me :-)
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
d) on alpha running 3.x.
> It was discussed about month ago on -current...
I don't consider this less important. Having the ability to do cross
builds helps maintaining FreeBSD on multiple platforms and also helps in
porting to new platforms.
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Josef Karthauser wrote:
> The reason for adopting a fall back solution it that it is not clear that
> setflags/getflags is the best choice of function name for manipulating
> file flags as it's a bit too generic a name. Whilst we're debating
> this point there's no point in having them as librar
> only. In -stable, and in -current before the end of December the
> following tools: ls, rm, chflags, find, xinstall and mtree used
> a common set of routines to manipulate file flags.
[snip]
> tool. At the beginnig of January, because of the proliferation of
> utilities using these functions,
> > I already have patches (somewhere :-) that solve this problem. I choose
not
> > to apply these before the release. I will fix installworld after the
> > release. For now, you can use the buildkernel and installkernel targets
> > (after a buildworld) to solve the (possibly complex) dependencies
> On 28-Jan-00 Jeroen Ruigrok van der Werven wrote:
> > ===> bin/pwd
> > install -c -s -o root -g wheel -m 555 pwd /bin
> > install -c -o root -g wheel -m 444 pwd.1.gz /usr/share/man/man1
> > ===> bin/rcp
> > install -c -s -o root -g wheel -m 4555 -fschg rcp /bin
> > /usr/libexec/ld-elf.so.1:
Sheldon Hearn wrote:
>
> On Sat, 15 Jan 2000 12:02:09 +0100, Marcel Moolenaar wrote:
>
> > No. build-tools are those tiny little utilities that are part of the
> > sources and are only used to build the sources.
>
> Okay, so how do we boot-strap lint? Ultima
es as earlier on it seemed to be
> leaving stale ones behind. I don't know if this is still the case but it
> looks a bit like it.
There should be a dependency from ${.OBJDIR} to Makefile so that when
Makefile is updated, ${.OBJDIR} is removed. Removing sources from
makefiles is a
.c 2000/01/10 08:54:09 1.11
+++ main.c 2000/01/10 17:47:33
@@ -304,7 +304,7 @@
if (tmpdir == 0) tmpdir = "/tmp";
len = strlen(tmpdir);
-i = len + 13;
+i = len + 17;
if (len && tmpdir[len-1] != '/')
++i;
--
Marcel Moolen
Neal Westfall wrote:
>
> ===> ../secure/lib/libcrypt
> make: don't know how to make crypt-shs.c. Stop
> *** Error code 2
Fixed. Thanks!
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc
"Jordan K. Hubbard" wrote:
>
> 10 days, folks! Make 'em count.. :)
>
If people would stop sending this to -committers, I will actually have
some time left in which to do some work :-)
Better still, stop it completely.
thanks,
--
Marcel Moolenaar
eak up... preferably with diffs :-)
\begin{talking to myself}
I have to finish those linux ports and PRs as well. Not to forget mumble
mumble, especially mumble mumble mumble...
\end{mumble mumble}
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking &
Michael Lucas wrote:
> The COMPAT_LINUX kernel option isn't needed any more, per Marcel. (At
> least, when I wrote an article on this, it wasn't.) You can probably
> remove COMPAT_LINUX entirely.
Assuming that you want to use the module of course...
-
broken but simple enough. If you
don't want X, don't recompile doscmd or don't install X. Any other
change only adds to the argument of making doscmd a port (or two), IMO.
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases
I still think doscmd should and can be a port, but I think it helps my
argument if I have the port ready to be committed and downloadable for
testing. It helps undermine the general objection that doscmd is very
dependent on the kernel, which I doubt...
If not, it will at least show me that I
11 support and one without.
But isn't that what our ports collection isn't all about. Examples:
kde11 vs kde11-i18n
nethack vs nethack-qt
*emacs*
Alternatively, the user can specify whether he/she wants X11 support by
adding -DUSE_XLIB or -DNO_X or whatever.
Not to forget that we can
Bruce Evans wrote:
>
> On Tue, 4 Jan 2000, Marcel Moolenaar wrote:
>
> > [sent to both -current and -arch]
> >
> > Hi,
> >
> > doscmd breaks cross-building, because it depends on X11 which obviously
> > is not in the source tree (see below). I
int1a.o int2f.o intff.o mem.o
mouse.o net.o port.o setver.o signal.o timer.o trace.o trap.o tty.o
xms.o -L/usr/X11R6/lib -lX11
/usr/X11R6/lib/libX11.so: file not recognized: File format not
recognized
*** Error code 1
Thanks,
--
Marcel Moolenaarmailto:[EMAIL PROTEC
akes a 'shut off translation for this pid' type
> syscall then execve()s the app. Kinda like nohup.
What about inheritence? Setting `the bit' for a process is one thing,
but what about it's children?
I think we should implement the 'no overlaying' pr
w kernel. Try the new kernel first, then the buildworld.
This is not a problem anymore, because we don't execute anything that is
compiled against the new sources.
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www
juan wrote:
>
> yacc -d /usr/src/usr.bin/colldef/parse.y
> *** Signal 12
>
> Stop in /usr/src/usr.bin/colldef.
Are you doing anything special? If not, try cleaning /usr/obj first and
make sure your source tree is ok.
--
Marcel Moolenaarmailto:[EMAIL
e-print-version
>/usr/src/kerberosIV/lib/libroken/../../../crypto/kerberosIV/lib/roken/make-print-version.c
> /usr/obj/usr/src/i386/usr/libexec/elf/ld: cannot open libgcc.a: No such file or
>directory
> *** Error code 1
Fixed, thanks.
--
Marcel Moolenaarmailto:[E
got some time to
think this over.
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
installworld. At this time you should
therefore not use `make world' yet. A full upgrade path can only be
offered if the kernel is also made along with a buildworld and is also
installed as part of the installation process. This requires a bit more
work though.
--
to-init dma. last night i committed a fix to
> make the ess cards use autoinit, so they should work now.
Ah, that's my cue!
Rebuilding kernel (may newpcm be a module soon :-)
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases
Jos Backus wrote:
>
> After some more digging I have found out why buildworlds are failing on my
> system: it's because I have NO_FORTRAN=true in /etc/make.conf.
[snip]
Thanks. Will be fixed.
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworki
be able to share the object tree as well, but this
requires /usr/obj/${MACHINE_ARCH} as the prefix for all builds, not just
the cross-builds. That way you can build an Alpha system on i386 and
install it on an Alpha from an NFS mounted object dir. Fortunately, it
only a symlink away :-)
HTH,
--
d problems.
Yes, anything is wrong. ${DESTDIR}/usr/include is already present in
CFLAGS and points to the proper include files.
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
The FreeBSD project
hat. It's now conditional
on COMPAT_43 which is wrong, because the osig* code is not 4.3BSD
specific.
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED
g their builds to work. Okay, what
>did I miss?
Your -current must be at least 6 if not 9 months old, right?
gcc doesn't have a mkstemps implementation anymore. This means that you
must has a -stable or -current that has the function in libc.
--
Marcel Moolenaar
Martin Cracauer wrote:
>
> In <[EMAIL PROTECTED]>, Marcel Moolenaar wrote:
> > It seems to me that when there's a PATH= assignment you don't want to
> > add anything to the cache or alternatively, clear the cache after
> > execution of the command h
to
add anything to the cache or alternatively, clear the cache after
execution of the command having a PATH= assignment.
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
The FreeBSD projectmailto
Martin Cracauer wrote:
>
> In <[EMAIL PROTECTED]>, Marcel Moolenaar wrote:
> > Sheldon Hearn wrote:
> > >
> > > On Tue, 14 Dec 1999 15:42:11 +0100, Marcel Moolenaar wrote:
> > >
> > > > > You set all those variables for the first m
./x.sh: make: not found
> >
> > ^^^
> > At this point PATH contains /usr/bin, so I don't think it's PATH
> > related.
>
> No, $PATH is restored to what is was before the first make command.
Yes, I know and as I said it contains /usr/bin.
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> Marcel Moolenaar writes:
> : #!/bin/sh
> : PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\
> : /usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:\
> : /usr/games:/usr/local/bin:/usr/X11R6
Sheldon Hearn wrote:
>
> On Tue, 14 Dec 1999 15:42:11 +0100, Marcel Moolenaar wrote:
>
> > > You set all those variables for the first make command, but not for the
> > > second. What did you expect to happen?
> >
> > That make(1) would execute.
>
&
Sheldon Hearn wrote:
>
> On Tue, 14 Dec 1999 14:30:59 +0100, Marcel Moolenaar wrote:
>
> > #!/bin/sh -ev
> > cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/i386 \
> > PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\
> > /usr/obj/usr/src/i386/usr/ga
Sheldon Hearn wrote:
>
> On Tue, 14 Dec 1999 14:48:51 +0100, Marcel Moolenaar wrote:
>
> > #!/bin/sh
> > PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\
> > /usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:\
> > /usr/games:/usr/loca
430152 Dec 11 13:05 /bin/sh
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
to do with the size of the new PATH
variable...
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
somewhere in a search path. Also, having games as part of FreeBSD
without a proper search path to them is also a bit odd.
Anyway, my 2c...
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
The FreeBSD project
: syntax error near line 1
> *** Error code 69
Yes. I had it built as a tool in my tests, but got lost somehow in the
final commit.
Thanks,
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
The FreeBSD proje
I have to re-enable sbc0 to see if any changes therein apply to ESS as
well. Should I have sbc0 in the first place?
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PRO
301 - 400 of 512 matches
Mail list logo
