LinuxQuestions.org

LinuxQuestions.org (http://www.linuxquestions.org/questions/index.php)
-   Slackware (http://www.linuxquestions.org/questions/forumdisplay.php?f=14)
-   -   Need a little help with a slackbuild I want to make (http://www.linuxquestions.org/questions/showthread.php?t=4175436956)

irgunII 11-13-2012 10:57 AM

Need a little help with a slackbuild I want to make
 
Hi gang,

I'm trying to make a slackbuild for an app that has a requirement. The requirement is fltk 1.3.

I have fltk 1.3 installed, but because it's named 'fltk13-config', the ./configure of the app source craps out because it's looking for 'fltk-config'.

In the slackbuild of the app I simply don't know how or where to change it so it will use the 'fltk13-config' instead of the 'fltk-config'.

Should it be somewhere in this section of the slackbuild?:

CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
./configure \
--enable-ssl \
--prefix=/usr \
--libdir=/usr/lib/${LIBDIRSUFFIX} \
--sysconfdir=/etc \
--localstatedir=/var \
--mandir=/usr/man \
--docdir=/usr/doc/$PRGNAM-$VERSION \
--build=$ARCH-slackware-linux


I'm not a programmer or anything like that but I can usually figure out enough to make a slackbuild work if I look at different other slackbuilds, but this one has me stumped. I'd like to build this slackbuild so that I can ask the maintainer of the app that requires this if I can take over maintenance, since the app that's on slackbuilds.org is pretty old.

markush 11-13-2012 03:14 PM

I'm not a programmer as well, but I would say that this is not possible with the Slackbuild.script. You would have to change the sources of the program (for which you are writing the SlackBuild.script).

But I would recommend to simply create a symlink (execute this code as root within the directory where the fltk13-config resides
Code:

ln -s fltk13-config fltk-config
afterwards building the package should work.

Well, you can of course put making the symlink into the SlackBuild.script, but be sure to use the correct path (using whereis).

Markus

irgunII 11-13-2012 03:34 PM

Quote:

Originally Posted by markush (Post 4828666)
I'm not a programmer as well, but I would say that this is not possible with the Slackbuild.script. You would have to change the sources of the program (for which you are writing the SlackBuild.script).

But I would recommend to simply create a symlink (execute this code as root within the directory where the fltk13-config resides
Code:

ln -s fltk13-config fltk-config
afterwards building the package should work.

Well, you can of course put making the symlink into the SlackBuild.script, but be sure to use the correct path (using whereis).

Markus

Hi,

Thanks, I appreciate the help and ideas, and not saying that is wrong or right, but I guess I need to clarify a little more...there is no fltk-config, but that is what the app's ./configure is looking for, yet the app itself *requires* fltk 1.3 (the config is looking for version(s) *lower* that 1.3), that's why I'm trying to figure out how to have the slackbuild use the fltk13-config that is installed from the fltk 1.3. If there's no fltk-config at all, then there's nothing to symlink to, is that correct or am I still missing something?

Surely there's a way to tell the app's ./configure to use the fltk13-config instead of looking for fltk-config. I just don't know how to write that into the slackbuild. :(

markush 11-13-2012 03:59 PM

You could look at the sources, most often theres a README or INSTALL file where configure is explained. Sometimes you can execute
Code:

./configure --help
and see the options.

I would also recommend to take a look at other Slackbuild.scripts, maybe you'll find a solution there.

Can you configure and compile the program without a Slackbuild.script? and how do you do this, could you please describe in detail? maybe this give us some hints what you mean. Which program is it you're writing the Slackbuild.script for?

Markus

TracyTiger 11-13-2012 04:14 PM

Quote:

Originally Posted by irgunII (Post 4828517)
I'm trying to make a slackbuild for an app that has a requirement. The requirement is fltk 1.3.

I'd like to build this slackbuild so that I can ask the maintainer of the app that requires this if I can take over maintenance, since the app that's on slackbuilds.org is pretty old.

Perhaps the Slackbuilds.org mailing list or their IRC Chat would be better place for your question since slackbuilds are what that group is all about.

solarfields 11-13-2012 04:22 PM

which is the program you want to compile?

BroX 11-14-2012 04:03 AM

Creating a symbolic link, as suggested by markush in post #2, is (probably) by far the easiest solution.

markush 11-14-2012 05:59 AM

The OP has already posted his question to the mailinglist of slackbuilds.org. The question there differs a bit from the posting here:
Quote:

Originally Posted by OP@slackbuilds.org
...
I'm trying to make a slackbuild for an app that has a requirement. The
requirement is fltk 1.3.

I have fltk 1.3 installed, but because it's named 'fltk13-config',
the ./configure of the app source craps out because it's looking for
'fltk-config'.

In the slackbuild of the app, I simply don't know how or where to change it so
it will look for and use the 'fltk13-config' instead of 'fltk-config'.

Should it be somewhere in this section of the slackbuild?:
...

he got an answer
Quote:

Originally Posted by ErikHanson@slackbuilds.org
I think you might be able to solve this with:

sed -i 's/fltk-config/fltk13-config/g' configure.in
autoreconf

which seems to be helpful.

Markus

irgunII 11-14-2012 07:37 PM

Yes, the sed thing did the trick.

I don't understand how a symlink would have worked if there is no plain fltk to link to. There is *only* the fltk13.

Anyway, I'd done a 'man sed' before I asked my question(s) here and the mailing list, but I get too confused too easily, especially when one just doesn't understand all the programming stuff, though the sed answer I got looks kind of simple. I'm going to look into the man page again and see if just a little here and a little there will help me understand it easier and better.

Oh, and the program was Dillo, btw.

Thanks again all for the suggestions and help!

irgunII

BroX 11-15-2012 01:42 AM

Quote:

Originally Posted by irgunII (Post 4829657)
I don't understand how a symlink would have worked if there is no plain fltk to link to. There is *only* the fltk13.

You would have created a link named 'fltk' pointing to 'fltk13'.

Good you got it solved the proper way with sed!


All times are GMT -5. The time now is 08:51 PM.