Re: Question about KBI change / new feature

> On Aug 23, 2023, at 1:06 AM, Warner Losh wrote: > > > > On Mon, Aug 21, 2023 at 9:42 AM Zhenlei Huang > wrote: > Hi, > > The https://www.freebsd.org/releases/14.0R/schedule/ > says CURRENT/14 's KBI is > froze >

Re: Question about KBI change / new feature

On Mon, Aug 21, 2023 at 9:42 AM Zhenlei Huang wrote: > Hi, > > The https://www.freebsd.org/releases/14.0R/schedule/ says CURRENT/14 's > KBI is froze > and new features should be avoided. > > I'm working on https://reviews.freebsd.org/D39638 (sysctl(9): Enable vnet > sysctl variables be loader tu

Re: question on socket server

On 2021-12-15 02:55, Piper H wrote: But I write this program to listen on port who sends a random str to the socket every 0.25 second. And there is no client connecting to the port. The server just runs there without problem. :( So I am not sure enough... use strict; package MyPackage; use

Re: question on socket server

t; > > > *Van:* Piper H > *Datum:* woensdag, 15 december 2021 11:55 > *Aan:* Ronald Klop > *CC:* freebsd-current@freebsd.org > *Onderwerp:* Re: question on socket server > > But I write this program to listen on port who sends a random str to > the socket every

Re: question on socket server

generic perl forum/ML. Van: Piper H Datum: woensdag, 15 december 2021 11:55 Aan: Ronald Klop CC: freebsd-current@freebsd.org Onderwerp: Re: question on socket server But I write this program to listen on port who sends a random str to the socket every 0.25 second. And there is no clie

Re: question on socket server

But I write this program to listen on port who sends a random str to the socket every 0.25 second. And there is no client connecting to the port. The server just runs there without problem. :( So I am not sure enough... use strict; package MyPackage; use base qw(Net::Server); my @fruit=qw(

Re: question on socket server

Hi, Just try it! I think you will get an error that you are writing to a not-connected socket. From "man 2 write": " [EPIPE]An attempt is made to write to a socket of type SOCK_STREAM that is not connected to a peer socket." See also "man 2 send" and "man 2 socket" for a lot

Re: Question about 'gptzfsboot'

On 2019-04-29 15:24, Ian Lepore wrote: > > I can't say anything at all about drm or other video driver issues, I'm > just not knowledgeable about that stuff at all. > > The only thing I was getting at was that the changes I made in r346675 > might make this error stop happening: > >gptzfsboo

Re: Question about 'gptzfsboot'

On 2019-04-29 14:58, Toomas Soome wrote: > > It means you have different issues - one is about gptzfsboot causing boot > problems and apparently it got fixed when you did update the bootcode (the > boot partition is global). But also you got bitten by DRM update, and since > you had old BE arou

Re: Question about 'gptzfsboot'

On Mon, 2019-04-29 at 14:47 -0400, Thomas Laus wrote: > On 2019-04-29 14:27, Thomas Laus wrote: > > It was more than a broken console. All of the other 2 computers > > that I > > upgraded to r346885 were essentially 'dead'. I could not even > > remotely > > login to them via ssh. All of them req

Re: Question about 'gptzfsboot'

> On 29 Apr 2019, at 21:47, Thomas Laus wrote: > > On 2019-04-29 14:27, Thomas Laus wrote: >> It was more than a broken console. All of the other 2 computers that I >> upgraded to r346885 were essentially 'dead'. I could not even remotely >> login to them via ssh. All of them required a hard

Re: Question about 'gptzfsboot'

On 2019-04-29 14:27, Thomas Laus wrote: > It was more than a broken console. All of the other 2 computers that I > upgraded to r346885 were essentially 'dead'. I could not even remotely > login to them via ssh. All of them required a hard power button reset > to get into single user mode to let

Re: Question about 'gptzfsboot'

On 2019-04-29 11:14, Ian Lepore wrote: > > I'm fighting my own video driver troubles (seems like a lot of that > going around lately); on an upgrade of a machine from 11-stable to 12- > stable I lost my console. > > But, a broken kernel and/or userland shouldn't affect your ability to > use the n

Re: Question about 'gptzfsboot'

On 2019-04-29 10:33, Thomas Laus wrote: > Updating to r346885 turned out to be a disaster! There were changes to > DRM between FreeBSD 13.0-CURRENT r346544 and r346885. The desktop that > I use for a build machine because it is much faster than any of my other > PC's installed kernel and world wi

Re: Question about 'gptzfsboot'

On Mon, 2019-04-29 at 10:33 -0400, Thomas Laus wrote: > > On 2019-04-28 22:27, Ian Lepore wrote: > > > > > > If you're using gptzfsboot, I guess you're using zfs? I just > > > fixed a > > > problem with probing disks for zfs volumes a few days ago > > > (r346675). > > > There is even some small

Re: Question about 'gptzfsboot'

> On 2019-04-28 22:27, Ian Lepore wrote: >> >> If you're using gptzfsboot, I guess you're using zfs? I just fixed a >> problem with probing disks for zfs volumes a few days ago (r346675). >> There is even some small chance it fixes this problem, because one of >> the things I noticed was that in

Re: Question about 'gptzfsboot'

On 2019-04-28 22:27, Ian Lepore wrote: > > If you're using gptzfsboot, I guess you're using zfs? I just fixed a > problem with probing disks for zfs volumes a few days ago (r346675). > There is even some small chance it fixes this problem, because one of > the things I noticed was that in one of

Re: Question about 'gptzfsboot'

On Sun, 2019-04-28 at 19:29 -0400, Thomas Laus wrote: > On 2019-04-28 08:07, Ronald Klop wrote: > > > > Is this the same as this? > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234 > > > > The messages are similar. The boot process will normally proceed on > the > second or third atte

Re: Question about 'gptzfsboot'

On Sun, Apr 28, 2019 at 5:30 PM Thomas Laus wrote: > On 2019-04-28 08:07, Ronald Klop wrote: > > > > Is this the same as this? > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234 > > > The messages are similar. The boot process will normally proceed on the > second or third attempt. On

Re: Question about 'gptzfsboot'

On 2019-04-28 08:07, Ronald Klop wrote: > > Is this the same as this? > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234 > The messages are similar. The boot process will normally proceed on the second or third attempt. On some days, I don't see this message appear and my laptops boot no

Re: Question about 'gptzfsboot'

On Fri, 26 Apr 2019 13:31:02 +0200, Thomas Laus wrote: List: I have been having gptzfsboot issues with my two laptops since 12.0 was still CURRENT. I receive 'error 1' on the first boot most days. gptzfsboot: error 1 LBA 18446744072709551608 gptzfsboot: error 1 LBA 1 gptzfsboot: No ZFS pools

Re: Question about 'gptzfsboot'

Toomas Soome [tso...@me.com] wrote: > > > I always update the bootcode with gpart each time when updating my system. > > > > Oh right, this from gptzfsboot… ok, I guess I should do something > I have been planning all along… Do you need some sort of quick workaround? > No quick workaround is

Re: Question about 'gptzfsboot'

> On 26 Apr 2019, at 16:20, Thomas Laus wrote: > > Toomas Soome [tso...@me.com] wrote: >> >> The key is about LBA in first message. Make sure you have latest >> boot code installed with gpart. >> > I always update the bootcode with gpart each time when updating my system. > Oh right, this f

Re: Question about 'gptzfsboot'

Toomas Soome [tso...@me.com] wrote: > > The key is about LBA in first message. Make sure you have latest > boot code installed with gpart. > I always update the bootcode with gpart each time when updating my system. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF __

Re: Question about 'gptzfsboot'

> On 26 Apr 2019, at 14:31, Thomas Laus wrote: > > List: > > I have been having gptzfsboot issues with my two laptops since 12.0 was > still CURRENT. I receive 'error 1' on the first boot most days. > > gptzfsboot: error 1 LBA 18446744072709551608 > gptzfsboot: error 1 LBA 1 > gptzfsboot: N

Re: Question mark on Lua menu box

On 02/03/18 12:55, Kyle Evans wrote: > On Fri, Mar 2, 2018 at 9:52 AM, Renato Botelho wrote: >> On 02/03/18 12:31, Kyle Evans wrote: >>> On Fri, Mar 2, 2018 at 6:06 AM, Renato Botelho wrote: Kyle, I've moved to Lua loader to help testing and it worked fine. The only odd thing

Re: Question mark on Lua menu box

On Fri, Mar 2, 2018 at 9:52 AM, Renato Botelho wrote: > On 02/03/18 12:31, Kyle Evans wrote: >> On Fri, Mar 2, 2018 at 6:06 AM, Renato Botelho wrote: >>> Kyle, >>> >>> I've moved to Lua loader to help testing and it worked fine. The only >>> odd thing I noted is the menu box with odd chars as you

Re: Question mark on Lua menu box

On 02/03/18 12:31, Kyle Evans wrote: > On Fri, Mar 2, 2018 at 6:06 AM, Renato Botelho wrote: >> Kyle, >> >> I've moved to Lua loader to help testing and it worked fine. The only >> odd thing I noted is the menu box with odd chars as you can see at [1]. >> >> My laptop is running a recent current (

Re: Question mark on Lua menu box

On Fri, Mar 2, 2018 at 6:06 AM, Renato Botelho wrote: > Kyle, > > I've moved to Lua loader to help testing and it worked fine. The only > odd thing I noted is the menu box with odd chars as you can see at [1]. > > My laptop is running a recent current (r330275) with ZFS and UEFI. > > [1] https://i

Re: Question mark on Lua menu box

On 2 March 2018 at 07:06, Renato Botelho wrote: > Kyle, > > I've moved to Lua loader to help testing and it worked fine. The only > odd thing I noted is the menu box with odd chars as you can see at [1]. Hi Renato, thanks for testing! Are you booting via BIOS or UEFI?

Re: Question about wmb() and rmb() and task switching

On Fri, Sep 23, 2016 at 01:46:15PM +0200, Hans Petter Selasky wrote: > Hi, > > Does use of wmb() and rmb() for amd64 as defined in > sys/amd64/include/atomic.h required use of critical_enter()/critical_exit(). > > I was looking at the code in sys/amd64/amd64/cpu_switch.S which switches > betwee

Re: Question about cam 4K quirks

On 11/04/2016 15:24, Tomoaki AOKI wrote: Thanks for your answer! On Sun, 10 Apr 2016 16:15:56 +0100 Steven Hartland wrote: On 10/04/2016 15:35, Tomoaki AOKI wrote: On Sun, 10 Apr 2016 06:59:04 -0600 Alan Somers wrote: On Sun, Apr 10, 2016 at 12:56 AM, Tomoaki AOKI wrote: Hi. Maybe f

Re: Question about cam 4K quirks

Thanks for your answer! On Sun, 10 Apr 2016 16:15:56 +0100 Steven Hartland wrote: > > > On 10/04/2016 15:35, Tomoaki AOKI wrote: > > On Sun, 10 Apr 2016 06:59:04 -0600 > > Alan Somers wrote: > > > >> On Sun, Apr 10, 2016 at 12:56 AM, Tomoaki AOKI > >> wrote: > >> > >>> Hi. Maybe freebsd-hard

Re: Question about cam 4K quirks

On 10/04/2016 15:35, Tomoaki AOKI wrote: On Sun, 10 Apr 2016 06:59:04 -0600 Alan Somers wrote: On Sun, Apr 10, 2016 at 12:56 AM, Tomoaki AOKI wrote: Hi. Maybe freebsd-hardware list would be the right place, but it's not so active. :-( Is 4K quirks needed for every HDDs/SSDs having physic

Re: Question about cam 4K quirks

On Sun, 10 Apr 2016 06:59:04 -0600 Alan Somers wrote: > On Sun, Apr 10, 2016 at 12:56 AM, Tomoaki AOKI > wrote: > > > Hi. Maybe freebsd-hardware list would be the right place, but it's not > > so active. :-( > > > > Is 4K quirks needed for every HDDs/SSDs having physical sector size > > 4096? >

Re: Question about cam 4K quirks

On Sun, Apr 10, 2016 at 12:56 AM, Tomoaki AOKI wrote: > Hi. Maybe freebsd-hardware list would be the right place, but it's not > so active. :-( > > Is 4K quirks needed for every HDDs/SSDs having physical sector size > 4096? > > If so, I would be able to provide patch for Crucial M550 and MX200. >

Re: question on support processor Intel Atom Z3735F

On Fri, 25 Mar 2016, Lundberg, Johannes wrote: One problem is that most of these devices have only 32 bit UEFI which FreeBSD does not support (except Intel Compute Stick which has 64 bit UEFI). The MinnowBoard has both 32-bit and 64-bit UEFI. My Turbot came with 64-bit UEFI, and the FreeBSD

Re: question on support processor Intel Atom Z3735F

One problem is that most of these devices have only 32 bit UEFI which FreeBSD does not support (except Intel Compute Stick which has 64 bit UEFI). I use special built Grub to boot a 64 bit Arch Linux on this chip, maybe same approach could be used to boot a 64 bit FreeBSD. However, you probably won

Re: question on support processor Intel Atom Z3735F

On Thu, Mar 24, 2016 at 10:06:05PM +0300, Владимир wrote: > Hello, please tell me whether the FreeBSD operating system Intel Atom > Z3735F? Which distribution I need to download? The CPU supports amd64 but AFAIK the Baytrail architecture only supports a 32-bit UEFI. So you need to create your o

Re: question on support processor Intel Atom Z3735F

Hi Vladimir, I believe you need x86 arch. Regards On Mar 24, 2016 3:37 PM, "Владимир" wrote: > Hello, please tell me whether the FreeBSD operating system Intel Atom > Z3735F? Which distribution I need to download? > > > > ___ > freebsd-...@freebsd.or

Re: question on support processor Intel Atom Z3735F

On 24.03.2016 22:06, Владимир wrote: > Intel Atom Z3735F Both x86 (32 bit) and amd64 (64 bit) will do. It depends on available memory. If you have 4GB or more installed, try amd64. -- // Lev Serebryakov signature.asc Description: OpenPGP digital signature

Re: question about pkgng

On Sun, February 2, 2014 4:58 pm, Waitman Gobble wrote: > Hi, > > > I updated my laptop to: > > > # uname -a > FreeBSD akira.waitman.net 11.0-CURRENT FreeBSD 11.0-CURRENT #1: Sun Feb 2 > 21:45:49 PST 2014 r...@akira.waitman.net:/usr/obj/usr/src/sys/AKIRA > amd64 > Scratch this question, it

Re: Question about socket timeouts

On Tue, Aug 27, 2013 at 7:10 AM, Vitja Makarov wrote: >> On Fri, Aug 23, 2013 at 7:04 AM, Vitja Makarov >> wrote: >>> 2013/8/23 Davide Italiano : >>> >>> I think that for socket's timeouts it's ok to have a HZ-precision. It >>> would be much more important to implement high-precision timeouts fo

Re: Question about socket timeouts

On Thu, Aug 29, 2013 at 6:03 PM, John Baldwin wrote: > On Monday, August 26, 2013 3:05:06 pm John Baldwin wrote: >> On Monday, August 26, 2013 2:23:44 pm Davide Italiano wrote: >> > Please consider the following patch: >> > http://people.freebsd.org/~davide/review/socket_timeout.diff >> > I've tes

Re: Question about socket timeouts

On Monday, August 26, 2013 3:05:06 pm John Baldwin wrote: > On Monday, August 26, 2013 2:23:44 pm Davide Italiano wrote: > > Please consider the following patch: > > http://people.freebsd.org/~davide/review/socket_timeout.diff > > I've tested it and it works OK. I got a timeout which is ~= 25ms usi

Re: Question about socket timeouts

2013/8/26 Davide Italiano : > Please consider the following patch: > http://people.freebsd.org/~davide/review/socket_timeout.diff > I've tested it and it works OK. I got a timeout which is ~= 25ms using > the testcase provided by the user. > The only doubt I have is about the range check, I've chan

Re: Question about socket timeouts

On Monday, August 26, 2013 2:23:44 pm Davide Italiano wrote: > On Fri, Aug 23, 2013 at 5:29 PM, John Baldwin wrote: > > On Friday, August 23, 2013 9:53:12 am Davide Italiano wrote: > >> On Fri, Aug 23, 2013 at 3:45 PM, John Baldwin wrote: > >> > On Friday, August 23, 2013 2:27:58 am Vitja Makarov

Re: Question about socket timeouts

On Fri, Aug 23, 2013 at 7:04 AM, Vitja Makarov wrote: > 2013/8/23 Davide Italiano : > > I think that for socket's timeouts it's ok to have a HZ-precision. It > would be much more important to implement high-precision timeouts for > select() and friends, if it's not done yet (sorry I'm running 9.1)

Re: Question about socket timeouts

On Fri, Aug 23, 2013 at 5:29 PM, John Baldwin wrote: > On Friday, August 23, 2013 9:53:12 am Davide Italiano wrote: >> On Fri, Aug 23, 2013 at 3:45 PM, John Baldwin wrote: >> > On Friday, August 23, 2013 2:27:58 am Vitja Makarov wrote: >> >> 2013/8/22 John Baldwin : >> >> > On Thursday, August 22

Re: Question about socket timeouts

On Friday, August 23, 2013 9:53:12 am Davide Italiano wrote: > On Fri, Aug 23, 2013 at 3:45 PM, John Baldwin wrote: > > On Friday, August 23, 2013 2:27:58 am Vitja Makarov wrote: > >> 2013/8/22 John Baldwin : > >> > On Thursday, August 22, 2013 12:18:48 am Vitja Makarov wrote: > >> >> 2013/8/21 Jo

Re: Question about socket timeouts

2013/8/23 Davide Italiano : > On Fri, Aug 23, 2013 at 3:45 PM, John Baldwin wrote: >> On Friday, August 23, 2013 2:27:58 am Vitja Makarov wrote: >>> 2013/8/22 John Baldwin : >>> > On Thursday, August 22, 2013 12:18:48 am Vitja Makarov wrote: >>> >> 2013/8/21 John Baldwin : >>> >> > On Monday, Augu

Re: Question about socket timeouts

On Fri, Aug 23, 2013 at 3:45 PM, John Baldwin wrote: > On Friday, August 23, 2013 2:27:58 am Vitja Makarov wrote: >> 2013/8/22 John Baldwin : >> > On Thursday, August 22, 2013 12:18:48 am Vitja Makarov wrote: >> >> 2013/8/21 John Baldwin : >> >> > On Monday, August 19, 2013 11:13:02 pm Daniel Eisc

Re: Question about socket timeouts

On Friday, August 23, 2013 2:27:58 am Vitja Makarov wrote: > 2013/8/22 John Baldwin : > > On Thursday, August 22, 2013 12:18:48 am Vitja Makarov wrote: > >> 2013/8/21 John Baldwin : > >> > On Monday, August 19, 2013 11:13:02 pm Daniel Eischen wrote: > >> >> On Mon, 19 Aug 2013, Adrian Chadd wrote:

Re: Question about socket timeouts

2013/8/22 John Baldwin : > On Thursday, August 22, 2013 12:18:48 am Vitja Makarov wrote: >> 2013/8/21 John Baldwin : >> > On Monday, August 19, 2013 11:13:02 pm Daniel Eischen wrote: >> >> On Mon, 19 Aug 2013, Adrian Chadd wrote: >> >> >> >> > Yes! Please file a PR! >> >> >> >> This sorta implies t

Re: Question about socket timeouts

On Monday, August 19, 2013 11:13:02 pm Daniel Eischen wrote: > On Mon, 19 Aug 2013, Adrian Chadd wrote: > > > Yes! Please file a PR! > > This sorta implies that both are acceptable (although, > the Linux behavior seems more desirable). > >http://austingroupbugs.net/view.php?id=369 No, that

Re: Question about socket timeouts

On Mon, 19 Aug 2013, Adrian Chadd wrote: Yes! Please file a PR! This sorta implies that both are acceptable (although, the Linux behavior seems more desirable). http://austingroupbugs.net/view.php?id=369 On 19 August 2013 12:33, Vitja Makarov wrote: Hi! Recently I was playing with sma

Re: Question about socket timeouts

Yes! Please file a PR! -adrian On 19 August 2013 12:33, Vitja Makarov wrote: > Hi! > > Recently I was playing with small socket timeouts. setsockopt(2) > SO_RCVTIMEO and found a problem with it: if timeout is small enough > read(2) may return before timeout is actually expired. > > I was un

Re: Question about portsdb (part of ports-mgmt/portupgrade)

On Sat, Jun 22, 2013 at 12:34:38PM + I heard the voice of Walter Hurry, and lo! it spake thus: > > But the corresponding action doesn't happen on 10.0-CURRENT > (r251572) until I do a 'portsdb -Fu'. > > Why the difference? Portsnap doesn't make/distribute INDEX-10 (until 10 spirals toward -S

Re: Question on building from sources.

Make fetch-recursive stops due to the vulnerability found in perl versions 5.8 to 5.16.3. What's the current status? Are there any patches? On Sat, Mar 30, 2013 at 8:10 PM, Erich Dollansky < erichsfreebsdl...@alogt.com> wrote: > Hi, > > On Sat, 30 Mar 2013 19:05:47 -0400 > Super Bisquit wrote

Re: Question on building from sources.

Hi, On Sat, 30 Mar 2013 19:05:47 -0400 Super Bisquit wrote: > Okay. I already have 10.0 on the machine from a year ago. What I have this sounds a bit old. > come up against is CLANG_IS_CC ="no" when trying to build run(4). > What is the current state of clang as cc compiler on ppc32? <-- This

Re: Question on building from sources.

That was the error that came up, apologies for not specifying such. I'm not trying to disable clang but am trying to build the system using what is there. This is about the time I need a powerpc laptop or a connection.. On Sat, Mar 30, 2013 at 7:09 PM, Glen Barber wrote: > On Sat, Mar 30,

Re: Question on building from sources.

On Sat, Mar 30, 2013 at 07:05:47PM -0400, Super Bisquit wrote: > Okay. I already have 10.0 on the machine from a year ago. What I have come > up against is CLANG_IS_CC ="no" when trying to build run(4). If you are trying to disable clang, you want to use: WITHOUT_CLANG_IS_CC=yes > What is th

Re: Question on building from sources.

Okay. I already have 10.0 on the machine from a year ago. What I have come up against is CLANG_IS_CC ="no" when trying to build run(4). What is the current state of clang as cc compiler on ppc32? <-- This needs to be fixed first. Thanks for the replies and sorry for any noise. On Fri, Mar 29, 20

Re: Question on building from sources.

Hi, On Fri, 29 Mar 2013 22:03:11 -0400 Glen Barber wrote: > On Fri, Mar 29, 2013 at 09:31:12PM -0400, Super Bisquit wrote: > > I have my QuickSilver and no internet connection. I have a few > > questions. 1. Do I download the latest for PowerPC(32bit) and then > > download the sources according

Re: Question on building from sources.

On Fri, Mar 29, 2013 at 09:31:12PM -0400, Super Bisquit wrote: > I have my QuickSilver and no internet connection. I have a few questions. > 1. Do I download the latest for PowerPC(32bit) and then download the > sources according to the Makefile. For ports, yes, you will to do 'make fetch' or 'mak

Re: nge(4), tl(4), wb(4) and rl(4) 8129 testers wanted [Re: Question about GPIO bitbang MII]

On 15 Oct 2011, at 22:56, Marius Strobl wrote: > > Could owners of nge(4), tl(4), wb(4) and rl(4) driven hardware (as for > rl(4) only 8129 need testing, 8139 don't) please give the following > patch a try in order to ensure it doesn't break anything? > for 9/head: > http://people.freebsd.org/

Re: nge(4), tl(4), wb(4) and rl(4) 8129 testers wanted [Re: Question about GPIO bitbang MII]

On Sun, Oct 16, 2011 at 02:46:23AM +0200, Damien Fleuriot wrote: > > > On 15 Oct 2011, at 22:56, Marius Strobl wrote: > > > > > Could owners of nge(4), tl(4), wb(4) and rl(4) driven hardware (as for > > rl(4) only 8129 need testing, 8139 don't) please give the following > > patch a try in orde

nge(4), tl(4), wb(4) and rl(4) 8129 testers wanted [Re: Question about GPIO bitbang MII]

Could owners of nge(4), tl(4), wb(4) and rl(4) driven hardware (as for rl(4) only 8129 need testing, 8139 don't) please give the following patch a try in order to ensure it doesn't break anything? for 9/head: http://people.freebsd.org/~marius/mii_bitbang.diff for 8: http://people.freebsd.org/~mari

Re: Question on freeBSD (5.1-CURRENT) portupgrade of Perl 5.8 andlibiconv 1.9.1_3

Hello, On Wed, Oct 22, 2003 at 01:21:10AM -0400, Joe Marcus Clarke wrote: > On Wed, 2003-10-22 at 01:14, Scott W wrote: > > Also, is there a way to pass configure options to portupgrade, or should > > I run make clean && ./configure for each port in an 'upgrade chain' and > > then force portupgr

Re: Question on freeBSD (5.1-CURRENT) portupgrade of Perl5.8andlibiconv 1.9.1_3

erformance" <[EMAIL PROTECTED]> To: "Joe Marcus Clarke" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "Scott W" <[EMAIL PROTECTED]> Sent: Wednesday, October 22, 2003 07:34 AM Subject: Re: Question on freeBSD (5.1-CURRENT) port

Re: Question on freeBSD (5.1-CURRENT) portupgrade of Perl 5.8andlibiconv 1.9.1_3

Joe Marcus Clarke wrote: On Wed, 2003-10-22 at 01:14, Scott W wrote: Hey all. In doing a portupgrade -RvN for windowmaker, Perl and libiconv were recompiled. I saved the log output and noticed several oddities I was wondering if anyone can explain? 1..several settings come up as undefined

Re: Question on freeBSD (5.1-CURRENT) portupgrade of Perl 5.8 andlibiconv 1.9.1_3

On Wed, 2003-10-22 at 01:14, Scott W wrote: > Hey all. In doing a portupgrade -RvN for windowmaker, Perl and libiconv > were recompiled. I saved the log output and noticed several oddities I > was wondering if anyone can explain? > > 1..several settings come up as undefined during the Perl bui

Re: Question related to FreeBSD Serial Console...

In message: <[EMAIL PROTECTED]> Gordon Tetlow <[EMAIL PROTECTED]> writes: : I've personally killed about 5 keyboards this way. I don't recommend hot : plugging PS/2 keyboards. PS/2 keyboards and mice are not hot pluggable. Mechanical switches do not meet the spec, but are less bad tha

Re: Question related to FreeBSD Serial Console...

On Tue, Sep 02, 2003 at 12:18:51PM +0100, [EMAIL PROTECTED] wrote: > Hiya > > > > Unfortunately, many motherboards (BIOSs?) won't initialise a PS/2 keyboard > > interface unless a keyboard is connected at boot time, so if you plug in a > > keyboard subsequently it won't work. Nothing the OS can d

Re: Question about genassym, locore.s and 0-sized arrays(showstopper for an icc compiled kernel)

On Sat, Sep 06, 2003 at 10:57:52AM +0200, Alexander Leidinger wrote: > > ---snip--- > % #include > > struct foo { > int tag; > char obj[]; > }; > > int main(void) { > struct foo bar; > > printf("%d\n", sizeof(struct foo)); > printf("%d\n", sizeof(bar));

Re: Question about genassym, locore.s and 0-sized arrays(showstopper for an icc compiled kernel)

On Sat, 6 Sep 2003 01:42:59 -0700 John-Mark Gurney <[EMAIL PROTECTED]> wrote: > Alexander Leidinger wrote this message on Sat, Sep 06, 2003 at 10:33 +0200: > > struct { > ^ try moving foo to here. > > int tag; > > char obj[]; > > } foo; > ^^^ from here. > Uhm... yes,

Re: Question about genassym, locore.s and 0-sized arrays(showstopper for an icc compiled kernel)

Alexander Leidinger wrote this message on Sat, Sep 06, 2003 at 10:33 +0200: > struct { ^ try moving foo to here. > int tag; > char obj[]; > } foo; ^^^ from here. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has be

Re: Question about genassym, locore.s and 0-sized arrays(showstopper for an icc compiled kernel)

On Fri, 5 Sep 2003 09:55:57 -0700 Marcel Moolenaar <[EMAIL PROTECTED]> wrote: > Interesting, What does icc do with: > > struct { > int tag; > char obj[]; > } foo; > > And what does the sizeof() operator give. ---snip--- % struct { int tag; char obj[]; } foo; int m

Re: Question about genassym, locore.s and 0-sized arrays(showstopper for an icc compiled kernel)

On Fri, Sep 05, 2003 at 10:55:07AM +0200, Alexander Leidinger wrote: > > > > It does, according to my reading of it. They may have an issue with > > dead code removal or element aliasing. The way to find out would be > > to see what they emit for "[]"... 0 lenth, or 1? > > % char array[]; > >

Re: Question about genassym, locore.s and 0-sized arrays(showstopper for an icc compiled kernel)

On Fri, Sep 05, 2003 at 07:34:39PM +1000, Bruce Evans wrote: > On Fri, 5 Sep 2003, I wrote: > > > ... > > If some values are unrepresentable then they need to be represtended > > using other values. E.g., add 1 to avoid 0, or multiply by the alignment > > size if some element of the tool chanin i

Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)

On Thu, Sep 04, 2003 at 11:28:58AM -0500, Dan Nelson wrote: > In the last episode (Sep 04), Alexander Leidinger said: > > - If we depend on it: how hard would it be to rewrite it to not depend > >on 0-sized arrays (and does someone volunteer to rewrite it)? It > >would be nice if someone

Re: Question about genassym, locore.s and 0-sizedarrays(showstopper for an icc compiled kernel)

On Fri, 05 Sep 2003 02:06:56 -0700 Terry Lambert <[EMAIL PROTECTED]> wrote: > Now try: > > struct foo { > char c; > int i; > long array[]; > }; > > struct foo foo;m > struct foo fee[1]; > struct foo fie[3]; > struct fo

Re: Question about genassym, locore.s and 0-sizedarrays(showstopper for an icc compiled kernel)

On Fri, 5 Sep 2003, I wrote: > ... > If some values are unrepresentable then they need to be represtended > using other values. E.g., add 1 to avoid 0, or multiply by the alignment > size if some element of the tool chanin instsists on rounding up things chain

Re: Question about genassym, locore.s and 0-sizedarrays(showstopperfor an icc compiled kernel)

Alexander Leidinger wrote: > On Fri, 05 Sep 2003 01:38:29 -0700 > Terry Lambert <[EMAIL PROTECTED]> wrote: > > Dan Nelson wrote: > > > I guess the correct question to be asking is "does the ELF format allow > > > 0-length symbols?" > > > > It does, according to my reading of it. They may have an i

Re: Question about genassym, locore.s and 0-sized arrays(showstopper for an icc compiled kernel)

On Fri, 05 Sep 2003 01:38:29 -0700 Terry Lambert <[EMAIL PROTECTED]> wrote: > Dan Nelson wrote: > > I guess the correct question to be asking is "does the ELF format allow > > 0-length symbols?" > > It does, according to my reading of it. They may have an issue with > dead code removal or elemen

Re: Question about genassym, locore.s and 0-sized arrays(showstopper for an icc compiled kernel)

On Thu, 4 Sep 2003, Marcel Moolenaar wrote: > On Fri, Sep 05, 2003 at 02:59:22AM +0200, Marius Strobl wrote: > > > > > > We use the size of the symbol (ie the size of the object identified > > > by the symbol) to pass around values. This we do by creating arrays. > > > If we want to export a C con

Re: Question about genassym, locore.s and 0-sizedarrays(showstopper for an icc compiled kernel)

Dan Nelson wrote: > I guess the correct question to be asking is "does the ELF format allow > 0-length symbols?" It does, according to my reading of it. They may have an issue with dead code removal or element aliasing. The way to find out would be to see what they emit for "[]"... 0 lenth, or 1

Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)

On Thu, 4 Sep 2003 15:57:31 -0700 Marcel Moolenaar <[EMAIL PROTECTED]> wrote: > On Thu, Sep 04, 2003 at 05:51:23PM -0500, Dan Nelson wrote: > > > > I guess the correct question to be asking is "does the ELF format allow > > 0-length symbols?" > > Of course. What size do you think a label should

Re: Question about genassym, locore.s and 0-sizedarrays(showstopper for an icc compiled kernel)

Alexander Leidinger wrote: > Dan Nelson <[EMAIL PROTECTED]> wrote: > > If you're talking FreeBSD 5, you should be able to simply subsitute a > > C99 "flexible array member" (basically replace "[0]" with "[]") and get > > the same effect. 0-length arrays are a gcc extension: > > > > http://gcc.gnu.

Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)

< said: > In theory, yes. In practice, maybe not. If I remember correctly, > the problem we're trying to solve is twofold: Actually, the problem we were trying to solve is simpler than that. genassym needs to be able to compute the values of certain constants from header files which are only acc

Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)

On Fri, Sep 05, 2003 at 02:59:22AM +0200, Marius Strobl wrote: > > > > We use the size of the symbol (ie the size of the object identified > > by the symbol) to pass around values. This we do by creating arrays. > > If we want to export a C constant 'FOOBAR' to assembly and the constant > > is def

Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)

On Thu, Sep 04, 2003 at 03:47:09PM -0700, Marcel Moolenaar wrote: > > We use the size of the symbol (ie the size of the object identified > by the symbol) to pass around values. This we do by creating arrays. > If we want to export a C constant 'FOOBAR' to assembly and the constant > is defined to

Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)

On Thu, Sep 04, 2003 at 05:51:23PM -0500, Dan Nelson wrote: > > I guess the correct question to be asking is "does the ELF format allow > 0-length symbols?" Of course. What size do you think a label should have otherwise? -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] ___

Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)

In the last episode (Sep 05), Alexander Leidinger said: > On Thu, 4 Sep 2003 11:28:58 -0500 > Dan Nelson <[EMAIL PROTECTED]> wrote: > > If you're talking FreeBSD 5, you should be able to simply subsitute > > a C99 "flexible array member" (basically replace "[0]" with "[]") > > and get the same effe

Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)

On Fri, Sep 05, 2003 at 12:14:11AM +0200, Alexander Leidinger wrote: > On Thu, 4 Sep 2003 11:28:58 -0500 > Dan Nelson <[EMAIL PROTECTED]> wrote: > > > If you're talking FreeBSD 5, you should be able to simply subsitute a > > C99 "flexible array member" (basically replace "[0]" with "[]") and get >

Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)

On Thu, 4 Sep 2003 11:28:58 -0500 Dan Nelson <[EMAIL PROTECTED]> wrote: > If you're talking FreeBSD 5, you should be able to simply subsitute a > C99 "flexible array member" (basically replace "[0]" with "[]") and get > the same effect. 0-length arrays are a gcc extension: > > http://gcc.gnu.org

Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)

In the last episode (Sep 04), Alexander Leidinger said: > At the moment I discussing an issue with Intel regarding 0-sized > arrays. gcc seems to be violating the standard and produces code with > an array size of "0", whereas icc produces code where an 0-sized > array has the size "1". This result

Re: Question related to FreeBSD Serial Console...

On Tue, Sep 02, 2003 at 12:18:51PM +0100 I heard the voice of [EMAIL PROTECTED], and lo! it spake thus: > > Keyboard and mouse manufacturers usually give dire warnings about plugging > in PS/2 devices when the machine is powered up, maybe that's the reason > why. I think it's more because the int

Re: Question related to FreeBSD Serial Console...

On Mon, Sep 01, 2003 at 05:29:09PM -0600, Scott Long wrote: > At one time I was working on patches to the loader to make the console > speed configurable. At the time, at least, I didn't see any evidence > that the settings were stored in the boot0 block, but maybe I was wrong. > In any case, fini

Re: Question related to FreeBSD Serial Console...

On Tue, 2003-09-02 at 01:33, Bruce Evans wrote: > About the original question: multiple consoles in the kernel are > unsupported in FreeBSD-4 but are standard in -current. Unfortunately, > their implementation is slightly incomplete even in -current. In > -current, you get them by booting with -D

  1   2   >