Messages in this thread | ![/](/images/icornerl.gif) | | Date | Wed, 16 Apr 2003 16:50:54 +0200 (CEST) | From | Ferry van Steen <> | Subject | Compilation problems |
| |
Sorry to bring this here, I know it's not the most correct place, but I wouldn't know where else to find people that know this (I've asked in several places)
First off, I have 2 computers a notebook with a P3, gentoo 1.4rc2 stage 1 and a athlon xp workstation with gentoo 1.4rc2. The workstation has an IDE controller for which partially open-source drivers are available.
At this moment I have 2 disks for linux in the workstation, one on the normal ide controller cause I couldn't get the RAID one to work and one on the RAID. As you might understand I want to loose the one on the normal IDE controller. Therefore, I started compiling on the notebook.
Both computers have gentoo from stage 1, all applications/libraries are thus fully optimized for the CPU they run on.
Now when I compile a 2.4.20 kernel on either of them, with the athlon CPU selected in the kernel config these run, no matter if it was compiled on the notebook or the workstation, they run fine on the workstation. However, if I compile the module on the notebook, against the sources of the kernel that was compiled for the workstation and -march=athlon (just like the kernel) this module will give unresolved symbols errors. If however I compile this module on the athlon it runs without a problem.
I don't know a whole lot about the lower level things of compilation like linkage, but what I think is that maybe part of the c libraries that have already been compiled are transferred (linked with) the module and that this P3 optimized code causes problems. This however are mere assumptions and raises questions like why isn't the kernel bothered by this? And AFAIK all P3 options should be supported on an Athlon-XP (that is /proc/cpuinfo has all the flags my p3 has as well).
Any ideas what might cause this behaviour?
Kind regards
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |