[Solved] Apps compiled from source never work and a security question

new2arch · 2008-02-25 13:31:11

Gentlemen,

I'm a Linux noob but in spite of that I managed to install Archlinux thanks to a fine How To Wiki.

1. I have a question regarding compiling from source in Arch - does it differ from other linuxdistros?
With other distros I normally install in /usr/local and that has worked flawless.

Take Pacman for instance: although I can see there is this Opera app available in the repo (via arch's home page -> search package), the 'pacman -S opera' tells me the app doesn't exist.

I've tried to download and install it from source following Opera's own 'how to' but the app fails to start, after a successful installation.
Same goes with other apps such as f-prot antivirus.

Did I miss something important here?

2. I installed Arch over FTP. How safe is it, considering I'm not behind a router and the iptables/firestarter was only installed after xfce4 was installed. What about open ports and such? I know there aren't many services enabled/listening but I noticed couple of daemons such as portmap being active during the installation process.

Thanks

Last edited by new2arch (2008-02-25 16:12:31)

niller · 2008-02-25 13:42:42

Hi there

Try pacman -Ss opera

This tells you that the packagename is opera-static.

For manually installing packages try reading about ABS and AUR in the wiki

Cheers,

ise · 2008-02-25 13:50:22

new2arch wrote:

Take Pacman for instance: although I can see there is this Opera app available in the repo (via arch's home page -> search package), the 'pacman -S opera' tells me the app doesn't exist.

Hi, another possibility is, that you are using x86_64. Opera isn't available on this platform (thanks to Opera). Instead try the opera from [unstable] repo, there is a x86_64 version of it. But take care in using [unstable] repo, your system MAY get broken.

Last edited by ise (2008-02-25 13:51:45)

jacko · 2008-02-25 13:55:09

This tells you that the packagename is opera-static

pacman -Sy opera-static

as for installing programs manually, u won't wanna do that in arch. Because arch has a wonderful (ABS, makepkg) system that works right along side pacman. makepkg generates a *pkg.tar.gz that can be installed and tracked with pacman. With this system u can install pre-compiled binaries or you can compile from source. The end result is the same, a package that is usable/installable by pacman.

Last edited by jacko (2008-02-25 13:56:12)

new2arch · 2008-02-25 13:57:31

@niller - Thanks. I'll give it a shot when I get back home. I always download the static version as the shared version never seemed to work on any linux distro.
I've read about the ABS but haven't tried it yet.

@ise - Yes, I'm running Arch intended for x86_64. The official Opera is only available for i386 system, but why does it fail to run on my system?

@jacko - Hm...I guess it's worth giving it a try since I've been recommended to use it twice already.

From a noob's point of view, I think Pacman is just wonderful and easy to use and checks dependencies without a glitch (so far). Don't see why Pacman generally receives bad rankings out there.

Last edited by new2arch (2008-02-25 14:01:48)

jacko · 2008-02-25 14:07:23

Don't see why Pacman generally receives bad rankings out there.

because it's command line and has to many switches for all the noobs. But, as u have seen, pacman is far from lacking and hard to use!!!

The official Opera is only available for i386 system, but why does it fail to run on my system?

because its the wrong ELF class.

Last edited by jacko (2008-02-25 14:09:22)

jacko · 2008-02-25 14:14:40

Pay attention to the arch=(..) line in both of these url's. One is only for i686 and the other is for i686, x86_64. The first url points to the package build that is in unstable repository and the one ise pointed to in his post. The second url is the one u tried to d/l using pacman -S opera. it failed because that is only available for i686.

http://cvs.archlinux.org/cgi-bin/viewcv … text/plain

new2arch · 2008-02-25 14:19:26

jacko wrote:

Pay attention to the arch=(..) line in both of these url's. One is only for i686 and the other is for i686, x86_64. The first url points to the package build that is in unstable repository and the one ise pointed to in his post. The second url is the one u tried to d/l using pacman -S opera. it failed because that is only available for i686.
http://cvs.archlinux.org/cgi-bin/viewcv … text/plain
http://cvs.archlinux.org/cgi-bin/viewcv … text/plain

Thanks for clearing that out. Will try the unstable repo.

new2arch · 2008-02-25 16:11:53

Opera problem solved. Running 9.5 (unstable) with no side-effects so far. Thanks.

eerok · 2008-02-25 16:13:55

new2arch wrote:

1. I have a question regarding compiling from source in Arch - does it differ from other linuxdistros?
With other distros I normally install in /usr/local and that has worked flawless.

Arch doesn't use /usr/local so it's not in your path. The progs you compiled might be okay... try providing the full path and see.

The more elegant solution is to build them as packages, as you've already heard.

new2arch · 2008-02-25 19:17:33

eerok wrote:

new2arch wrote:
1. I have a question regarding compiling from source in Arch - does it differ from other linuxdistros?
With other distros I normally install in /usr/local and that has worked flawless.
Arch doesn't use /usr/local so it's not in your path. The progs you compiled might be okay... try providing the full path and see.
The more elegant solution is to build them as packages, as you've already heard.

Oh, I didn't know /usr/local was not in the default path. That explains it...
I have studied the Archwiki on how to build own packages and it does not seem to be very easy.
It seems it is easier to install from source as long as I have the correct paths.

kumico · 2008-02-26 13:33:54

you can add /usr/local to the path in /etc/profile to make it global or in your ~/.bashrc or ~/.bash_profile to make it available to your user session.
a pkgbuild is pretty simple once you get used to it,
you may be put off by packaging standards, you can ignore them, they are only for people intending to share
with other via the AUR for example.

you can copy one of the existign ones, either the prototypes or jsut anyone from the aur,
then change stuff you fidn necessary, like pkgname, pkgver, etc.
and add the same build commands you'd use otherwise to the build()
and usualy for a make install, just add DESTDIR=$startdir/pkg etc.,... just practice you'll get the hang of it very quickly

new2arch · 2008-02-27 04:31:29

kumico wrote:

you can add /usr/local to the path in /etc/profile to make it global or in your ~/.bashrc or ~/.bash_profile to make it available to your user session.
a pkgbuild is pretty simple once you get used to it,
you may be put off by packaging standards, you can ignore them, they are only for people intending to share
with other via the AUR for example.
you can copy one of the existign ones, either the prototypes or jsut anyone from the aur,
then change stuff you fidn necessary, like pkgname, pkgver, etc.
and add the same build commands you'd use otherwise to the build()
and usualy for a make install, just add DESTDIR=$startdir/pkg etc.,... just practice you'll get the hang of it very quickly

Hi Kumico, thanks for the tip.
Or I could try using Arch's default paths as long as the applications don't mind. But it's nice to have an alternative solution should any trouble arise.

Regarding pkgbuild, I'll probably start to use it when I feel more comfy with the Arch environment itself.
Using the terminal to perform...well, just about everything, rather than having a nice gui isn't actually bad, but there sure is a transition for a newbie to adapt to.

Arch Linux

#1 2008-02-25 13:31:11

[Solved] Apps compiled from source never work and a security question

#2 2008-02-25 13:42:42

Re: [Solved] Apps compiled from source never work and a security question

#3 2008-02-25 13:50:22

Re: [Solved] Apps compiled from source never work and a security question

#4 2008-02-25 13:55:09

Re: [Solved] Apps compiled from source never work and a security question

#5 2008-02-25 13:57:31

Re: [Solved] Apps compiled from source never work and a security question

#6 2008-02-25 14:07:23

Re: [Solved] Apps compiled from source never work and a security question

#7 2008-02-25 14:14:40

Re: [Solved] Apps compiled from source never work and a security question

#8 2008-02-25 14:19:26

Re: [Solved] Apps compiled from source never work and a security question

#9 2008-02-25 16:11:53

Re: [Solved] Apps compiled from source never work and a security question

#10 2008-02-25 16:13:55

Re: [Solved] Apps compiled from source never work and a security question

#11 2008-02-25 19:17:33

Re: [Solved] Apps compiled from source never work and a security question

#12 2008-02-26 13:33:54

Re: [Solved] Apps compiled from source never work and a security question

#13 2008-02-27 04:31:29

Re: [Solved] Apps compiled from source never work and a security question

Board footer