On (2003/11/24 15:39), Kevin Oberman wrote:
> > > I end up with the following when I run `make world` on 5.1-RELEASE-p10.
> >
> > Did you read UPDATING?
>
> I fear a bikeshed, but I really think it may be past time to remove
> the 'world' target from /usr/src/Makefile.inc1. It is rarely useful
On (2003/11/13 14:02), Eric Anderson wrote:
> I'm not having any luck - I'm started to feel like I'm missing something
> here :)
>
> I cvsup'd yesterday afternoon, and did my usual make buildworld, kernel,
> install kernel, single user mode, then make installworld - except it
> bombed on the i
On (2003/11/10 11:35), Alexander Leidinger wrote:
> > Is there any plan to make it into the kernel ?
>
> AFAIK the author of ALTQ said we shouldn't import it. Search the mailing
> lists @FreeBSD.org for the reason.
If anyone finds that message in the archives, please post a URL. I
can't find it
On (2003/11/04 15:46), Jeff Roberson wrote:
> > The thing is, I'm using 4BSD, not ULE, so I wouldn't trouble Jeff to
> > look for a cause for that specific problem in ULE.
>
> How long have you been seeing this? Are you using a usb mouse? Can you
> try with PS/2 if you are?
Since my last updat
On (2003/11/03 13:38), Brooks Davis wrote:
> I've sent mail to both his FreeBSD address and the one on the IPFilter
> homepage. If anyone knows a reliable way to communicate with him, that
> would be useful.
The latter address works, but he's terrible with email, by his own
admission. If you do
On (2003/11/04 09:29), Eirik Oeverby wrote:
> The problem is two parts: The mouse tends to 'lock up' for brief moments
> when the system is under load, in particular during heavy UI operations
> or when doing compile jobs and such.
> The second part of the problem is related, and is manifested by
On (2003/10/09 16:57), Jeff Roberson wrote:
> > For me, the sluggish mouse problem manifests under these conditions:
> >
> > 1) Use a USB mouse, not a PS2 mouse.
>
> Is this _only_ with usb?
For me, yes. -CURRENT gets a little sluggish with either scheduler, but
the noticible difference between
On (2003/10/09 00:28), Scott Sipe wrote:
> Anything that seems disk intensive: bzip2 (unbzip2ing one big file makes
> this happen), making world, building ports, etc makes my X environment
> practically unusable. Mouse stutters, reaction times is very slow, feels
> 10x more sluggish than normal.
On (2003/09/24 20:18), John Birrell wrote:
> > Okay, so what are we supposed to do to ports that are now broken because
> > -pthread doesn't exist (e.g. devel/pwlib)?
>
> -pthread is back in current. It just had a little holiday. It's back,
> refreshed, eager and willing to do the deed. 8-)
That
On (2003/09/23 19:35), Daniel Eischen wrote:
> The applications is free to link to whatever it wants;
> we're not changing that. If it wants to link to 1:1
> libthr or whatever, then it had better be sure to use
> -lthr because -pthread won't do it regardless of whether
> it is a NOOP or not.
Ok
On (2003/09/04 14:44), Paul Richards wrote:
> Overwriting a file that's currently executing results in a "Text file
> busy" error.
>
> When did this start happening?
>
> This was something that was fixed way back on FreeBSD but it seems to be
> a problem again.
Really? I've never seen it "fixe
On (2003/09/02 09:43), Ian Freislich wrote:
> > I posted one approach to this today... touch a file right before you
> > start installworld, then consider anything not newer than that file a
> > candidate for disposal. There is currently something weird going on in
> > /usr/lib though... a lot of
On (2003/08/29 11:48), Robert Watson wrote:
> The differences here seem to be:
>
> (1) I'm using -O, not -O2
> (2) I'm optimizing -mcpu as pentiumpro, not pentium4
Isn't pentium4 a known-broken optimization at the moment?
Ciao,
Sheldon.
___
[EMAIL PRO
On (2003/08/29 11:41), Mike Jakubik wrote:
> Yes, I can see that its not working. But this is a solution to the cause,
> not the problem. Shouldn't this be fixed?
Depends on how much work is involved in fixing it, and what the negative
impact is of leaving it. Do you know what the impact is?
>
On (2003/08/29 11:30), Mike Jakubik wrote:
> Why should I have to turn off all my optimization options when building
> world?
Because it's not working? Mind you, it's only -O2 that you're
recommended to turn off; -O works fine.
> This shouldn't be like that. 4.x always compiled fine with -O2 an
Hi Matthew,
Dude, your libmap.conf work ROCKS! Finally, a painless way to play
around with the impact of various threading implementations on Java
without tearing any hair out over symlinks and such.
Thanks!
Sheldon.
___
[EMAIL PROTECTED] mailing list
On (2003/07/21 23:41), Adam wrote:
> Perhaps you should try working with Java 1.4.x on FreeBSD before you
> assume something about me that's highly inaccurate. I think you'll find
> very quickly that it doesn't work nicely unless the process is running
> as root.
So that this doesn't stick in pe
On (2003/07/15 13:35), Byron Schlemmer wrote:
> Being the curious person that I am, I tried the following from the truss
> manpage :
>
> % truss /bin/echo hello
> truss: cannot open /proc/1805/mem: No such file or directory
> truss: cannot open /proc/curproc/mem: No such file or directory
>
> Is
On (2003/06/19 20:06), Tobias Roth wrote:
> you compare a stable linux kernel branch with an unstable freebsd branch.
> please make yourself familiar with freebsds (and possibly linux') release
> process before you make statements like this. you will only piss off the
> people that are trying to h
On (2003/06/01 23:53), Narvi wrote:
> > The absence of credible Java support in FreeBSD has lost us significant
> > penetration in the past, and it would be disastrous if the perceptions
> > of the past shaped the future.
>
> credible rather sounds like 'comes on the installation cd, doesn't have
On (2003/06/01 00:50), Daniel Eischen wrote:
> > I just built jdk13 a couple of days ago. No problem whatsoever. You
> > guys must have rotten karma or something.
>
> Did you already have a native JDK installed?
I built the native 1.4.1 JDK two weeks ago, first without the native JDK
for boots
On (2003/04/02 07:38), Terry Lambert wrote:
> Is the disk I/O really that big of an issue? All writes will
> be on underlying non-blocking descriptors; I guess you are
> saying that the interleaved I/O is more important, further
> down the system call interface than the top, and this becomes
> an
On (2003/04/02 09:43), Michael W . Lucas wrote:
> > You sure you didn't get caught in the middle of a cvsup mirror sync? I
> > have an IP_EVIL world and kernel running fine here.
>
> According to some folks on IRC, it was renamed to "IP_EF" in
> src/sys/netinet/ip.h, but not renamed in ping.c.
>
On (2003/04/02 09:20), Michael W . Lucas wrote:
> While I'm all for a sense of humor, and agree that implementation of
> the IP_EVIL flag is vital for FreeBSD to be a modern operating system,
> it stops being funny when it breaks world.
You sure you didn't get caught in the middle of a cvsup mirr
On (2003/04/02 06:05), Terry Lambert wrote:
> > I think Jeff (or someone else?) said, that some web browsers gain
> > "something" too (serialization issues with libc_r)? I had the impression
> > that this also applies to UP systems.
> >
> > Do I misremember this? If not, does it not apply to UP s
On (2003/04/02 21:48), Bruce Evans wrote:
> > Some of us have been waiting for that behaviour for a long time (long
> > before you started working on ULE).
>
> Er, this is the normal behaviour in FreeBSD-3.0 through FreeBSD-4.8,
> so you shouldn't have waited more than negative 4 years for it :-)
On (2003/04/02 01:54), Jeff Roberson wrote:
> It probably still needs some tweaking but it seems to be MUCH better now.
> New algorithm entirely.
>
> nice +20 processes will not run if anything else wants to.
Some of us have been waiting for that behaviour for a long time (long
before you starte
On (2003/03/19 20:43), Andrew Mace wrote:
> Thanks for Your reply. Your right, I'm in the wrong league here :-). I had
> 5.0 RELEASE installed before, but the jdk1.4 port wouldn't compile and there
> is no binary package. But now that I have it compiled and packaged can I just
> install it on 5.0
On (2003/02/13 14:00), Soeren Schmidt wrote:
> I've prepared a patch that brings the ATA driver to the next level.
You've brought ata in under cam? ;-)
*duck*
Sorry, couldn't resist.
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body o
Hi folks,
Can anyone think of a good way to implement an installworld /
installkernel seat-belt for source upgrades from stable to current?
What I'm looking for is a way for installworld and installkernel in the
current source to look for some signature in the target filesystem that
suggests that
On (2003/01/20 11:04), Martin Blapp wrote:
> http://people.freebsd.org/~mbr/ports/openoffice-port-1.02.tgz
>
> There is one bug (crash) which I'd like to have fixed before I
> update the port. And OpenOffice.org needs to announce OpenOffice.org
> version 1.02 officially.
>
> Maybe you don't have
Hi folks,
Could someone with an up-to-date -CURRENT (as of anything since
Wednesday last week) and OpenOffice let me know whether OpenOffice's
swriter works?
For me, works just implies that it starts up on a blank document before
core dumping, and then accepts at least one character of input.
Th
On (2003/01/14 10:22), local.freebsd.current wrote:
> >In the meantime we _really_ have to ship 5.0-RELEASE, we keep
> >slipping it.
>
> That sounds like "it's time to ship so we're going to ship".
>
> I'm not trying to get up anyone's nose here, but aren't there
> objective release criteria?
Y
Make sure you have rev 1.289 of sys/sys/proc.h, which is expected to fix
the problem you're reporting.
Ciao,
Sheldon.
- Original Message -
Date: Sun, 12 Jan 2003 18:14:51 -0800
From: walt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: world broken at libkvm
> cc -O -pipe -mcpu
On (2002/12/01 19:36), Kris Kennaway wrote:
> > /usr/bin/mmroff
> > /usr/bin/afmtodit
> >
> > /usr/sbin/adduser
> > /usr/sbin/rmuser
>
> These must be converted before 5.0-R.
Unless we make installation of the perl package happen automatically as
part of sysinstall. I spent an hour loo
On (2002/11/20 11:00), Chris Howells wrote:
> I'd love to... sadly I do not know how to. I've only been messing
> around with FreeBSD for around a week (though I'm experienced with
> Linux, but getting bored of it) and am trying 5.0 because 4.7 locks up
> when I try to access my PC Card (maybe Car
On (2002/11/19 15:17), Carl Schmidt wrote:
> The following PR has two patches attached which address the lack of some
> documentation of make.conf in the manual page. It also contains a patch
> for make.conf to fix style inconsistencies and two (if I recall
> correctly) items which are documented
On (2002/11/15 14:45), Vallo Kallaste wrote:
> Yes. For what it's worth, I think that system should be airtight out
> of the box and the consequences for average desktop user (as I am)
> clearly documented in handbook. Users who will not read the fine
> documentation fully deserve the pain.
Well,
On (2002/11/15 09:48), Soeren Schmidt wrote:
> > Don't you think it makes more sense for the kernel to start off with
> > more restrictive permissions, and have the administrator determine
> > whether more restrictive permissions are appropriate?
>
> Actually no I dont.
> The security aware admin
On (2002/11/14 19:27), Soeren Schmidt wrote:
> > - insecure permissions. Among other holes, these allowed the world to
> > erase cd-rw's.
>
> Use rc.devfs for that as it was intended.
Don't you think it makes more sense for the kernel to start off with
more restrictive permissions, and have t
On (2002/11/13 15:06), Dag-Erling Smorgrav wrote:
> > I think it's pretty clear that negative time arguments to sleep(1) are
> > not portable.
>
> I have, somewhere in my big bag of tricks, an unfinished patch which
> would allow us to implement negative sleep times by directing the PSU
> to emit
On (2002/11/12 16:37), Nate Lawson wrote:
> I've found an interesting contradiction and was wondering what behavior
> sleep should have. It checks for a command line flag with getopt(3) and
> exits with usage() if it finds one. However, it then checks for a '-' or
> '+' sign. If negative, it be
On (2002/11/12 22:17), Doug Barton wrote:
> In case another vote is needed, I've always been opposed to the wrapper.
> tobez and I put some work into getting the use.perl script in the port
> to DTRT shortly after the demise of base perl, and I'm still willing to
> help fine tune it if needed.
I
On (2002/11/12 08:55), Jason Vervlied wrote:
> I am having problems with a Samba share on my -current box, I just
> installed from 20021103-SNAP. I did recompile my kernel with the following
> options.
I'll bet your problem as nothing to do with Samba. What you have is a
problem with smbfs.
> H
On (2002/11/08 18:13), Daniel Eischen wrote:
> > The problem is that you cannot have 4.x packages and 5.x packages
> > co-mingled on the same system. that's what I'm trying to fix. You'd
> > have to rebuild the 4.x packages before they are fixed.
>
> I don't think this is a show-stopper. Just
On (2002/10/29 13:06), Matthew Dillon wrote:
> :Most of the speed difference is WITNESS, INVARIANTS, and other
> :debugging code that's turned on by default in the config files
> :for -current. You can turn most of it off. That said, -current
> :is slower than -stable in a number of places, so e
On (2002/10/23 11:31), Terry Lambert wrote:
> AHA!
>
> The reason an FFS write resulted in an SMBFS read is that
> you had mmap()'ed an SMBFS file, and then wrote a mapped
> but-not-in-core page to the target FFS file.
Well, a similar problem occurred with cat(1), which doesn't use mmap().
Howe
On (2002/10/23 18:00), Sheldon Hearn wrote:
> Confirmed with rev 1.9 of subr_mchain.c.
>
> However, I notice that this only happens with files of 8145 bytes size
> or larger.
>
> [server]
> # for i in `jot 512 7680`; do
> dd if=/dev/zero of=$i bs=$i cou
On (2002/10/23 18:21), Vitaly Markitantov wrote:
> > Umm, guys. The code was dereferencing NULL pointers in the mbchain
> > code which was fixed yesterday. Please test it out with the fixed
> > mbchains code.
>
> Yes, it not panics now, but again, when i copy to/from
> smbfs share i get:
>
>
On (2002/10/23 16:16), Nigel Weeks wrote:
> I recently heard a comparison between Linux and FreeBSD that I found
> amusing.
Use freebsd-chat next time, please.
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On (2002/10/22 10:48), John Baldwin wrote:
> > This is the one I'm seeing everytime while trying to copy file from
> > ro smbfs mount. -current is about four days old, smbfs.ko _is_
> > compiled with -DSMP and in sync with kernel.
>
> Can you compile smbfs into your kernel 'options SMBFS' instead
On (2002/10/18 19:38), Benno Rice wrote:
> I have just discovered the hard way that the kthread.9 manual page is
> slightly out of date.
>
> Having never done man page work before, I've attached a diff of the
> proposed change and if someone could give this a once-over and fix
> and/or commit it,
On (2002/10/15 11:48), Nate Lawson wrote:
> cd /usr/src/gnu/usr.bin/binutils; make cleandir; make depend; make all
> install
Isn't this a bad idea? First, you may not remove stale object files
from the src tree, and second, you may leave stale .depend files in the
src tree, which will cause you
On (2002/10/10 06:55), James Howard wrote:
> > If you want to maintain it, I'd be delighted! Are you a committer?
>
> I could use a new hobby, but I am not a committer.
Have you given up on your grep implementation? :-)
Quite a few folks were really looking forward to it.
Ciao,
Sheldon.
To U
On (2002/10/09 22:03), Terry Lambert wrote:
> The other problem with an mtree.obsolete is that it assumes
> the the upgrade process completes successfully. This doesn't
> mean that it completes without an error in the upgrade process,
> it means that the resulting system functions.
Why not just
On (2002/10/04 13:26), Poul-Henning Kamp wrote:
> What was the concensus on the xmlwf program, did we want it in
> the tree or not ? Would it be useful to anybody or is it just
> a hackers-proof-of-concept thing ?
I think it needs to stay out of the base system, so that 3rd party
applications a
On (2002/10/02 13:57), Marc Recht wrote:
> IMO 1. would be better with a complete expat. So the ports could use
> the system version and probably/maybe the drift between the official-
> and system-version will not be that big. And compared to Perl expat it
> rather small. So the bloat couldn't be
On (2002/10/02 16:27), Bruce Evans wrote:
> It is a devfs issue that devfs moves things into the kernel where they
> harder to control and more fatal if they are got wrong.
If it's just ownerships and permissions you're worried about, I think
the issue could be made moot by some /etc support for
On (2002/09/30 21:09), Poul-Henning Kamp wrote:
> Provided nothing terminal pops up in the next 5 days, GEOM will
> become default in -current on Saturday 5th of october.
>
> Please test it now on _your_ configuration and tell me if it
> fails to work.
There are problems in -CURRENT that have h
On (2002/09/02 12:44), Steve Kargl wrote:
> > : I've had to add ex, touch and gencat to the installworld target. And
> > : I've still not manged to complete a installworld.
> > :
> > : anybody else see this?
> >
>
> Strange, I just did a "make buildworld ... mergermaster"
> sequence and I did
On (2002/09/01 19:12), Marc Fonvieille wrote:
> I had "freeze at boot" problem with my laptop and -CURRENT:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=42262
>
> I found the solution: setting hw.pci.enable_io_modes to 0.
> So I have a question: that sysctl has to be =1 by default? I mean if
On (2002/08/28 20:32), Jens Schweikhardt wrote:
> # > Yes, use plain TERM=xterm. It's got color now as it should. I'm
> # > thinking of removing xterm-color if I can't resolve the
> # > enter_alt_charset_mode stuff. Let me know if TERM=xterm does not
> # > work as expected in mutt et al. I'll po
Hi Jens,
I just updated to the latest -current and my TERM=xterm-color applications
(mutt and centericq) are broken.
Mutt shows this when I start vi as my editor or run fetchmail:
"TERMCAP", line 0, terminal 'xterm-color': enter_alt_charset_mode but no acs_chars
My centericq window ends up usi
On 12 Aug 2002 12:40:20 +0400, "Vladimir B. " Grebenschikov wrote:
> There is patch to teach rcNG do not try dhcp on not-connected ethernet.
>
> simply put
> ifconfig_fxp0="dhcp-if-carrier"
> into rc.conf
>
> It will be interested to somebody
For what it's worth, I think this rocks.
> Theor
On (2002/07/28 09:49), Szilveszter Adam wrote:
> > is firewall support built into the -current kernel or does it need to be
> > compiled in?
>
> It is not in GENERIC, but you can always either compile it in, or load
> it from a module by editing /boot/loader.conf.
Beware!
AFAIK, the kernel-loa
On (2002/07/25 11:45), Martin Bundgaard wrote:
> I have a problem. When trying to do a 'make buildworld' on a (freshly
> fetched) -current source-tree, I quickly get an error:
Other people have pointed out the cause of the problem.
However, please note for future reference that what you're doin
On (2002/07/23 12:08), Yann Berthier wrote:
>Thanks a lot, patch applied, and all is going fine. Peter: I knew you
>would come up with a solution :)
>(well, feel free to call it bandaid, but it solves the problem BTW)
To quote Terry Lambert on what he calls Occam's Corollary:
On (2002/07/22 18:48), Szilveszter Adam wrote:
> I have a kernel and world from Saturday, it seems reasonably ok in
> console mode (does not panic although it is used as an ADSL router) but
> in X, it locks up very easily. I tried it with Mozilla on Sunday, it
> froze twice within as many hours,
On (2002/07/21 21:08), Eric Anholt wrote:
> You don't have XFree86-4 uninstalled, or don't have it uninstalled
> successfully. Just removing the XFree86-4 metaport doesn't remove the
> miniports that contain the actual files. If you are going to build
> without using portupgrade, you should sta
On (2002/07/17 01:52), Dima Dorfman wrote:
> The devfs(8) manual page is a pretty good reference of the existing
> features and semantics, but it lacks polish needed to be able to serve
> as an introduction.
Actually, I think it's brilliant.
The only nits are the weird sections, which made it h
On (2002/07/17 06:49), Rob Hughes wrote:
> > ===> sbin/newfs
> > /usr/home/des/tinderbox/sparc64/src/sbin/newfs/mkfs.c: In function `fsinit':
> > /usr/home/des/tinderbox/sparc64/src/sbin/newfs/mkfs.c:711: structure has no member
>named `di_createtime'
> > *** Error code 1
> >
> > Stop in /usr/h
On (2002/07/11 11:01), Benjamin Close wrote:
>I'm using current from just after the KSE & libc_r fix. However it
> appears that XFree86-client c++ stuff is still broken. Is there a
> planned time when this will be fixed or am I missing something else?
> (XFree-libraries compiled and instal
On (2002/07/10 19:15), Dirk Engling wrote:
> Maybe this would be more interesting to
> the mozilla guys but mozilla compiles on
> 2.95.3, so I think, the problem is related
> to gcc-3.1
As far as I know, ports/lang/gcc31 is still required to build mozilla.
Ciao,
Sheldon.
To Unsubscribe: send m
On (2002/07/08 13:52), Peter Wemm wrote:
> I have found some of them. And what is really scary is that I have
> verified that some of what Terry has been FUD'ing(*) about for our TLB
> (mis)management is actually correct. :-(
Ha! Justice!
All those who slapped me around on IRC for defending
On (2002/07/05 17:24), Sheldon Hearn wrote:
> You and Paul are both pretty "out there" if you think -current users
> will graciously accept a new world order in which ports linked
> dymanically against system libraries won't work between a system upgrade
> and the
On (2002/07/05 05:22), Terry Lambert wrote:
> > This would not fit in with the rest of the world target, which doesn't
> > clean out stale headers, stale libraries or stale binaries.
> > Special-casing certain things will surprise people.
>
> Headers and libraries arguably should be removed, so
On (2002/07/03 13:29), Garance A Drosihn wrote:
> With his patches I was able to compile and install imake. I was
> able to compile XFree86-4-libraries, but the 'make install' of it
> fails for me after getting most of the way through. I suspect
> this is a build problem, not a cc problem.
Yes
On (2002/07/02 14:13), Sid Carter wrote:
> Anything obvious I missed ?
Yes. You haven't been reading your mail. :-)
There's known instability at present, that is believed to relate to
changes made to libc_r in the last month, or to the recent KSE update
and its impact on libc_r.
Ciao,
Sheldon
On (2002/06/30 11:15), Szilveszter Adam wrote:
> Grrr, hit me baby one more time.
>
> One of the diffs included a completely gratuitous one-line change which
> I made yesterday night while I was tired and neglected to correct today.
>
> So, the patchset again. (Take three!)
I've tested your pa
On (2002/06/30 00:46), Jeremy Lea wrote:
> +#ifndef SharedDepCplusplusLibraryTarget
> +#define SharedDepCplusplusLibraryTarget [...]
This patch would fix the build. Did it also fix the linking problems
involving -lstdc++ for glxinfo, or were the patches that handle
${CXXLIB} still required?
Ci
On (2002/06/27 16:33), Sheldon Hearn wrote:
> I got this testing the RMEM_LIMIT patches, but it only crops up after
> about an hour of heavy ports building. You'll get this for just any
> binary that uses mmap().
>
> Unfortunately, I haven't had time to pro
On (2002/06/26 19:00), Dag-Erling Smorgrav wrote:
> Wed Jun 26 19:00:10 PDT 2002
> /usr/libexec/ld-elf.so.1: /usr/bin/cvs: Shared object has no run-time symbol table
I got this testing the RMEM_LIMIT patches, but it only crops up after
about an hour of heavy ports building. You'll get this for
On Wed, 26 Jun 2002 13:25:57 +0200, Sheldon Hearn wrote:
> I think I have a handle on this now. If you fix it before you hear back
> from me, let me know so I can stop wasting time on it. XF84-4 test
> builds are slow. :-)
Okay, it looks like a bit of a mess.
I've copied
On (2002/06/25 22:02), Szilveszter Adam wrote:
> > I've tried `make install' and `make CXX=/usr/local/bin/g++31 install',
> > where that g++31 comes from the lang/gcc31 port, and either way,
> > XFree86-4-clients fails with:
>
> There is another problem, however, and this is that the libGLU buil
On (2002/06/25 10:06), David O'Brien wrote:
> On Tue, Jun 25, 2002 at 09:21:57AM +0200, Sheldon Hearn wrote:
> > Could someone put me out of my misery and show me "the right way" to
> > build XFree86-4 on -current at the moment.
> >
> > I've trie
On (2002/06/25 10:20), Mark Murray wrote:
> How's this?
>
> int handle;
> template = "/tmp/mumble";
> char *cmd;
> handle = mkstemp(template); // template is modified
> asprintf(cmd, "prog > %s", template);
> system(cmd);
> close(handle); // bye-bye file
It would be failsafe if you test
Hi folks,
Could someone put me out of my misery and show me "the right way" to
build XFree86-4 on -current at the moment.
I've tried `make install' and `make CXX=/usr/local/bin/g++31 install',
where that g++31 comes from the lang/gcc31 port, and either way,
XFree86-4-clients fails with:
/usr/X1
Hi folks,
When was soundcard.h moved from machine to sys? A large number of ports
expect to find it in machine, and I can't find a __FreeBSD_version bump
supporting the change.
So I need to find out when it happened and piggy-back on the nearest
__FreeBSD_version bump. :-(
Ciao,
Sheldon.
To
On Tue, 11 Jun 2002 07:29:56 MST, Juli Mallett wrote:
> > I don't think you should worry too much about _not_ getting
> > reasonable output from POSIX-conformant utilities. :-)
>
> I'd read SUS's ps(1) escription a little closer. Very few guarantees
> with it.
My POSIX.2 (1993) suggests that
On Tue, 11 Jun 2002 06:46:13 MST, Juli Mallett wrote:
> > Piping commands through other commands seems icky?
>
> Relying on reasonable output from ps(1) seems icky when you can extract the
> data yourself and not have to worry about formatting getting in the way of
> processing data properly.
On Tue, 11 Jun 2002 05:15:17 MST, Juli Mallett wrote:
>
> As some of you may have noticed, I've done some poking of ps(1) lately, and
> this has brought attention of people who have ideas for things that they
> would like to see done to ps(1) :) The most notable request was for a
> feature I'v
On Thu, 06 Jun 2002 10:14:52 MST, "David O'Brien" wrote:
> > There are still issues with the C++ compiler in the base system that
> > make building X and some other C++ ports tricky.
>
> There is no issue with the C++ compiler. There is issue with the X
> source that uses depreciated features
On Wed, 05 Jun 2002 16:44:55 CST, Scott Long wrote:
> Ok, I finally feel the need to speak up here.
>
> DES,
>
> FREEFALL CVS IS NOT THE PLACE TO PUT EXPERIMENTAL CODE THAT BREAKS WORLD!
> PERIOD!
>
> Don't give me any crap about "It's -current, you should expect breakage."
> You are abusing
On Wed, 05 Jun 2002 15:36:04 +0200, Andrea Campi wrote:
> I've been seeing a compile error in gnu/lib/libstdc++ for days now. Since no
> one else reported it (not even tinderbox) I can only wonder what's up, and
> expecially how to get out of this.
Show the compile error.
Ciao,
Sheldon.
To U
On Wed, 05 Jun 2002 23:58:14 MST, Doug Barton wrote:
> I'm currently testing a buildworld prior to importing NetBSD's stat(1)
> into the tree. Once that's done, if you have suggestions for
> improvements I'm sure that they would be interested. I'll be happy to
> work with you on adding useful b
On 05 Jun 2002 08:46:59 GMT, Christopher Nehren wrote:
> I've been monitoring the -CURRENT mailing list for about a day or two,
> and haven't seen anything that's really broken (except for GCC 3.x,
> which I don't use anyway). So, is it "safe" to upgrade to -CURRENT yet?
> TIA for the info,
> C
On Wed, 05 Jun 2002 15:13:28 +0200, Poul-Henning Kamp wrote:
> I have uploaded an updated version of the UFS2 patch:
>
> http://phk.freebsd.dk/patch/ufs2.patch
>
> Please test this!
Is this something we can drop in and expect to work / panic / corrupt
our filesystems without any change
On 05 Jun 2002 15:01:24 +0200, Dag-Erling Smorgrav wrote:
> > Looks like this is going to be necessary after each
> > buildworld, then. :-/
>
> No. Mergemaster should not use Perl, and the fact that it does is a
> bug.
That's probably an overstatement. Perl used to be in the base
system, a
On Wed, 29 May 2002 09:27:50 MST, "Dan Trainor" wrote:
> Being that -CURRENT's C++ compiler is b0rked, how long will it be until
> it's problems have been resolved? I've seen many problems with it
> lately, and it kinda made me worried, almost to the point where I
> thought a re-install from t
On Sun, 26 May 2002 15:28:44 MST, Lamont Granquist wrote:
> I got non-deterministic internal compiler errors when I was trying to
> compile mozilla. At the same time I was compiling gnome in another
> terminal window. It only happened with mozilla, it was non-deterministic
> in that I could d
1 - 100 of 596 matches
Mail list logo
