I have discovered that the configure for xorg and for the viaopenchrome all abort and complain about pkgtool. I have EVERYTHING installed and it says it can't find X11 or Xorg.pc in /var/log/packages is all the installed descriptors and NONE of them say .pc anything.

My question is what do I need to do to fix this problem. both configure scripts halt and complain about missing packages. I really need to compile openchrome. but nothing in my system is adequate.

so I really need detailed instructions on how to make general changes to pkgtool and its data.

What "configure for xorg" are you talking about? Did you build the new X from source or just try to slap a bunch of packages in your outdated system?

You might want to upgrade Slackware...

You probably mean "pkg-config" and not "pkgtool". Your problems have nothing to do with Slackware's pkgtools. Your Slackware is just old.

Eric

Yes I know that my system is old. I need to fix the problem and need information about what changes were made in pkg-config and pkg-tool. all I want to do is UPGRADE my system.

I recommend backing up your important files and doing a fresh install of the latest Slackware. Slackware 13RC1 has already been released, so it might be a good time to install -current, but the release will probably be official soon.

Are you trying to tell me you dont know how to fix that system? I was asking how the pkg system changed. that is apparently the wrong question to ask. it seems nobody knows except maybe the one who changed it.

Apparently you are asking all the wrong questions. This "the pkg system changed" has nothing to do with your problem of not being able to compile software. The tool "pkgtool" is a Slackware script and part of Slackware's "pkgtools" package - which also contains 'installpkg', 'removepkg', 'upgradepkg' and friends. It has nothing to do with compiling binaries, it is only used for the management of Slackware packages.

The program "pkg-config" on the other hand is part of the "pkg-config" package that Slackware ships. This belongs to the toolkit (if you wish) that enables you to compile source code into binaries.

What you need to do is start providing us with actual error messages instead of trying to annoy the people who stepped in to help you. We do not work with crystal balls in this forum - there's the "Sourcemage Linux" distribution for that kind of stuff.

Eric

ok I want to configure Xorg.1.5.3 and viaopenchrome both abort with error messages like X11 is missing and via complains that it connot find .pc and requests the path. i dont know how to respond to those errors

I know that all my packages are in var/log/packages
I copied the X11.xxxx to x11.xxxx.pc and tried again but got a similar message. both problems may be a script in the configure script but I dont know where to look for it because it is recusive.

With "actual error messages" I meant, copy whatever you see on your terminal console into a post in this thread. Without the literal text of the errors you are experiencing we can not even begin to troubleshoot your issue.

But what I suspect is that you are trying to compile the xorg-server 1.5.3 sources on Slackware 10.2. Without seeing your errors, I would say that this will have a high probability of failing. Slackware 10.2 is just too old to support the compilation of modern software without also upgrading a lot of other parts of your system. If you think your computer is too old to be able to run Slackware 12.2 or newer, then I would not even consider trying to upgrade your X.Org.

The best you can do (even if it sounds like a lot of work) is to start from scratch: save all your personal data, save the contents of the /etc/ directory, wipe clean your computer and install a fresh Slackware 12.2 (or 13.0 when it is released). Then restore your personal data from the backup you made.

Eric

sorry cannot copy to this computer from my system. but I understand the general tenor. upgrade stupid. we dont know nothing about antique systems.

none of the advice was helpful and I already knew that my system was tool old. the PC are both NEW machines and require open chrome. maybe Ican get the newer system onto my network and the web.


thanks for the fish

So upgrade it. Getting it to 11 seems easy enough.

11 was released in December 2006, IIRC.

the problem is I cannot connect the linux systems to the web. I have tried for several months and then I had to preplace BOTH machines. and the machine have viachrome9 built into the motherboard. Now that is why I wanted to upgrade my system. but since connecting to the web is problematic I cannot perform those particular actions. sigh. I cannot connect to the web from my linux system. end of statement. I know that lots of people download patches and even whole systems. I am downloading ISO Slackware into my winXP system. it is very very unlikely to work but I am trying. I will let the "solution" work until it fails.

and no I do not think this was a solution. it was an evasion.

Perhaps you should open a new thread for help in getting those machines connected to the Internet. If your XP machine can connect, it should be possible to get the Linux computer connected as well, unless you are using some Windows-centric method of connecting to your ISP.

Coming back to your complaint "upgrade stupid. we dont know nothing about antique systems", of course we know about antique systems. The issue is that upgrading X.Org to 1.5.3 means that so much else needs to be upgraded (gcc, glibc, and others) that you will end up with an unmaintainable mix of old and new - if it works at all. It is better in the long run to scratch your old Slackware installation and put a new version of Slackware on it. At least you will be sure that all software components will have been tried and tested and compiled with the right options.

You mentioned that you were unable to get the error messages from your Slackware computer to your Internet-connected machine and into this thread. This is an option> when you want to capture the output of your compilation process, add the following to the end of your commandline:

This will re-direct a copy of all output (errors too) to the file "build.log" in your current directory. You can then transfer this build.log to your XP computer using a floppy (mcopy build.log a:) or using a USB stick.

Eric

just for the record I downloaded the 12.2 cdrom image and found out that it would probably work in a rw cd but I dont have one and could not verify that there was actually any usable data in the object. it was the right size but it has many bytes of 0000. I think that is a quirk of cdroms. but it does not change the fact that downloading the image is not usable. and I dont have enough memory or otherwise to process it. I discovered that when I reinstalled my system it removed my virtual memory data tables swapon -a nolonger works normally.

sigh I have slept since then and need to recreate the files.
I do know how to do it. but sometimes remembering is hard.
then i should be able to process the file and determine if it is sane.

I have two linux systems one on this machine and a standalone machine. the goal is to connect those systems to the web. I upgraded my machines to new motherboards and chrome9cl video on board. that is how my 10.2 systems got into this peculiar situation. I will recreate my virtual memory pagefiles and see if i can improve my inspection of the cdrom image.