I have the same problem, that I resolve by changing boot order in the
bios settings to usb-drive as first boot device. (note, not in quick
boot order menu).
05.06.2013 22:11, Miguel Clara пишет:
> Done:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=179342
>
>
>
> On Wed, Jun 5, 2013 at 7:45 PM,
TB --- 2013-06-06 08:00:25 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-06-06 08:00:25 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-06-06 08:00:25 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-06-06 08:00:25 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-06-06 08:00:25 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-06-06 08:00:25 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-06-06 08:00:25 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-06-06 08:00:25 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-06-06 11:02:10 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-06-06 11:02:10 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-06-06 11:02:04 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-06-06 11:02:04 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-06-06 10:54:02 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-06-06 10:54:02 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-06-06 12:11:54 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-06-06 12:11:54 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-06-06 10:54:02 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-06-06 10:54:02 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-06-06 11:57:36 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-06-06 11:57:36 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-06-06 11:57:36 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-06-06 11:57:36 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
Looks like a bug upstream. If this port worked in FreeBSD-9, then the
difference might be the switch from gcc to clang. You could try
compiling the port with gcc. Just add these lines to /etc/make.conf
CC=gcc
CXX=g++
CPP=gcpp
Note: that will change the compiler used for ALL ports, as well as
k
Last time I've checked lxde was unfortunately not worth hassle.
e.g. it depends on /proc
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Can-t-compile-lxpanel-tp5817985p5818153.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
On Thu, 06 Jun 2013 09:19:20 -0600, asomers wrote:
> Looks like a bug upstream. If this port worked in FreeBSD-9, then the
> difference might be the switch from gcc to clang. You could try
> compiling the port with gcc. Just add these lines to /etc/make.conf
>
> CC=gcc CXX=g++
> CPP=gcpp
>
>
On Thu, 06 Jun 2013 08:37:10 -0700, Jakub Lach wrote:
> Last time I've checked lxde was unfortunately not worth hassle.
>
> e.g. it depends on /proc
>
Sorry, I'm no expert, but is that a problem? I routinely mount proc on
/proc in fstab. Is that what you are referring to? Is it undesirable to
d
On Sun, 2013-06-02 at 19:57 -0400, Rick Macklem wrote:
> Ian Lepore wrote:
> > On Sat, 2013-06-01 at 20:28 -0400, Rick Macklem wrote:
> > > Lars Eggert wrote:
> > > > Hi,
> > > >
> > > > to conclude this thread, the patch below allows one to specify an
> > > > nfs
> > > > rootfs via the ROOTDEVNAME
Hi All,
The system is:
-
% uname -a
FreeBSD test.bsam.ru 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r251470: Thu
Jun 6 20:18:03 SAMT 2013
b...@test.bsam.ru:/usr/obj/usr/src/sys/BB64X amd64
-
I try to use (a new and empty) DESTDIR and get this error at
installkernel:
-
[...]
===> zlib (ins
On Jun 6, 2013, at 18:21, Walter Hurry wrote:
> On Thu, 06 Jun 2013 09:19:20 -0600, asomers wrote:
>> Looks like a bug upstream. If this port worked in FreeBSD-9, then the
>> difference might be the switch from gcc to clang. You could try
>> compiling the port with gcc. Just add these lines to
On Jun 3, 2013, at 11:29 AM, Marcel Moolenaar wrote:
>
>> * Even if the python code is wrong, is this one of those things that's
>> going to keep biting us going forward? Interactions between
>> dlopen/dlsym/rtld/library dependencies/embedded malloc
>> replacements/etc has been accumulated a lar
On Thu, Jun 6, 2013 at 9:54 AM, Ian Lepore wrote:
> Well, I started out just testing Lars' patch (it works) but that
> inspired me to pick up the work I toyed with months ago in this area, to
> try to get BOOTP_NFSROOT to respect other root-path options such as
> setting vfs.root.mountfrom in the
on 06/06/2013 22:03 Boris Samorodov said the following:
> I try to use (a new and empty) DESTDIR and get this error at
> installkernel:
I think that 'make hierarchy' is expected in this case before any installation
actions.
--
Andriy Gapon
___
freebsd-
22 matches
Mail list logo