I've run into some problems that I think many others have encountered as
well. In a word...
headers...
My solution and frustration with them have lead me to write the story below.
Sorry about the length but I needed the therapy. 8->
I - The Beginning
Once upon a time I found a nice OS from overseas (I live in the US) named
Linux. Linux was European and of Finnish ancestory. As such, it was free
of the bonds and ties to the evil Imperial Empire. The Empire's
stormtroopers were powerless against it. It was a wonderful piece of work,
wrought by the keys of many dedicated souls from around the world. The
number imprinted upon this work was 0.96 but, alas, it also wore two patches.
It was also not blind, for it could c. This was of little consequence though,
for it was easily wrestled to the surface of my drive and ground up into
bits by HLU's GNU 2.2.2. Life was good.
II - A New Threat Appears
On the horizon a new beast soon appeared, however. This one had been tagged
0.97 and it wore one patch underscored by a single line. In some ways 97 was
better than 96 but there were some peculiarities with it. 97 had its arms and
legs in different places than 96 did. It's appendages in themselves were also
different. Once again I attempted to wrest the beast to the ground and was
successful. But confilict was looming in the air. HLU's GNU 2.2.2 tried and
tried to grind up the new beast. After much sputtering and wheezing, new
links were forged (although only symbolic) and 97 finally succumbed. HLU's
GNU 2.2.2 was once again victorious.
III - Defeat or Victory
After the battle a journey throught the disk sides revealed many head(er)s
strewn about. Some were real, some were just symbols of others lying
elsewere. Some appeared to be twins, but closer inspection revealed their
hearts were made of different mettle, although their family ties were
apparent.
In retrospect was this victory worth it, or, in some twisted way, did the
beast 97 really win? One thing was for sure, include(ing) a big mess and I
was responsible for its cleanup. The latest battle showed its effects.
HLU's GNU 2.2.2 was no longer the strong code grinder that it once was. It
was easily confused. The procedures that once were friends and were
willingly processed by HLU's GNU 2.2.2 were now in protest. Anarchy was
sure to follow. At this time I knew what it was that I had to do. Make
peace with 97's older sibling and resign myself to the fact that the beast
97 and I would have to remain at arm's length for the foreable future.
IV - Prolog
All is not lost however because there is a rumor in the kingdom that out of
this battle a new and stronger presence shall be reborn. It will appear as
HLU's GNU 2.2.2d, d for short. It is said that d will be able to easily
crush such outlaws as ps, free and w. It is also rumored that the beast in
97 can also be tamed without the price paid previously. We eagerly look
forward to that day when once again peace, tranquility and order will once
again be included.
The End
For those who couldn't follow the story I'll summarize. I was running Linux
0.96cpl2 and tried to convert to 0.97pl1+1. In compiling the kernel, many
headers were out of place as compared to the previous version. And for
those asking, yes, I did install the link between /usr/include/linux and
/usr/src/linux/include/linux. After finally getting 0.97 to compile, the
include directories were a mess. Programs that would compile before would
no longer compile cleanly, citing header confilcts. After beating this
problem around for a while I decided to go back to 0.96cpl2 until the header
problem could be resolved. From what I've read in previous postings some if
not all of the problems with the headers are to be fixed in the d release of
GNU C (HLU, any confirmation of this :) I contemplated hacking the headers
to get everything to compile but didn't feel comfortable with this solution.
So what it comes down to is this:
- Does anybody have any idea how the headers are supposed to be arranged
and what their contents should be?
- Which ones go where, which versions should be used, which ones shouldn't
be used, where can they be found?
- Should the headers included with the GNU 2.2.2 release in
0.96cpl2inc.tar.Z be used as well as those included with the 0.97
kernel? (I wasn't using them)
Any help that anybody could give would be appreciated. And "No!" I don't plan
on quitting my day job. :)
Thanks.
Ray Balister
| Chuck Ebbert | Why do so many machines need "noapic"? |
| Linus Torvalds | Linux 2.6.27 |
| Alan Cox | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Bart Van Assche | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| Frank Lichtenheld | Re: Trying to use git-filter-branch to compress history by removing large, obsolet... |
| Imran M Yousuf | Re: [kernel.org users] [RFD] On deprecating "git-foo" for builtins |
| Petr Baudis | Re: VCS comparison table |
| Aubrey Li | git clone problem through HTTP |
| Richard Stallman | Real men don't attack straw men |
| Marcos Laufer | dmesg IBM x3650 OpenBSD 4.3 |
| Parvinder Bhasin | OpenBSD and SYNFlood / DDoS protection |
| sonjaya | openvpn on openbsd 4.1 |
| Hugh Dickins | Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
| Arjan van de Ven | Re: [GIT]: Networking |
| Jens Axboe | Re: [BUG] New Kernel Bugs |
| Francois Romieu | Re: 8169 Intermittent ifup Failure Issue With RTL8102E Chipset in Intel's New D945... |
| Shared swap partition | 10 hours ago | Linux general |
| high memory | 2 days ago | Linux kernel |
| semaphore access speed | 2 days ago | Applications and Utilities |
| the kernel how to power off the machine | 2 days ago | Linux kernel |
| Easter Eggs in windows XP | 2 days ago | Windows |
| Root password | 2 days ago | Linux general |
| Where/when DNOTIFY is used? | 2 days ago | Linux kernel |
| How to convert Linux Kernel built-in module into a loadable module | 2 days ago | Linux kernel |
| Linux 2.6.24 and I/O schedulers | 2 days ago | Linux kernel |
| USB Driver -- Interrupt Polling -- A Little Help Please | 3 days ago | Linux general |
