|
OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
Like a few new ports, midori/webkit is a W.I.P.. which unfortunately will not compile with the system compiler. (It needs GCC 4).
That error would seem to indicate some sort of environment problem, as I've built a cross-compiler independent of the ports system before. Sorry I couldn't be of more assistance.. |
|
||||
I was using Midori for a month and removed it because of the stability issues.
If I recall correctly I used snapshot of packages to install it. I have not noticed people complaining on ports[AT]openbsd about broken Midori port so I would have to suspect that something is messed up with your system. Without additional information about your system it is very hard to say why is compilation failing. Grub the latest snapshot of the OS and latest ports tree to make sure everything is in sync. |
|
||||
Looking at the makefile for Midori, I don't see any requirement for gcc 4.2; so I'm going to guess that your gcc 4.2 is actually getting in the way of the default compiler during the configuration step.
Midori has changed between 4.4 and -current; it's not clear from your problem description what you are running. If you are running -current in amd64 or i386, at the moment there is a -current package for midori for those archs available from your nearest mirror that has -current packages: i386 built December 13 amd64 build December 17 |
|
|||
Quote:
Midori needs to be compiled with GCC 4 because the Webkit library is.. at least I think that's the case. It's a sad cruel world.. but we gotta live in it. |
|
||||
sorry, i'm running 4.4. I was reading on how to track current ports so I could see if doing that would correct my problem. I'd like to run the newer version of midori that is in current but without having to rebuild my entire system to current...
__________________
"The basic tool for the manipulation of reality is the manipulation of words. If you can control the meaning of words, you can control the people who must use the words." -Philip K. Dick |
|
||||
Quote:
$ make print-build-depends Sorry about that.It is doubtful you could get it running. Even if you were able to shoehorn the package in (such as with -F libdepends), or manually unpack and install the .tgz, there is no guarantee it would even execute. See FAQ 15.4.1. |
|
||||
I should note:
"Upgrading" from 4.4-release or 4.4-stable to -current is fairly easy. Step 1: back up your OS Step 2: "upgrade" to most recent snapshot Step 3: run sysmerge Step 4: Check the "Following -current" FAQ for anything sysmerge might have missed. At that point, you may optionally upgrade installed packages to the most recently available prebuilt snapshot packages available for your architecture. # pkg_add -iu Since snapshot packages are never in sync with snapshots, you may find some inconsistencies which cause some packages to fail to install. The script(1) program in concert with col(1) is helpful for finding errors in the midst of hundreds of package upgrades. |
|
||||
Thanks to jggimi pointers I was able to upgrade my system to 4.4-current just too a week because of the machines speed...but I still get the same build error when trying to make the midori port and the package give a list of other errors.
I use no midori for me, thanks again.
__________________
"The basic tool for the manipulation of reality is the manipulation of words. If you can control the meaning of words, you can control the people who must use the words." -Philip K. Dick |
|
||||
If you are running either amd64 or i386, you might try installing the snapshot package -- no build required.
You'll find it in /pub/OpenBSD/snapshots/packages/<arch> at major mirrors. Here's a list of some of the mirrors and their snapshot and snapshot packages dates: http://gruiik.info/up2date.html |
|
|||
I am aware of the age of this thread but it does pertain to a current problem.
On 4.8 RELEASE sparc64, I had the same problem. What I did: Remove the port. Downloaded the source package. Built the dependencies from ports. Built and installed following INSTALL. The browser still crashes due to not finding "default stock theme." 1.) I've read it calls upon the gtyk Tango theme. 2) I've also read it is the default browser for Xfce. I'm using Xfce4 and Midori is still crashing. |
|
|||
Code:
(gdb) bt No stack. (gdb) core-file /home/boogers/midori.core Core was generated by `midori'. Program terminated with signal 11, Segmentation fault. #0 0x00000002170115dc in ?? () (gdb) bt #0 0x00000002170115dc in ?? () #1 0x00000002170115d4 in ?? () Previous frame identical to this frame (corrupt stack?) (gdb) Code:
(gdb) bt #0 0x000000021161a348 in poll () from /usr/lib/libc.so.56.0 #1 0x000000020769dee8 in _thread_kern_poll (wait_reqd=Variable "wait_reqd" is not available. ) at /usr/src/lib/libpthread/uthread/uthread_kern.c:760 #2 0x000000020769f054 in _thread_kern_sched (scp=0x0) at /usr/src/lib/libpthread/uthread/uthread_kern.c:382 #3 0x000000020769b378 in pthread_cond_timedwait (cond=0x2078a41a0, mutex=0x2078a4198, abstime=0x20a969e68) at /usr/src/lib/libpthread/uthread/uthread_cond.c:431 #4 0x0000000207695ed8 in _thread_gc (arg=Variable "arg" is not available. ) at /usr/src/lib/libpthread/uthread/uthread_gc.c:181 #5 0x00000002076958d8 in _thread_start () at /usr/src/lib/libpthread/uthread/uthread_create.c:242 #6 0x00000002076958a0 in pthread_attr_setstackaddr () at /usr/src/lib/libpthread/uthread/uthread_create.c:234 #7 0x00000002076958a0 in pthread_attr_setstackaddr () at /usr/src/lib/libpthread/uthread/uthread_create.c:234 Previous frame identical to this frame (corrupt stack?) (gdb) next Single stepping until exit from function poll, which has no line number information. Program received signal SIGINFO, Information request. 0x000000021161a34c in poll () from /usr/lib/libc.so.56.0 (gdb) quit |
|
|||
It's an unfortunate fact that some software doesn't run as expected on architectures like the sparc/sparc64, they have strange memory alignment requirements and are big-endian.
POSIX threads also have some issues on OpenBSD that are being worked on, the OpenBSD kernel isn't aware of threads yet.. it's all implemented entirely in userland, the libpthreads library is just modular "uthreads" and "rthreads (kernel)" aren't in a separate library. Midori on my (..mostly -CURRENT) i386/amd64 systems work fine, although it's not my #1 browser as of yet.. it's still a little rough around the edges, Firefox works better in most cases for me. Posting debugging information like that here won't likely help, you should update to a snapshot and try a -CURRENT Midori package.. otherwise send an email to ports@ and the maintainer. |
|
|||
I'll return to it later.
before this was posted, there was no reference in Google for the memory addresses above; doesn't that seem a bit strange? I'll ask the lists after I reboot the Sun Blade 1000. |
|
|||
It appears you are making the assumption that applications/libraries will be loaded at the same locations at each invocation. This isn't true.
|
|
|||
How do I properly trace while running the program in gdb?
|
|
|||
Pardon me if you're specifically a midori fan, but if you're looking for a webkit based lighter weight browser, have you tried Marco Peereboom's xxxterm? I'm not crazy about the vi command prompt as browser interface idea, but it does seem to be stable and starts up quickly. At least it starts quickly for something that's able to render better than dillo or lynx.
|
|
|||
@Mr-Biscuit: You can't, not easily.. and debugging threaded programs in gdb is a real pita, not something a novice should try attempting.
Also, packages are generally stripped and/or built without debugging symbols.. so the gdb output is entirely unhelpful for debugging. It makes no sense for you to continue further without having tested the -CURRENT port, sometimes things get broken and fixed.. bulk ports builds only happen occasionally on non-x86/amd64 platforms. |
|
|||
Thirdm: xxxterm works great, I just need to redo the conf file tweaks.
The log changes: Quote:
BSDfan666 (et al): I built the package from the website source with debugging. Whatever this default theme is doesn't seem to be in the search path for this version or the one in ports. I'll ask the maintainer if it has ever been tested on sparc64. If anything on this reply seems sarcastic or biting.... it's not. I just woke up. My apologies for any misunderstanding. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
SSH on port 443 | maxrussell | General software and network | 4 | 6th April 2009 05:16 AM |
PF: strange port 21 | iwi | OpenBSD Security | 3 | 25th November 2008 02:21 PM |
port info | sniper007 | FreeBSD General | 6 | 14th November 2008 11:46 AM |
VNC port forwarding help | revzalot | OpenBSD Security | 3 | 10th September 2008 06:59 AM |
vlc port failing | maxrussell | FreeBSD Ports and Packages | 11 | 27th May 2008 04:38 PM |