[head tinderbox] failure on sparc64/sun4v
TB --- 2010-06-18 03:35:58 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-06-18 03:35:58 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2010-06-18 03:35:58 - cleaning the object tree TB --- 2010-06-18 03:36:14 - cvsupping the source tree TB --- 2010-06-18 03:36:14 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2010-06-18 03:36:55 - building world TB --- 2010-06-18 03:36:55 - MAKEOBJDIRPREFIX=/obj TB --- 2010-06-18 03:36:55 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-06-18 03:36:55 - TARGET=sun4v TB --- 2010-06-18 03:36:55 - TARGET_ARCH=sparc64 TB --- 2010-06-18 03:36:55 - TZ=UTC TB --- 2010-06-18 03:36:55 - __MAKE_CONF=/dev/null TB --- 2010-06-18 03:36:55 - cd /src TB --- 2010-06-18 03:36:55 - /usr/bin/make -B buildworld >>> World build started on Fri Jun 18 03:36:56 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Jun 18 04:37:38 UTC 2010 TB --- 2010-06-18 04:37:38 - generating LINT kernel config TB --- 2010-06-18 04:37:38 - cd /src/sys/sun4v/conf TB --- 2010-06-18 04:37:38 - /usr/bin/make -B LINT TB --- 2010-06-18 04:37:38 - building LINT kernel TB --- 2010-06-18 04:37:38 - MAKEOBJDIRPREFIX=/obj TB --- 2010-06-18 04:37:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-06-18 04:37:38 - TARGET=sun4v TB --- 2010-06-18 04:37:38 - TARGET_ARCH=sparc64 TB --- 2010-06-18 04:37:38 - TZ=UTC TB --- 2010-06-18 04:37:38 - __MAKE_CONF=/dev/null TB --- 2010-06-18 04:37:38 - cd /src TB --- 2010-06-18 04:37:38 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Jun 18 04:37:38 UTC 2010 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] : undefined reference to `systrace_probe_func' subr_trap.o(.text+0x11c): In function `syscallenter': : undefined reference to `systrace_probe_func' subr_trap.o(.text+0x128): In function `syscallenter': : undefined reference to `systrace_probe_func' subr_trap.o(.text+0x198): In function `syscallenter': : undefined reference to `systrace_probe_func' subr_trap.o(.text+0x1a8): more undefined references to `systrace_probe_func' follow *** Error code 1 Stop in /obj/sun4v/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-06-18 04:49:31 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-06-18 04:49:31 - ERROR: failed to build lint kernel TB --- 2010-06-18 04:49:31 - 3392.73 user 656.26 system 4412.91 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sun4v.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[head tinderbox] failure on powerpc/powerpc
TB --- 2010-06-18 02:49:53 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-06-18 02:49:53 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2010-06-18 02:49:53 - cleaning the object tree TB --- 2010-06-18 02:50:19 - cvsupping the source tree TB --- 2010-06-18 02:50:19 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2010-06-18 02:50:48 - building world TB --- 2010-06-18 02:50:48 - MAKEOBJDIRPREFIX=/obj TB --- 2010-06-18 02:50:48 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-06-18 02:50:48 - TARGET=powerpc TB --- 2010-06-18 02:50:48 - TARGET_ARCH=powerpc TB --- 2010-06-18 02:50:48 - TZ=UTC TB --- 2010-06-18 02:50:48 - __MAKE_CONF=/dev/null TB --- 2010-06-18 02:50:48 - cd /src TB --- 2010-06-18 02:50:48 - /usr/bin/make -B buildworld >>> World build started on Fri Jun 18 02:50:49 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Jun 18 04:26:19 UTC 2010 TB --- 2010-06-18 04:26:19 - generating LINT kernel config TB --- 2010-06-18 04:26:19 - cd /src/sys/powerpc/conf TB --- 2010-06-18 04:26:19 - /usr/bin/make -B LINT TB --- 2010-06-18 04:26:19 - building LINT kernel TB --- 2010-06-18 04:26:19 - MAKEOBJDIRPREFIX=/obj TB --- 2010-06-18 04:26:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-06-18 04:26:19 - TARGET=powerpc TB --- 2010-06-18 04:26:19 - TARGET_ARCH=powerpc TB --- 2010-06-18 04:26:19 - TZ=UTC TB --- 2010-06-18 04:26:19 - __MAKE_CONF=/dev/null TB --- 2010-06-18 04:26:19 - cd /src TB --- 2010-06-18 04:26:19 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Jun 18 04:26:19 UTC 2010 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror vers.c linking kernel subr_trap.o(.text+0x8b6): In function `syscallenter': : undefined reference to `systrace_probe_func' subr_trap.o(.text+0x8be): In function `syscallenter': : undefined reference to `systrace_probe_func' subr_trap.o(.text+0x916): In function `syscallenter': : undefined reference to `systrace_probe_func' *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-06-18 04:37:32 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-06-18 04:37:32 - ERROR: failed to build lint kernel TB --- 2010-06-18 04:37:32 - 5133.50 user 848.81 system 6458.72 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[head tinderbox] failure on sparc64/sparc64
TB --- 2010-06-18 03:09:26 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-06-18 03:09:26 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2010-06-18 03:09:26 - cleaning the object tree TB --- 2010-06-18 03:09:46 - cvsupping the source tree TB --- 2010-06-18 03:09:46 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2010-06-18 03:10:14 - building world TB --- 2010-06-18 03:10:14 - MAKEOBJDIRPREFIX=/obj TB --- 2010-06-18 03:10:14 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-06-18 03:10:14 - TARGET=sparc64 TB --- 2010-06-18 03:10:14 - TARGET_ARCH=sparc64 TB --- 2010-06-18 03:10:14 - TZ=UTC TB --- 2010-06-18 03:10:14 - __MAKE_CONF=/dev/null TB --- 2010-06-18 03:10:14 - cd /src TB --- 2010-06-18 03:10:14 - /usr/bin/make -B buildworld >>> World build started on Fri Jun 18 03:10:14 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Jun 18 04:12:49 UTC 2010 TB --- 2010-06-18 04:12:49 - generating LINT kernel config TB --- 2010-06-18 04:12:49 - cd /src/sys/sparc64/conf TB --- 2010-06-18 04:12:49 - /usr/bin/make -B LINT TB --- 2010-06-18 04:12:49 - building LINT kernel TB --- 2010-06-18 04:12:49 - MAKEOBJDIRPREFIX=/obj TB --- 2010-06-18 04:12:49 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-06-18 04:12:49 - TARGET=sparc64 TB --- 2010-06-18 04:12:49 - TARGET_ARCH=sparc64 TB --- 2010-06-18 04:12:49 - TZ=UTC TB --- 2010-06-18 04:12:49 - __MAKE_CONF=/dev/null TB --- 2010-06-18 04:12:49 - cd /src TB --- 2010-06-18 04:12:49 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Jun 18 04:12:50 UTC 2010 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] : undefined reference to `systrace_probe_func' subr_trap.o(.text+0x11c): In function `syscallenter': : undefined reference to `systrace_probe_func' subr_trap.o(.text+0x128): In function `syscallenter': : undefined reference to `systrace_probe_func' subr_trap.o(.text+0x198): In function `syscallenter': : undefined reference to `systrace_probe_func' subr_trap.o(.text+0x1a8): more undefined references to `systrace_probe_func' follow *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-06-18 04:26:19 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-06-18 04:26:19 - ERROR: failed to build lint kernel TB --- 2010-06-18 04:26:19 - 3425.17 user 693.46 system 4613.32 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sparc64.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[head tinderbox] failure on ia64/ia64
TB --- 2010-06-18 01:09:11 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-06-18 01:09:11 - starting HEAD tinderbox run for ia64/ia64 TB --- 2010-06-18 01:09:11 - cleaning the object tree TB --- 2010-06-18 01:09:28 - cvsupping the source tree TB --- 2010-06-18 01:09:28 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile TB --- 2010-06-18 01:09:54 - building world TB --- 2010-06-18 01:09:54 - MAKEOBJDIRPREFIX=/obj TB --- 2010-06-18 01:09:54 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-06-18 01:09:54 - TARGET=ia64 TB --- 2010-06-18 01:09:54 - TARGET_ARCH=ia64 TB --- 2010-06-18 01:09:54 - TZ=UTC TB --- 2010-06-18 01:09:54 - __MAKE_CONF=/dev/null TB --- 2010-06-18 01:09:54 - cd /src TB --- 2010-06-18 01:09:54 - /usr/bin/make -B buildworld >>> World build started on Fri Jun 18 01:09:54 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Jun 18 02:32:22 UTC 2010 TB --- 2010-06-18 02:32:22 - generating LINT kernel config TB --- 2010-06-18 02:32:22 - cd /src/sys/ia64/conf TB --- 2010-06-18 02:32:22 - /usr/bin/make -B LINT TB --- 2010-06-18 02:32:22 - building LINT kernel TB --- 2010-06-18 02:32:22 - MAKEOBJDIRPREFIX=/obj TB --- 2010-06-18 02:32:22 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-06-18 02:32:22 - TARGET=ia64 TB --- 2010-06-18 02:32:22 - TARGET_ARCH=ia64 TB --- 2010-06-18 02:32:22 - TZ=UTC TB --- 2010-06-18 02:32:22 - __MAKE_CONF=/dev/null TB --- 2010-06-18 02:32:22 - cd /src TB --- 2010-06-18 02:32:22 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Jun 18 02:32:22 UTC 2010 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] rm -f hack.c MAKE=/usr/bin/make sh /src/sys/conf/newvers.sh LINT cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror vers.c linking kernel subr_trap.o(.text+0x290): In function `syscallenter': : undefined reference to `systrace_probe_func' subr_trap.o(.text+0x291): In function `syscallenter': : undefined reference to `systrace_probe_func' *** Error code 1 Stop in /obj/ia64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-06-18 02:49:53 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-06-18 02:49:53 - ERROR: failed to build lint kernel TB --- 2010-06-18 02:49:53 - 4779.91 user 744.11 system 6041.80 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-ia64-ia64.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Anyone running GNOME on 9-CURRENT? How do you convince evolution-data-server to build?
Hi there, On Fri, Jun 18, 2010 at 06:57:56AM +0800, Buganini wrote: > I'm using it without problem, > do you have any of *_HEIMDAL or *_KERBEROS in make.conf/src.conf? No. The problem, as far as I can tell, is that the search for krb5 in the configure script tests three options, (mit, heimdal and sun) all of which fail. The heimdal test *should* have succeeded, because the linker flags are (correctly) generated by a call to `/usr/bin/krb5-config gssapi --libs` (this is one of the port patches against the up-stream script. The problem is that those flags haven't actually worked for quite a while (on my system, anyway). Vis: configure:16119: cc -o conftest -O2 -pipe -g -DLDAP_DEPRECATED -fno-strict-aliasing -I/usr/local/include -I/usr/local/include/db4 1 -L/usr/local/lib -pthread conftest.c -L/usr/lib -L/usr/lib -lgssapi -lheimntlm -lkrb5 -lhx509 -lcom_err -lcrypto -lasn1 -lro ken -lcrypt >&5 /usr/lib/libhx509.so: undefined reference to `MD2_Init' /usr/lib/libhx509.so: undefined reference to `MD2_Final' /usr/lib/libhx509.so: undefined reference to `MD2_Update' configure:16119: $? = 1 Now what I don't understand is why the linker fails to find those symbols, given that they *are* defined in libcrypto, which is also listed on the linker command line there. I suspect that it has something to do with the way that shared libraries are constructed: they seem to contain their own list of dependencies, and somehow /usr/lib/libhx509.so.10 does *not* know that it depends on /lib/libcrypto.so.6 (ldd shows only a dependency on /lib/libc.so.7). I regret that I don't know enough linker fu or make infrastructure fu to know where to suggest a tweak, but I believe that the necessary tweak is to the base system build of libhx509.so, rather than the ports in question. What I *really* don't understand is why this seems to be working for everyone else... (My system was last re-built from csup'd source on Thursday 17 June, by the way, so it's not out of date.) Cheers, -- Andrew ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Dell Perc 5/i Performance issues
On Jun 17, 2010, at 4:50 PM, oizs wrote: > I've bought a Dell Perc 5/i because I couldn't make the onboard marvell > 88sx7042 work with 8.0/8.1 or current, but as lucky as I am, the best I can > do with 4x1.5tb samsung in raid5 is 60MB/s writes and 90MB/s reads, with > bbu/write-back/adaptive-read-ahead. > > I was expecting at least twice of that, and I'm not sure what can I do to get > that speed. (I've read man 7 tuning with no success) Switch to using RAID-10 rather than RAID-5. It's normal for RAID-5 to have worse write performance than that of a single drive. Regards, -- -Chuck ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Dell Perc 5/i Performance issues
Hi, I've bought a Dell Perc 5/i because I couldn't make the onboard marvell 88sx7042 work with 8.0/8.1 or current, but as lucky as I am, the best I can do with 4x1.5tb samsung in raid5 is 60MB/s writes and 90MB/s reads, with bbu/write-back/adaptive-read-ahead. I was expecting at least twice of that, and I'm not sure what can I do to get that speed. (I've read man 7 tuning with no success) As far as I know this controller should be as fast as on other systems. (Freebsd.org mx1 has one of these cards.) I'm hoping somebody on the list reads this and helps because I can't afford to buy another card. Thanks in advance, -zsozso ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Anyone running GNOME on 9-CURRENT? How do you convince evolution-data-server to build?
I'm using it without problem, do you have any of *_HEIMDAL or *_KERBEROS in make.conf/src.conf? -- Buganini On Fri, Jun 18, 2010 at 6:50 AM, Andrew Reilly wrote: > I've been trying on-and-off for weeks, and haven't been able to > crack it. The configure script goes looking for Kerberos 5 and > can't find it, even though it's in the base. > > Cheers, > > -- > Andrew > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Anyone running GNOME on 9-CURRENT? How do you convince evolution-data-server to build?
I've been trying on-and-off for weeks, and haven't been able to crack it. The configure script goes looking for Kerberos 5 and can't find it, even though it's in the base. Cheers, -- Andrew ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Having a problem with security/libassuan-1 when compiling gnupg.
[ FYI, this message should have gone to freebsd-po...@freebsd.org ... ]
On 06/17/10 11:20, Kevin Oberman wrote:
2.0.0 should be the preferred version, but its API is incompatible with
the old one. Many ports using libassuan (listed in UPDATING) have not
been updated to support V2, so the libassuan-1 port was created.
As soon as deskutils/kdepim4 and security/{dirmngr|gnupg|gpa|opensc} are
updated, there will be a need to move to 2.0.0.
Well, I just made it a lot worse. :) As Kevin points out here, the new
version of libassuan is not compatible with the old. This decision on
the part of the gnupg folks has its merits, but is unarguably
inconvenient during the transition.
On May 11th I approached the authors of the ports that depend on
libassuan asking about their plans for updating (minus ale@
unfortunately, opensc's dependency is conditional, thus I missed it
until I grep'ed the tree instead of relying on INDEX). The status of the
affected ports is as follows:
1. gnupgAlready handled because 2.0.15 required the update
2. dirmngr They had an RC ready to go, which they released after I poked
them a bit. :)
So these first 2 are now done.
3. kdepim4 My understanding is that the version currently under
development has support for libassuan 2.0.0, and will be released in
August. The kde@ folks have indicated that if there is a need to update
it sooner they can most likely do that based on patches that are
currently available.
4. gpa The svn version supports assuan 2.0.0, but the release of this
new version has not yet been scheduled.
5. opensc ale@ has indicated that he would prefer to wait to update his
port until a new version that supports assuan 2.0.0 is released.
> I am unsure what happens when some ports want v1 and others want v2.
> This may not be an issue if the updated ports can be deal with either
> API, but I have no idea whether that is the case.
The current situation is that having both versions installed is
incompatible. My preference would be that the maintainers of the
affected ports upgrade to depend on assuan 2.0.0 and then we can remove
libassuan-1. If it becomes necessary to support having both versions
installed then "Plan C" at this point would be to modify libassuan-1 to
support this.
hth,
Doug
--
... and that's just a little bit of history repeating.
-- Propellerheads
Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [CFT] BSDL iconv in base system
El 2010. 06. 17. 23:21, Anonymous escribió: Gabor Kovesdan writes: [...] $ make installworld TARGET=i386 DESTDIR=/b/bbb ... ===> usr.bin/mkcsmapper (install) install -s -o root -g wheel -m 555 mkcsmapper /b/bbb/usr/bin strip: /b/bbb/usr/bin/mkcsmapper: File format not recognized install: wait: No such file or directory *** Error code 70 If cross-compiling doesn't work, how did you build the former one that gave you that error? Here is my guess libiconv_modules compiles fine but installs both normal and lib32 objdir into /usr/lib when lib32 should use /usr/lib32. Oh, this seems like a relevant guess. I'll have to handle it in the Makefile then by checking if we are cross-compiling and I'll also have to add an #ifdef or something in the libc part to select the module path conditionally. mkcsmapper/mkesdb are failing to install because they're treated as build-tools for host system and never compiled for target system. However, they're not included in lib32 target and so are not built for i386 arch during normal buildworld on amd64 host where host = target. Yes, another good catch. Thanks a lot for your comments. -- Gabor Kovesdan FreeBSD Volunteer EMAIL: ga...@freebsd.org .:|:. ga...@kovesdan.org WEB: http://people.FreeBSD.org/~gabor .:|:. http://kovesdan.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [CFT] BSDL iconv in base system
Gabor Kovesdan writes: [...] >>$ make installworld TARGET=i386 DESTDIR=/b/bbb >>... >>===> usr.bin/mkcsmapper (install) >>install -s -o root -g wheel -m 555 mkcsmapper /b/bbb/usr/bin >>strip: /b/bbb/usr/bin/mkcsmapper: File format not recognized >>install: wait: No such file or directory >>*** Error code 70 >> > If cross-compiling doesn't work, how did you build the former one that > gave you that error? Here is my guess libiconv_modules compiles fine but installs both normal and lib32 objdir into /usr/lib when lib32 should use /usr/lib32. mkcsmapper/mkesdb are failing to install because they're treated as build-tools for host system and never compiled for target system. However, they're not included in lib32 target and so are not built for i386 arch during normal buildworld on amd64 host where host = target. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [CFT] BSDL iconv in base system
ok. after installing world i get this when bootingt up: Starting powerd. Starting musicpd. path: invalid filesystem charset: ISO-8859-15 /usr/lib/i18n/libiconv_std.so.4: unsupported file layout/usr/lib/i18n/libiconv_std.so.4: unsupported file layout/usr/lib/i18n/libiconv_std.so.4: unsupported file layout/usr/lib/i18n/libiconv_std.so.4: unsupported file layout/usr/lib/i18n/libiconv_std.so.4: unsupported file layout pid 1078 (mpd), uid 1001: exited on signal 6 Abort trap /etc/rc: WARNING: failed to start musicpd Starting mpdscribble. GLib: Cannot convert message: Conversion from character set 'UTF-8' to 'ASCII' is not supported /usr/lib/i18n/libiconv_std.so.4: unsupported file layout/usr/lib/i18n/libiconv_std.so.4: unsupported file layout/usr/lib/i18n/libiconv_std.so.4: unsupported file layout/usr/lib/i18n/libiconv_std.so.4: unsupported file layoutoption parsing failed: Conversion from character set 'ASCII' to 'UTF-8' is not supported /etc/rc: WARNING: failed to start mpdscribble Seems like the very same error that was already reported.Was it just a normal build? I never got such a result but will look into the Makefiles to find out how ia32 compatibility works. -- Gabor Kovesdan FreeBSD Volunteer EMAIL: ga...@freebsd.org .:|:. ga...@kovesdan.org WEB: http://people.FreeBSD.org/~gabor .:|:. http://kovesdan.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [CFT] BSDL iconv in base system
Does it respect lib32?
I don't know to much about the ia32 compatibility layer but I used
conventional FreeBSD Makefiles to build the stuff. I'll try to figure
out what's going wrong but unfortunately I don't have an amd64 test
machine to build.
$ iconv -f ascii
iconv: iconv_open(UTF-8, ascii): Invalid argument
/usr/lib/i18n/libiconv_std.so.4: unsupported file layoutzsh: exit 1
iconv -f ascii
$ file /usr/lib/i18n/libiconv_std.so.4
/usr/lib/i18n/libiconv_std.so.4: ELF 32-bit LSB shared object, Intel 80386,
version 1 (FreeBSD), dynamically linked, stripped
$ uname -vm
FreeBSD 9.0-CURRENT #0 r209191=1463b20-dirty: Tue Jun 15 04:59:40 UTC 2010
h...@raphael.local:/a/objdir/a/dirty_build/sys/PHOENIX amd64
BTW, I tried to crosscompile i386 and got error on installing
usr.bin/{mkesdb,mkcsmapper}.
$ make installworld TARGET=i386 DESTDIR=/b/bbb
...
===> usr.bin/mkcsmapper (install)
install -s -o root -g wheel -m 555 mkcsmapper /b/bbb/usr/bin
strip: /b/bbb/usr/bin/mkcsmapper: File format not recognized
install: wait: No such file or directory
*** Error code 70
If cross-compiling doesn't work, how did you build the former one that
gave you that error?
--
Gabor Kovesdan
FreeBSD Volunteer
EMAIL: ga...@freebsd.org .:|:. ga...@kovesdan.org
WEB: http://people.FreeBSD.org/~gabor .:|:. http://kovesdan.org
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Having a problem with security/libassuan-1 when compiling gnupg.
> Date: Thu, 17 Jun 2010 13:00:42 -0500
> From: eculp
>
> Quoting Kevin Oberman :
>
> >> Date: Thu, 17 Jun 2010 12:03:48 -0500
> >> From: eculp
> >> Sender: owner-freebsd-curr...@freebsd.org
> >>
> >> Having a problem with security/libassuan-1 when compiling gnupg. I
> >> did the upgrade to libassuan-2.0.0 following the instructions in
> >> UPDATING and this is the first problem that I have seen.
> >>
> >> ===> gnupg-2.0.14_3 depends on package: libassuan-1>=1.0.5 - not found
> >> ===>Verifying install for libassuan-1>=1.0.5 in
> >> /usr/ports/security/libassua
> >> n-1
> >>
> >> ===> libassuan-1-1.0.5 conflicts with installed package(s):
> >>libassuan-2.0.0
> >>
> >>They install files into the same place.
> >>Please remove them first with pkg_delete(1).
> >> *** Error code 1
> >>
> >> Stop in /usr/ports/security/libassuan-1.
> >> *** Error code 1
> >>
> >> Stop in /usr/ports/security/gnupg.
> >>
> >> ===>>> make failed for security/gnupg
> >> ===>>> Aborting update
> >>
> >> Any suggestions will be appreciated.
> >
> > Sorry. Just re-read the message.
> >
> > Since you already have libassuan-2.0.0 installed, you will probably need
> > to:
> > pkg_delete -f libassuan-2.0.0
> > portinstall libassuan-1
> > or
> > portmaster security/libassuan-1
>
>
> Thanks a lot, Kevin. It is now working fin as far as I can tell. I
> was confused as to which was the prefered version for Current and was
> sure that I had seen somewhere that is was 2.x but was probably
> confused with another port.
2.0.0 should be the preferred version, but its API is incompatible with
the old one. Many ports using libassuan (listed in UPDATING) have not
been updated to support V2, so the libassuan-1 port was created.
As soon as deskutils/kdepim4 and security/{dirmngr|gnupg|gpa|opensc} are
updated, there will be a need to move to 2.0.0. I am unsure what happens
when some ports want v1 and others want v2. This may not be an issue if
the updated ports can be deal with either API, but I have no idea
whether that is the case.
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: ober...@es.net Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Having a problem with security/libassuan-1 when compiling gnupg.
Quoting Kevin Oberman : Date: Thu, 17 Jun 2010 12:03:48 -0500 From: eculp Sender: owner-freebsd-curr...@freebsd.org Having a problem with security/libassuan-1 when compiling gnupg. I did the upgrade to libassuan-2.0.0 following the instructions in UPDATING and this is the first problem that I have seen. ===> gnupg-2.0.14_3 depends on package: libassuan-1>=1.0.5 - not found ===>Verifying install for libassuan-1>=1.0.5 in /usr/ports/security/libassua n-1 ===> libassuan-1-1.0.5 conflicts with installed package(s): libassuan-2.0.0 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Stop in /usr/ports/security/libassuan-1. *** Error code 1 Stop in /usr/ports/security/gnupg. ===>>> make failed for security/gnupg ===>>> Aborting update Any suggestions will be appreciated. Sorry. Just re-read the message. Since you already have libassuan-2.0.0 installed, you will probably need to: pkg_delete -f libassuan-2.0.0 portinstall libassuan-1 or portmaster security/libassuan-1 Thanks a lot, Kevin. It is now working fin as far as I can tell. I was confused as to which was the prefered version for Current and was sure that I had seen somewhere that is was 2.x but was probably confused with another port. Thanks again, ed -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Having a problem with security/libassuan-1 when compiling gnupg.
> Date: Thu, 17 Jun 2010 12:03:48 -0500 > From: eculp > Sender: owner-freebsd-curr...@freebsd.org > > Having a problem with security/libassuan-1 when compiling gnupg. I > did the upgrade to libassuan-2.0.0 following the instructions in > UPDATING and this is the first problem that I have seen. > > ===> gnupg-2.0.14_3 depends on package: libassuan-1>=1.0.5 - not found > ===>Verifying install for libassuan-1>=1.0.5 in > /usr/ports/security/libassua > n-1 > > ===> libassuan-1-1.0.5 conflicts with installed package(s): >libassuan-2.0.0 > >They install files into the same place. >Please remove them first with pkg_delete(1). > *** Error code 1 > > Stop in /usr/ports/security/libassuan-1. > *** Error code 1 > > Stop in /usr/ports/security/gnupg. > > ===>>> make failed for security/gnupg > ===>>> Aborting update > > Any suggestions will be appreciated. Sorry. Just re-read the message. Since you already have libassuan-2.0.0 installed, you will probably need to: pkg_delete -f libassuan-2.0.0 portinstall libassuan-1 or portmaster security/libassuan-1 -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Having a problem with security/libassuan-1 when compiling gnupg.
> Date: Thu, 17 Jun 2010 12:03:48 -0500 > From: eculp > Sender: owner-freebsd-curr...@freebsd.org > > Having a problem with security/libassuan-1 when compiling gnupg. I > did the upgrade to libassuan-2.0.0 following the instructions in > UPDATING and this is the first problem that I have seen. > > ===> gnupg-2.0.14_3 depends on package: libassuan-1>=1.0.5 - not found > ===>Verifying install for libassuan-1>=1.0.5 in > /usr/ports/security/libassua > n-1 > > ===> libassuan-1-1.0.5 conflicts with installed package(s): >libassuan-2.0.0 > >They install files into the same place. >Please remove them first with pkg_delete(1). > *** Error code 1 > > Stop in /usr/ports/security/libassuan-1. > *** Error code 1 > > Stop in /usr/ports/security/gnupg. > > ===>>> make failed for security/gnupg > ===>>> Aborting update > > Any suggestions will be appreciated. > > TIA, > > ed > > Kernel: > 9.0-CURRENT FreeBSD 9.0-CURRENT #6: Sun Jun 6 06:23:48 CDT 2010 > > Today's world. > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > Read /usr/ports/UPDATING. Should be the first entry. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: an addition to top(1)
On Sat, 19 Dec 1998, Andy Farkas wrote: I've always thought that top(1) should display the system uptime. Here's a patch. The code was cut straight out of /usr/src/usr.bin/w/w.c My apologies for a late reply :) but that code displays 30 seconds longer uptime than what it really is. See PR bin/147934 at http://www.freebsd.org/cgi/query-pr.cgi?pr=147934 for more details and a patch. Best Regards, -- Janne Snabb / EPIPE Communications sn...@epipe.com - http://epipe.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Having a problem with security/libassuan-1 when compiling gnupg.
Having a problem with security/libassuan-1 when compiling gnupg. I did the upgrade to libassuan-2.0.0 following the instructions in UPDATING and this is the first problem that I have seen. ===> gnupg-2.0.14_3 depends on package: libassuan-1>=1.0.5 - not found ===>Verifying install for libassuan-1>=1.0.5 in /usr/ports/security/libassua n-1 ===> libassuan-1-1.0.5 conflicts with installed package(s): libassuan-2.0.0 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Stop in /usr/ports/security/libassuan-1. *** Error code 1 Stop in /usr/ports/security/gnupg. ===>>> make failed for security/gnupg ===>>> Aborting update Any suggestions will be appreciated. TIA, ed Kernel: 9.0-CURRENT FreeBSD 9.0-CURRENT #6: Sun Jun 6 06:23:48 CDT 2010 Today's world. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: devd and/or ACPI not reporting a heat problem
In message: <4c187778.9060...@freebsd.org>
Doug Barton writes:
: Howdy,
:
: I thought my heat problems were over with this laptop thanks to all
: the great suggestions I've received about powerd, no stepping, etc. (I
: also propped up both the back and the front to make a nice big air
: pocket.) I've always been pretty religious about blowing the dust off
: the fans and heat sinks, but I guess it's been dustier than I thought
: lately because I finally "caught" my laptop doing what it's been doing
: for the last 2 weeks, which is (occasionally) powering down when it
: was unattended; and the problem was heat.
:
: Of course I've been running devd all along, and so I initially ruled
: out the heat problem due to this entry in devd.conf:
:
: # Notify all users before beginning emergency shutdown when we get
: # a _CRT or _HOT thermal event and we're going to power down the system
: # very soon.
: notify 10 {
: match "system" "ACPI";
: match "subsystem" "Thermal";
: match "notify" "0xcc";
: action "logger -p kern.emerg 'WARNING: system temperature too high,
: shutting down soon!'";
: };
:
: I'm not getting any of those notices in the logs, so I was looking
: other places. (I do get other ACPI-related activity from devd, such as
: the notice that it's going on and off AC power.)
:
: So, 2-part question, how can I make sure that devd gets the message,
: and how do I make sure that the notice comes _before_ the BIOS forces
: the system to power off. I.e., I'd like to have some sort of devd
: notice that comes in time to do a clean shutdown, or perhaps some
: other mitigation strategy prior to the BIOS taking over.
You may need a simple cron entry that checks the temperature and
report when it is getting close. acpi should be reporting thermal
events before then that aren't 0xcc, but if not, that's the fallback
that people use.
Sadly, at least for one of my laptops, I've seen sudden 10-20C spikes
which trigger this. I think this laptop is badly broken, and don't
use it any more.
Warner
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r209240 ia64 -> buildworld -> undefined reference to `lzma_physmem'
On 06/17/2010 06:15, Anton Shterenlikht wrote: > I've r209203 kernel on ia64 box. > Now I'm trying to rebuild world to r209240. > I get these errors. > > Please advise > grep -rn lzma_physmem /usr/include ? /usr/include/lzma/hardware.h:51:extern LZMA_API(uint64_t) lzma_physmem(void) lzma_nothrow; I would suggest updating your headers if something similar is not found & try rebuilding world with -DALWAYS_CHECK_MAKE. You should be able to continue your build after this. -DNO_CLEAN will get you through it. Regards, -- jhell ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: how to set up UTF8 russian in -current?
On Thu, Jun 17, 2010 at 08:20:00AM +0400, Andrey V. Elsukov wrote: > On 17.06.2010 5:57, Alexandre "Sunny" Kovalenko wrote: > > Can you specifically point out things that do not work for you in the > > xterm window? I am able to create files and directories with Cyrillic > > names, use Cyrillic strings as the command parameters, etc. It has been > > working for me for quite a long time, so I could not really remember > > what, if anything, I had to do, but we can compare settings if you'd > > like to. I do use Gnome, though, so some of its pixie dust could have > > been spilled onto xterm. > > > > I have attached small screenshot as an illustration -- if this is not > > what you are talking about, please, accept my apology for the noise. > > I think Anton said about console localization (not X Window). well, after Ed's reply I got console localisation back. It was apparently TEKEN_* option in kernel that broke it. I'm struggling to get console localisation in xterm. Here's a small example of what I get: http://seis.bris.ac.uk/~mexas/xterm-mangled-russian.png I have this in /etc/rc.conf: font8x8="cp866-8x8" font8x14="cp866-8x14" font8x16="cp866b-8x16" keymap="ru.koi8-r" scrnmap="koi8-r2cp866" And these environment variables in shell: LANG=en_US.ISO8859-1 LC_CTYPE=ru_RU.KOI8-R TERM=xterm XTERM_VERSION=XTerm(258) XTERM_LOCALE=ru_RU.KOI8-R XTERM_SHELL=/bin/tcsh many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
r209240 ia64 -> buildworld -> undefined reference to `lzma_physmem'
I've r209203 kernel on ia64 box. Now I'm trying to rebuild world to r209240. I get these errors. Please advise many thanks anton crunchide -k _crunched_vi_stub vi.lo ld -dc -r -o id.lo id_stub.o /usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/id/id.o crunchide -k _crunched_id_stub id.lo ld -dc -r -o chroot.lo chroot_stub.o /usr/obj/usr/src/rescue/rescue//usr/src/usr.sbin/chroot/chroot.o crunchide -k _crunched_chroot_stub chroot.lo ld -dc -r -o chown.lo chown_stub.o /usr/obj/usr/src/rescue/rescue//usr/src/usr.sbin/chown/chown.o crunchide -k _crunched_chown_stub chown.lo cc -static -o rescue rescue.o cat.lo chflags.lo chio.lo chmod.lo cp.lo date.lo dd.lo df.lo echo.lo ed.lo exp .lo getfacl.lo hostname.lo kenv.lo kill.lo ln.lo ls.lo mkdir.lo mv.lo pkill.lo ps.lo pwd.lo realpath.lo rm.l rmdir.lo setfacl.lo sh.lo stty.lo sync.lo test.lo rcp.lo csh.lo atacontrol.lo badsect.lo camcontrol.lo ccdc nfig.lo clri.lo devfs.lo dmesg.lo dump.lo dumpfs.lo dumpon.lo fsck.lo fsck_ffs.lo fsck_msdosfs.lo fsdb.lo fs rand.lo gbde.lo geom.lo ifconfig.lo init.lo kldconfig.lo kldload.lo kldstat.lo kldunload.lo ldconfig.lo md5. o mdconfig.lo mdmfs.lo mknod.lo mount.lo mount_cd9660.lo mount_msdosfs.lo mount_nfs.lo mount_ntfs.lo mount_n llfs.lo mount_udf.lo mount_unionfs.lo newfs.lo newfs_msdos.lo nos-tun.lo ping.lo reboot.lo restore.lo rcorde .lo route.lo routed.lo rtquery.lo rtsol.lo savecore.lo spppcontrol.lo swapon.lo sysctl.lo tunefs.lo umount.l atmconfig.lo ping6.lo ipf.lo zfs.lo zpool.lo mca.lo dhclient.lo head.lo mt.lo sed.lo tail.lo tee.lo gzip.lo bzip2.lo xz.lo tar.lo vi.lo id.lo chroot.lo chown.lo /usr/obj/usr/src/rescue/rescue/../librescue/exec.o /usr obj/usr/src/rescue/rescue/../librescue/getusershell.o /usr/obj/usr/src/rescue/rescue/../librescue/login_clas .o /usr/obj/usr/src/rescue/rescue/../librescue/popen.o /usr/obj/usr/src/rescue/rescue/../librescue/rcmdsh.o usr/obj/usr/src/rescue/rescue/../librescue/sysctl.o /usr/obj/usr/src/rescue/rescue/../librescue/system.o -lc ypt -ledit -lkvm -ll -ltermcap -lutil -lalias -lcam -lcurses -ldevstat -lipsec -lipx -lzfs -lnvpair -luutil lavl -lgeom -lbsdxml -ljail -lkiconv -lmd -lreadline -lsbuf -lufs -lz -lbz2 -llzma -larchive -lcrypto -lm xz.lo(.text+0x5672): In function `hardware_init': : undefined reference to `lzma_physmem' xz.lo(.text+0x6a42): In function `list_file': : undefined reference to `lzma_index_memused' xz.lo(.text+0x6c62): In function `list_file': : undefined reference to `lzma_index_stream_flags' xz.lo(.text+0x6c92): In function `list_file': : undefined reference to `lzma_index_stream_padding' xz.lo(.text+0x6e22): In function `list_file': : undefined reference to `lzma_index_stream_count' xz.lo(.text+0x6e52): In function `list_file': : undefined reference to `lzma_index_block_count' xz.lo(.text+0x6ee2): In function `list_file': : undefined reference to `lzma_index_checks' xz.lo(.text+0x6f32): In function `list_file': : undefined reference to `lzma_index_stream_count' xz.lo(.text+0x6f52): In function `list_file': : undefined reference to `lzma_index_block_count' xz.lo(.text+0x6fd2): In function `list_file': : undefined reference to `lzma_index_checks' xz.lo(.text+0x70f2): In function `list_file': : undefined reference to `lzma_index_iter_init' xz.lo(.text+0x7122): In function `list_file': : undefined reference to `lzma_index_iter_next' xz.lo(.text+0x7252): In function `list_file': : undefined reference to `lzma_index_stream_count' xz.lo(.text+0x7292): In function `list_file': : undefined reference to `lzma_index_block_count' xz.lo(.text+0x73d2): In function `list_file': : undefined reference to `lzma_index_checks' xz.lo(.text+0x74b2): In function `list_file': : undefined reference to `lzma_index_stream_count' xz.lo(.text+0x74f2): In function `list_file': : undefined reference to `lzma_index_block_count' xz.lo(.text+0x7632): In function `list_file': : undefined reference to `lzma_index_checks' xz.lo(.text+0x77e2): In function `list_file': : undefined reference to `lzma_index_stream_count' xz.lo(.text+0x7802): In function `list_file': : undefined reference to `lzma_index_block_count' xz.lo(.text+0x7862): In function `list_file': : undefined reference to `lzma_index_checks' xz.lo(.text+0x78a2): In function `list_file': : undefined reference to `lzma_index_stream_count' xz.lo(.text+0x7922): In function `list_file': : undefined reference to `lzma_index_iter_init' xz.lo(.text+0x7962): In function `list_file': : undefined reference to `lzma_index_iter_next' xz.lo(.text+0x7ae2): In function `list_file': : undefined reference to `lzma_index_iter_rewind' xz.lo(.text+0x7b42): In function `list_file': : undefined reference to `lzma_index_iter_next' xz.lo(.text+0x7ec2): In function `list_file': : undefined reference to `lzma_index_stream_count' xz.lo(.text+0x7ee2): In function `list_file': : undefined reference to `lzma_index_block_count' xz.lo(.text+0x7f62): In function `list_file': : undefined reference to `lzma_index_iter_init' xz.lo(.text+0
Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
- Original Message
>> From: Ganbold
>> To: PseudoCylon
>> Cc: freebsd-current@freebsd.org; Ganbold Tsagaankhuu
>> Sent: Wed, June 16, 2010 6:33:47 AM
>> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>>
>> AK-san,
>
>PseudoCylon wrote:
>>>
>
>Strange, looks like this time works as expected, but sometimes it
>doesn't work.
>
>In some cases it doesn't work and you can find complete tcpdump output
> from very beginning to the modem hang:
>
Hello,
Are following true?
When manually load/reload hostapd, works
When loaded by rc.conf, doesn't work
If so, please try attached patch. (patch to if_run.c only) Or, here is a
patched file.
http://gitorious.org/run/run/blobs/raw/cmdq_fix/dev/usb/wlan/if_run.c
When auto-loading, the driver is brought up and down a few times. It might be
the cause. So, when you test, please reboot rspro and let rc.conf handle init
process rather than manually start driver/hostapd. And
#arp -d -a
on rspro, freebsd laptop. and macbook would help for testing. (If it works on
mac) So, that clients have to send arp request. If macbook receives "who-has
192.168.1.50" arp request packets, it should work. If macbook supports
# tcpdump -vv -xxx -i wlan0 'arp'
and see if macbook gets this.
19:34:30.469720 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
192.168.1.50 tell 192.168.1.1, length 46
0x: 0030 5462 3d24 0806 0001
0x0010: 0800 0604 0001 0030 5462 3d24 c0a8 0101
0x0020: c0a8 0132
0x0030:
AK
-- begin patch --
diff --git a/dev/usb/wlan/if_run.c b/dev/usb/wlan/if_run.c
index e4fc8d2..f302246 100644
--- a/dev/usb/wlan/if_run.c
+++ b/dev/usb/wlan/if_run.c
@@ -17,7 +17,7 @@
*/
#include
-__FBSDID("$FreeBSD: src/sys/dev/usb/wlan/if_run.c,v 1.11 2010/06/14 23:01:50
jkim Exp $");
+__FBSDID("$FreeBSD$");
/*-
* Ralink Technology RT2700U/RT2800U/RT3000U chipset driver.
@@ -830,9 +830,6 @@ run_vap_create(struct ieee80211com *ic,
if(sc->rvp_cnt++ == 0)
ic->ic_opmode = opmode;
-if(opmode == IEEE80211_M_HOSTAP)
-sc->cmdq_run = RUN_CMDQ_GO;
-
DPRINTF("rvp_id=%d bmap=%x rvp_cnt=%d\n",
rvp->rvp_id, sc->rvp_bmap, sc->rvp_cnt);
@@ -894,7 +891,9 @@ run_cmdq_cb(void *arg, int pending)
for(i = sc->cmdq_exec; sc->cmdq[i].func && pending;
i = sc->cmdq_exec, pending--){
DPRINTFN(6, "cmdq_exec=%d pending=%d\n", i, pending);
-if(sc->cmdq_run == RUN_CMDQ_GO){
+if(sc->cmdq_run == RUN_CMDQ_GO ||
+(sc->cmdq_key_set == RUN_CMDQ_GO &&
+sc->cmdq[i].func == run_key_set_cb)){
/*
* If arg0 is NULL, callback func needs more
* than one arg. So, pass ptr to cmdq struct.
@@ -4798,7 +4797,7 @@ run_stop(void *arg)
ifp->if_drv_flags &= ~(IFF_DRV_RUNNING | IFF_DRV_OACTIVE);
sc->ratectl_run = RUN_RATECTL_OFF;
-sc->cmdq_run = sc->cmdq_key_set;
+sc->cmdq_run = RUN_CMDQ_ABORT;
RUN_UNLOCK(sc);
-- end patch --
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ntpq: write to localhost failed: Network is unreachable
On Wed, Jun 16, 2010 at 07:07:07PM +0100, Matthew Seaman wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 16/06/2010 18:15:32, Anton Shterenlikht wrote: > > On Wed, Jun 16, 2010 at 06:08:35PM +0100, Matthew Seaman wrote: > >> -BEGIN PGP SIGNED MESSAGE- > >> Hash: SHA1 > >> > >> On 16/06/2010 17:59:10, Anton Shterenlikht wrote: > >>> After a recent upgrade to r209156 I get this error: > >>> > >>> $ ntpq -p > >>> ntpq: write to localhost failed: Network is unreachable > >>> > >>> Please advise > >> > >> What does 'ifconfig -a' and 'netstat -rn' say? > > > > $ ifconfig -a > > em0: flags=8843 metric 0 mtu 1500 > > > > options=209b > > ether 00:13:21:5b:05:1c > > inet 137.222.187.28 netmask 0xff00 broadcast 137.222.187.255 > > inet6 fe80::213:21ff:fe5b:51c%em0 prefixlen 64 scopeid 0x1 > > nd6 options=29 > > media: Ethernet autoselect (1000baseT ) > > status: active > > em1: flags=8802 metric 0 mtu 1500 > > > > options=209b > > ether 00:13:21:5b:05:1d > > media: Ethernet autoselect (100baseTX ) > > status: active > > lo0: flags=8049 metric 0 mtu 16384 > > options=3 > > inet 127.0.0.1 netmask 0xff00 > > inet6 ::1 prefixlen 128 > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > > nd6 options=21 > > > > $ netstat -rn > > Routing tables > > > > Internet: > > DestinationGatewayFlagsRefs Use Netif Expire > > default137.222.187.250UGS 065512em0 > > 127.0.0.1 link#3 UH 0 293lo0 > > 137.222.187.0/24 link#1 U 010861em0 > > 137.222.187.28 link#1 UHS 00lo0 > > > > Internet6: > > Destination Gateway Flags > > Netif Expire > > ::/96 ::1 UGRS > > lo0 > > ::1 ::1 UH > > lo0 > > :::0.0.0.0/96 ::1 UGRS > > lo0 > > fe80::/10 ::1 UGRS > > lo0 > > fe80::%em0/64 link#1U > > em0 > > fe80::213:21ff:fe5b:51c%em0 link#1UHS > > lo0 > > fe80::%lo0/64 link#3U > > lo0 > > fe80::1%lo0 link#3UHS > > lo0 > > ff01:1::/32 fe80::213:21ff:fe5b:51c%em0 U > > em0 > > ff01:3::/32 ::1 U > > lo0 > > ff02::/16 ::1 UGRS > > lo0 > > ff02::%em0/32 fe80::213:21ff:fe5b:51c%em0 U > > em0 > > ff02::%lo0/32 ::1 U > > lo0 > > > > > > > >> What happens if you try and ping localhost? > > > > $ ping -c5 localhost > > PING localhost (127.0.0.1): 56 data bytes > > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.109 ms > > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.103 ms > > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.060 ms > > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.059 ms > > 64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.059 ms > > > > --- localhost ping statistics --- > > 5 packets transmitted, 5 packets received, 0.0% packet loss > > round-trip min/avg/max/stddev = 0.059/0.078/0.109/0.023 ms > > Nothing obviously wrong there. Perhaps ntpd is not running? > (Not sure quite why that should cause an error message about > reachability of localhost: I suppose it's not completely unreasonable > though.) > > If ntpd is running, then try restarting it. If the problem still > persists, then it looks like you've found a bug. # ps ax | grep ntp 55043 ?? Rs 0:00.02 /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntpd.drif 55050 0 R+ 0:00.00 grep ntp # ntpq -p ntpq: write to localhost failed: Network is unreachable # /etc/rc.d/ntpd restart Stopping ntpd. Waiting for PIDS: 55043. Starting ntpd. # ps ax | grep ntp 55113 ?? Ss 0:00.02 /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntpd.drif 55127 0 R+ 0:00.00 grep ntp # ntpq -p ntpq: write to localhost failed: Network is unreachable # Matthew, many thanks for your help. I still think it's much more likely the error is due to my misconfiguration than a bug. I think I've seen something like this before, just can't find anything in mail archives. I'll try asking on @current list. thanks again anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 __
