[Solved] Fedora 18 problems with package conflicts

[Bart]

Hi,

I just installed Fedora 18 in a VirtualBox (Host: Win7).
I just went with the defaults, and installed binutils.

I manged to download and install fpc 2.6.2 (from installscript) and it seems to run fine.
I checked out the lazarus sources from svn.
Did
make all OPT="-gl -gs"

And it failed (not unexpectedly)  with
/usr/bin/ld: cannot find -lpthread
/usr/bin/ld: cannot find -ldl
/usr/bin/ld: cannot find -lc

So i think I need devel packages for libc, libdl (?) and libpthread (?)

I tried to install libc-devel package (using apper), but this failed:
Test Transaction Errors:
file /usr/lib/audit from install of glibc-2.16-30.fc18.i686
conflicts with file from package
audit-2.2.2-2.fc18.i686

Trying to remove audit package results in same error message.

So basically I'm stuck now.

Two more things about this Fedora bug me:

• I cannot copy contents from xterm to clipboard
• sudo does not accept my root password, but yet i can login as root, and can use su to become root. Apper also at times does not accept my root paswoord. Only way out is to reboot (the common Windows solution...)

Can anyone help?

[Blaazen]

AFAIK Zeljan uses Fedora. Try to ask him on mailing list (he also comes here but maybe not so often).

ad 1) Copying:
In xterm it is not very clear for me too. Whatever I select (with mouse), text appears in Klipper. Shift+Insert is for paste.
(contrary to Konsole (KDE4 app.) where Ctrl+Shift+C, Ctrl+Shift+V works well).

ad 2) Not sure here too. Distros are different, for example on Chakra or Kubuntu, "sudo make install"+password (for fpc) is enough, on openSuSE I had to use "su"+password+"make install".

[BigChimp]

Yep. On Debian, FreeBSD, I think OSX I'm used to do a su -i to go to root, while on Ubuntu I could do sudo -i

As sudo is seemingly installed you could set up the sudoers file to allow root access, IIRC, visudo is the command to edit that file.

[Bart]

I am a little bit further now.

I used rpm to find out why I could not remove audit, and finally I succeeded in removing it:

[root@localhost lazarus]# rpm -e setroubleshoot-server setroubleshoot-plugins setroubleshoot
[root@localhost lazarus]# rpm -e audit

install from "apper":
glibc-devel

Next try to build lazarus fails, but we're getting ahead:

Linking ../lazarus
/usr/bin/ld: warning: ../link.res contains output sections; did you forget -T?
/usr/bin/ld: cannot find -lgdk_pixbuf-2.0
/usr/bin/ld: cannot find -lgtk-x11-2.0
/usr/bin/ld: cannot find -lgdk-x11-2.0
/usr/bin/ld: cannot find -lpango-1.0
/usr/bin/ld: cannot find -latk-1.0
lazarus.pp(132,1) Error: Error while linking

install from "apper":
gdk-pixbuf2-devel-2.26.5-1.fc18.i686
gtk2-devel-2.24.16-1.fc18.i686
pango-devel-1.32.3-1.fc18.i686
atk-devel-2.6.0-1.fc18.i686

Next try to build lazarus fails, but we're getting ahead:

Compiling lazarus.pp
Compiling resource ../units/i386-linux/gtk2/lazarus.or
Linking ../lazarus
/usr/bin/ld: warning: ../link.res contains output sections; did you forget -T?
/lib/libEGL.so.1: undefined reference to `wl_display_dispatch_queue_pending'
lazarus.pp(132,1) Error: Error while linking
lazarus.pp(132,1) Fatal: There were 1 errors compiling module, stopping
Fatal: Compilation aborted

Googling suggests that this is part of mesa-libwayland-egl, so:

install from "apper":
mesa-libwayland-egl-9.1-3.fc18.i686
mesa-libwayland-egl-devel-9.1-3.fc18.i686
(mesa-libEGL and mesa-libEGL-devel were already installed)

Alas, linking still fails at the same point with the same message.

So, what next?

Bart

[Blaazen]

So you already use Wayland? It is very new project, I never had distro with it yet.

[Bart]

I don't use wayland.
Lazarus GTK2 seems to require it!

Why?

Bart

[Fred vS]

Hello.
Have you try installing from .deb files ?
https://ask.fedoraproject.org/question/9733/open-deb-files/

[marcov]

I don't use wayland.
Lazarus GTK2 seems to require it!

Lazarus uses GTK2 and X11. If you provide versions of these libraries that link to wayland, that would cause this.
 
The problem is not in Lazarus, but in the installation of the requisites (which are quite ordinary btw). Did you per chance enable some experimental repository?

[Dick, from the internet]

sudo does not accept my root password, but yet i can login as root, and can use su to become root. Apper also at times does not accept my root paswoord. Only way out is to reboot (the common Windows solution...)

I cannot give advice on your compilation issue, however here is a quick down and dirty for sudo.  Properly configured, sudo will ease a little frustration with changing back and forth with su, or trying to login with root <never a good option>

http://www.sudo.ws/sudo/intro.html

When using sudo,  use your user password, not the root password.  If you have not modified /etc/sudoers using visudo, first open 'Users and Groups' and ensure that you are a member of the wheel group. Then execute visudo with:

Code: [Select]

[me@localhost ~] su -c visudo
<use root password>
and remove the # from one of these lines:

## Allows people in group wheel to run all commands
#%wheel   ALL=(ALL)   ALL   <<------Here

## Same thing without a password
 %wheel   ALL=(ALL)   NOPASSWD: ALL    <<----- or Here

use normal vi commands:
i        = start editing
ESC  = end editing
:wq    = write changes and exit <note colon before wq>

note that I have uncommented the line allowing me to run commands without using a password each time, this is okay for me, as I am the only one who touches my system.

  regards,
     geno

[Bart]

Lazarus uses GTK2 and X11. If you provide versions of these libraries that link to wayland, that would cause this.
 
The problem is not in Lazarus, but in the installation of the requisites (which are quite ordinary btw). Did you per chance enable some experimental repository?

I installed Fedora 18 and did not change any default settings.
By default the wayland libs are not installed (I installed them afterwards to see if the error would go away).

I installed the required devel packages using apper, which downloaded them from I don't know where.

Also the message points to the libEGL file, so whatever references to `wl_display_dispatch_queue_pending' seems to make ld think it resides in libEGL?

How do I find out whick package causes this?

Bart

[Bart]

Finally solved.

Did a full "yum update" and several hours later: presto.
Lazarus builds, and runs (at first glance).

Bart