search for: antix

...10:29:41.000000000 +0000 @@ -4762,7 +4762,7 @@ done ;; esac -TARGETS_TO_BUILD="CBackend MSIL $TARGETS_TO_BUILD" +TARGETS_TO_BUILD="CBackend" TARGETS_TO_BUILD=$TARGETS_TO_BUILD It didn't work. I get these link failures: make[2]: Entering directory `/home/foad/svn/antix/toolchain/trunk/toolchain/obj/llvm-obj/tools/llc' llvm[2]: Linking Debug executable llc /home/foad/svn/antix/toolchain/trunk/toolchain/obj/llvm-obj/tools/llc/Debug/ llc.o: In function `ForceCodegenLinking': /home/foad/svn/antix/toolchain/trunk/toolchain/llvm/llvm/include/llvm/CodeGe n/LinkA...

Hello, I am looking to employ a graduate developer who can demonstrate experience of working with the LLVM technology and community and who is willing to take on an exciting and challenging role at Antix Labs limited. There is a job spec posted on our web site: http://antixlabs.com/aboutUs/vacancies.html If you are interested, or would like to know more, please contact us through recruitment at antixlabs.com with your CV and a covering letter. Thanks and regards, Mike Foss Chie...

Hello ALL! First, I apologize for sending question that spill-out from the scope of this list. However, you might be essentially the best informants. In brief, I am thinking to give second shot to the Debian. Currently I am using Ubuntu 9.04, but Debian still teases me, so to say. I used to use Debian testing (Lenny at that time), but when Lenny became stable, things became very shaky in

On 03/19/2017 01:12 AM, Ady Ady via Syslinux wrote: > Regarding distros for older computers, there are several. The > problem, at least at this point, is bootability. Although Antix is > for older computers, it is also based on Debian and the latest > ISOLINUX will also be bigger than 32KiB. Perhaps Knoppix or some (of > the many) PuppyLinux would still use ISOLINUX 4.xx or older. SUSE > derivatives also use v. 4.xx. Slackware derivatives too. DSL used to > prov...

David Christensen wrote: > It seems that most Linux distributions I look at are dropping support > for 32-bit hardware. Aren't you using Debian? AFAIK jessie supports i586, so if Pentium is old enough for you you're good to go for likely at least two more years. After that I guess I'd be using old unsupported Debians for the ancient ones. I don't have this old hw on the

I've built a debug build of llvm 2.6, and llvm-gcc 2.6 for arm-elf with --enable-checking=yes. On the attached test case (which is g++.dg/expr/bitfield4.C from the GCC 4.2 testsuite) I get: $ cc1plus bitfield4.ii -emit-llvm-bc -o bitfield4.o -quiet cc1plus: /home/foad/svn/antix/toolchain/branches/w/foad/2757llvm26/toolchain/llvm/llvm-gcc/gcc/llvm-convert.cpp:999: llvm::Value* TreeToLLVM::Emit(tree_node*, const MemRef*): Assertion `(Result == 0 || (((enum tree_code) (((exp)->common.type))->common.code) == VOID_TYPE) || isa<VectorType>(ConvertType(((exp)->com...

.... It seems nouveau with the early 3.x kernels does not work at all on this NV04 video card. I think 3.4 is the first version with nouveau included in the kernel? Have tried 3.1 (Slacko Puppy 5.3.3), a 3.4.106 kernel I built on the Arch Linux system with the 2.6.35 kernel that does work, and 3.5 (AntiX Linux 12). Puppy and AntiX fall back to the VESA driver, and Arch with the custom 3.4.106 kernel and X 1.8.1.902 just drops to a text screen. All try to use nouveau, and all give the same "(EE) [drm] failed to open device" message in Xorg.0.log. -- You are receiving this mail because:...

...with the > early 3.x kernels does not work at all on this NV04 video card. I think 3.4 > is the first version with nouveau included in the kernel? Have tried 3.1 > (Slacko Puppy 5.3.3), a 3.4.106 kernel I built on the Arch Linux system with > the 2.6.35 kernel that does work, and 3.5 (AntiX Linux 12). Puppy and AntiX > fall back to the VESA driver, and Arch with the custom 3.4.106 kernel and X > 1.8.1.902 just drops to a text screen. All try to use nouveau, and all give > the same "(EE) [drm] failed to open device" message in Xorg.0.log. nouveau was first merged...

Hello: I'm running R 2.7.1 in Antix (Mepis kernel but heavily debian based). I have installed libcairo2 (1.6.4-6.1). I tried installing the Cairo package since I'm interested in generating some SVG graphs, and I got the following message: Only partial output (lines with no): .... checking if R was compiled with the RConn patch...

I'm the founder and lead developer of the lightweight Linux distro Swift Linux. I'm currently in the process of switching from the old antiX Linux base to the new Linux Mint Debian Edition base. The new Swift Linux will be using LightDM instead of SLiM. I've found that replacing LMDE's default GDM display manager with SLiM disables many functions (like audio). Restoring these functions means messing around with groups and per...

...unit "file1". My question is: can I tell that these three (llvm) compile units are in fact components of the single (non-LLVM) compile unit? Or is there some other way I should be determining which (non-LLVM) compile unit the records are part of? Many thanks! -- Regards, Richard Smith Antix Labs Ltd 400 Thames Valley Park Drive, Reading, Berkshire, RG6 1PT Tel.: +44 (0) 118 357 0 357

On Sun, Mar 19, 2017 at 04:34:06PM -0700, David Christensen via Syslinux wrote: > > If anyone knows of a Linux distribution targeted at 32-bit hardware, > please say so. > Please elaborate

...i586. Debian 8.x "Jessie" is supposed to support at least i586. Debian 9.x "Stretch" is supposed to support at least i686. I already posted, in a very recent email, possible Linux distributions that support 32-bit. The (non-exhaustive) alternatives, mostly ignored, included Antix, which specifically aims at old systems (and it is based on Debian). Regarding Debian's installer not being able to continue at a certain point of the process, it is probably not finding the packages. D-I needs to know where that (list of) packages are. The content of the original ISO ima...

Hi Folks, There are no Localisation features incorporated in the rsync code, from what I can see, and hence no Language Translation files. I see pertinent strings, in the "main.c" (output_summary function) and "flist.c" files, which are used by the rprintf function. I could use xgettext with "rprintf" as the function search parameter to produce a .pot file. Are

On 03/18/2017 04:15 PM, Ady Ady via Syslinux wrote: > >> On 03/18/2017 01:18 AM, Ady Ady via Syslinux wrote: >>> _ With the USB device connected to (one of) the problematic >>> computer(s), power up the system and get into the BIOS setup. In >>> the BIOS setup screen(s), change the boot order in such way that >>> the USB device is recognized as first

...mplify things when you want to customize a/your own Linux distribution (considering that isohybrid is, for the most part, read-only, while using SYSLINUX allows for writing). Regarding distros for older computers, there are several. The problem, at least at this point, is bootability. Although Antix is for older computers, it is also based on Debian and the latest ISOLINUX will also be bigger than 32KiB. Perhaps Knoppix or some (of the many) PuppyLinux would still use ISOLINUX 4.xx or older. SUSE derivatives also use v. 4.xx. Slackware derivatives too. DSL used to provide a floppy-emulatio...

Hi, I've actually run R quite a bit in Windows. I've had a release 8.04 of Ubuntu running a laptop for 3 days now. After struggling for much of that time to install R, I finally figured out that Dell shipped with the sources.list obsolete or just plain wrong. So I finally got it installed last night (for some reason v2.6.2, not v2.9.x). This morning I was able to download and install

Hi, > Suppose I have the following source: > > file1: > #include "file2" > #include "file3" > int fn1(void) ... > > file2: > int a; > > file3: > int fn2(void) ... > > then fn1, along with all the base types etc appear to be in compile unit > "file1", the variable a appears to be in compile unit

...laptop with NVIDIA G86M [GeForce 8400M GT] ID: 10de:0426 This is mostly copied from https://bugzilla.kernel.org/show_bug.cgi?id=204851 This errant behavior is similarly exhibited by openSUSE Tumbleweed, 15.0, 13.1 and 12.2; Linuxmint 19.0 live installation media; Knoppix 8.2 and 8.6 live media; antiX 17.4. Using vanilla kernel 5.2.14 on Tumbleweed doesn't help. Actual behavior: 1-nouveau kernel module doesn't load 2-ttys limited to 1024x768 mode 3-X runs only with VESA or FBDEV drivers and limited to 1024x768 mode 4-/dev/dri/card0 is absent 5-hwinfo reports HDTV display supports maximu...