Re: [CURRENT]: claws-mail and firefox fail with "Invalid alignment"
21.02.2014 20:03, O. Hartmann пишет: > On Fri, 21 Feb 2014 19:00:13 +0100 > "O. Hartmann" wrote: > >> On Fri, 21 Feb 2014 18:49:13 +0100 >> Dimitry Andric wrote: >> >>> On 21 Feb 2014, at 18:40, O. Hartmann >>> wrote: On every FreeBSD 11.0-CURRENT #0 r262294: Fri Feb 21 14:11:20 CET 2014 amd64 I run neither claws-mail nor firfox run after the last buildworld. They fail both with the error Invalid alignment Does anyone see this problem too? I tried to recompile claws-mail and firefox, but without success (compilation succeeded, but the error stays). What happened here? How to solve? >>> Can you try reverting r262277, rebuilding libexec/rtld-elf and >>> reinstalling it, and seeing if that fixes it? >>> >>> -Dimitry >>> >> Hello Dimitry, >> >> in r262277 there is no change in libexec/rtld-elf, I had to go back to >> r262270. I did as requested and reinstalling libexec/rtld-elf fixes >> the reported issue. >> >> Regards, >> Oliver > Sorry, it is r262276 > I have the same issue with firefox and thunderbird. Reverting libexec/rtld-elf to r262276 solves a problem. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [CURRENT]: claws-mail and firefox fail with "Invalid alignment"
The problem is still present in r262325. Verified with Firefox. 2014-02-22 9:12 GMT+01:00 Alexandr : > 21.02.2014 20:03, O. Hartmann пишет: > > On Fri, 21 Feb 2014 19:00:13 +0100 > > "O. Hartmann" wrote: > > > >> On Fri, 21 Feb 2014 18:49:13 +0100 > >> Dimitry Andric wrote: > >> > >>> On 21 Feb 2014, at 18:40, O. Hartmann > >>> wrote: > On every FreeBSD 11.0-CURRENT #0 r262294: Fri Feb 21 14:11:20 CET > 2014 amd64 I run neither claws-mail nor firfox run after the last > buildworld. They fail both with the error > > Invalid alignment > > Does anyone see this problem too? I tried to recompile claws-mail > and firefox, but without success (compilation succeeded, but the > error stays). > > What happened here? How to solve? > >>> Can you try reverting r262277, rebuilding libexec/rtld-elf and > >>> reinstalling it, and seeing if that fixes it? > >>> > >>> -Dimitry > >>> > >> Hello Dimitry, > >> > >> in r262277 there is no change in libexec/rtld-elf, I had to go back to > >> r262270. I did as requested and reinstalling libexec/rtld-elf fixes > >> the reported issue. > >> > >> Regards, > >> Oliver > > Sorry, it is r262276 > > > > I have the same issue with firefox and thunderbird. Reverting > libexec/rtld-elf to r262276 solves a problem. > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: BSD XXI Manifesto [agree] [intersting]
On 2/22/14, 2:54 PM, Adrian Chadd wrote: On 21 February 2014 20:59, Allan Jude wrote: I can see the remote controlled installer being especially useful for 'appliance' type devices, like FreeNAS, pfSense, FUDO, etc. How would your phone find the address of the machine once it boots off the USB, so you could access the web server? "what apple does." I redeemed an itunes card to day.. and all I had to do was hold it up to the camera and it read the numbers off the card.. nice.. -a ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [CURRENT]: claws-mail and firefox fail with "Invalid alignment"
Am 22.02.2014 10:03, schrieb Ranjan1018 .: > The problem is still present in r262325. Verified with Firefox. Just for the record. With r262334 the problem seems to be solved, Firefox, Thunderbird etc. work again :-) Thanks to davidxu@ for the quick fix. Greetings, Rainer Hurling > 2014-02-22 9:12 GMT+01:00 Alexandr : > >> 21.02.2014 20:03, O. Hartmann пишет: >>> On Fri, 21 Feb 2014 19:00:13 +0100 >>> "O. Hartmann" wrote: >>> On Fri, 21 Feb 2014 18:49:13 +0100 Dimitry Andric wrote: > On 21 Feb 2014, at 18:40, O. Hartmann > wrote: >> On every FreeBSD 11.0-CURRENT #0 r262294: Fri Feb 21 14:11:20 CET >> 2014 amd64 I run neither claws-mail nor firfox run after the last >> buildworld. They fail both with the error >> >> Invalid alignment >> >> Does anyone see this problem too? I tried to recompile claws-mail >> and firefox, but without success (compilation succeeded, but the >> error stays). >> >> What happened here? How to solve? > Can you try reverting r262277, rebuilding libexec/rtld-elf and > reinstalling it, and seeing if that fixes it? > > -Dimitry > Hello Dimitry, in r262277 there is no change in libexec/rtld-elf, I had to go back to r262270. I did as requested and reinstalling libexec/rtld-elf fixes the reported issue. Regards, Oliver >>> Sorry, it is r262276 >>> >> >> I have the same issue with firefox and thunderbird. Reverting >> libexec/rtld-elf to r262276 solves a problem. >> ___ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[head tinderbox] failure on powerpc/powerpc
TB --- 2014-02-22 15:59:09 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2014-02-22 15:59:09 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014-02-22 15:59:09 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2014-02-22 15:59:09 - cleaning the object tree TB --- 2014-02-22 15:59:09 - /usr/local/bin/svn stat /src TB --- 2014-02-22 15:59:12 - At svn revision 262334 TB --- 2014-02-22 15:59:13 - building world TB --- 2014-02-22 15:59:13 - CROSS_BUILD_TESTING=YES TB --- 2014-02-22 15:59:13 - MAKEOBJDIRPREFIX=/obj TB --- 2014-02-22 15:59:13 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-02-22 15:59:13 - SRCCONF=/dev/null TB --- 2014-02-22 15:59:13 - TARGET=powerpc TB --- 2014-02-22 15:59:13 - TARGET_ARCH=powerpc TB --- 2014-02-22 15:59:13 - TZ=UTC TB --- 2014-02-22 15:59:13 - __MAKE_CONF=/dev/null TB --- 2014-02-22 15:59:13 - cd /src TB --- 2014-02-22 15:59:13 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Sat Feb 22 15:59:20 UTC 2014 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -DSHELL -I. -I/src/bin/sh -DRESCUE -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /src/bin/sh/error.c cc -O2 -pipe -DSHELL -I. -I/src/bin/sh -DRESCUE -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /src/bin/sh/eval.c cc -O2 -pipe -DSHELL -I. -I/src/bin/sh -DRESCUE -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /src/bin/sh/exec.c /src/bin/sh/exec.c: In function 'typecmd_impl': /src/bin/sh/exec.c:650: internal compiler error: in var_ann, at tree-flow-inline.h:127 Please submit a full bug report, with preprocessed source if appropriate. See http://www.freebsd.org/send-pr.html> for instructions. *** Error code 1 Stop. bmake[5]: stopped in /src/bin/sh *** Error code 1 Stop. bmake[4]: stopped in /obj/powerpc.powerpc/src/rescue/rescue *** Error code 1 Stop. bmake[3]: stopped in /src/rescue/rescue *** Error code 1 Stop. bmake[2]: stopped in /src/rescue *** Error code 1 Stop. bmake[1]: stopped in /src *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2014-02-22 18:17:31 - WARNING: /usr/bin/make returned exit code 1 TB --- 2014-02-22 18:17:31 - ERROR: failed to build world TB --- 2014-02-22 18:17:31 - 7117.95 user 969.44 system 8301.83 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-powerpc-powerpc.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[HEADSUP] Jenkins running in FreeBSD cluster
Hi, I just wanted to let the FreeBSD community know that with the help of some FreeBSD hackers, we have set up an initial Jenkins Continuous Integration server in the FreeBSD cluster. We are the jenkins-admin team and you can contact us at jenkins-ad...@freebsd.org. We have a few initial builds going and you can see things here: https://jenkins.freebsd.org We are still working on a few problems, and have some ambitious plans moving forward, which you can read about on our status page: http://wiki.freebsd.org/Jenkins Lastly, if you are able to attend the FreeBSD DevSummit in Ottawa later this year, we will have a working group discussion on Jenkins and Continuous Integration testing for FreeBSD on May 15, 2014: https://wiki.freebsd.org/201405DevSummit/Jenkins We'd love to get more FreeBSD hackers involved to get this going and improve continuous integration and testing on FreeBSD. We would like to use the freebsd-test...@freebsd.org mailing list for followup discussions. I'd like to thank my fellow members of the jenkins-admin team for helping to get things going: Steve Kreuzer Li-Wen Hsu Steve Wills R. Tyler Croy If we can integrate more automated testing of FreeBSD with this, that would be really great! -- Craig ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
libinit idea
https://github.com/brunolauze/libnit
I know there's really big debate about init system but here's my tentative to
propose a new model to replace rc.
Let's call it libinit but the name as no significance for now.
I started coding a library with the following architecture.
the main idea is to rewrite rc in C language.
a utility called system would act a little bit like service command does.
a folder would contains libraries instead of scripts inside [target]/etc/rc.d
so we can add as many librairies a user desire and interlink the order of each
piece among all like in rc.
each library would follow and expose the following pattern:
char **provide(); /* returns all the PROVIDE a library contains */
then for each provide() value the library would expose :
XXX_provide()
XXX_require()
XXX_before()
XXX_keywords()
and optionally:
XXX_canstart();
XXX_prestart();
XXX_start();
XXX_status();
XXX_stop();
and also:
XXX_mycommand(int argc, char **argv);
essentially repeating the rc.subr model
system utilty would source /etc/defaults/rc.conf, then source result of
rc_conf_files loaded
On init, /sbin/init would call /sbin/system init instead of running script
/etc/rc
on init, system would scan folder (let's suppose /lib/init.d and
/usr/local/init.d for now)
try dlopen() each *.so* files
and grab provide(); xxx_provide(), xxx_require(), xxx_before() and
xxx_keyword() for each one.
compile a list of "service" discovered and do an "rcorder".
The benefits is to avoid firing so many utility to manage to init the system.
Replicating all small helper function from rc to C language like load_kld would
avoid opening a process and do real syscall at moment.
Heavily use pthread, waitpid, etc...
So instead of firing /sbin/devfs /dev rule -s 1 applyset
call direcly what's would run inside devfs -> rule_main in
src/sbin/devfs/rule.c ...
cut the fat
here's an example to show /etc/rc.d/abi conversion to abi.c
abi.h:
#ifndef __ABI_H__
#define __ABI_H__
#include "../default.h"
#define PROVIDE abi
#define REQUIRE { "archdep" }
#define KEYWORD { NOJAIL }
#include "../common.h"
#endif
abi.c:
#include "abi.h"
int sysvipc_start()
{
if (load_kld("sysvmsg"))
if (load_kld("sysvsem"))
return load_kld("sysvshm");
return -1;
}
int linux_start()
{
return load_kld("linux");
}
int srv4_start()
{
if (load_kld("svr4elf") == 0)
return load_kld("svr4");
return (-1);
}
#define __canstart
int abi_canstart()
{
return is_enabled("sysvipc") || is_enabled("linux") ||
is_enabled("srv4");
}
int abi_start()
{
int err1 = 0, err2 = 0, err3 = 0;
if (is_enabled("sysvipc")) err1 = sysvipc_start();
if (is_enabled("linux")) err2 = linux_start();
if (is_enabled("srv4")) err3 = srv4_start();
return err1 && err2 && err3;
}
#include "../common.c"
where common.h and common.c implement everything by default a little bit like
rc.subr does.
e.g: PID_FILE and COMMAND macros implement the start by itself, etc...
as you can see really similar to what we have in the script file...
Then the system utility would also allow digging into the libraries with
command like:
system accounting rotatelog
etc..
I uploaded a quick start to show some code and expose more the idea.
https://github.com/brunolauze/libinit
Thanks in advance for your comments.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: base unzip on 10-STABLE/ 11-HEAD "unzip: skipping non-regular entry"
> Hello, > > Unfortunately, this is the case with *zips from Dropbox (Download > as .zip) directory option. > > $ /usr/bin/unzip file.zip > Archive: file.zip > unzip: skipping non-regular entry '' > unzip: skipping non-regular entry 'A B C D.pdf' > > archivers/unzip manages this case though... > > $ /usr/local/bin/unzip file.zip > Archive: file.zip > warning: stripped absolute path spec from / > mapname: conversion of failed > inflating: A B C D.pdf > > Tested on 10-STABLE, but should be the same on HEAD. % /usr/bin/unzip sr003-02-24192.zip Archive: sr003-02-24192.zip unzip: Mac metadata is too large: 2520404 > 128K bytes FAIL % unzip -t sr003-02-24192.zip Archive: sr003-02-24192.zip unzip: Mac metadata is too large: 2520404 > 128K bytes really? % /usr/local/bin/unzip -t sr003-02-24192.zip Archive: sr003-02-24192.zip testing: sr003-02-24192.wav OK testing: __MACOSX/OK testing: __MACOSX/._sr003-02-24192.wav OK getting better % /usr/local/bin/unzip sr003-02-24192.zip -x __MACOSX/* Archive: sr003-02-24192.zip inflating: sr003-02-24192.wav Flawless victory :) Base unzip isn't very useful. Having it first in the path is just annoying. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: base unzip on 10-STABLE/ 11-HEAD "unzip: skipping non-regular entry"
Hi, Please file PRs for these. The author is quite prompt at fixing these issues. -a On 22 February 2014 15:05, Matthew Rezny wrote: >> Hello, >> >> Unfortunately, this is the case with *zips from Dropbox (Download >> as .zip) directory option. >> >> $ /usr/bin/unzip file.zip >> Archive: file.zip >> unzip: skipping non-regular entry '' >> unzip: skipping non-regular entry 'A B C D.pdf' >> >> archivers/unzip manages this case though... >> >> $ /usr/local/bin/unzip file.zip >> Archive: file.zip >> warning: stripped absolute path spec from / >> mapname: conversion of failed >> inflating: A B C D.pdf >> >> Tested on 10-STABLE, but should be the same on HEAD. > > % /usr/bin/unzip sr003-02-24192.zip > Archive: sr003-02-24192.zip > unzip: Mac metadata is too large: 2520404 > 128K bytes > > FAIL > > % unzip -t sr003-02-24192.zip > Archive: sr003-02-24192.zip > unzip: Mac metadata is too large: 2520404 > 128K bytes > > really? > > % /usr/local/bin/unzip -t sr003-02-24192.zip > Archive: sr003-02-24192.zip > testing: sr003-02-24192.wav OK > testing: __MACOSX/OK > testing: __MACOSX/._sr003-02-24192.wav OK > > getting better > > % /usr/local/bin/unzip sr003-02-24192.zip -x __MACOSX/* > Archive: sr003-02-24192.zip > inflating: sr003-02-24192.wav > > Flawless victory :) > > Base unzip isn't very useful. Having it first in the path is just annoying. > > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: libinit idea
On Sat, Feb 22, 2014 at 5:54 PM, Bruno Lauzé wrote:
> https://github.com/brunolauze/libnit
>
> I know there's really big debate about init system but here's my tentative to
> propose a new model to replace rc.
>
> Let's call it libinit but the name as no significance for now.
>
> I started coding a library with the following architecture.
>
> the main idea is to rewrite rc in C language.
>
> a utility called system would act a little bit like service command does.
>
> a folder would contains libraries instead of scripts inside [target]/etc/rc.d
> so we can add as many librairies a user desire and interlink the order of
> each piece among all like in rc.
>
libraries don't belong in [target]/etc/rc.d, they would have to be in
{/usr,}/lib{exec,}/rc.d or ${PREFIX}/lib{exec,}/rc.d
--
DISCLAIMER:
No electrons were maimed while sending this message. Only slightly bruised.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
