Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] Porting llvm-gcc-4.2"
2008 Nov 03
0
[LLVMdev] Porting llvm-gcc-4.2
llvm-gcc bits are but a small part of it. You need to add a new target
to llvm. Please read llvm documentation and llvmdev archieve for more
information.
Evan
On Nov 2, 2008, at 7:38 AM, Thorsten Glaser wrote:
> Hello,
>
> how would I go porting llvm-gcc-4.2 to an “unknown” platform, i.e.
> MirBSD? For regular gcc, I’d have to add stuff to gcc/gcc/config/
> and patch quite
2008 Nov 03
2
[LLVMdev] clang
Anton Korobeynikov dixit:
>> Any suggestions?
>Please do read http://clang.llvm.org/get_started.html about correct
>way of building clang.
Oh, I did. I took LLVM and Clang from the very same SVN revision even,
placed clang in llvm/tools/ and built. This has worked on GNU/Linux
for me once, but clang-current seems to rely on things not yet in llvm.
Like I said, I’m using r58565 for
2008 Nov 09
0
[LLVMdev] clang
Dixi quod…
>Like I said, I’m using r58565 for both llvm and clang (now).
Must have been broken, as r58935 for both works.
I’ve even fixed some system headers for clang now, and mksh
– http://mirbsd.de/mksh – builds fine and passes the regression
tests (with the Xcode version, about 83% of it failed, back then).
Now up to llvm-gcc *sigh*…
//mirabilos
--
Sometimes they [people] care too
2008 Nov 11
3
[LLVMdev] llvm-gcc fails to build libgcc when built with itself
Hello,
I’m trying the following thing:
• build and install llvm with mgcc (system compiler)
• build and install llvm-gcc with mgcc
• build llvm with llvm-gcc
• deinstall llvm(old), install llvm(new)
• build llvm-gcc with llvm-gcc(old)
• deinstall llvm-gcc(old), install llvm-gcc(new)
However, I have the problem that the llvm-gcc(new) does not work: after
it is compiled, it tries to build libgcc2
2012 Apr 20
2
klibc 2.0~rc3-1 ./. mksh 40.9.20120414-2
Hi,
after changing mksh to no longer use mkstemp, I decided to try
and build mksh-static with klcc on most platforms, in Debian.
Here are the results by Debian architecture:
alpha (4) fails
amd64 works
armel works
armhf (3) fails
i386 works
ia64 works
m68k (1) workaround
mips works
mipsel works
powerpc (2) fails
ppc64 works (!)
s390 works
s390x works
sparc works
Architectures not listed either
2008 Nov 02
0
[LLVMdev] 2.4 Pre-release (v2)
Tanya M. Lattner dixit:
>LLVMers,
>
>The 2.4 pre-release (v2) is available for testing:
>http://llvm.org/prereleases/2.4/
Is it correct that there is no matching clang distfile?
A checkout of clang r58548 does not build with the prerelease,
seems to require a newer version of llvm-current.
(But then, maybe it’d be best anyway if I port llvm-current to
MirBSD, because it’ll be easier
2008 Oct 31
7
[LLVMdev] 2.4 Pre-release (v2)
LLVMers,
The 2.4 pre-release (v2) is available for testing:
http://llvm.org/prereleases/2.4/
If you have time, I'd appreciate anyone who can help test the release.
Please do the following:
1) Download/compile llvm source, and either compile llvm-gcc source or use
llvm-gcc binary.
2) Run make check, send me the testrun.log
3) Run "make TEST=nightly report" and send me the
2014 Nov 06
3
No thanks for breaking third-party applications
Hi *,
I was just debugging why TFTP booting did not work any more
on a system that had pxelinux.0 was updated.
?Since version 5.00, support for 16-bit COMBOOT modules has been
dropped, and c32 modules switched from the COM32 object format to ELF.?
Ugh. Well, updating the *.c32 files was enough to make the
Linux discless thingy work again. BUT!
The MirBSD bootloader actually took advantage of
2014 Dec 05
2
vesamenu back to text before booting
On Fri, 5 Dec 2014, Ady wrote:
> > > If so: http://www.syslinux.org/wiki/index.php/Mboot.c32
> >
> > I?m not permitted to edit either that page or its talk page.
> > Do I submit the content addition here, then?
>
> Please do.
Okay, MediaWiki syntax docs follow. Note I have tested those
only a bit, and not within the vesamenu context, but if mboot.c32
resets to
2008 Nov 12
0
[LLVMdev] llvm-gcc fails to build libgcc when built with itself
Can you bootstrap llvm-gcc (configure with --enable-bootstrap)?
Ciao,
Duncan.
2014 Dec 05
8
vesamenu back to text before booting
On Fri, 5 Dec 2014, Gene Cumm wrote:
> >> mostly in C and be BIOS-only) or making the MirOS kernel act like
> >> either an MBOOT kernel or a Linux kernel (for their boot protocols),
The MirBSD _bootloader_ (not kernel) can act as a Multiboot kernel.
It can then use disc access (not PXE), or you can pass it the ?real?
kernel, but also e.g. configuration files, as Multiboot
2014 Dec 05
0
vesamenu back to text before booting
> On Fri, 5 Dec 2014, Gene Cumm wrote:
>
> > >> mostly in C and be BIOS-only) or making the MirOS kernel act like
> > >> either an MBOOT kernel or a Linux kernel (for their boot protocols),
>
> The MirBSD _bootloader_ (not kernel) can act as a Multiboot kernel.
> It can then use disc access (not PXE), or you can pass it the "real"
> kernel, but
2012 May 15
5
[PATCH 0/5] resubmitting pending patches
Hi,
I?ve gone through the mailing list archives and hereby want
to resubmit my pending patches. Most are independent of each
other, except the m68k patch which will only be complete if
sigsuspend is also fixed. (It can be applied before that,
though.)
http://www.zytor.com/pipermail/klibc/2012-January/003173.html
[PATCH] fix m68k support
Resubmitted here as 0005. While there was a question from
2013 Nov 11
2
[PATCH 3/3] arm64: Introduce arm64 support
Steve Capper dixit:
>> Do we need the fpregs saved even though klibc doesn't do fp?
>For gcc targetting Aarch64, We can only guarantee that d8-d15 are
>left alone when -mgeneral-regs-only is supplied for building klibc
>and any software linked against klibc. I would much prefer to
We can enforce this in klcc, just like -mregparm=3 is used by
the i386 target.
bye,
//mirabilos
2011 Feb 27
4
[PATCH] Add minimal mkstemp(3) implementation.
This uses time, ASLR and pid for randomisation. (Closes: #516774)
Signed-off-by: Thorsten Glaser <tg at mirbsd.org>
---
usr/include/stdlib.h | 2 +
usr/klibc/Kbuild | 2 +-
usr/klibc/mkstemp.c | 93 ++++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 96 insertions(+), 1 deletions(-)
create mode 100644 usr/klibc/mkstemp.c
diff --git a/usr/include/stdlib.h
2014 Dec 03
4
vesamenu back to text before booting
On Tue, 2 Dec 2014, H. Peter Anvin wrote:
> This is the default unless the "quiet" option is set.
Hmm.
tglaser at luna:/srv/tftp $ fgrep -ri quiet .
Binary file ./hdt.c32 matches
Binary file ./ldlinux.c32 matches
Binary file ./vmlinuz matches
Binary file ./linux.c32 matches
Binary file ./debian-installer/jessie/amd64/linux matches
Binary file ./debian-installer/jessie/i386/linux
2012 May 18
1
[sh4] klibc SIGILL
Hi sh4 porters,
I?ve just fixed a regression of klibc to build from source
on sh4 using the sumotsu.debian.net porterbox (thanks for
making one available) and found a problem with your archi-
tecture: all binaries built with klibc (shared and static)
get a SIGILL (illegal instruction).
I suspect that different CFLAGS are needed. Please, someone,
have a look at it; a release of klibc 2.0 upstream
2012 May 25
4
klibc breakage on alpha, need porterbox
Hi,
is there a DD-accessible porterbox somewhere (slow would be ok,
as this is smallish software) with an up-to-date sid (enough to
install the recently-built libklibc-dev 2.0~rc5-1 and all other
B-D of mksh 40.9.20120518-1, as well as strace and gdb-minimal)?
Similarily to http://www.zytor.com/pipermail/klibc/2012-May/003229.html
I found klibc-compiled programmes on Alpha to fail (SIGSEGV
2011 Jan 29
2
On the trail of sigsuspend(2)
SIGSUSPEND(2) Linux Programmer's Manual SIGSUSPEND(2)
NAME
sigsuspend - wait for a signal
SYNOPSIS
#include <signal.h>
int sigsuspend(const sigset_t *mask);
? and ?
SIGSUSPEND(2) BSD Programmer's Manual SIGSUSPEND(2)
NAME
sigsuspend - atomically release blocked signals and wait for interrupt
SYNOPSIS
2014 Dec 05
0
vesamenu back to text before booting
> On Fri, 5 Dec 2014, Ady wrote:
>
> > > > If so: http://www.syslinux.org/wiki/index.php/Mboot.c32
> > >
> > > I?m not permitted to edit either that page or its talk page.
> > > Do I submit the content addition here, then?
> >
> > Please do.
>
> Okay, MediaWiki syntax docs follow. Note I have tested those
> only a bit, and not