Re: stdout changes break some ports

2002-03-31 Thread Terry Lambert
Garance A Drosihn wrote: > >How does one fix this in a library? I've been moving the > >initialization to main() for applications. > > If all else fails, have some global static variable, and check > the value in the routine(s) which care. if the flag variable > is still zero, then initialize t

Re: stdout changes break some ports

2002-03-31 Thread Oliver Braun
* Kris Kennaway <[EMAIL PROTECTED]> [2002-03-31 08:48]: > On Sun, Mar 24, 2002 at 05:54:36PM -0800, Kris Kennaway wrote: > > On Sun, Mar 24, 2002 at 06:43:13PM -0700, M. Warner Losh wrote: > > > > > : David O'Brien committed a workaround to the clog port yesterday to > > > : move the initializer

Re: stdout changes break some ports

2002-03-31 Thread Garance A Drosihn
At 10:46 PM -0800 3/30/02, Kris Kennaway wrote: >On Sun, Mar 24, 2002 at 05:54:36PM -0800, Kris Kennaway wrote: > > On Sun, Mar 24, 2002 at 06:43:13PM -0700, M. Warner Losh wrote: > > > No. This isn't something that is guaranteed to work per > > > the standards, iirc. The proper fix is to put

Re: stdout changes break some ports

2002-03-31 Thread Terry Lambert
Terry Lambert wrote: > Kris Kennaway wrote: > > How does one fix this in a library? I've been moving the > > initialization to main() for applications. > > Use assembly glue to put it in a linker set that gets pulled > in by the .init code. > > This will only work for user space code, since it

Re: stdout changes break some ports

2002-03-30 Thread Terry Lambert
Kris Kennaway wrote: > How does one fix this in a library? I've been moving the > initialization to main() for applications. Use assembly glue to put it in a linker set that gets pulled in by the .init code. This will only work for user space code, since it depends in the crt0 treating it like

Re: stdout changes break some ports

2002-03-30 Thread Kris Kennaway
On Sun, Mar 24, 2002 at 05:54:36PM -0800, Kris Kennaway wrote: > On Sun, Mar 24, 2002 at 06:43:13PM -0700, M. Warner Losh wrote: > > > : David O'Brien committed a workaround to the clog port yesterday to > > : move the initializer to main() instead of trying to do it statically. > > : > > : Is t

Re: stdout changes break some ports

2002-03-25 Thread Kris Kennaway
On Mon, Mar 25, 2002 at 09:30:39PM -0800, Doug Barton wrote: > On Sun, 24 Mar 2002, Kris Kennaway wrote: > > > OK. Someone needs to go and fix those 84 ports then. > > > > http://bento.freebsd.org/errorlogs/5-latest-4-latest.html > > Has anyone contacted the maintainers? I'm sure that n

Re: stdout changes break some ports

2002-03-25 Thread Doug Barton
On Sun, 24 Mar 2002, Kris Kennaway wrote: > OK. Someone needs to go and fix those 84 ports then. > > http://bento.freebsd.org/errorlogs/5-latest-4-latest.html Has anyone contacted the maintainers? I'm sure that not all of them are on this list. It may be a good way to get a slightly m

Re: stdout changes break some ports

2002-03-24 Thread Kris Kennaway
On Sun, Mar 24, 2002 at 06:43:13PM -0700, M. Warner Losh wrote: > : David O'Brien committed a workaround to the clog port yesterday to > : move the initializer to main() instead of trying to do it statically. > : > : Is this something which is supposed to work? > > No. This isn't something tha

Re: stdout changes break some ports

2002-03-24 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> Kris Kennaway <[EMAIL PROTECTED]> writes: : The changes to the definitions of stdout/stdin/stderr from a while : back caused a number of ports to break (somewhere around 84, according : to bento). For example, the cap port fails like this: : : http://b