On 2018-05-21, Peter Hessler wrote:
> i386 and amd64 are different platforms, so of course you get different
> packages.
>
> Within the same platform, all binaries that are built should run on all
> possible members of that platform.
>
> So, code will be compiled WITHOUT AVX support, unless it ca
Okey, thanks both for the help!
Elias.
>> do I still get the same package ?
Yes.
cc(1) does not use microarchitecture-specific features unless you provide
"-march" explicitly.
Other BSDs do it, but OpenBSD does not. So, cc(1) only knows that you are
building something for amd64.
There should not be any difference between nehalem and co
i386 and amd64 are different platforms, so of course you get different packages.
Within the same platform, all binaries that are built should run on all
possible members of that platform.
So, code will be compiled WITHOUT AVX support, unless it can be detected
at runtime (e.g. mplayer/ffmpeg). I
Hi,
I understand that about the builds and packages.
I will re write my question in another form:
If I build, say, firefox on a i386 machine I get a package, and
another if I build firefox on amd64, they differ.
If I build firefox on an amd64 machine WITHOUT AVX support I get a
package, if now I bu
Hello.
OpenBSD team does not recommend to build anything that exists in packages.
>>If so, building from ports would produce a different code?
In most cases ports are not aware of your microarchitecture.
See my question and Theo's answer.
https://www.mail-archive.com/misc@openbsd.org/msg160878.h
Hi,
I have this question in my mind for a time now, if I download OpenBSD
and install all the applications from packages do OpenBSD and the apps
use for example AVX512 ? I mean, if I understand correctly, the
compiler should optimize the code for a given set of instructions,
given that, for example
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09/04/16 04:35, STeve Andre' wrote:
> On 09/03/16 11:32, Harald Dunkel wrote:
>> On 09/03/16 12:40, Ted Unangst wrote:
>>> there's some repo surgery in progress. it should be fixed eventually.
>>>
>> What exactly does this mean?
>>
>>
> It mean
On 2016-09-04, STeve Andre' wrote:
>>> there's some repo surgery in progress. it should be fixed eventually.
>>>
>> What exactly does this mean?
>>
> It means that something went wrong, and steps were being taken
> to fix it.
No, it was just some directories being moved around.
> Not very often,
On 09/03/16 11:32, Harald Dunkel wrote:
On 09/03/16 12:40, Ted Unangst wrote:
Teno Deuter wrote:
installed a fresh 6.0 AMD64 and tried to build 'stable' from source.
Here is what I did as 'root' (as described in:
http://www.openbsd.org/stable.html):
export CVSROOT=anon...@anoncvs1.ca.openbsd.
Yes, the repos should be done with their surgery now. Please let us
know if you still see issues.
On 2016 Sep 03 (Sat) at 13:11:42 +0200 (+0200), Teno Deuter wrote:
:meaning I shall try at a later time?
:
:Thank you
:
:On Sat, Sep 3, 2016 at 12:40 PM, Ted Unangst wrote:
:> Teno Deuter wrote:
:>>
On 09/03/16 12:40, Ted Unangst wrote:
> Teno Deuter wrote:
>> installed a fresh 6.0 AMD64 and tried to build 'stable' from source.
>>
>> Here is what I did as 'root' (as described in:
>> http://www.openbsd.org/stable.html):
>>
>> export CVSROOT=anon...@anoncvs1.ca.openbsd.org:/cvs
>> cd /usr; cvs c
Hello Teno,
I have successfully updated five OpenBSD 5.9 to 6.0 on release day ,
following https://www.openbsd.org/faq/upgrade60.html
After, I rebuilt all them to stable branch from:
$ cd /usr
$ cvs -qd anon...@anoncvs.ca.openbsd.org:/cvs get -rOPENBSD_6_0 -P src
Was magical as expected.
Rega
meaning I shall try at a later time?
Thank you
On Sat, Sep 3, 2016 at 12:40 PM, Ted Unangst wrote:
> Teno Deuter wrote:
>> installed a fresh 6.0 AMD64 and tried to build 'stable' from source.
>>
>> Here is what I did as 'root' (as described in:
>> http://www.openbsd.org/stable.html):
>>
>> expor
Teno Deuter wrote:
> installed a fresh 6.0 AMD64 and tried to build 'stable' from source.
>
> Here is what I did as 'root' (as described in:
> http://www.openbsd.org/stable.html):
>
> export CVSROOT=anon...@anoncvs1.ca.openbsd.org:/cvs
> cd /usr; cvs checkout -P -rOPENBSD_6_0 src
there's some re
installed a fresh 6.0 AMD64 and tried to build 'stable' from source.
Here is what I did as 'root' (as described in:
http://www.openbsd.org/stable.html):
export CVSROOT=anon...@anoncvs1.ca.openbsd.org:/cvs
cd /usr; cvs checkout -P -rOPENBSD_6_0 src
# cd /usr/src/sys/arch/$(uname -m)/conf
# config
Is that always true? I don't think that's always true. Take wpa-psk
which does not just work for me on current or 4.5, or how I've never
seen linux unable to sleep a laptop but I've plenty of machines that
OpenBSD's sleep is funky with.
The important thing is that that's always the -ideal-, wheras
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Furman wrote:
If you like troubleshooting then OpenBSD is going to be no fun for you.
OpenBSD "Just Works"
You'll also find that your best friend is 'man' instead of 'google'.
That's an adjustment that takes time for Linux refugees ... ;-)
Chuck Robey writes:
> Like I said above, I'm getting my sources via cvsup, and since they're the src
> with no tag or date, so I would suppose you'd call this "current".
The general advice for building a system using -current sources is to
start with the most recent snapshot you can get your h
On Wed, 13 May 2009 01:01:40 -0400, "Chuck Robey"
said:
> between FreeBSD and OpenBSD. Getting this new OS up is really turning
> out to be
> fun (I like troubleshooting).
If you like troubleshooting then OpenBSD is going to be no fun for you.
OpenBSD "Just Works"
This isn't Linux or FreeBSD
Dorian B|ttner wrote:
> Chuck Robey schrieb:
> Did you not only read the manual but the faq also? And is your system
> actually running a version before 2008/11/11?
> http://www.de.openbsd.org/faq/upgrade-old.html
No, 4.5 just came out, right? Anyhow, I saw the FAQ about PIE, so my question's
an
Chuck Robey schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm still working on getting my system in shape to let me do the coding I'm
after. In doing my building of /usr/src, I'm hitting an odd problem, maybe if
you listen, you could let me know if you recognize it.
BTW, to begin with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm still working on getting my system in shape to let me do the coding I'm
after. In doing my building of /usr/src, I'm hitting an odd problem, maybe if
you listen, you could let me know if you recognize it.
BTW, to begin with, I've read the manual
23 matches
Mail list logo
