ching configure files
> to use ${PTHREAD_LIBS} instead of -pthread, and pushing PTHREAD_LIBS
> into the ports' CONFIGURE_ENV.
I don't think that CONFIGURE_ENV should be modified in each port's makefile
to cope with PTHREAD_LIBS. It's supposed to be a ports-wid
ted
> third-party app with a library other than libpthread (libkse).
I think you are probably right. We need to remember that third party apps
fit best in ports if they work out of the box without patches and twiddles.
We probably should only rely on P
On Wed, Sep 24, 2003 at 01:49:50AM -0400, Daniel Eischen wrote:
> It would be nice to be able to support all our thread
> libraries, but I grow weary.
I grow weary yesterday.
--
John Birrell
___
[EMAIL PROTECTED] mailing list
http://lists.freeb
t
library, but most ports won't see that.
--
John Birrell
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ke things confusing, but having
more than one thread library is more confusing than a change to -pthread.
--
John Birrell
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
(e.g. -lc_r or -lpthread).
--
John Birrell
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
on. Then he's happy for it to become a noop.
I susect theat this puts much of the work on a few people rather than many.
I hope it doesn't require a volley of emails to each port maintainer to
resolve each one. People have jumped off buildings for less than that!
On Sat, Sep 20, 2003 at 07:24:07PM -0700, Kris Kennaway wrote:
> 3) You, John Birrell, and whoever else is interested in fixing these
> ports can work on them at your own pace without disrupting life for
> the rest of the users. Once they're all fixed, we can turn the error
> bac
t is a point
*NINE* release after all.
Unfreeze the ports tree then! I'm not a ports committer, but I'm willing
to help out fixing the problems on -current if that would help. Lets
go forward, not back.
--
John Birrell
___
[EMAIL PROTECTED] ma
have been allowed), the ports tree should
be unlocked. The fixes are simple. Make them and move on.
--
John Birrell
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
is what?
I assume it's not a bios setup problem since RELENG_4 works fine. The kernels
are net booted (using etherboot) over the very device that -current hangs
on. Weird.
Any hints on what is going on?
--
John Birrell
___
[EMAIL
It seems what I really should be using is:
makeoptions KERNEL_KO=foo
That gives me what I need.
--
John Birrell
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ernel
KERNEL_KO?= ${KERNEL}
KODIR?= /boot/${KERNEL}
Comments?
--
John Birrell
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
OT_COMCONSOLE_SPEED=38400, and then the kernel with CONSPEED=38400 to
get all the ducks in a row.
But it would be even nicer if both boot2 and the kernel would just work with
whatever baud rate the bios set.
--
John Birrell
___
[EMAIL PROTECTED
. Once I set the port range in /etc/pccard.conf to
override the default, the CompactFlash card worked fine.
--
John Birrell
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
urrent machine up and running I'd like to sort out
the uprade issues while I'm still prepared to trash the install.
Peter's grim reaper email is a regular reminder. I think I'm up to number 11. Hehehehe.
--
John Birrell
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
; case checked
first and an message printed accordingly before making the core dump as a
last resort (in favour of shooting the whole foot off - one toe is better
than the whole foot!).
--
John Birrell
___
[EMAIL PROTECTED] mailing list
http://lists.free
el
manually before doing the installworld. Then things will go according to plan.
If you don't do that, you'll get a core dump from sh when the installcheck is
performed by src/Makefile.inc1 and you won't be sure what has gone wrong
if you didn't notice that the new kernel you supposedly
you need. Then reboot. If it doesn't work, netboot again and
have another go.
--
John Birrell
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Sun, Mar 12, 2000 at 11:07:40PM -0800, David O'Brien wrote:
> On Mon, Mar 13, 2000 at 02:52:02PM +1100, John Birrell wrote:
> > Is it just me, or are the weak symbols in libc_r confusing the linker?
>
> Not just you. Jason and Mike Smith brought this to my attention o
ven the requirement
> for the non-weak symbol to always appear between the reference and
> the weak symbol.
I agree. Thanks for helping out.
--
John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/
[EMAIL PROTECTED] [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
24 :jb 0x8048214
0x8048226 : ret
0x8048227 : nop
End of assembler dump.
... then libc_r is broken.
TIA.
--
John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/
[EMAIL PROTECTED] [EMAIL PROTECTED]
To Unsubscribe: send ma
call the _read() syscall will call the user's read() function
instead. That's broken. We really need to change libc in the way that
NetBSD did with their namespace.h stuff. This ensures that the internals
of libc call the hidden names, not the weakly exported ones.
--
John Birrell - [EMAIL PROT
o resolve weak symbols would have been better. It's
too late for that now, though, since you can change the semantics on the
shared loader.
--
John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL P
ve
got lost in the version upgrades.
>
> Don't ya just love people who say "we" need to do stuff? :-)
"Don't ya just love tools people who say "we" need to do stuff to tools?"
8-)
--
John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cim
8-)
I can't comment about the relative performance, because I have
nothing to compare it against. It works fine for me.
--
John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with &quo
rks,
RTEMS, WinNT, NetBSD, Linux, SunOS, ...
I'm still trying to find a simple way to build gcc/egcs for each based
on the way you build FreeBSD's host compiler.
--
John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourn
. I'd like to remove the search paths altogether,
leaving the gcc LIB_SPEC and LD_LIBRARY_PATH environment variable to get
the /right/ path all the time.
Any objections?
--
John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourn
pective of vn, since
that is what is biting me 8-).
--
John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
like it does for the one you open.
--
John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
-Brw /dev/rvn0 blah' causes
the machine to panic. I've patched vnstrategy() to fail gracefully
if bp->b_dev->s_drv1 is NULL, but I'm still looking for the place
where the dev1 entry is supposed to be initialised.
--
John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cim
in _thread_fd_lock_debug () from /usr/lib/libc_r.so.4
You are linking against both libc _and_ libc_r. "Don't do that!"
--
John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
e is people actually
doing the work. To get in-principle approval before doing a substantial
amount of work, ask [EMAIL PROTECTED] My bet is they won't object.
--
John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Aus
IR would be required rather than optional, but that
path can't be in PATH because it contains only files in the target
format, not tools that run on the host.
> P.S. /usr/cross is what OpenBSD uses, but I'm not married to that
> name.
Does OpenBSD use /usr/cross for the
where TARGET is a name quite close to that which
binutils knows. Using the environment variable "TARGET" is a little
problematic for me because it is easily confused (at least by my
brain 8-) with .TARGET.
> I've been using the cross binaries for a variety of purposes, so I
> hav
Greg Lehey wrote:
> > Well, you asked!
>
> And you answered :-)
>
> So where were you at 3 am this morning?
In a land far, far, far away. Then I woke up. 8-)
--
John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A,
least it would save people unnecessary
> pain. Note, of course, that I have now committed the correct file,
> which I had forgotten last night.
>
> What do you others think?
I think you shouldn't sleep.
Well, you asked!
--
John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http:
Gary Palmer wrote:
> John Birrell wrote in message ID
> <199906020405.oaa05...@cimlogic.com.au>:
> > If you were reading the commit messages, you would have noticed that
> > phk said he mailed patches for vinum and i4b to the respective authors.
> > i4b has since b
Leif Neland wrote:
> On Wed, 2 Jun 1999, John Birrell wrote:
> > If you were reading the commit messages, you would have noticed that
> > phk said he mailed patches for vinum and i4b to the respective authors.
> > i4b has since been fixed (AFAIK) and vinum is wai
around China on his way to Usenix.... I doubt that he'll
be able to do anything for a few weeks. Just be patient.
--
John Birrell - j...@cimlogic.com.au; j...@freebsd.org
http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscri
e 3rd party program
was linked against.
--
John Birrell - j...@cimlogic.com.au; j...@freebsd.org
http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current&quo
Doug Rabson wrote:
> I think the only state which I need to know about is PS_DEAD. If we marked
> dead threads in the public struct it might simplify things.
You use PS_RUNNING too. We could just tie down those two as PS_DEAD = 0
and PS_RUNNING = 1.
--
John Birrell - j...@cimlogic.com
nge that gdb was compiled against (the states probably
should be in the common header) and if the state number is out of
that range, just display the number. Then we just need to ensure we
add new states at the end.
--
John Birrell - j...@cimlogic.com.au; j...@freebsd.org
http://www.cimlogic.com.au/
ader file defining such a structure.
--
John Birrell - j...@cimlogic.com.au; j...@freebsd.org
http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
a real problem, I could do this I guess.
Maybe we should just isolate the things that gdb is allowed to look at
and document them as "cast in stone".
--
John Birrell - j...@cimlogic.com.au; j...@freebsd.org
http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 300
, any statically linked applications
will be out-of-sync (if an internal change has been made to libc_r).
I'm not sure there is an easy solution to this.
--
John Birrell - j...@cimlogic.com.au; j...@freebsd.org
http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3
we end up with a similar
problem to the all too familiar "struct proc size mismatch".
--
John Birrell - j...@cimlogic.com.au; j...@freebsd.org
http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to major
ort 0x300 irq 11 iomem 0xd8000
pseudo-device loop
pseudo-device ether
Nice and simple, but after the ROOTDEVNAME changes, it cannot work. Sulk.
The ROOTDEVNAME stuff needs to be fixed to allow this. Local disks and
disk controllers should be optional.
--
John Birrell - j...@cimlogic.com.au; j.
ould _boot_ the kernel. Now it just hangs.
--
John Birrell - j...@cimlogic.com.au; j...@freebsd.org
http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Rev 1.67 of npx.c changed a #ifdef SMP to #ifdef 1, preventing the
test for the hardware coprocessor. This breaks support for 386 processors
without math coprocessors. Grrr.
--
John Birrell - j...@cimlogic.com.au; j...@freebsd.org
http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A
comp.os.linux.misc, and at least one person
> who's got some other Linux benchmarking tools and is relatively
> knowledgable on the subject. This is just the first place I've asked
> where I've gotten any semi-intelligble answers so far.
There's a moral there somewhe
now seems like a good time
to start using egcs as the system compiler, even if things are a bit
bumpy for a while. Many people who started using -current during the
2.X vs 3.0 time can use 3.X-stable without losing much, if anything.
--
John Birrell - j...@cimlogic.com.au; j...@freebsd.o
h his (pet) software
> as candidate for the base distribution, then the base will
> grow without bounds. How long did it take to kill tcl from
> the base distribution, and how long will it take to kill f2c?
IMHO, "Just Do It". Ask David. 8-)
--
John Birrell -
asing the cd-rom?
>
> Convince your University to get a large quantity of cd-roms
> from WC and resell the disks to the students?
Or convince FreeBSD developers to simply add a DHCP client to the base
sources and build a boot/install floppy with that functionality.
No user cos
#x27;s eye. I have TERM=vt100 in my FreeBSD
environment, dxterm configured with the "Numeric Keypad" option checked
and vt100 emulation, so keypad keys are 0.123456789, just like you'd
expect. It's not vi that's the problem, just your termcap setting doesn't
match the k
ueue. Does anyone know the
> reuirements on yield() and would it continue to function for us if
> it worked the same as sched_yield()?
FWIW, the yield syscall is _not_ built into libc, so I doubt there will
be anything that actually uses it. I think you should just keep
sched_yield
e drops off or goes inactive.
--
John Birrell - j...@cimlogic.com.au; j...@freebsd.org
http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
e future. All people seem to want to do is
stomp on others who try to contribute something.
--
John Birrell - j...@cimlogic.com.au; j...@freebsd.org
http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
ointer/long sizes and endian-ness.
>
> This is where I disagree. Too often people cast away the bugs and end
> up with overflow and sign problems.
We still have Bruce to review code for inappropriate casts etc. Try and
stop him. 8-)
--
John Birrell - j...@cimlogic.com.au; j...@freebsd.org
Bruce. The government told people not to
drink the water. Sigh.
My fallback strategy was to win the Olympics for Sydney and then hope
they get bombed. Time will tell...
--
John Birrell - j...@cimlogic.com.au; j...@freebsd.org
http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne V
ke to join these purists? Come on,
we have bullets for you all...
--
John Birrell - j...@cimlogic.com.au; j...@freebsd.org
http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to majord...@freebsd.org
with "unsub
ithout casts (if possible) that will compile cleanly with
-Wall is a reasonable thing to ask IMO. In my experience, the resulting
code tends to be more portable across architectures with different
pointer/long sizes and endian-ness.
Just my 0.02, and I hate style(9) anyway.
--
John Birrell - j...@cimlo
p GNU tools too.
Now all custom code lives in KLDs which get loaded by the application
which replaces init and a simple 20 line kernel config file suits all
target hardware versions.
--
John Birrell - j...@cimlogic.com.au; j...@freebsd.org
http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box
63 matches
Mail list logo
