LinuxQuestions.org
Visit Jeremy's Blog.
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 11-09-2010, 01:52 PM   #1
astanton
Member
 
Registered: Nov 2010
Distribution: Slackware64 -current
Posts: 82

Rep: Reputation: 5
Question Transmission Slackbuild fails to compile on Slackware64 13.1


I installed libevent, and that went ok, but following installation of the libevent-1.4.13-x86_64-1_SBo.tgz package I got the following error when running transmission.SlackBuild:

Code:
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking how to create a ustar tar archive... gnutar
checking build system type... i486-slackware-linux-gnu
checking host system type... i486-slackware-linux-gnu
checking for style of include used by make... GNU
checking for i486-slackware-linux-gcc... no
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/tmp/SBo/transmission-2.03':
configure: error: C compiler cannot create executables
See `config.log' for more details.
NOTE: There is no 'config.log'

Aren't the SlackBuilds x86_64 capable unless stated otherwise? i.e., when I installed others, they went fine, and when there were two different versions the 32 and 64 bit source had separate links.

Is there an easy way to tell (other than when, for example, NetBeans said there is no 64 bit SlackBuild available) if a SlackBuild is 64 bit capable?

Finally, if I go "multi-lib", and then start installing packages built w/SlackBuilds (or compiling/installing directly from source), will the 64 bit version be built for my platform automatically, or is there some way to choose 64 as opposed to 32 when there's a 64 bit version?

Last edited by astanton; 11-09-2010 at 01:54 PM.
 
Old 11-09-2010, 02:12 PM   #2
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Rep: Reputation: 223Reputation: 223Reputation: 223
Transmission compiles fine on 64bit.
The Slackbuilds.org Slackbuild appears correct, and functions as expected here.

Did you by chance alter the CFLAGS? That's a common error that happens with misspellings in the CLFAGS line.

Check what your uname -m returns as well.
Quote:
checking build system type... i486-slackware-linux-gnu
Is a dead give away for me

Last edited by disturbed1; 11-09-2010 at 02:15 PM.
 
Old 11-09-2010, 02:13 PM   #3
rmjohnso
Member
 
Registered: Mar 2006
Location: Wisconsin
Distribution: Slackware64-Current
Posts: 294

Rep: Reputation: 43
Are you using 13.1 or -current? If you are using -current, did you insalled libelf? If I remember correctly, I had the same problem compiling anything until I installed libelf.
 
Old 11-09-2010, 04:14 PM   #4
astanton
Member
 
Registered: Nov 2010
Distribution: Slackware64 -current
Posts: 82

Original Poster
Rep: Reputation: 5
Quote:
Originally Posted by disturbed1 View Post
Transmission compiles fine on 64bit.
The Slackbuilds.org Slackbuild appears correct, and functions as expected here.

Did you by chance alter the CFLAGS? That's a common error that happens with misspellings in the CLFAGS line.

Check what your uname -m returns as well.
uname -m returns "x86_64", and I'm running 13.1, not -current.

How would I check to see if the CFLAGS was somehow altered? I don't know how I would go about doing that, and as far as I know, I haven't done anything to alter it.

and uname -a returns:

Code:
$ uname -a
Linux medusa 2.6.33.4 #3 SMP Wed May 12 23:13:09 CDT 2010 x86_64 AMD Turion(tm) 64 X2 Mobile Technology TL-56 AuthenticAMD GNU/Linux
Thanks for your help so far

Last edited by astanton; 11-09-2010 at 04:18 PM.
 
Old 11-09-2010, 05:12 PM   #5
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Rep: Reputation: 223Reputation: 223Reputation: 223
Did you download the SlackBuild from here - http://slackbuilds.org/repository/13.../transmission/

What happens if you execute the SlackBuild this way -
Code:
ARCH=x86_64 sh transmission.SlackBuild
Older SlackBuilds did not have the uname -m case stanza to automatically set arch, and required users to either pass ARCH= or edit the SlackBuilds by hand. If you're using an older SlackBuild, this could be the case.
 
Old 11-09-2010, 05:44 PM   #6
astanton
Member
 
Registered: Nov 2010
Distribution: Slackware64 -current
Posts: 82

Original Poster
Rep: Reputation: 5
Thumbs up

Quote:
Originally Posted by disturbed1 View Post
Did you download the SlackBuild from here - http://slackbuilds.org/repository/13.../transmission/

What happens if you execute the SlackBuild this way -
Code:
ARCH=x86_64 sh transmission.SlackBuild
When I do that.... We have "Transmission"

Quote:
Originally Posted by disturbed1 View Post
Older SlackBuilds did not have the uname -m case stanza to automatically set arch, and required users to either pass ARCH= or edit the SlackBuilds by hand. If you're using an older SlackBuild, this could be the case.
it appears that is is there, partially, but on the third line in the code snippet below it appears to hardwire the SlackBuild to treat it as i486 (Am I correct here?).

There is a case statement dealing with uname -m, but if the ARCH is hardwired otherwise before that then the case statement nested in the if statement is never tested.

If that's correct, then would one just merely remove the reference in the third line of the code below, and if so, to what?

Code:
PRGNAM=transmission
VERSION=2.03
ARCH=${ARCH:-i486}
BUILD=${BUILD:-1}
TAG=${TAG:-_SBo}

if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) ARCH=i486 ;;
    arm*) ARCH=arm ;;
       *) ARCH=$( uname -m ) ;;
  esac
fi
  
CWD=$(pwd)
TMP=${TMP:-/tmp/SBo}
PKG=$TMP/package-$PRGNAM
OUTPUT=${OUTPUT:-/usr/local/packages}
  
DOCUMENTATION="AUTHORS COPYING INSTALL NEWS README"

if [ "$ARCH" = "i486" ]; then
  SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  LIBDIRSUFFIX=""
elif [ "$ARCH" = "i686" ]; then
  SLKCFLAGS="-O2 -march=i686 -mtune=i686"
  LIBDIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fPIC"
  LIBDIRSUFFIX="64"
else
  SLKCFLAGS="-O2"
  LIBDIRSUFFIX=""
fi
Thanks for solving this one. I wanted to use Transmission at times instead of ktorrent
 
Old 11-09-2010, 05:49 PM   #7
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Rep: Reputation: 223Reputation: 223Reputation: 223
Quote:
Originally Posted by astanton View Post
When I do that.... We have "Transmission"

it appears that is is there, partially, but on the third line in the code snippet below it appears to hardwire the SlackBuild to treat it as i486 (Am I correct here?)
That's it. Case solved

I'll fire off an email to the Script maintainer so they can fix it.
 
Old 11-09-2010, 06:20 PM   #8
Michielvw
Member
 
Registered: May 2005
Location: Leicester,UK
Distribution: Slackware
Posts: 108

Rep: Reputation: 19
Fixed this in my branch, so it'll get pushed out on mext update.
 
1 members found this post helpful.
Old 11-09-2010, 09:50 PM   #9
bnguyen
Member
 
Registered: Jul 2010
Distribution: Slackware
Posts: 125

Rep: Reputation: 32
Another part that could be also 'improved' is to substitute 'VERSION=2.03' by new standard 'VERSION=${VERSION:-2.03}'. I personally don't like the idea of having to edit the SlackBuild to make it works when compiling another version. Actually I reported this to the maintainer and he said he will do that in next update.
 
Old 11-10-2010, 06:21 PM   #10
astanton
Member
 
Registered: Nov 2010
Distribution: Slackware64 -current
Posts: 82

Original Poster
Rep: Reputation: 5
Cool!

I stepped on a bug

Thanks for all the help! And glad I had something to contribute as well.
 
  


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
cannot compile qjackctl from slackbuild on slackware64-current trumpet_tom Slackware 10 06-13-2011 12:57 PM
[SOLVED] bluez.Slackbuild fix for Slackware64-13.0 drumz Slackware 5 05-04-2010 11:30 PM
How can I make PyQt4 slackbuild compile in Slackware64 <current>...? Alexvader Slackware 9 12-30-2009 07:45 AM
Slackbuild of Scilab 5.1 fails under Slackware64 13... is this reproducible...?? Alexvader Slackware 21 11-29-2009 02:29 PM
For the Krusader fans on slackware64 slackbuild ROXR Slackware 0 07-20-2009 06:03 PM


All times are GMT -5. The time now is 02:50 AM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration