You are not logged in.

#1 2007-07-07 15:06:01

pelle.k
Member
From: Åre, Sweden (EU)
Registered: 2006-04-30
Posts: 667

having some "bad" binaries/libs lately.

I just reinstalled arch, and i'm having this slight problem. packages from PKGBUILDS i compiled in my old installation, have working binaries (i saved them, just in case). However, when i compile them from my new fresh install, these same application won't work any more. I was thinking someone else might have some insight on this? I know there has been some upgrades of both makepkg.conf, and probably glibc and whole lot of other stuff that could be responsible.
If you wonder, i'm building bmp (because i "--enable-gnome-vfs") bmp-itouch and bmp-docklet.

bmp-itouch;

The program 'beep-media-player' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAccess (attempt to access private resource denied)'.
  (Details: serial 7 error_code 10 request_code 33 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

bmp-docklet;
this one is funny, the new bmp-docklet works with old bmp, but the old bmp-docklet works with both new and old bmp package...
I can't reproduce the error anymore, but there was something about "allocate memory" and "glibc error".

Suggestions would be appreciated smile

Last edited by pelle.k (2007-07-07 15:06:26)


"Your beliefs can be like fences that surround you.
You must first see them or you will not even realize that you are not free, simply because you will not see beyond the fences.
They will represent the boundaries of your experience."

SETH / Jane Roberts

Offline

Board footer

Powered by FluxBB