dive, the -W option does that. The most hopeful and ambitious example:'src2pkg -A -I -W sometarball' to automatically do as much as possible, install the resulting package and clean up the temp files.

For your gnome stuff have a look here:
http://distro.ibiblio.org/pub/linux/...E-COMPAT-2.10/

You need all the stuff through group 3 for gneumeric (plus libgsf? or something like that). See the HOWTO for the build order or just download the packages if you want. You can also see the examples which are installed with src2pkg for an example GroupBuild script which will help you automate the build if you decide to do it that way.

Ah thanks very much. Didn't see the -W switch. Will have another go at gnumeric then

dive, that -W options cleans everything up good. gnashley, I used that script of yours yesterday and its awsome stuff, I am not sure but since I was doing it from inside Xfce it seemed to hang on 'make' or the process is tremendously long because the size of scribus and I had no idea how long it was suppose to take. .tar.bz2 downloaded into /build where I had put the script. Later I did use src2pkg to build .tgz pkg and that took forever to compile too, I think scribus is bigger than slackware12 pkg. I already have Ooffice and gimp. lol So I am having second thoughts about installing scribus,until have a clearer concept of how I want to use Slackware12. My priority is web server, I have an Xp and mac so I installed all the graphic programs on XP since it has newest hardware. As I work on setting up my power book, I see it is more like Slackware, looks like some unix branch off probably accounting for greater stability over MS. hmmm
I would like to shh into Slack and Xp with it. LOLOL Can I adopt your script to OS X? Will I ever get my web pages up? LOL Know this is way off topic but its fun! Thanks

dive, look at lufbery's post 42

Use putty from XP to access Linux box.

Hi,
What is the position at the moment with src2pkg regarding
tool chain building from source code?

Has anyone tried?
How should I even begin?
Should I even try?

The background to this is that when src2pkg version 1.0.0 came
I tried but it proved more challenging than I was anticipating.

Only after a great deal of help from gnashley and others on this
forum was I able to make the first few packages of a tool chain.

However it proved that I could install these on other computers
with only a minimal Slackware installation and use them to build
the rest of the chain.

There are plenty of examples around on internet of how to build
tool chains from source code.

John

Do you want 1 toolchain package, or a cross chain, or something else? Most of my work has been with cross (and canadian-cross) toolchains, so I'm afraid I'm not in a great position to advise, however that said:

Building a toolchain shouldn't be any more difficult than anything else (except for the long ./configure and maybe installing it using -REAL not -JAIL or -DESTDIR) ...

src2pkg typically has a 1 to 1 relationship with tarball to package, but clearly a toolchain is made of multiple programs/tarballs. Gilbert has a src2pkg script for gcc here, if all you need is a variety of compiler versions:
http://distro.ibiblio.org/pub/linux/....6/gcc.src2pkg

There's no reason you couldn't script a chain build - binutils, gcc stage 1, glibc, gcc stage 2 - with src2pkg, other than the fact you'll end up with one package for each app.

For cross work, I'd suggest installing everything to /opt/mycrosschain ( --prefix=... ) and then tarring the result up for transportation. Investigate the original makepkg to build a package out of /opt/mycrosschain. For native work you can use the same approach, and add in some /etc/profile.d/mycrosschain.sh script to make sure the chain is in everyone's PATH at the start.

You can use the same approach for the cross chains, too, but I think it might be better to deal with them in makefiles.

Erm, so, in closing ... "Can't see why not." but "Don't really understand what you want."

Keep us informed! =)
- Piete.

Edit: As I wrote that, it occurred to me that we've done this before ... so I dug out the original thread and had a read through. What struck me was that you were attempting to use src2pkg from the commandline, explicitly passing the arguments you need. I suspect you need to look at using the scripting facilities of src2pkg and adding some environment variables like CC into it. I can foresee problems with variable scoping under bash if you attempt something like:

CC=gcc-avr
src2pkg ...

The following is an example of what I mean:

Or install Cygwin and use SSH. Cygwin is pretty cool because it's a complete, Linux-like environment that runs in Windows. You can compile and install a whole bunch of Linux software and have it run natively in your Windows installation.

http://www.cygwin.com/

Installation is a breeze too. I used both Putty and SSH in Cygwin and had better results from Cygwin. I could also run X-windows programs from my Linux computer remotely on the Windows computer using Cywing's X-windows environment.

Now back to your regularly scheduled src2pgk discussion.

Regards,

-Drew

I prefer a separate package for every member of the chain.
Mainly because some members are updated more often than others.

Going back to Gilberts posts "The Magic Package Maker comes of age"
and "src2pkg-1.6 released" gives the background.

You will also see that another member tuxdev recommended that I take
a look at clfs. I took that advice and even went as far as doing a
build but so far only the embedded so not a Slackware alternative at the
moment. Many thanks tuxdev if you ever read this.

At first I used command line but when 1.6 came I tried a script and to
edit it to use the cross-compiler without success.

I have not yet installed 1.9.2 just wondering if the time has come to
try again.

Although my main interest is avr there are similar procedures for say
mips and arm.

Since source code builds are well documented. There are instructions in
the tarball. Is there any way that I can use src2pkg to track a source code
installation on Slackware and get at least a script or even a pkg ?

John

I have come across a problem with xscreensaver: http://www.linuxquestions.org/questi...nsaver-615543/

Can I confirm the functionality of a couple of switch combinations please? If I use -DEST or -JAIL the package isn't installed unless I use the -I switch as well. But if I use -REAL the package is installed regardless of whether I use -I. The behaviour I see with the following command line is that the package is created and installed:
It's no big deal since I build on a test box anyway. I'm still learning how to use src2pkg so I just want to make sure I understand what I've done so far.

src2pkg should never permanently install an application. -REAL does install the app on the system, then rolls back the system. The rollback can fail, but that's rare and means the install scripts are doing funny things. If that's the case, then you need to manually install the application into $PKG_DIR. You may have to write a doinst.sh as well.

That's not what I'm seeing here. I just uninstalled the php-5.2.5-i686-1.tgz package I created with that command. I also made sure that the installed files were actually deleted, the entry in /var/log/packages was deleted, Apache was stopped (for the module) and the previous /tmp/php* directories were gone.

After running src2pkg the package was successfully created, the temporary files under /tmp/php* were deleted and no entry has been created under /var/log/packages. However, the files are installed (under /usr/local/lib/php, etc.). Also, this time, the list of files in /var/log/packages/php-5.2.5-i686-1 has the first 2 characters missing for each line. For example r/local/man/man1/php.1 instead of usr/local/man/man1/php.1.

Checking my bash history, the command I actually ran was:
Since my other packages work properly, I'm pretty sure that the problem is with something I'm doing - I just haven't figured it out yet.

I encountered that corrupt package DB bug a little while back in 1.9.2. Make sure you are running the most current version (1.9.3-2). The corrupt file means that uninstalling will not actually delete any files (you can see that by reading the output of removepkg).

Thanks for that - I've upgraded from 1.9.2-2 to 1.9.3-2 and the DB problem has gone away.