Tiny Core Base > Release Candidate Testing
Core v7.0beta2
curaga:
--- Quote from: dentonlt on January 20, 2016, 08:43:02 PM ---Sorry - I'm confused. 4.2.8 is on kernel.org, but to bump to 4.2.9 I pick up patches from ... ?
--- End quote ---
It was released by Canonical, they have 4.2 as a long-term kernel in an Ubuntu version. Official name is 4.2.8-ckt1. Then we have some of our own patches.
--- Quote from: vt1431 on January 21, 2016, 03:42:18 AM ---Running 5.2.0 "gcc -v ..." shows no "--with-arch=i486 --with-tune=i686" which was present in 4.9.1:
--- End quote ---
It should work with just a 486 target though, which is correct on both.
edit: From your earlier "gcc -v" output, we see that gcc applied -march=i486. This is what the --with-arch option would do, it sets the default -march, it doesn't affect the new gcc's build process.
--- Quote ---What drawbacks would be possible from using gcc4.9.1-compiled kernel modules with 4.x kernel?
--- End quote ---
It won't work if you mix compilers. The kernel and modules must be compiled by the same gcc version. If you build it all, the gcc version doesn't matter much, as the kernel supports every gcc version from 3.4 up, IIRC.
Applied your patch, thanks.
Juanito:
--- Quote from: gerald_clark on January 20, 2016, 11:58:27 AM ---Search does not find them. It seems to be an indexing problem.
--- End quote ---
'seems to be OK now?
Juanito:
--- Quote from: andyj on January 20, 2016, 11:31:06 AM ---My "two other comments" were about a HD installation. There isn't a dependency for fltk-1.1.10 in any of the .dep files in optional, but it is in tc-install.sh so I'm suggesting that script needs to be updated. As you say, if someone wants to use a different window manager shouldn't that be the only one loaded?
--- End quote ---
tc-install.sh corrected fltk-1.1.10 -> fltk-1.3 - thanks
ezremaster still depends on fltk-1.1.10, which is why I guess it is still there in the CorePlus iso
I agree, that if you choose a different wm, then it should be the only one loaded - patches to tc-install.sh would be gratefully received :)
Of course you can edit onboot.lst to suit once tc-install exits.
gerald_clark:
--- Quote from: Juanito on January 21, 2016, 05:46:49 AM ---
--- Quote from: gerald_clark on January 20, 2016, 11:58:27 AM ---Search does not find them. It seems to be an indexing problem.
--- End quote ---
'seems to be OK now?
--- End quote ---
Yes. Thanks.
andyj:
Further testing reveals that loading libXdamage or libXxf86vm will also change the permissions on /dev/fuse to 1600, and that loading i2c-KERNEL or libX11-dev will reset them to 1666. At this point I'm going to need a pretty good reason not to just set them to 1666 in the open-vm-tools load script just to be sure, since there doesn't appear to be much control over the fuse situation at this point.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version