On Jun 21, 2015, at 1:05 PM, Garrett Cooper wrote:
> On Jun 21, 2015, at 3:16, Trond Endrestøl
> wrote:
>> Am I the only one who fails to build recent base/head (r284673) on
>> pretty recent base/head (r284639)? This is on amd64 with ZFS and BEs.
>
> ...
>
>> CC=clang
>> CXX=clang++
>> CPP=cla
On Jan 23, 2013, at 12:14 AM, Alie Tan wrote:
> Seems this check-in causing compilation error:
>
> http://freshbsd.org/commit/freebsd/r245828
>
> -nonliteral -c /usr/src/usr.sbin/pkg_install/lib/pkgng.c -o pkgng.o
> /usr/src/usr.sbin/pkg_install/lib/pkgng.c:53:45: error: expected ')'
>rc
On Jan 21, 2013, at 10:13 PM, AN 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
> ***
On Aug 2, 2012, at 3:32 PM, Steve Kargl wrote:
> Libc built today.
> Start X with fvwm window manager.
> Open xterm and su to root.
>
> 1. Use nedit to edit a file and close.
>
> fvwm drops core. If fvwm does not drop core repeat 1 until
> she does.
>
> (gdb) bt
> #0 0x4841e294 in __jemalloc_
On Jun 13, 2012, at 8:31 AM, John Baldwin wrote:
> I tracked down a weird bug at work on the older jemalloc in FreeBSD 8/9 that
> a
> co-worker tripped over. Specifically, if you build the program below and
> link
> it with gold, the program will have an _end symbol that is on an odd address
On May 21, 2012, at 8:57 AM, Hartmut Brandt wrote:
> it seems that there is a syntax error in malloc_np.h. It contains lines like:
>
> int allocm(void **ptr, size_t *rsize, size_t size, int flags)
>__attribute__(nonnull(1));
>
> The problem is that the syntax of the attributes actually requ
On May 9, 2012, at 12:01 AM, Stefan Farfeleder wrote:
> On Tue, May 08, 2012 at 03:59:42PM -0700, Jason Evans wrote:
>> On May 8, 2012, at 2:58 PM, Stefan Farfeleder wrote:
>>> On Tue, May 08, 2012 at 02:47:59PM -0700, Jason Evans wrote:
>>>> On May 8, 2012, at 2:
On May 8, 2012, at 2:58 PM, Stefan Farfeleder wrote:
> On Tue, May 08, 2012 at 02:47:59PM -0700, Jason Evans wrote:
>> On May 8, 2012, at 2:37 PM, Stefan Farfeleder wrote:
>>> On Tue, May 08, 2012 at 12:48:17PM -0400, Steve Wills wrote:
>>>> On 05/08/12 00:46, Jason
On May 8, 2012, at 2:37 PM, Stefan Farfeleder wrote:
> On Tue, May 08, 2012 at 12:48:17PM -0400, Steve Wills wrote:
>> On 05/08/12 00:46, Jason Evans wrote:
>>>
>>> How recent is your system? This problem should have been fixed by
>>> r234569, so if you
On May 7, 2012, at 12:19 PM, Steve Wills wrote:
>> On Apr 21, 2012, at 11:54 AM, David Wolfskill wrote:
>>> After applying Dimitry Andric's patches to contrib/jemalloc and
>>> replacing
>>> /usr/bin/as with one built last Sunday, I was finally(!) able to rebuild
>>> head as of 234536:
>>>
>>> Free
lable if needed, and if necessary I
> can go back to those revision and recompile world+kernel to see its behavior.
>
> Any help from freebsd-current@ (perhaps Jason Evans can help us) will be
> appreciated. Any additional info, like source revisions, can be provided. I
> wo
On Apr 28, 2012, at 5:09 AM, Aleksandr Rybalko wrote:
>>> On Apr 21, 2012, at 11:54 AM, David Wolfskill wrote:
But contrib/jemalloc/src/arena.c contains a function,
arena_chunk_validate_zeroed():
175 static inline void
176 arena_chunk_validate_zeroed(arena_chunk_
On Apr 25, 2012, at 9:39 AM, Ruslan Ermilov wrote:
> So you removed _malloc_options that was part of the documented
> programming API, while some software made use of it.
>
> While removing part of the documented API was definitely a bad
> idea, you didn't provide any mean to detect this change
>
On Apr 21, 2012, at 11:54 AM, David Wolfskill wrote:
> After applying Dimitry Andric's patches to contrib/jemalloc and replacing
> /usr/bin/as with one built last Sunday, I was finally(!) able to rebuild
> head as of 234536:
>
> FreeBSD freebeast.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #7
On Apr 20, 2012, at 1:14 PM, Jason Evans wrote:
> On Apr 20, 2012, at 1:10 PM, Dimitry Andric wrote:
>> On 2012-04-20 21:54, Jason Evans wrote:
>>> On Apr 20, 2012, at 12:49 PM, Dimitry Andric wrote:
>>>> I think the best solution would be for jemalloc to avoid
On Apr 20, 2012, at 1:10 PM, Dimitry Andric wrote:
> On 2012-04-20 21:54, Jason Evans wrote:
>> On Apr 20, 2012, at 12:49 PM, Dimitry Andric wrote:
> ...
>>> I think the best solution would be for jemalloc to avoid using obvious
>>> names like "chunksize" fo
On Apr 20, 2012, at 12:49 PM, Dimitry Andric wrote:
> On 2012-04-20 15:55, Michael Pounov wrote:
>> On Fri, 20 Apr 2012 05:57:18 -0700
>> David Wolfskill wrote:
> ...
>>> The update after 234416 was to 234454; the attempted buildworld failed:
> ...
>>> /usr/bin/as: out of memory allocating 4194304
On Apr 17, 2012, at 2:06 PM, AN wrote:
> # uname -a
> : Conf string ends with key
> FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #10 r234389: Tue Apr 17
> 16:05:11 EDT 2012 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64
>
> […]
>
> and from UPDATING i did:
> ln -s aj /etc/malloc.conf
>
On Apr 17, 2012, at 12:10 PM, John Nielsen wrote:
> On Apr 17, 2012, at 8:58 AM, O. Hartmann wrote:
>> On 04/17/12 14:51, Ivan Klymenko wrote:
>>> В Tue, 17 Apr 2012 10:42:13 +0200
>>> "O. Hartmann" пишет:
>>>
>>> remove /etc/malloc.conf
>>
>> simple and efficient ;-)
>
> I encountered this tod
As a result of the recent jemalloc update, the format for /etc/malloc.conf has
changed. If your system has an old-style /etc/malloc.conf, you will want to
delete it prior to installworld, and optionally re-create it using the new
format after rebooting. See malloc.conf(5) for details (specific
On Apr 17, 2012, at 4:26 AM, FreeBSD Tinderbox wrote:
> /obj/powerpc.powerpc/src/tmp/usr/lib/libc.so: undefined reference to
> `__sync_sub_and_fetch_8'
> /obj/powerpc.powerpc/src/tmp/usr/lib/libc.so: undefined reference to
> `__sync_add_and_fetch_8'
This (and the similar error for powerpc64, arm
On Apr 13, 2012, at 3:43 PM, David O'Brien wrote:
> On Thu, Apr 12, 2012 at 01:19:56PM -0700, Jason Evans wrote:
>> On Apr 12, 2012, at 11:41 AM, David O'Brien wrote:
> It looks like you could run './FREEBSD-upgrade extract' from a check out
> of ssh://s
On Apr 12, 2012, at 11:41 AM, David O'Brien wrote:
> On Wed, Apr 04, 2012 at 09:56:45PM -0700, Jason Evans wrote:
>> I have the current version of jemalloc integrated into libc as
>> contrib/jemalloc:
>> http://people.freebsd.org/~jasone/patches/jemalloc_20120404b
On Apr 5, 2012, at 6:33 AM, John Baldwin wrote:
> On Thursday, April 05, 2012 12:56:45 am Jason Evans wrote:
>>
>> * Will the utrace feature be missed? I removed it some time ago, mainly
>> because traces are impossibly large for most real-world use cases.
>
> I will
On Apr 5, 2012, at 10:52 AM, Konstantin Belousov wrote:
> On Wed, Apr 04, 2012 at 09:56:45PM -0700, Jason Evans wrote:
>> I have the current version of jemalloc integrated into libc as
>> contrib/jemalloc:
>>
>> http://people.freebsd.org/~jasone/patches/jemalloc_
I have the current version of jemalloc integrated into libc as contrib/jemalloc:
http://people.freebsd.org/~jasone/patches/jemalloc_20120404b.patch
This is the first update to FreeBSD's jemalloc in over two years, and the
differences are huge (faster, better introspection, hopefully fewe
On 06/17/2011 02:35 PM, Marius Strobl wrote:
On Fri, Jun 17, 2011 at 03:31:29PM -0400, Nathaniel W Filardo wrote:
On Fri, Jun 17, 2011 at 08:07:13PM +0200, Marius Strobl wrote:
Using bonnie++ I can't reproduce this (didn't try mysql) but I have
I seem to have good luck reproducing it with "-r
Mark Atkinson wrote:
I updated my kernel/world yesterday and thunderbird 3.0.2 started core
dumping after I completed the upgrade. It continued to do so on
previously good operations after a full re-compile.
I noticed that some jemalloc changes went in and was wondering if anyone
else was noti
On Wed, Jan 30, 2002 at 11:14:48PM +0100, Gérard Roudier wrote:
>
> Linux can be fixed, but the useless writes of the existing Athlons from
> the very fast cache to the relatively very slow memory cannot. And all
> Athlon users may well pay this penalty under any OS... unless we want to
> disabl
On Wed, Jan 16, 2002 at 05:04:31PM +1100, Bruce Evans wrote:
> On Tue, 15 Jan 2002, David Wolfskill wrote:
>
> > >Date: Tue, 15 Jan 2002 16:46:17 -0800 (PST)
> > >From: John Baldwin <[EMAIL PROTECTED]>
> > >Two questions:
> >
> > >1) Do you have WITNESS on in your kernel config?
> >
> > Yes, in b
On Sun, Aug 12, 2001 at 02:35:22PM -0700, John Polstra wrote:
>
> Maybe they swapped the labels on the chips too. :-)
Well, it apparently doesn't fry anything to have the chips reversed, so
maybe I should try swapping them just to make sure. =)
Jason
To Unsubscribe: send mail to [EMAIL PROTECT
On Sat, Aug 11, 2001 at 01:04:07PM -0700, John Polstra wrote:
>
> I have no argument about the keyboard probes. I just want to add
> that in the case of the Belkin OmniView, it should be noted that
> Belkin shipped a bunch of them with a couple of EPROM chips swapped
> accidentally. There's a p
On Tue, Jul 10, 2001 at 11:16:32PM +0200, Tomasz Paszkowski wrote:
> On Mon, Jul 09, 2001 at 05:55:56PM -0400, [EMAIL PROTECTED] wrote:
> > Well, it started out discussing the next release of nvi and promptly
> > concluded, that it would require upgrading dbm. So, now the issue is --
> > whic
On Thu, Jun 07, 2001 at 09:33:22PM +1000, Idea Receiver wrote:
>
> I dont know if this is cause by -current, I have not yet try on the
> -stable. However, I just write here, maybe someone can help me.. :P
>
> recently, I wrote a multithread network server for my work. what it does
> is to accept
I had exactly the same thing happen to /var on an SMP test box using
-current as of 16 May. It happened once out of about a half dozen panics.
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, Feb 01, 2001 at 02:08:54PM -0500, Mike Heffner wrote:
>
> Is this a problem with the thread scheduler or is this somehow related to the
> application?
>
> (gdb) bt
> #0 0x284d74cc in poll () from /usr/lib/libc.so.5
> #1 0x2848ce74 in thread_kern_poll (wait_reqd=1)
> at /usr/src/lib
On Tue, Jan 30, 2001 at 01:18:05PM -0800, Julian Elischer wrote:
> Jason Evans wrote:
> >
> > Mutexes should be used in places where simplelocks were used. With few
> > exceptions, sleep mutexes should be used (even though simplelocks were spin
> > locks). Se
On Tue, Jan 30, 2001 at 01:56:26PM +0200, John Hay wrote:
> Booting with a kernel built from today's source (with devfs also in),
> I see this lock order reversal message:
>
> ###
> Routing daemons:.
> Doing IPv6 network setup:add net :::0.0.0.0: gateway ::1
>
On Wed, Jan 31, 2001 at 04:54:30AM +1000, Andrew Kenneth Milton wrote:
> However, recently simple_lock and friends seem to have disappeared, and the
> kernel modules make some use of them (although there is still reference
> to it in machine/smptests.h)
>
> It looked like I could replace them wit
On Sat, Jan 27, 2001 at 03:19:04PM -0600, Jonathan Lemon wrote:
> Actually, the new check appears to be incorrect, as seen by the code
> fragments below:
Whoops. I obviously looked at the wrong #define when making the change.
Thanks for pointing out the mistake.
Jason
To Unsubscribe: send mai
On Sat, Jan 27, 2001 at 12:48:36PM -0800, Matthew Jacob wrote:
> Somewhere in between, Jason Evans wrote:
> > On Sat, Jan 27, 2001 at 12:36:41PM -0800, Matthew Jacob wrote:
> > >
> > > Oh, I suppose, I did find that... well, mainly I wanted the person who made
&
On Sat, Jan 27, 2001 at 12:36:41PM -0800, Matthew Jacob wrote:
>
> Oh, I suppose, I did find that... well, mainly I wanted the person who made
> the change to actually broadcast to NIC maintainers what the expectations
> were...
The code that prints these warnings out has existed for a while. H
On Sat, Jan 27, 2001 at 12:33:23AM -0800, Root Dude wrote:
>
> Here's a first step.
This is very disappointing, Julian. You've duplicated work that I've
already done, and if you've been paying attention at all, you know that it
was already done. Even if you haven't been paying attention, I fin
On Wed, Jan 24, 2001 at 09:21:06PM +0100, Poul-Henning Kamp wrote:
>
> cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
>-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
>-nostdinc -I- -I. -I../.. -I../../dev -I../../../include
>-I../
On Wed, Jan 24, 2001 at 03:37:24PM +0200, Maxim Sobolev wrote:
> "Daniel M. Eischen" wrote:
>
> > For porters, the __FreeBSD_version has been bumped to 500016 to
> > reflect the above change.
>
> Could you please bump version number of libc/libc_r shared libraries, so the
> programs linked with o
On Mon, Jan 22, 2001 at 12:16:38PM -0800, Mike Smith wrote:
> In the meantime, perhaps we could
> ask that one of the SMPng rules of engagement mandate that no mutex
> structures or structure members should ever be exported as part of a
> userspace interface?
This sounds fine in principle, but
On Sun, Jan 21, 2001 at 01:06:15PM -0500, Bosko Milekic wrote:
>
> > http://people.freebsd.org/~jasone/diffs/mutex_f_3.diff
>
> This looks like a variation of Peter's mutex.diff which moves a bunch of
> macros to kern/kern_mutex.c from sys/mutex.h - so is it final now that we
> will move the
Peter Wemm noticed that WITNESS currently causes a kernel trap the alpha.
The bug also exists on x86, but does not necessarily cause any problems.
If you run into problems (probably during boot), there is a patch available
that should fix the WITNESS problem:
http://people.freebsd.org/~jasone/dif
On Wed, Jan 17, 2001 at 07:42:26PM +0100, Soren Schmidt wrote:
> > Basically if you're expecting me or the SMP team to figure out
> > what's going on without more info, you're pretty much out of luck.
>
> See above, not really possible, we have been trying to find some
> (affordable) HW that coul
On Thu, Dec 28, 2000 at 06:12:32PM -0800, Alfred Perlstein wrote:
> * Jason Evans <[EMAIL PROTECTED]> [001228 11:48] wrote:
> > A while back I was porting an sshd implementation that was developed on
> > NetBSD to FreeBSD, and discovered that some definitions are missing in
A while back I was porting an sshd implementation that was developed on
NetBSD to FreeBSD, and discovered that some definitions are missing in our
termios.h. I looked at the SUSv2 standard, and it appears to me that this
is a bug in FreeBSD. Can someone who is more knowledgeable in this area
ple
On Mon, Dec 18, 2000 at 12:01:19PM -0600, Peter Schultz wrote:
> Hi,
>
> I'm seeing a crash related to libc_r.
> Could someone please instruct me as
> to how to build a debug version.
cd /usr/src/lib/libc_r
make clean
DEBUG_FLAGS=-g3 make
make install
Jason
To Unsubscribe: send mail to [EMAIL
On Thu, Oct 12, 2000 at 12:41:29PM +0900, Jun Kuriyama wrote:
> At 11 Oct 2000 18:43:14 GMT,
> John Baldwin <[EMAIL PROTECTED]> wrote:
> > I don't know. Can you try to narrow down the date by cvsupping or
> > cvs updating with date tags to see when it started slowing down?
>
> I've checked with
On Fri, Sep 15, 2000 at 03:40:12PM +0100, Konstantin Chuguev wrote:
> Udo Schweigert wrote:
>
> > after a fresh build of -current openssh does not work if connecting to the
> > root-user. For example (tested from a -stable machine, but the same from
> > 4.1-RELEASE):
>
> Yes, I've been seeing th
On Thu, Sep 07, 2000 at 03:31:06PM -0400, Wesley Morgan wrote:
> On Wed, 6 Sep 2000, Jason Evans wrote:
>
> > A static tag, named PRE_SMPNG, was created at 18:00 PDT. The SMP patches
> > have now been committed.
>
> Is it safe to follow src-sys from PRE_SMPNG and every
A static tag, named PRE_SMPNG, was created at 18:00 PDT. The SMP patches
have now been committed.
There are a number of known issues, and we are actively tracking them on
the SMP web page at:
http://people.freebsd.org/~jasone/smp/
If you run into issues that appear related to the SMP changes,
[-smp dropped from cc list.]
On Tue, Sep 05, 2000 at 09:57:05PM -0700, Matthew Jacob wrote:
> Jason- I think we'd all appreciate a UTC timestamp suitable for -D that we
> can all use to checkout stuff prior to the big change.
I initially wrote:
> Also in compliance with the SMP project announcem
On Tue, Sep 05, 2000 at 06:37:38PM -0700, David O'Brien wrote:
> What is the status of the Alpha bits? Will we have a working kernel
> after the commit, or should we site tight for a week while the Alpha bits
> are tweaked into working status?
It should work (compile and run), though interrupt t
) before sending email to the lists. For
more extensive information about the SMP project, see the project web page
at:
http://people.freebsd.org/~jasone/smp/
Let the fun begin!
Jason Evans
SMP Project Manager
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current&qu
On Sun, Aug 20, 2000 at 12:14:05PM +, Nik Clayton wrote:
> On Mon, Jun 19, 2000 at 11:53:30AM -0700, Jason Evans wrote:
> > Summary: -current will be destabilized for an extended period (on the order
> > of months). A tag (not a branch) will be laid down before the initial
&
On Tue, Jun 20, 2000 at 09:41:57AM +0200, Poul-Henning Kamp wrote:
>
> Am I the only person who miss a brief document which tells what
> the outcome of the meeting was ?
I'm at USENIX right now, so I'm a bit strapped for time to work on this.
Still, I plan to email a brief summary of the meeting
On Mon, Jun 19, 2000 at 05:34:47PM -0700, Matthew Dillon wrote:
> Ok, I have put up a web page that will track my efforts.
>
> http://apollo.backplane.com/FreeBSDSmp/
On this page, you say:
The algorithms described on this page are essentially the BSDI algorithms
plus accomodation
Summary: -current will be destabilized for an extended period (on the order
of months). A tag (not a branch) will be laid down before the initial
checkin, and non-developers should either stick closely to that tag until
the kernel stabilizes, or expect large doses of pain. This tag will be
laid
On Wed, Mar 15, 2000 at 11:51:52AM +0300, Zherdev Anatoly wrote:
> Hello.
>
> I have some problem with MySQL & 4.0
>
> If MySQL compile -static on last snapshots (I tried snapshots 2214
> & 2313), mysqld don't work correctly.
> After starting mysqld listen port and don't print errors, bu
On Mon, Mar 13, 2000 at 06:12:22PM +1100, John Birrell wrote:
> I deleted the weak definitions in the _THREAD_SAFE PRSYSCALL in
> lib/libc/i386/SYS.h and the problem goes away. I don't understand why
> Jason needed to add them in the first place.
I didn't need to add them. At some point during a
On Wed, Mar 01, 2000 at 09:30:43AM -0500, Daniel M. Eischen wrote:
> I haven't run any other regression tests. I'll do that when I get
> some more time. Jason, can you also take a look at these changes and
> run some tests on them?
I just moved a couple of days ago and all my test boxes are sti
On Fri, Feb 18, 2000 at 11:05:31AM -0800, Matthew Dillon wrote:
> I also think that a single guard page at the base of the
> stack may be insufficient for some applications. I'm
> considering adding yet another field to vm_map_entry
> 'vm_pindex_t guard_pages' which allows the nu
On Thu, Feb 17, 2000 at 11:29:57AM -0500, Daniel Eischen wrote:
>
> How about we remove the #if defined()s for:
>
> _POSIX_THREAD_PROCESS_SHARED
> _POSIX_THREAD_PRIO_PROTECT
> _POSIX_THREAD_PRIO_INHERIT
> _POSIX_THREAD_PRIORITY_SCHEDULING
>
> from our ?
Yes, it looks like use of the la
On Wed, Feb 16, 2000 at 03:33:58PM -0800, Matthew Dillon wrote:
> Is anyone interested in me doing this for the 4.0 release? It would
> help both our current threads model and the linux threads model a lot.
> I can do it in a day and it should be trivial to test, the modifications
>
On Wed, Feb 16, 2000 at 02:13:39PM -0800, Jason Evans wrote:
> On Wed, Feb 16, 2000 at 01:18:13PM -0800, Matthew Dillon wrote:
> > This deals with a mmap+fork bomb that can cause the kernel to
> > eat all of KVM in vm_map_entry structures. The default limit
> &
On Wed, Feb 16, 2000 at 01:18:13PM -0800, Matthew Dillon wrote:
> This deals with a mmap+fork bomb that can cause the kernel to
> eat all of KVM in vm_map_entry structures. The default limit
> should be set generously enough for people using the current
> FreeBSD threads incarnat
On Fri, Jan 28, 2000 at 12:05:21AM -0800, Kris Kennaway wrote:
>
>/home/kris/tmp/world/obj/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/alpha/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/gnu/usr.bin/cc/cpp/../cc_int/libcc_int.a(choose-temp.o):
> In function `choose_temp_base':
> choose-
On Thu, Jan 27, 2000 at 06:09:17PM -0800, Jordan K. Hubbard wrote:
> ===> libexec/getNAME
> cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/libexec/getNAME/ge
> tNAME.c
> cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -o getNAME getNAME.o
> gzip -cn /usr/src/libexec/getNAME/getNA
On Fri, Jan 21, 2000 at 03:47:27PM -0800, David O'Brien wrote:
> On Fri, Jan 21, 2000 at 02:22:51PM -0800, Jason Evans wrote:
> >
> > I did a 'make includes' during my testing, so I didn't have this
> > problem.
> ...
> >
> > In any case,
On Fri, Jan 21, 2000 at 10:11:57AM -0800, Bill Swingle wrote:
> I updated my source tree around 10pm PST last night (01/20) and made
> world only to find it broken this morning. I reupdated my tree just now
> and it doesnt look like any files that might fix this have been touched.
> Anyone else se
On Wed, Jan 19, 2000 at 12:21:50PM -0500, Daniel Eischen wrote:
> > No, I was just busy doing other things.
> >
> > There is potentially one good reason to leave these changes in place for
> > now: they allow proper thread cancellation in libc_r as it stands right
> > now. This seems to me like
On Wed, Jan 19, 2000 at 01:36:43AM -0800, David O'Brien wrote:
> On Thu, Jan 13, 2000 at 06:53:25AM -0500, Daniel Eischen wrote:
> > On Wed, 12 Jan 2000, David O'Brien wrote:
> > > I don't see why a plain function like mkstemp() should be written so
> > > specially. Couldn't all the hiding/changi
On Thu, Jan 13, 2000 at 08:35:16PM +0100, Wilko Bulte wrote:
> I resurrected things by grabbing an 'old' .4 library from another Alpha.
> Now things work again.
In case you missed it, I checked in a probable fix for the bug that got you
last time around. You might try again now.
Jason
To Unsu
The buildworld problem that I introduced is due to cc_fbsd directly
compiling and linking in src/lib/libc/stdio/mktemp.c. This is in my
opinion a questionable practice, since it adds dependencies to the
internals of the libc code, which has just been proven to bite. =)
Aesthetics aside, I'm not
On Thu, Jan 13, 2000 at 12:16:31AM +0100, Wilko Bulte wrote:
> On Wed, Jan 12, 2000 at 01:22:25PM -0800, Jason Evans wrote:
> > On Wed, Jan 12, 2000 at 10:07:25PM +0100, Wilko Bulte wrote:
> > > On Wed, Jan 12, 2000 at 09:56:22PM +0200, Mark Murray wrote:
> > > > H
On Thu, Jan 13, 2000 at 12:16:31AM +0100, Wilko Bulte wrote:
> On Wed, Jan 12, 2000 at 01:22:25PM -0800, Jason Evans wrote:
> > On Wed, Jan 12, 2000 at 10:07:25PM +0100, Wilko Bulte wrote:
> > > On Wed, Jan 12, 2000 at 09:56:22PM +0200, Mark Murray wrote:
> > > > H
On Wed, Jan 12, 2000 at 10:07:25PM +0100, Wilko Bulte wrote:
> On Wed, Jan 12, 2000 at 09:56:22PM +0200, Mark Murray wrote:
> > Hi
> >
> > Anyone else seeing this?
> >
> > cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H
>-DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-
On Wed, Jan 12, 2000 at 11:16:38AM -0800, Jason Evans wrote:
> On Wed, Jan 12, 2000 at 02:57:41PM +0100, Pascal Hofstee wrote:
> > With my CURRENT-tre updated within an hour ago ... Buildworld is broken.
> >
> > cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H
> &g
On Wed, Jan 12, 2000 at 09:56:22PM +0200, Mark Murray wrote:
> Hi
>
> Anyone else seeing this?
>
> cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H
>-DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\"
>-DPREFIX=\"/usr/obj/usr/src/i386/usr\"
>-I/usr/obj/u
On Wed, Jan 12, 2000 at 02:57:41PM +0100, Pascal Hofstee wrote:
> With my CURRENT-tre updated within an hour ago ... Buildworld is broken.
>
> cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H
> -DDEFAULT_TARGET_VERSION=\ "2.95.2\"
> -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\"
> -DPREFI
On Fri, Jan 07, 2000 at 07:36:11PM -0500, Luoqi Chen wrote:
> > In an effort to chase down a libc_r bug, I compiled libc_r with CFLAGS=-g
> > (and later CFLAGS=-g3), but ran into linker problems as a result.
> >
> > blitz:~> gcc poll.c -pthread
> > /usr/lib/libc_r.so: undefined reference to `__si
In an effort to chase down a libc_r bug, I compiled libc_r with CFLAGS=-g
(and later CFLAGS=-g3), but ran into linker problems as a result.
blitz:~> gcc poll.c -pthread
/usr/lib/libc_r.so: undefined reference to `__sigisempty'
Even the simplest of C programs will get this linker error if using t
On Tue, Dec 28, 1999 at 05:34:34PM -0500, Daniel Eischen wrote:
> On Tue, 28 Dec 1999, Soren Schmidt wrote:
> > It seems Kenneth Wayne Culver wrote:
> > > I can't get the nist port to compile:
> > > c++ -g -O2 -Wall -DDO_NIST -DPACKAGE=\"ac3dec\" -DVERSION=\"0.5.5\"
> > > -I../../inc -c bitstrea
On Sat, Nov 27, 1999 at 11:40:08AM -0800, Alfred Perlstein wrote:
> On Sat, 27 Nov 1999, Mark Murray wrote:
>
> > Hi
> >
> > "make world" is broken in libc_r. Simple fix is to replace all
> > "socklen_t" with "int".
>
> libc_r likes to pull data from /usr/include instead of the
> source tree,
ying on the -pthread linker
magic. This is high on Daniel Eischen's wish list, so maybe he already
has something in the works. =)
If you know of other outstanding issues that have a prayer of being
addressed before 4.0 ships, please speak up.
Jason
Jason Evans <[EMAIL PROTECTED]>
h
I need a clue about process memory layout, and am hoping someone can
provide it. I wrote a program to discover what address ranges mmap() can
handle (trying to hack growable stacks into libc_r), and came up with the
following output (annotations in `[]'):
FreeBSD donner 4.0-CURRENT FreeBSD
91 matches
Mail list logo
