hello nathan;
i know about the makefile in rtlinux_kernel_2_3.tar.gz.
i know about the makefile in the alpha.rpm.
someone has changed the makefile to say it is
linux-2.4.0-test1 when it is not. someone is
playing games with the makefile.
check it out.
download linux-2.4.0-test1 from www.kernel.org.
download rtlinux-3.0-pre8.tar.gz
tar -xzvf rtlinux-3.0-pre8.tar.gz
cd rtlinux-3.0
tar -xzvf ../linux-2.4.0-test1.tar.gz
cd linux
patch -p1 <../kernel_patch-2.4
cd ../..
diff -u --recursive --brief rtlinux_kernel_2_3 rtlinux-3.0/linux
you will find that the two directories are not
the same. there are differences.
now try.
linux-2.3.99-pre9.tar.gz
pre10-pre3.gz (patch)
mkdir linux-2.3.99-pre10-pre3
cd linux-2.3.99-pre10-pre3
tar -xzvf ../linux-2.3.99-pre9.tar.gz
cd linux
mv * ..
cd ..
rm -rf linux
patch -p1 <../pre10-pre3
patch -p1 <../rtlinux-3.0/kernel_patch-2.4
cd ..
diff -u --recursive --brief rtlinux_kernel_2_3 linux-2.3.99-pre10-pre3
they are the same.
On Wed, 25 Oct 2000, Nathan Paul Simons wrote:
On Tue, Oct 24, 2000 at 12:07:59PM -0500, Terry L. Ridder wrote:
terrylr> hello;
terrylr>
terrylr> been there, done that, does not work.
terrylr>
terrylr> rtlinux_kernel_2_3.tar.gz is linux-2.2.99-pre10-pre3
terrylr> which is not even linux-2.4.0-test1.
terrylr> there are differences.
nathan>
nathan> Hmm, last time i checked, rtlinux_kernel_2_3.tar.gz is 2.4.0-test1,
nathan> but i didn't put that package together. i'll look at it.
nathan>
terrylr> rtlinux_kernel_2_3.tar.gz has the same wrong
terrylr> patches to the three config.in files. i have
terrylr> written cort about that before.
terrylr> make xconfig dies because of those wrong patches.
nathan>
nathan> Yes, make xconfig needs to be fixed.
nathan> i'll see if i can get it fixed before we release pre9.
nathan>
terrylr> i am not the only one who has had problems with
terrylr> those config.in files.
terrylr>
terrylr> rtlinux-3.0-pre8.alpha.rpm is not:
terrylr> 1. a complete linux kernel source tree.
nathan>
nathan> Yes, it makes it considerably smaller and allows
nathan> people to get RTLinux up and running quickly.
nathan> It should have all header files necessary
nathan> to compile an RTLinux program.
nathan> If you want the complete kernel tree, just
nathan> grab the pre-patched one (which should be fixed soon).
nathan>
terrylr> 2. wants to put the files in /usr/rtlinux....
terrylr> which is in my opinion non-standard.
nathan>
nathan> What standard? Where do you think it should be and why?
nathan>
they should be in /usr/src
terrylr> rtlinux-3.0-pre8.alpha.rpm is built using
terrylr> linux-2.3.99-pre10-pre3.
nathan>
nathan> That's funny. i built that RPM, and i know i used 2.4.0-test1.
nathan>
no you did not.
terrylr> forgive me, but how can you say that you are sticking
terrylr> with linux-2.4.0-test1 when nothing indicates that
terrylr> you even using linux-2.4.0-test1? everything indicates
terrylr> that you are using linux-2.3.99-pre10-pre3, which as
terrylr> i stated above is not linux-2.4.0-test1, there are
terrylr> differences.
nathan>
nathan> npsimons@hq:~$ cp ~ftp/pub/rtlinux/v3/rtlinux_kernel_2_3.tar.gz .
nathan> npsimons@hq:~$ tar -xzf rtlinux_kernel_2_3.tar.gz
nathan> npsimons@hq:~$ vim rtlinux_kernel_2_3/Makefile
nathan> VERSION = 2
nathan> PATCHLEVEL = 4
nathan> SUBLEVEL = 0
nathan> EXTRAVERSION = -test1
nathan> <rest of toplevel Linux Makefile snipped for brevity>
nathan> <FYI, hq = ftp.fsmlabs.com>
nathan>
i could change the makefile of linux-2.0.38 to say it
is linux-2.4.0-test1. what the makefile says it is is
meaningless. a diff of the two linux kernel source directories
tells me that what is labeled by fsmlabs.com as linux-2.4.0-test1
is really linux-2.3.99-pre10-pre3.
terrylr> i do not know what alpha platform fsmlabs.com is developing
terrylr> on, but i can tell you that on an alpha pc164 is does not
terrylr> work. what version of gcc are you using to compile
terrylr> rtlinux-3.0-pre8 on the alpha platform?
nathan>
nathan> gcc-2.95.2.
nathan> Admittedly, we don't test RTLinux on a
nathan> large number of Alphas, but we do
nathan> compile kernels and modules with the
nathan> "generic" machine type so that they should
nathan> work everywhere.
nathan>
gcc-2.95.2 will not work on all alphas.
it does not work on my alpha. particular
it blows it's brains out when compiling
the emc software from nist which i am porting
to the alpha.
see below the caveats for gcc-2.95
particularly see the paragraphs i have marked
with '--->'.
<begin quote>
http://gcc.gnu.org/gcc-2.95/caveats.html
GCC 2.95 Caveats
GCC 2.95 will issue an error for invalid asm statements
that had been silently accepted by earlier versions of
the compiler. This is particularly noticeable when compiling
older versions of the Linux kernel (2.0.xx). Please refer
to the FAQ for more information on this issue.
GCC 2.95 implements type based alias analysis to disambiguate
memory references. Some programs, particularly the Linux kernel
violate ANSI/ISO aliasing rules and therefore may not operate
correctly when compiled with GCC 2.95. Please refer to the FAQ for
more information on this issue.
--->GCC 2.95 has a known bug in its handling of complex variables
--->for 64bit targets. Instead of silently generating incorrect code,
--->GCC 2.95 will issue a fatal error for situations it can not handle.
--->This primarily affects the Fortran community as Fortran makes more
--->use of complex variables than C or C++.
GCC 2.95 has an integrated libstdc++, but does not have an
integrated libg++. Furthermore old libg++ releases will not work with
GCC 2.95. You can retrieve a recent copy of libg++ from the
GCC ftp server. Note most C++ programs only need libstdc++.
--->Exception handling may not work with shared libraries,
--->particularly on alphas, hppas, rs6000/powerpc and mips based
--->platforms.
--->Exception handling is known to work on x86 GNU/Linux
--->platforms with shared libraries.
In general, GCC 2.95 is more rigorous about rejecting invalid
C++ code or deprecated C++ constructs than G++ 2.7, G++ 2.8, EGCS
1.0, or EGCS 1.1. As a result it may be necessary to fix C++
code before it will compile with GCC 2.95. G++ is also converting
toward the ISO C++ standard; as a result code which was previously
valid (and thus accepted by other compilers and older versions
of g++) may no longer be accepted. The flag -fpermissive may allow
some non-conforming code to compile with GCC 2.95.
--->GCC 2.95 compiled C++ code is not binary compatible with
--->EGCS 1.1.x, EGCS 1.0.x or GCC 2.8.x.
GCC 2.95 does not have changes from the GCC 2.8 tree that were
made between Sept 30, 1998 and April 30, 1999 (the official end of
the GCC 2.8 project). Future GCC releases will include all the
changes from the defunct GCC 2.8 sources.
<end quote>
terrylr> i have been through rtlinux.org many times.
terrylr> i have tried nearly everything before attempting
terrylr> to make linux-2.4.0-test9 work with rtlinux-3.0-pre8.tar.gz
terrylr> on my own.
--
Terry L. Ridder
Blue Danube Software (Blaue Donau Software)
"We do not write software, we compose it."
digging deep, i feel my conscience burn
i need to know who and what i am
this hunger jolts me from complacency
rocks me, makes me meet myself
----kendall payne---closer to myself---
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
