Updating src tree:
P src/doc/3RDPARTY
P src/external/gpl3/gcc/dist/gcc/doc/cpp.1
P src/external/gpl3/gcc/dist/gcc/doc/cpp.info
P src/external/gpl3/gcc/dist/gcc/doc/g++.1
P src/external/gpl3/gcc/dist/gcc/doc/gcc.1
P src/external/gpl3/gcc/dist/gcc/doc/gcc.info
P src/external/gpl3/gcc/dist/gcc/doc/gc
With sources updated on 2016-07-06 at 23:59:55 UTC, I'm getting
dependall ===> external/gpl3/gcc/usr.bin/gcov
# symlink gcov/gmp.h
rm -f gmp.h
...
# symlink gcov/mpfr.h
rm -f mpfr.h
ln -s /build/netbsd-local/src/external/lgpl3/mpfr/dist/src/mpfr.h mpfr.h
#create gcov/.depend
rm -f .dep
On Tue, Jul 05, 2016 at 09:34:11PM +0200, Thomas Klausner wrote:
> On Tue, Jul 05, 2016 at 08:27:54PM +0100, Robert Swindells wrote:
> >
> > Thomas Klausner wrote:
> > >I've updated to a -current from today, and now three USB disks that
> > >attached fine a month ago don't provide any sd* devices
[...]
dependall ===> external/gpl3/gcc/usr.bin/libcpp
dependall ===> external/gpl3/gcc/usr.bin/libdecnumber
dependall ===> external/gpl3/gcc/usr.bin/gcov
# link gcov/gcov
/usr/src/obj/tooldir.NetBSD-7.99.33-amd64/bin/x86_64--netbsd-c++
--sysroot=/usr/src/obj/destdir.amd64 -pie -shared-libg
On Tue, Jul 05, 2016 at 06:31:17PM +0100, Jonathan Perkin wrote:
> Then name them PAX_MPROTECT_SKIP and PAX_ASLR_SKIP to follow
> CHECK_SHLIBS_SKIP, CHECK_INTERPRETER_SKIP, etc?
That name isn't very helpful in that it doesn't say what the default
action is. A better name would be something like PA
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2016.07.06.11.37.58.
An extract from the build.sh output follows:
--- dependall-lto-wrapper ---
--- collect-util
Hello,
On Fri, 1 Jul 2016 19:17:59 -0500 (CDT)
"John D. Baker" wrote:
> I decided to try building evbmips-mips64el with GCC 5.4 (-V HAVE_GCC=53).
> Starting with a completely empty OBJDIR/DESTDIR, etc., building eventually
> failed with:
>
> [...]
> --- ramdiskbin ---
> # link ramdisk/ram
co...@sdf.org writes:
> http://i.imgur.com/4f6rFVs.jpg ?
Yup! Just like that! :)
-tih
--
Elections cannot be allowed to change anything. --Dr. Wolfgang Schäuble
On Wed, Jul 06, 2016 at 11:48:01AM +0200, Tom Ivar Helbekkmo wrote:
> Oops again! The laptop had a really outdated BIOS. Upgrading gets me
> to a situation where nouveau tries to use the monitor for a console, but
> fails to bitmap it properly, so the screen looks like a psychedelic work
> of art
Tom Ivar Helbekkmo writes:
> Now I can build a kernel that'll try to use MSI with the wm0 on it.
With the updated BIOS, and ACPI enabled, MSI works fine on my wm0. :)
Note to self: always update the BIOS *first*, then look for other
possible problems.
-tih
--
Elections cannot be allowed to c
Tom Ivar Helbekkmo writes:
> Tom Ivar Helbekkmo writes:
>
>> nouveaufb0 at nouveau0
>> nouveau0: info: registered panic notifier
>>
>> ...and then it just sits there.
>
> Oops! Turns out it's not hung, it's just not displaying its console.
Oops again! The laptop had a really outdated BIOS. U
Masanobu SAITOH writes:
> I tried the latest -current and it didn't crash. Could you retry?
Never mind - I fixed it: I thought I'd upgraded the BIOS on this laptop
recently, but it turns out it was running a really old one. Flashing
the latest version available from Dell fixed the ACPI problem
On 2016/07/06 18:06, Tom Ivar Helbekkmo wrote:
Masanobu SAITOH writes:
I got a Latitude E6400 via an auction. I tried -current and it
worked with MSI. While checking your dmesg, I noticed that you
didn't use ACPI. I tried without ACPI and I could reproduce the
problem. Without ACPI, any ioapi
Masanobu SAITOH writes:
> I got a Latitude E6400 via an auction. I tried -current and it
> worked with MSI. While checking your dmesg, I noticed that you
> didn't use ACPI. I tried without ACPI and I could reproduce the
> problem. Without ACPI, any ioapic isn't attached. knakaraha said
> it migh
14 matches
Mail list logo