Is cross-compiling with Rust even possible on OpenBSD? I don't see
rustup available, and ran into the below issues when trying a couple of
different triples, with an attempted no_std "hello world".
Thank you.
On 2025-01-21 17:13:11-0700, Luke A. Call wrote:
> I'm att
Compiling
baremetal_rust v0.1.0 (/home/lacall/proj/learnrust/no_std)
error[E0463]: can't find crate for `core`
|
= note: the `x86_64-unknown-none` target may not be installed
= help: consider downloading the target with `rustup target add
x86_64-unknown-none`
For more informati
On 2023-04-08, lorenzo wrote:
> Hello, I'm trying to use clang to cross-compile an embedded risc-v project
> from my amd64 host. The problem is that it looks like the riscv target isn't
> available and I only have targets related to my host gpu and cpu. Is there a
> way to add other targets as
Hello, I'm trying to use clang to cross-compile an embedded risc-v project from
my amd64 host. The problem is that it looks like the riscv target isn't
available and I only have targets related to my host gpu and cpu. Is there a
way to add other targets as well like on other clang distributions?
On Wed, Jul 23, 2008 at 10:27 AM, dermiste <[EMAIL PROTECTED]> wrote:
> and what about NetBSD on qemu ? sure you'll get speed loss, but you
> won't have to worry about inconsistencies ...
it is certainly another option, though I feel rather involved at this
point, and interested in fixing what ev
and what about NetBSD on qemu ? sure you'll get speed loss, but you
won't have to worry about inconsistencies ...
On Wed, Jul 23, 2008 at 3:48 PM, Jason Beaudoin <[EMAIL PROTECTED]> wrote:
> Nick and Ted,
>
> Thank you for the responses.
>
>> The warning never kills the process. That warning is ge
Nick and Ted,
Thank you for the responses.
> The warning never kills the process. That warning is generated by
> OpenBSD's modified ld(1). It looks like the error is in a shellscript
> (perhaps `nbmake`?). Probably something is getting generated wrong
> because OpenBSD doesn't work the way NetBSD
On 7/17/08, Jason Beaudoin <[EMAIL PROTECTED]> wrote:
> has anyone attempted (maybe with success) building a NetBSD toolchain
> on OpenBSD?
This would fall more into the NetBSD camp. After all, it's their toolchain.
> NetBSD has a build script that facilitates building the system,
> includi
On Thu, Jul 17, 2008 at 12:16 AM, Jason Beaudoin
<[EMAIL PROTECTED]> wrote:
> Hiya!
>
> maybe I'll get flames for inquiring, but I'll try anyway:
>
> has anyone attempted (maybe with success) building a NetBSD toolchain
> on OpenBSD?
>
> I understand that this might seem senseless to some folks, bu
Hiya!
maybe I'll get flames for inquiring, but I'll try anyway:
has anyone attempted (maybe with success) building a NetBSD toolchain
on OpenBSD?
I understand that this might seem senseless to some folks, but it's a
good option for my situation. From the research I've done (archives,
google, etc
John Tate wrote:
How would I go about cross compiling OpenBSD from i386 to sparc64?
I am just interested because I want to build a system from a faar faster
processor if possible.
In general, cross-compiling isn't supported on OpenBSD, except when
bringing up a new architecture. Wh
have had a hand in cross-compiling gcc and binutils on an i386 Linux-
2.4 box, but I'm still not quite sure if this also applies to *BSD. Anyway,
hope this idea works.
Good luck.
Jason
On 10/6/06, John Tate <[EMAIL PROTECTED]> wrote:
How would I go about cross compiling OpenBSD from i
How would I go about cross compiling OpenBSD from i386 to sparc64?
I am just interested because I want to build a system from a faar faster
processor if possible.
John.
--
Faced with the fact that Intelligent Design doesn't meet the criteria for a
scientific theory, leading proponent rede
David Diggles <[EMAIL PROTECTED]> wrote:
> I have a source tree for 3.8-stable, updated using cvsup. Have
> successfully used this source tree to do a 'make build' for i386,
> however, when I attempt the first step for cross compiling for mac68k:
> ( cd /usr/src; make
I have a source tree for 3.8-stable, updated using cvsup. Have
successfully used this source tree to do a 'make build' for i386,
however, when I attempt the first step for cross compiling for mac68k:
( cd /usr/src; make TARGET=mac68k cross-distrib )
It hangs at the following:
(cd /u
I have a source tree for 3.8-stable, updated using cvsup. Have
successfully used this source tree to do a 'make build' for i386,
however, when I attempt the first step for cross compiling for mac68k:
( cd /usr/src; make TARGET=mac68k cross-distrib )
It hangs at the following:
(cd /u
Brett Lymn said:
> Did I say stress anywhere?
You didn't, but you should have.
> I said test. Sure, doing a build will
> stress the machine but all it really tests is that the tool chain is
> functional and that the kernel is functional enough to handle the
> build.
That's actually pretty func
On Wed, Jul 13, 2005 at 10:22:41AM -0500, Marco Peereboom wrote:
>
> >
> > 1) At no point in time did I advocate no testing of the output
> > binaries. Regardless of whether those binaries are produced via a
> > native build or a cross build. Testing the binaries is a _good_ thing
> > and shoul
On Thu, Jul 14, 2005 at 12:21:45AM +0930, Brett Lymn wrote:
> On Tue, Jul 12, 2005 at 04:11:01PM +0200, Artur Grabowski wrote:
> >
> > Seriously. You really don't see the correlation between using something
> > and finding bugs? What planet are you from?
> >
>
> Quite a strong correlation actual
On Tue, Jul 12, 2005 at 04:11:01PM +0200, Artur Grabowski wrote:
>
> Seriously. You really don't see the correlation between using something
> and finding bugs? What planet are you from?
>
Quite a strong correlation actually Art. Since you appear a bit
confused allow me to spell it out for you.
On 07/12/05 22:42, Maslan <[EMAIL PROTECTED]> wrote:
Nutty McSquirrel, please keep your advice for yourself as i wont
accept advice from a hotmail guy.
"What's in a name"... ROFL, what's the difference with a gmail guy?
In general I would say hotmail guys are older and probably wiser.
+++che
Brett Lymn <[EMAIL PROTECTED]> writes:
> > ASSUMING YOU EVER SEE IT.
> > If you don't see a bug, you ship crap.
> >
>
> That applies for both native and cross-built. THERE IS NO DIFFERENCE
> AN UNSEEN BUG MAY BE THERE REGARDLESS. It has happened in the past to
> OpenBSD and it may just happen a
On Tue, Jul 12, 2005 at 07:10:02AM -0400, Nick Holland wrote:
>
> a bit of a disconnect with reality.
> You need your build done in half an hour rather than an hour?
> This argument line is nonsense. If you bought an amd64 to back up your
> Soekris box, you blew it.
>
That statement assumes too
Brett Lymn wrote:
> On Mon, Jul 11, 2005 at 03:09:42PM -0401, Nick Holland wrote:
>>
>> Let's see...what possibly fanless, low-power platforms do we have?
>>...
>> i386..ok, but you can native build on on Really Fast Stuff.
>>
>
> Uh huh... unless your Really Fast Stuff happens to be an amd64 b
On Mon, Jul 11, 2005 at 03:09:42PM -0401, Nick Holland wrote:
>
> Let's see...what possibly fanless, low-power platforms do we have?
>...
> i386..ok, but you can native build on on Really Fast Stuff.
>
Uh huh... unless your Really Fast Stuff happens to be an amd64 box in
which case you are no l
On Mon, Jul 11, 2005 at 08:28:05PM +0930, Brett Lymn wrote:
> On Sun, Jul 10, 2005 at 03:38:29PM -0400, Nick Holland wrote:
> >
> > If your machine is too slow to do what you need it to do, you need a
> > faster machine. Cross compiling is not the answer to your problem.
>>> Brett Lymn 11-Jul-05 13:44 >>>
>
> And _all_ supported boot methods including network booting are tested?
Yes. That is one specific part of the pre-release testing we do.
On Mon, Jul 11, 2005 at 02:55:39PM +0200, Artur Grabowski wrote:
>
> Understanding the answer to this question is the difference between
> having architectures that actually work and are used and architecutres
> that are "supported", meaning they are added to a long list.
>
... and the lack of a
Brett Lymn <[EMAIL PROTECTED]> writes:
> > Not cross compiling and actively discouraging cross compilation is why
> > all OpenBSD architectures are constantly stress tested and therefore
> > relatively stable while some other projects that shall not be named
> >
ne of the slower architectures...
>
> Not cross compiling and actively discouraging cross compilation is why
> all OpenBSD architectures are constantly stress tested and therefore
> relatively stable while some other projects that shall not be named
> don't even have working
; a hour or two instead of days. It means developers can do more stuff
> because they are not waiting for the slower processors to grind
> through a compile.
Not cross compiling and actively discouraging cross compilation is why
all OpenBSD architectures are constantly stress tested and theref
On Sun, Jul 10, 2005 at 03:38:29PM -0400, Nick Holland wrote:
>
> If your machine is too slow to do what you need it to do, you need a
> faster machine. Cross compiling is not the answer to your problem.
>
Not so Nick. There may be some cases where you deliberately have a
slow
well and good if it wern't for the fact that under the
> projects goals it lists
>
> Provide a good cross compile/development platform.
>
> Which is probably a good reason why people, including my self once, have
> asked
> why cross compiling doesn't work on
nder the
projects goals it lists
Provide a good cross compile/development platform.
Which is probably a good reason why people, including my self once, have asked
why cross compiling doesn't work on OpenBSD.
>
> You may get small bits compiled, but you will find it very difficult
&
On Sun, Jul 10, 2005 at 10:54:45AM +0100, Tom Cosgrove wrote:
>
> BSD (whether OpenBSD or any other flavor) is not Linux or anything else
> like that. It is a complete operating system, in use in production in
> many places.
>
No need to go to Hurd. NetBSD is able to be built on a foreign
oper
>>> Maslan 10-Jul-05 09:50 >>>
>
> Thanks alot
> for making it clear, gcc will be another problem.
> but sometimes u really need to cross-compile os on another one as in
> case of hurd.
Sigh. The Hurd home page says "GNU/Hurd.. is completely self-contained
(you can compile all parts of it using G
Thanks alot
for making it clear, gcc will be another problem.
but sometimes u really need to cross-compile os on another one as in
case of hurd.
On 7/10/05, Tom Cosgrove <[EMAIL PROTECTED]> wrote:
> >>> Maslan 10-Jul-05 08:16 >>>
> >
> > On 7/10/05, Maslan <[EMAIL PROTECTED]> wrote:
> > > Pain let
>>> Maslan 10-Jul-05 08:16 >>>
>
> On 7/10/05, Maslan <[EMAIL PROTECTED]> wrote:
> > Pain let u learn more, besides i've some extra time. i used to make
> > my own LFS, and i missing this in BSD.
> > but what things i should consifer when trying so.
> > the compiler are almost the same gcc.
"Almos
38 matches
Mail list logo
