FreeBSD_HEAD_i386 - Build #4320 - Fixed

[jenkins-admin]

FreeBSD_HEAD_i386 - Build #4320 - Fixed:

Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4320/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4320/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4320/console

Change summaries:

309667 by delphij:
Fix typo.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: webcamd panic - is it just me?

[Anton Shterenlikht]

>From s...@freebsd.org Wed Dec  7 03:31:16 2016
>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215000
>>
>> I think this started after moving from 10.3 to 11.0.
>>
>> Does nobody else see this panic?
>
>I do not see that panic, however, I do suspect it is the specific cuse 
>module you are loading.  It is possible that you are loading a module 
>compiled for 10 when you are running 11.  Regardless, you should not be 
>loading cuse4bsd any longer.  cuse(4) is part of FreeBSD 11 now. 
>cuse_load="YES" is what you want.

Thanks for the hint. I'll try this.
If you are right, then the documentation is outdated:

WEBCAMD(8)  FreeBSD System Manager's Manual WEBCAMD(8)

*skip*

 webcamd requires the cuse4bsd(3) kernel module. To load the driver as a
 module at boot time, place the following line in loader.conf(5):

cuse4bsd_load="YES"

*skip*

AUTHORS
 webcamd was written by Hans Petter Selasky hsela...@freebsd.org.
 This man page was written by Dru Lavigne d...@freebsd.org.

FreeBSDSeptember 4, 2014   FreeBSD

Strange that there is no version in the last line.

Also:

# man 4 cuse
No manual entry for cuse

Did you mean cuse(3)?

Many thanks

Anton
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

emulators/qemu: qemu ports failing due to compiler error on 12-CURRENT

[O. Hartmann]

Hello out there.

I try my first steps in cross compiling ports with poudriere and therefore I 
try to setup
an appropriate jail and QEMU environment.

Well, I'm failing at the jail setup due to the non-exitence of any suitable QEMU
environment and for that I tried to figure out to find some proper HOWTO. 
Searching via google ave some hints, but in questions which QEMU from ports 
should be
used, all leave me alone, so I tried

emulators/qemu
emulators/qemu-devel
emulators/qemu-static

emulators/qemu is known for me to fail since months and the days of 11-CURRENT, 
there is a
compiler error spit out with clang 3.8 and now 3.9. The very same for 
qemu-devel (both
ports used with standard options, no extras). See also Bug 214873
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214873) and Bug 215100
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215100).

I tried also emulators/qemu-static, but it also fails compiling on most recent 
12-CURRENT
(as the others, too, also my poudriere environment, which has also CURRENT 
jails) with 

[...]
/usr/bin/ld:../config-host.ld:14: syntax error
c++: error: linker command failed with exit code 1 (use -v to see invocation)
[...]

in several occurences.

At the moment I feel lost at this point, since the likelyhood of all ports 
failing is
either incompatibility with CURRENT/clang 3.9 or something is weird with my 
setup. But on
the other hand, my poudriere environment is setup a kind of "vanilla" - no 
extras, just
straight forward compiler options.

I need some advice here how to build QEMU on my on.

Pleas CC me, I do not subscribe "freebsd-ports" list. And please apoligize for
crossposting, but I didn't really know to which list this might could belong 
to. 

Thanks in advance for patience and advice,

Oliver


-- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).


pgpqCHFB8tbV_.pgp
Description: OpenPGP digital signature

Re: Is there possible run a MacOS X binary

[Warner Losh]

On Mon, Dec 5, 2016 at 12:31 PM, Kevin P. Neal  wrote:
> On Mon, Dec 05, 2016 at 02:49:07PM -0300, Nilton Jose Rizzo wrote:
>>
>>
>>  Sorry for cross posting (-current and -ports)
>>
>>
>> Is there any emulator like linuxator to run Mac OS X binaries, or
>> is ther any licensing problem?
>
> It may be possible to make an emulator for Darwin (the OS that Mac OS sits
> on top of), but an emulator for Mac OS would probably require a legal copy
> of Mac OS.
>
> So, no, there is no Mac OS emulator for FreeBSD. And I'd be surprised if
> it ever happened.

NetBSD has (or had) a macho image activator, which is the first step
in this process. But Kevin is right that most of the functionality of
MacOS isn't in the kernel, and you'd need a copy of MacOS to run it in
emulation. Plus there's a lot of Mach code that MacOS depends on that
has no simple counterparts in FreeBSD, and that would be a lot of work
to make happen. It's one of the things that's a barrier to entry for a
simple, straight forward launchd port, for example.

Warner
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Is there possible run a MacOS X binary

[David Chisnall]

On 5 Dec 2016, at 19:31, Kevin P. Neal  wrote:
> 
>> Is there any emulator like linuxator to run Mac OS X binaries, or 
>> is ther any licensing problem?
> 
> It may be possible to make an emulator for Darwin (the OS that Mac OS sits
> on top of), but an emulator for Mac OS would probably require a legal copy
> of Mac OS.
> 

NetBSD started working on one, and had it at a state where it could run the 
Darwin version of XFree86 (which should give you some idea of how old it was), 
but it couldn’t run the Mac Window Server and I don’t think it’s maintained. 
It’s not very interesting, because you need all of the frameworks and programs 
from OS X for it to be useful, and the license prohibits using them in such a 
way (and even if you did get it to work, you wouldn’t be able to run Mac apps 
at the same time as X apps without running XQuartz, and at that point you may 
as well just run macOS).

There is a more recent project called Darling (https://www.darlinghq.org) that 
tries to run Mac apps on Linux using a custom Mach-O loader, bits of GNUstep, 
and some of their own stuff.  No one has ever tried using it on FreeBSD, to the 
best of my knowledge.  It’s GPLv3, so I’m not motivated to contribute to it 
(though it does incorporate some of my code in various places).

David



smime.p7s
Description: S/MIME cryptographic signature

Re: Is there possible run a MacOS X binary

[Matthieu Volat]

On Mon, 5 Dec 2016 14:31:06 -0500
"Kevin P. Neal"  wrote:

> On Mon, Dec 05, 2016 at 02:49:07PM -0300, Nilton Jose Rizzo wrote:
> > 
> > 
> >  Sorry for cross posting (-current and -ports)
> > 
> > 
> > Is there any emulator like linuxator to run Mac OS X binaries, or 
> > is ther any licensing problem?
> 
> It may be possible to make an emulator for Darwin (the OS that Mac OS sits
> on top of), but an emulator for Mac OS would probably require a legal copy
> of Mac OS.
> 
> So, no, there is no Mac OS emulator for FreeBSD. And I'd be surprised if
> it ever happened.
> 

You can have a look at darling  which aim to 
provide the macos(x) equivalent to wine (so, no kernel bits?), but given how 
I'm currently struggling with wine on FreeBSD, I would not bet this will work 
without some porting.

(Note that lots of parts of macos are closed source (frameworks, and aqua), so 
unlike linux, you can't just grab their libraries like that, and there's the 
problem of the display)

-- Matthieu


pgpRb8PLhC1tU.pgp
Description: OpenPGP digital signature

Re: Is there possible run a MacOS X binary

[K. Macy]

>
>
>
A MachO activator is indeed not useful without an OSX install.

But let's be honest, Mach IPC is a loadable kernel module requiring no real
kernel changes. It's not upstreamable because of a general poor
understanding of IPC by noisy commentators and a religious aversion to a
technology perceived as having failed in the marketplace of ideas.



On Wed, Dec 7, 2016 at 10:45 Warner Losh  wrote:

> On Mon, Dec 5, 2016 at 12:31 PM, Kevin P. Neal 
> wrote:
>
> > On Mon, Dec 05, 2016 at 02:49:07PM -0300, Nilton Jose Rizzo wrote:
>
> >>
>
> >>
>
> >>  Sorry for cross posting (-current and -ports)
>
> >>
>
> >>
>
> >> Is there any emulator like linuxator to run Mac OS X binaries, or
>
> >> is ther any licensing problem?
>
> >
>
> > It may be possible to make an emulator for Darwin (the OS that Mac OS
> sits
>
> > on top of), but an emulator for Mac OS would probably require a legal
> copy
>
> > of Mac OS.
>
> >
>
> > So, no, there is no Mac OS emulator for FreeBSD. And I'd be surprised if
>
> > it ever happened.
>
>
>
> NetBSD has (or had) a macho image activator, which is the first step
>
> in this process. But Kevin is right that most of the functionality of
>
> MacOS isn't in the kernel, and you'd need a copy of MacOS to run it in
>
> emulation. Plus there's a lot of Mach code that MacOS depends on that
>
> has no simple counterparts in FreeBSD, and that would be a lot of work
>
> to make happen. It's one of the things that's a barrier to entry for a
>
> simple, straight forward launchd port, for example.
>
>
>
>
>
>
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: emulators/qemu: qemu ports failing due to compiler error on 12-CURRENT

[Dimitry Andric]

On 07 Dec 2016, at 10:42, O. Hartmann  wrote:
> 
> I try my first steps in cross compiling ports with poudriere and therefore I 
> try to setup
> an appropriate jail and QEMU environment.
> 
> Well, I'm failing at the jail setup due to the non-exitence of any suitable 
> QEMU
> environment and for that I tried to figure out to find some proper HOWTO.
> Searching via google ave some hints, but in questions which QEMU from ports 
> should be
> used, all leave me alone, so I tried
> 
> emulators/qemu
> emulators/qemu-devel
> emulators/qemu-static
> 
> emulators/qemu is known for me to fail since months and the days of 
> 11-CURRENT, there is a
> compiler error spit out with clang 3.8 and now 3.9. The very same for 
> qemu-devel (both
> ports used with standard options, no extras). See also Bug 214873
> (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214873) and Bug 215100
> (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215100).

I couldn't reproduce the compilation errors, it builds fine for me until
the link phase.


> I tried also emulators/qemu-static, but it also fails compiling on most 
> recent 12-CURRENT
> (as the others, too, also my poudriere environment, which has also CURRENT 
> jails) with
> 
> [...]
> /usr/bin/ld:../config-host.ld:14: syntax error
> c++: error: linker command failed with exit code 1 (use -v to see invocation)
> [...]

But this I *can* reproduce.  It appears qemu wants to set the text
segment start address, using the -Ttext-segment=0x6000 option to ld.

However, our base ld does not yet support this option, and then the
configure script tries to patch the default linker script using the
following construct:

  $ld --verbose | sed \
-e '1,/==/d' \
-e '/==/,$d' \
-e "s/[.] = [0-9a-fx]* [+] SIZEOF_HEADERS/. = $textseg_addr + 
SIZEOF_HEADERS/" \
-e "s/__executable_start = [0-9a-fx]*/__executable_start = 
$textseg_addr/" > config-host.ld

Unfortunately, it seems to run /usr/local/bin/ld in this case, and this
results in the following busted linker script line, which cannot be
parsed:

  PROVIDE (__executable_start = 0x6000SEGMENT_START("text-segment", 
0x08048000)); . = SEGMENT_START("text-segment", 0x08048000) + SIZEOF_HEADERS;

If it would use /usr/bin/ld instead, the patching would succeed, and
the line would become:

  PROVIDE (__executable_start = 0x6000); . = 0x6000 + SIZEOF_HEADERS;

which is probably what was intended.

Probably, the configure script needs to be patched to run base ld,
or use the same ld invocation for both checking the -Ttext-segment
option support and patching the linker script.

-Dimitry



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Is there possible run a MacOS X binary

[Nilton Jose Rizzo]

Em Wed, 07 Dec 2016 18:57:36 +, K. Macy escreveu
> >
> >
> >
> A MachO activator is indeed not useful without an OSX install.
> 
> But let's be honest, Mach IPC is a loadable kernel module requiring 
> no real kernel changes. It's not upstreamable because of a general poor
> understanding of IPC by noisy commentators and a religious aversion 
> to a technology perceived as having failed in the marketplace of ideas.
> 
> On Wed, Dec 7, 2016 at 10:45 Warner Losh  wrote:
> 
> > On Mon, Dec 5, 2016 at 12:31 PM, Kevin P. Neal 
> > wrote:
> >
> > > On Mon, Dec 05, 2016 at 02:49:07PM -0300, Nilton Jose Rizzo wrote:
> >
> > >>
> >
> > >>
> >
> > >>  Sorry for cross posting (-current and -ports)
> >
> > >>
> >
> > >>
> >
> > >> Is there any emulator like linuxator to run Mac OS X binaries, or
> >
> > >> is ther any licensing problem?
> >
> > >
> >
> > > It may be possible to make an emulator for Darwin (the OS that Mac OS
> > sits
> >
> > > on top of), but an emulator for Mac OS would probably require a legal
> > copy
> >
> > > of Mac OS.
> >
> > >
> >
> > > So, no, there is no Mac OS emulator for FreeBSD. And I'd be surprised if
> >
> > > it ever happened.
> >
> >
> >
> > NetBSD has (or had) a macho image activator, which is the first step
> >
> > in this process. But Kevin is right that most of the functionality of
> >
> > MacOS isn't in the kernel, and you'd need a copy of MacOS to run it in
> >
> > emulation. Plus there's a lot of Mach code that MacOS depends on that
> >
> > has no simple counterparts in FreeBSD, and that would be a lot of work
> >
> > to make happen. It's one of the things that's a barrier to entry for a
> >
> > simple, straight forward launchd port, for example.
> >
> >
> >
> >
> >
> >
> >
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


   Thankx for all comments.  I know and understood all difficult.
   
   I'll have to spend my money on the purchase a Machintosh machine.

---
/*
**Nilton José RizzoUFRRJ
**http://www.rizzo.eng.br  http://www.ufrrj.br
**http://lattes.cnpq.br/0079460703536198
**/

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"