LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-08-2010, 11:35 PM   #1
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,844

Rep: Reputation: 452Reputation: 452Reputation: 452Reputation: 452Reputation: 452
Error compiling Blood Frontier using sbopkg


I'm having a problem compiling Blood Frontier on Slackware64-current. I believe this problem is also related to why I can't use make xconfig as well. Here is a bit of the error.

Code:
g++ -O2 -fPIC -Wall -fsigned-char -DINTERFACE -DIRC -Ishared -Iengine -Igame -Ienet/include -I/usr/X11R6/include `sdl-config --cflags` -o shared/cube.h.gch.tmp shared/cube.h
In file included from shared/cube.h:14:
/usr/include/string.h:33:20: error: stddef.h: No such file or directory
In file included from /usr/include/stdio.h:75,
                 from shared/cube.h:15:
/usr/include/libio.h:53:21: error: stdarg.h: No such file or directory
In file included from shared/cube.h:19:
/usr/include/limits.h:125:26: error: no include path in which to search for limits.h
In file included from /usr/include/bits/socket.h:31,
                 from /usr/include/sys/socket.h:40,
                 from /usr/include/netinet/in.h:25,
                 from enet/include/enet/unix.h:11,
                 from enet/include/enet/enet.h:18,
                 from shared/cube.h:68:
/usr/include/limits.h:125:26: error: no include path in which to search for limits.h
In file included from shared/cube.h:14:
/usr/include/string.h:44: error: 'size_t' has not been declared
/usr/include/string.h:48: error: 'size_t' has not been declared
/usr/include/string.h:57: error: 'size_t' has not been declared
/usr/include/string.h:64: error: 'size_t' has not been declared
/usr/include/string.h:67: error: 'size_t' has not been declared
/usr/include/string.h:74: error: 'size_t' has not been declared
/usr/include/string.h:76: error: 'size_t' has not been declared
/usr/include/string.h:81: error: 'size_t' has not been declared
/usr/include/string.h:87: error: 'size_t' has not been declared
/usr/include/string.h:114: error: 'size_t' has not been declared
/usr/include/string.h:116: error: 'size_t' has not been declared
/usr/include/string.h:131: error: 'size_t' has not been declared
/usr/include/string.h:139: error: 'size_t' has not been declared
/usr/include/string.h:145: error: 'size_t' has not been declared
/usr/include/string.h:152: error: 'size_t' does not name a type
In file included from shared/cube.h:14:
/usr/include/string.h:167: error: 'size_t' does not name a type
/usr/include/string.h:181: error: 'size_t' has not been declared
/usr/include/string.h:282: error: 'size_t' does not name a type
/usr/include/string.h:286: error: 'size_t' does not name a type
/usr/include/string.h:380: error: 'size_t' has not been declared
/usr/include/string.h:381: error: 'size_t' has not been declared
/usr/include/string.h:387: error: 'size_t' has not been declared
/usr/include/string.h:390: error: 'size_t' has not been declared
/usr/include/string.h:397: error: 'size_t' does not name a type
/usr/include/string.h:404: error: 'size_t' does not name a type
/usr/include/string.h:436: error: 'size_t' has not been declared
/usr/include/string.h:449: error: 'size_t' has not been declared
/usr/include/string.h:453: error: 'size_t' has not been declared
/usr/include/string.h:457: error: 'size_t' has not been declared
/usr/include/string.h:460: error: 'size_t' has not been declared
/usr/include/string.h:538: error: 'size_t' has not been declared
/usr/include/string.h:550: error: 'size_t' has not been declared
/usr/include/string.h:575: error: 'size_t' has not been declared
/usr/include/string.h:578: error: 'size_t' has not been declared
/usr/include/string.h:591: error: 'size_t' has not been declared
In file included from /usr/include/stdio.h:75,
                 from shared/cube.h:15:
I have a parallel install of current on another partition that does not have this problem. Somewhere along the line I screwed something up somehow. I just wish I knew where to look first.

There is a lot more of this error, I have only shown a small part. I will attach the whole thing as a txt. I did run a diff on a few of these, and their is no difference in the files showing an error between the partitions.
Attached Files
File Type: txt error.txt (24.6 KB, 17 views)

Last edited by mlangdn; 03-08-2010 at 11:36 PM. Reason: A bit more info.
 
Old 03-09-2010, 05:34 AM   #2
dunric
Member
 
Registered: Jul 2004
Distribution: Void Linux, former Slackware
Posts: 498

Rep: Reputation: 100Reputation: 100
Make sure glibc, gcc and gcc-g++ packages are properly installed. Missing header files contain above mentioned packages.
 
Old 03-09-2010, 06:42 AM   #3
XGizzmo
Member
 
Registered: Mar 2007
Distribution: Slackware
Posts: 264

Rep: Reputation: 69
May also want to install/reinstall the kernel headers package.
 
Old 03-09-2010, 09:27 AM   #4
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,844

Original Poster
Rep: Reputation: 452Reputation: 452Reputation: 452Reputation: 452Reputation: 452
I just compiled a custom kernel a couple of days ago, and it worked just fine. This problem has been around for a few weeks. I also compiled Urban Terror just fine. All of this using sbopkg. (except for the kernel)
 
Old 03-09-2010, 11:07 AM   #5
knudfl
LQ 5k Club
 
Registered: Jan 2008
Location: Copenhagen DK
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,511

Rep: Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641
You have one error only ..
Quote:
error: stddef.h: No such file or ...
error: stdarg.h: No such file or ...
g++ can't find the gcc headers in
/usr/lib64/gcc/x86_64-slack64-linux/4.x.x/include/
( The path looks something like that in my slamd64-12.1 ).

I.e. you may have to use :
make CXX="g++ -I /<path-to-the-gcc-headers>"
.....
 
Old 03-10-2010, 05:19 AM   #6
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,844

Original Poster
Rep: Reputation: 452Reputation: 452Reputation: 452Reputation: 452Reputation: 452
The test partition works fine. I'm just gonna blow this one away and start over. I have good backups and can put it back together in a couple of hours. It all began when I had multilib enabled on this machine. I'll never do that again. It was just for google earth anyways. Its probably sumpin' simple, but I give up.
 
Old 03-29-2010, 01:18 PM   #7
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,844

Original Poster
Rep: Reputation: 452Reputation: 452Reputation: 452Reputation: 452Reputation: 452
All-righty, then.
I did not blow away this install. Most things worked the way it was expected to work. I was able to compile most programs, including custom kernels. But some things refused to go as planned - Bloodfrontier being one of these problems. Getting xconfig to work was another. I just refused to give up.

Today, I decided to revisit this vexing problem. Thanks to knudfl, I finally stumbled onto the problem. His above post about gcc headers made me search out and thoroughly through the system files. Those pesky includes were indeed missing. Since I am running -current, I had assumed that I upgraded gcc and indeed the 4.4.3 folder was in place. That said, none of the include files were in there anywhere. I am my own worst enemy(a).

Now one must wonder how I was ever able to compile anything? There is a simple answer to that as well. Alien's multilib 4.4.2 was still in place. I was running multilib at one point, then decided I didn't need that capability just for Google earth. I thought all of that was blown away at one point. I was wrong, and just plain brain dead in this case.

Bloodfrontier happily compiled just now. Xconfig is now working again, and I bet I solved a host of future problems as well.

I thank, and apologize to all that responded in this thread, and a thread I had for my problem with xconfig that was caused by my own stupidity. I will mark this as solved.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
sbopkg error message. glore2002 Slackware 23 09-18-2009 05:27 PM
Blood II: The Chosen WINE Error Chargh Linux - Games 19 06-09-2009 07:28 AM
Sbopkg error adriv Slackware 5 04-09-2009 04:11 PM
Blood Frontier - Cube2 based FPS - Interesting grenade assortment farslayer Linux - Games 4 02-16-2009 06:24 AM
LXer: Blood Frontier: The Latest Open-Source FPS LXer Syndicated Linux News 1 02-02-2009 07:39 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:45 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration