LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
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 02-06-2008, 01:26 PM   #16
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,298
Blog Entries: 61

Rep: Reputation: Disabled

I get the same results for 'uname -m' and 'uname -i' with a Sempron 2600+.
 
Old 02-06-2008, 07:28 PM   #17
swampdog2002
Member
 
Registered: Jul 2005
Distribution: Slackware 12.2, 13.0, openSUSE 11.2
Posts: 400

Rep: Reputation: 33
gnashley, I received your email with the attached file, and replaced the existing 01-pre process file with this one. I compiled a few programs and I did not notice any errors in relation to the previous version of src2pkg. Among one of the packages I used src2pkg on, both before and after the file replacement, was for FileZilla. Here is the output from the package compilation using src2pkg 1.9.4 w/ new file:
Code:
root@slack-deathstar:/home/swampdog/Downloads# src2pkg FileZilla_3.0.6_src.tar.bz2 
Notice - Source name contains capital letters.
Resetting package name - Using: filezilla_3.0.6
Found source archive: FileZilla_3.0.6_src.tar.bz2
Deleting old build files - Done
Creating working directories:
   PKG_DIR=/tmp/filezilla_3.0.6-src-pkg-1
   SRC_DIR=/tmp/filezilla_3.0.6-src-src-1
Unpacking source archive - Done
Correcting source permissions - Done
Checking for patches - None found
Found configure script - Configuring sources using:
   CFLAGS=-O3 -march=athlon-xp -pipe -fomit-frame-pointer ./configure --prefix=/usr
Configuration has been - Successful!
Compiling sources - Using: 'make'
Compiling has been - Successful!
Installing in jail root - Using: 'make install'
Safe installation - Successful!
Processing package content:
Correcting package permissions - Done
Stripping ELF binaries - Done
Checking for standard documents - Done
NOTICE!  Moving man pages installed under usr/share/man to usr/man
Compressing man pages - Done
Creating slack-desc - Creating slack-desc file in PKG_DIR
Copying slack-desc to: new.slack-desc in CWD.
   The files new.slack-desc (and new.slack-required) are copies
   of the slack-desc (and slack-required) files inserted in the
   package. If you want to change the content, edit and then
   save the files as simply slack-desc (and slack-required).
   Otherwise, they are re-created when you repeat the build.
Searching for links in PKG_DIR - None found
Making installable package - Done
Package Creation - Successful! - Package Location:
/tmp/filezilla_3.0.6-src-athlon_xp-1.tgz

Last edited by swampdog2002; 02-06-2008 at 07:29 PM.
 
Old 02-06-2008, 11:08 PM   #18
tuxdev
Senior Member
 
Registered: Jul 2005
Distribution: Slackware
Posts: 2,012

Rep: Reputation: 115Reputation: 115
You need to use the -n and -v switches since the archive has a weird name.
 
Old 02-07-2008, 02:24 AM   #19
gnashley
Amigo developer
 
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,928

Original Poster
Rep: Reputation: 612Reputation: 612Reputation: 612Reputation: 612Reputation: 612Reputation: 612
Yeah, Tim is right. This is not good:
Resetting package name - Using: filezilla_3.0.6
(this means that the version is 'src'. These errors with name and vesrion are not dangerous, but it will keep upgradepkg from working properly.
This will fix that problem
src2pkg -n=filezilla -v=3.0.6 FileZilla_3.0.6_src.tar.bz2

Otherwise, thanks very much for testing the new CFLAGS code -it seems to be working as expected. Only time will tell if those options are really the best ones to use -I can imagine that -O3 might be a problem for some compiles, but maybe not.
So if you ever have problems with this let me know. I also have doubts about whether to set the ARCH=athlon_xp by default for packages compiled this way. I believe that such packages should run alright on regular ix86 machines so it may not be desirable to name them with ARCH=athlon_xp. If you don't like this you can alwas specify the ARCH (with -a=i486). I'm interested in what you, the users, think about this so that I can set default values which are agreeable to the users whenever it seems to be a harmless matter of preference.
Thanks again!
 
Old 02-07-2008, 06:04 AM   #20
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,298
Blog Entries: 61

Rep: Reputation: Disabled
Just Googling for "CFLAGS" and other relevant stuff, came across this:

http://forums.gentoo.org/viewtopic-t-388225.html
 
Old 02-07-2008, 06:14 AM   #21
samac
Senior Member
 
Registered: Mar 2004
Location: Kirkwall, Orkney
Distribution: Linux Mint 20.3 - Cinnamon
Posts: 1,425

Rep: Reputation: 139Reputation: 139
Hi gnashley

Tested your new addition, and it works just like the file that was replaced.

The packages that worked before work now, and the packages that I was inadequate for, well I am still inadequate.

The only problems that I have had were caused by my lack of knowledge. So I have dug out my old university notes on shell programming and begun revising.

samac
 
Old 02-07-2008, 06:31 AM   #22
crashmeister
Senior Member
 
Registered: Feb 2002
Distribution: t2 - trying to anyway
Posts: 2,541

Rep: Reputation: 47
You can always use -mtune=native if you really only need the result to run on one specific cpu (being the same type it was build on).AFAIK this option was introduced with gcc 4.0 - was the first time I got aware of it anyway.

native
This selects the CPU to tune for at compilation time by determining the processor type of the compiling machine. Using -mtune=native will produce code optimized for the local machine under the constraints of the selected instruction set. Using -march=native will enable all instruction subsets supported by the local machine (hence the result might not run on different machines)

The -Os (size optimized)switch is normally safer to use than -O3 if you just compile everything with the same switch - it enables all the O2 options minus the ones that increase size.The result should still be plenty fast and the load time decreases because the binary is optimized for size.
To get the last drop of performance out of databases and the likes you'll need to set specific options anyway.
 
Old 02-07-2008, 08:44 AM   #23
swampdog2002
Member
 
Registered: Jul 2005
Distribution: Slackware 12.2, 13.0, openSUSE 11.2
Posts: 400

Rep: Reputation: 33
Quote:
Originally Posted by gnashley View Post
Yeah, Tim is right. This is not good:
Resetting package name - Using: filezilla_3.0.6
(this means that the version is 'src'. These errors with name and vesrion are not dangerous, but it will keep upgradepkg from working properly.
This will fix that problem
src2pkg -n=filezilla -v=3.0.6 FileZilla_3.0.6_src.tar.bz2
Thanks. I was wondering why I had problems with launching the application after I had installed this with installpkg. For some reason, I received a message stating that FileZilla was unable to access the data directory, and that I needed to set a specific variable to point to this location. I'll give this another attempt with the switches -n and -v.
 
Old 02-07-2008, 09:09 AM   #24
gnashley
Amigo developer
 
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,928

Original Poster
Rep: Reputation: 612Reputation: 612Reputation: 612Reputation: 612Reputation: 612Reputation: 612
swampdog2002, That runtime error sounds like something else. You may need to pass something to the configure script. I quickly downloaded the sources to see what options are avialable. Looks like this may be what you need: --datarootdir=/usr/share
You can tell src2pkg to pass that to configure by using this -e='--datarootdir=/usr/share' along with the already mentioned options for correcting the name and version.

Thanks for everyone who has replied and tested. Thanks especially to brianL and crashmeister for the excellent links on the subject.
 
  


Reply



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
Athlon 64 3500+ v. Athlon 64 X2 3800+ v. EE/SFF Jorophose General 17 06-09-2007 11:49 PM
Athlon 64 meinzorn Slackware 2 09-01-2006 02:05 AM
Athlon 64 X2 tomythius Linux - Hardware 2 03-24-2006 08:16 PM
Athlon 64 spotslayer Linux - Hardware 4 01-04-2005 02:59 PM
Is it an ATHLON, or ATHLON-THUNDERBIRD ? qwijibow Linux - General 5 07-27-2004 06:33 AM

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

All times are GMT -5. The time now is 07:31 PM.

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