FreeBSD Port: graphics/cbrpager
Hi. I've a problem. cbrpager isn't working. When I try to open a file, nothing happens. I'm using FreeBSD 10.0-RELEASE-p7 32bits. Here is the output: $ cbrpager Cannot open temporary file /tmp/cbrsu3j4s cbrpager: Fatal IO error 2 (No such file or directory) on X server :0.0. Hope someone can help me. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Can't build lang/gcc port on i386: segmentation fault
With recent ports tree on stable-10 i386 attempting to build lang/gcc always cause segfault at this place. Log below. Any ideas? libtool: compile: /usr/ports/lang/gcc/work/build/./gcc/xgcc -B/usr/ports/lang/gcc/work/build/./gcc/ -B/usr/local/i386-portbld-freebsd10.1/bin/ -B/usr/local/i386-portbld-freebsd10.1/lib/ -isystem /usr/local/i386-portbld-freebsd10.1/include -isystem /usr/local/i386-portbld-freebsd10.1/sys-include -DHAVE_CONFIG_H -I. -I../.././../gcc-4.8.3/libquadmath -g -O2 -pipe -march=core2 -DLIBICONV_PLUG -fno-strict-aliasing -MT strtod/strtoflt128.lo -MD -MP -MF strtod/.deps/strtoflt128.Tpo -c ../.././../gcc-4.8.3/libquadmath/strtod/strtoflt128.c -fPIC -DPIC -o strtod/.libs/strtoflt128.o In file included from /usr/ports/lang/gcc/work/gcc-4.8.3/libstdc++-v3/include/precompiled/stdc++.h:94:0: /usr/ports/lang/gcc/work/build/i386-portbld-freebsd10.1/libstdc++-v3/include/valarray:1233:1: internal compiler error: Segmentation fault } // namespace ^ no stack trace because unwind library not available Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html for instructions. gmake[6]: *** [i386-portbld-freebsd10.1/bits/stdc++.h.gch/O2g.gch] Error 1 -- http://ache.vniz.net/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Can't build lang/gcc port on i386: segmentation fault
It was without BOOTSTRAP and JAVA. With BOOTSTRAP it builds fine, so apparently some incompatibilities with clang happens. On 12.09.2014 15:21, Andrey Chernov wrote: With recent ports tree on stable-10 i386 attempting to build lang/gcc always cause segfault at this place. Log below. Any ideas? libtool: compile: /usr/ports/lang/gcc/work/build/./gcc/xgcc -B/usr/ports/lang/gcc/work/build/./gcc/ -B/usr/local/i386-portbld-freebsd10.1/bin/ -B/usr/local/i386-portbld-freebsd10.1/lib/ -isystem /usr/local/i386-portbld-freebsd10.1/include -isystem /usr/local/i386-portbld-freebsd10.1/sys-include -DHAVE_CONFIG_H -I. -I../.././../gcc-4.8.3/libquadmath -g -O2 -pipe -march=core2 -DLIBICONV_PLUG -fno-strict-aliasing -MT strtod/strtoflt128.lo -MD -MP -MF strtod/.deps/strtoflt128.Tpo -c ../.././../gcc-4.8.3/libquadmath/strtod/strtoflt128.c -fPIC -DPIC -o strtod/.libs/strtoflt128.o In file included from /usr/ports/lang/gcc/work/gcc-4.8.3/libstdc++-v3/include/precompiled/stdc++.h:94:0: /usr/ports/lang/gcc/work/build/i386-portbld-freebsd10.1/libstdc++-v3/include/valarray:1233:1: internal compiler error: Segmentation fault } // namespace ^ no stack trace because unwind library not available Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html for instructions. gmake[6]: *** [i386-portbld-freebsd10.1/bits/stdc++.h.gch/O2g.gch] Error 1 -- http://ache.vniz.net/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Can't build lang/gcc port on i386: segmentation fault
Hi Andrey, On Fri, 12 Sep 2014, Andrey Chernov wrote: With recent ports tree on stable-10 i386 attempting to build lang/gcc always cause segfault at this place. Log below. Any ideas? this is actually the primary test platform I use for every single commit to this port. Plus I've been running weekly testers for about a year (until I switch that to GCC 4.9 a few months ago), which has never exhibited that. Is there anything special on your end (in base, hardware, options...)? Gerald ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Can't build lang/gcc port on i386: segmentation fault
On 12.09.2014 16:12, Gerald Pfeifer wrote: Hi Andrey, On Fri, 12 Sep 2014, Andrey Chernov wrote: With recent ports tree on stable-10 i386 attempting to build lang/gcc always cause segfault at this place. Log below. Any ideas? this is actually the primary test platform I use for every single commit to this port. Plus I've been running weekly testers for about a year (until I switch that to GCC 4.9 a few months ago), which has never exhibited that. Is there anything special on your end (in base, hardware, options...)? As I just found, it builds with BOOTSTRAP nice, so apparently clang makes some damage. You can see CFLAGS in the log. Swap is 4GB I think it is large enough. Nothing special otherwise. -- http://ache.vniz.net/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Can't build lang/gcc port on i386: segmentation fault
On 12.09.2014 16:18, Andrey Chernov wrote: On 12.09.2014 16:12, Gerald Pfeifer wrote: Hi Andrey, On Fri, 12 Sep 2014, Andrey Chernov wrote: With recent ports tree on stable-10 i386 attempting to build lang/gcc always cause segfault at this place. Log below. Any ideas? this is actually the primary test platform I use for every single commit to this port. Plus I've been running weekly testers for about a year (until I switch that to GCC 4.9 a few months ago), which has never exhibited that. Is there anything special on your end (in base, hardware, options...)? As I just found, it builds with BOOTSTRAP nice, so apparently clang makes some damage. You can see CFLAGS in the log. Swap is 4GB I think it is large enough. Nothing special otherwise. BTW, previous 4.7* as lang/gcc build fine even without BOOTSTRAP. -- http://ache.vniz.net/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Can't build lang/gcc port on i386: segmentation fault
On Fri, 12 Sep 2014, Andrey Chernov wrote: As I just found, it builds with BOOTSTRAP nice, so apparently clang makes some damage. You can see CFLAGS in the log. Swap is 4GB I think it is large enough. Nothing special otherwise. BTW, previous 4.7* as lang/gcc build fine even without BOOTSTRAP. I am curious, what happens when you try lang/gcc48? My expectation would be both lang/gcc and lang/gcc48 to behave the same, since it's a very similar codebase, gcc48 just a bit newer on the same branch. We could make BOOTSTRAP the default for lang/gcc, though not doing that and thus building a lot faster has been one of the features of lang/gcc. -- Since it does not reproduce for me, do others see the same failure? Gerald ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Can't build lang/gcc port on i386: segmentation fault
On 12.09.2014 16:42, Gerald Pfeifer wrote: On Fri, 12 Sep 2014, Andrey Chernov wrote: As I just found, it builds with BOOTSTRAP nice, so apparently clang makes some damage. You can see CFLAGS in the log. Swap is 4GB I think it is large enough. Nothing special otherwise. BTW, previous 4.7* as lang/gcc build fine even without BOOTSTRAP. I am curious, what happens when you try lang/gcc48? My expectation would be both lang/gcc and lang/gcc48 to behave the same, since it's a very similar codebase, gcc48 just a bit newer on the same branch. We could make BOOTSTRAP the default for lang/gcc, though not doing that and thus building a lot faster has been one of the features of lang/gcc. -- Since it does not reproduce for me, do others see the same failure? Segfault is exact the same but comes from strange place - in the middle of configure check. I will try with MAKE_JOBS_UNSAFE=yes -- http://ache.vniz.net/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Can't build lang/gcc port on i386: segmentation fault
On 12.09.2014 17:06, Andrey Chernov wrote: On 12.09.2014 16:42, Gerald Pfeifer wrote: On Fri, 12 Sep 2014, Andrey Chernov wrote: As I just found, it builds with BOOTSTRAP nice, so apparently clang makes some damage. You can see CFLAGS in the log. Swap is 4GB I think it is large enough. Nothing special otherwise. BTW, previous 4.7* as lang/gcc build fine even without BOOTSTRAP. I am curious, what happens when you try lang/gcc48? My expectation would be both lang/gcc and lang/gcc48 to behave the same, since it's a very similar codebase, gcc48 just a bit newer on the same branch. We could make BOOTSTRAP the default for lang/gcc, though not doing that and thus building a lot faster has been one of the features of lang/gcc. -- Since it does not reproduce for me, do others see the same failure? Segfault is exact the same but comes from strange place - in the middle of configure check. I will try with MAKE_JOBS_UNSAFE=yes With MAKE_JOBS_UNSAFE error finally shown in proper place, but remains (it was misplaces in original lang/gcc report too, different file compiled in the log, not O2g.gch): mkdir -p ./i386-portbld-freebsd10.1/bits/stdc++.h.gch /usr/ports/lang/gcc48/work/build/./gcc/xgcc -shared-libgcc -B/usr/ports/lang/gcc48/work/build/./gcc -nostdinc++ -L/usr/ports/lang/gcc48/work/build/i386-portbld-freebsd10.1/libstdc++-v3/src -L/usr/ports/lang/gcc48/work/build/i386-portbld-freebsd10.1/libstdc++-v3/src/.libs -B/usr/local/i386-portbld-freebsd10.1/bin/ -B/usr/local/i386-portbld-freebsd10.1/lib/ -isystem /usr/local/i386-portbld-freebsd10.1/include -isystem /usr/local/i386-portbld-freebsd10.1/sys-include-x c++-header -nostdinc++ -g -O2 -pipe -march=core2 -DLIBICONV_PLUG -fno-strict-aliasing -DLIBICONV_PLUG -I/usr/ports/lang/gcc48/work/build/i386-portbld-freebsd10.1/libstdc++-v3/include/i386-portbld-freebsd10.1 -I/usr/ports/lang/gcc48/work/build/i386-portbld-freebsd10.1/libstdc++-v3/include -I/usr/ports/lang/gcc48/work/gcc-4.8-20140904/libstdc++-v3/libsupc++ -O2 -g /usr/ports/lang/gcc48/work/gcc-4.8-20140904/libstdc++-v3/include/precompiled/stdc++.h -o i386-portbld-freebsd10.1/bits/stdc++.h.gch/O2g.gch In file included from /usr/ports/lang/gcc48/work/gcc-4.8-20140904/libstdc++-v3/include/precompiled/stdc++.h:94:0: /usr/ports/lang/gcc48/work/build/i386-portbld-freebsd10.1/libstdc++-v3/include/valarray:1233:1: internal compiler error: Segmentation fault } // namespace ^ no stack trace because unwind library not available Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html for instructions. gmake[6]: *** [i386-portbld-freebsd10.1/bits/stdc++.h.gch/O2g.gch] Error 1 -- http://ache.vniz.net/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Can't build lang/gcc port on i386: segmentation fault
Trying gcc49 (without BOOTSTRAP and JAVA), error in slightly different file but still inside stdc++: mkdir -p ./i386-portbld-freebsd10.1/bits/stdc++.h.gch /usr/ports/lang/gcc49/work/build/./gcc/xgcc -shared-libgcc -B/usr/ports/lang/gcc49/work/build/./gcc -nostdinc++ -L/usr/ports/lang/gcc49/work/build/i386-portbld-freebsd10.1/libstdc++-v3/src -L/usr/ports/lang/gcc49/work/build/i386-portbld-freebsd10.1/libstdc++-v3/src/.libs -L/usr/ports/lang/gcc49/work/build/i386-portbld-freebsd10.1/libstdc++-v3/libsupc++/.libs -B/usr/local/i386-portbld-freebsd10.1/bin/ -B/usr/local/i386-portbld-freebsd10.1/lib/ -isystem /usr/local/i386-portbld-freebsd10.1/include -isystem /usr/local/i386-portbld-freebsd10.1/sys-include-x c++-header -nostdinc++ -g -O2 -pipe -march=core2 -DLIBICONV_PLUG -fno-strict-aliasing -DLIBICONV_PLUG -I/usr/ports/lang/gcc49/work/build/i386-portbld-freebsd10.1/libstdc++-v3/include/i386-portbld-freebsd10.1 -I/usr/ports/lang/gcc49/work/build/i386-portbld-freebsd10.1/libstdc++-v3/include -I/usr/ports/lang/gcc49/work/gcc-4.9-20140903/libstdc++-v3/libsupc++ -O2 -g -std=gnu++0x /usr/ports/lang/gcc49/work/gcc-4.9-20140903/libstdc++- v3/include/precompiled/stdc++.h \ -o i386-portbld-freebsd10.1/bits/stdc++.h.gch/O2ggnu++0x.gch In file included from /usr/ports/lang/gcc49/work/build/i386-portbld-freebsd10.1/libstdc++-v3/include/unordered_set:48:0, from /usr/ports/lang/gcc49/work/gcc-4.9-20140903/libstdc++-v3/include/precompiled/stdc++.h:116: /usr/ports/lang/gcc49/work/build/i386-portbld-freebsd10.1/libstdc++-v3/include/bits/unordered_set.h:1354:1: internal compiler error: Segmentation fault } // namespace std ^ no stack trace because unwind library not available Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html for instructions. gmake[6]: *** [i386-portbld-freebsd10.1/bits/stdc++.h.gch/O2ggnu++0x.gch] Error 1 -- http://ache.vniz.net/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Can't build lang/gcc port on i386: segmentation fault
On Fri, 12 Sep 2014 17:26:24 +0400 Andrey Chernov a...@freebsd.org wrote: On 12.09.2014 17:06, Andrey Chernov wrote: On 12.09.2014 16:42, Gerald Pfeifer wrote: On Fri, 12 Sep 2014, Andrey Chernov wrote: As I just found, it builds with BOOTSTRAP nice, so apparently clang makes some damage. You can see CFLAGS in the log. Swap is 4GB I think it is large enough. Nothing special otherwise. BTW, previous 4.7* as lang/gcc build fine even without BOOTSTRAP. I am curious, what happens when you try lang/gcc48? My expectation would be both lang/gcc and lang/gcc48 to behave the same, since it's a very similar codebase, gcc48 just a bit newer on the same branch. We could make BOOTSTRAP the default for lang/gcc, though not doing that and thus building a lot faster has been one of the features of lang/gcc. -- Since it does not reproduce for me, do others see the same failure? Segfault is exact the same but comes from strange place - in the middle of configure check. I will try with MAKE_JOBS_UNSAFE=yes With MAKE_JOBS_UNSAFE error finally shown in proper place, but remains (it was misplaces in original lang/gcc report too, different file compiled in the log, not O2g.gch): Can you try with NO_CPU_CFLAGS=yes ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Can't build lang/gcc port on i386: segmentation fault
On 12.09.2014 18:23, Tijl Coosemans wrote: With MAKE_JOBS_UNSAFE error finally shown in proper place, but remains (it was misplaces in original lang/gcc report too, different file compiled in the log, not O2g.gch): Can you try with NO_CPU_CFLAGS=yes It works! But CPU optimizations are gone... -- http://ache.vniz.net/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Can't build lang/gcc port on i386: segmentation fault
On Fri, 12 Sep 2014 18:43:09 +0400 Andrey Chernov a...@freebsd.org wrote: On 12.09.2014 18:23, Tijl Coosemans wrote: With MAKE_JOBS_UNSAFE error finally shown in proper place, but remains (it was misplaces in original lang/gcc report too, different file compiled in the log, not O2g.gch): Can you try with NO_CPU_CFLAGS=yes It works! But CPU optimizations are gone... Then I suspect clang produces a 64 bit instruction somewhere with -march=core2. Maybe toolchain@ would be interested in debugging this further. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Can't build lang/gcc port on i386: segmentation fault
From: Andrey Chernov With recent ports tree on stable-10 i386 attempting to build lang/gcc always cause segfault at this place. /usr/ports/lang/gcc/work/build/i386-portbld-freebsd10.1/libstdc++-v3/include/valarray:1233:1: internal compiler error: Segmentation fault } // namespace ^ lang/gcc (4.8.3 and 4.8.3_1) successfully built under 8.4 i386, but using gcc-4.8.3_1 for building firefox-esr-24.7.0,1 also segfaults: dtrace -x nolibs -G -C -s ../../../js/src/devtools/javascript-trace.d -o mozjs-d trace.o ArgumentsObject.o BytecodeCompiler.o BytecodeEmitter.o CharacterEncoding .o DateTime.o Debugger.o Eval.o ExecutableAllocator.o FoldConstants.o ForkJoin.o GlobalObject.o Interpreter.o Intl.o Iteration.o LifoAlloc.o MapObject.o Marking .o Memory.o Module.o Monitor.o NameFunctions.o Nursery.o Object.o ObjectImpl.o P ageBlock.o ParallelArray.o ParseMaps.o ParseNode.o Parser.o Probes.o Profilers.o PropertyKey.o RegExp.o RegExpObject.o RegExpStatics.o RootMarking.o SPSProfiler .o ScopeObject.o SelfHosting.o Shape.o Stack.o Statistics.o StoreBuffer.o String .o StringBuffer.o TestingFunctions.o ThreadPool.o TokenStream.o Unicode.o Verifi er.o Xdr.o YarrCanonicalizeUCS2.o YarrInterpreter.o YarrPattern.o YarrSyntaxChec ker.o Zone.o jsalloc.o jsanalyze.o jsapi.o jsarray.o jsatom.o jsbool.o jsclone.o jscntxt.o jscompartment.o jscrashreport.o jsdate.o jsdbgapi.o jsdtoa.o jsexn.o jsfriendapi.o jsfun.o jsgc.o jsinfer.o jsiter.o jsmath.o jsmemorymetrics.o jsnat ivestack.o jsnum.o jsobj.o json.o jsonparser.o jsopcode.o jsperf.o jsprf.o jspro pertytree.o jsproxy.o jsreflect.o jsscript.o jsstr.o jstypedarray.o jsutil.o jsw atchpoint.o jsweakmap.o jsworkers.o jswrapper.o prmjtime.o sharkctl.o AliasAnaly sis.o AsmJS.o AsmJSLink.o AsmJSSignalHandlers.o BacktrackingAllocator.o Bailouts .o BaselineBailouts.o BaselineCompiler-shared.o BaselineCompiler.o BaselineFrame .o BaselineFrameInfo.o BaselineIC.o BaselineInspector.o BaselineJIT.o BitSet.o B ytecodeAnalysis.o C1Spewer.o CodeGenerator-shared.o CodeGenerator.o EdgeCaseAnal ysis.o EffectiveAddressAnalysis.o Ion.o IonAnalysis.o IonBuilder.o IonCaches.o I onFrames.o IonMacroAssembler.o IonSpewer.o JSONSpewer.o PerfSpewer.o LICM.o LIR. o LinearScan.o LiveRangeAllocator.o Lowering-shared.o Lowering.o MCallOptimize.o MIR.o MIRGraph.o MoveResolver.o ParallelArrayAnalysis.o ParallelFunctions.o Ran geAnalysis.o RegisterAllocator.o Safepoints.o Snapshots.o StupidAllocator.o Type Policy.o UnreachableCodeElimination.o VMFunctions.o ValueNumbering.o Assembler-x 86-shared.o BaselineCompiler-x86-shared.o BaselineIC-x86-shared.o CodeGenerator- x86-shared.o IonFrames-x86-shared.o Lowering-x86-shared.o MoveEmitter-x86-shared .o Assembler-x86.o Bailouts-x86.o BaselineCompiler-x86.o BaselineIC-x86.o CodeGe nerator-x86.o Lowering-x86.o MacroAssembler-x86.o Trampoline-x86.o ExecutableAll ocatorPosix.o OSAllocatorPosix.o ARMAssembler.o MacroAssemblerARM.o MacroAssembl erX86Common.o YarrJIT.o CTypes.o Library.o pm_stub.o gmake[3]: *** [mozjs-dtrace.o] Segmentation fault: 11 (core dumped) gmake[3]: Leaving `/usr/ports/www/firefox-esr/work/mozilla-esr24/obj-i386-portbld-freebsd8.4/js/src' ~ # gdb /usr/sbin/dtrace /usr/ports/www/firefox-esr/work/mozilla-esr24/obj-i386-portbld-freebsd8.4/js/src/dtrace.core ... (gdb) bt #0 0x28201af7 in free () from /lib/libc.so.7 #1 0x280c2e85 in dt_free () from /lib/libdtrace.so.2 #2 0x280be582 in dtrace_work () from /lib/libdtrace.so.2 #3 0x280bef7d in dtrace_work () from /lib/libdtrace.so.2 #4 0x280bfc4c in dtrace_program_link () from /lib/libdtrace.so.2 #5 0x0804be21 in ?? () #6 0x2834ac00 in ?? () #7 0x283821e0 in ?? () #8 0x0002 in ?? () #9 0x2831b018 in ?? () #10 0x00ad in ?? () #11 0x28312304 in ?? () #12 0x in ?? () (gdb) I know that firefox-esr in fresh ports tree is 31, but I don't want to upgrade firefox to Australis (29+). So, after upgrading lang/gcc to gcc-4.8.3_1 I installed also gcc47-4.7.4_1,1. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: svn commit: r368031 - head/mail/thunderbird
Am 12.09.2014 um 17:48 schrieb Baptiste Daroussin: Great so it is now broken for anyone using gcc from ports on system without libstdc++.so.6... Sorry for that. The actual issue is that if you have any port without proper dependencies earlier in the from-source upgrade list than thunderbird or firefox (thunderbird-i18n), and you upgrade one of the requisites (lang/gcc in this case) of the gecko port, then this is what happens: - the gcc upgrade rips the libstdc++.so out from the recorded thunderbird|firefox RPATH (gcc47-gcc48) - thunderbird or firefox cannot be run - Uses/gecko.mk cannot determine the version and marks the *-i18n port BROKEN - update chain is broken. I've now reverted the damage to the thunderbird port, and added BUILD_DEPENDS to firefox-i18n, firefox-esr-i18n, and thunderbird-i18n, to make sure that port upgraders such as portmaster know to update these only after updating firefox/thunderbird. I apologize for the rumble along the way. signature.asc Description: OpenPGP digital signature
Re: Can't build lang/gcc port on i386: segmentation fault
l...@lena.kiev.ua writes:
With recent ports tree on stable-10 i386 attempting to build lang/gcc
always cause segfault at this place.
/usr/ports/lang/gcc/work/build/i386-portbld-freebsd10.1/libstdc++-v3/include/valarray:1233:1:
internal compiler error: Segmentation fault
} // namespace
^
lang/gcc (4.8.3 and 4.8.3_1) successfully built under 8.4 i386, but
using gcc-4.8.3_1 for building firefox-esr-24.7.0,1 also segfaults:
dtrace -x nolibs -G -C -s ../../../js/src/devtools/javascript-trace.d -o
mozjs-d
trace.o ArgumentsObject.o ...
gmake[3]: *** [mozjs-dtrace.o] Segmentation fault: 11 (core dumped)
gmake[3]: Leaving
`/usr/ports/www/firefox-esr/work/mozilla-esr24/obj-i386-portbld-freebsd8.4/js/src'
Not related to lang/gcc. Try poking on dtrace@ maillist to find out
which commits in /stable/10 fix C++ userland tracing.
# from Mk/bsd.gecko.mk
.if ${PORT_OPTIONS:MDTRACE}
. if ${OSVERSION} 1000510
BROKEN= dtrace -G crashes with C++ object files
...
I know that firefox-esr in fresh ports tree is 31, but I don't want
to upgrade firefox to Australis (29+). So, after upgrading lang/gcc
to gcc-4.8.3_1 I installed also gcc47-4.7.4_1,1.
Partial updates are not supported. www/libxul still tracks esr24 until
esr31 is unbroken so you can copy patches from there like a fix for
--disable-dtrace in files/patch-bug1046224.
-
VFEmail.net - http://www.vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mod_auth_xradius fails with apache-2.4
Hi,
Thanks for the report. Yes, you're correct.
Ports team, I'm flooded at the moment. Can someone please
commit the one-character fix to www/mod_auth_xradius? It
should only work with Apache 2.2.
Thanks,
==ml
On Tue, Sep 09, 2014 at 03:47:28PM +0200, Andreas Nilsson wrote:
Hello,
since they changed apache default from 2.2 to 2.4 in ports
mod_auth_xradius has been failing? to build over here. Should it
perhaps just have
USE_APACHE=22 (and not 22+)?
Best regards
Andreas Nilsson
Building www/mod_auth_xradius
build started at Tue Sep 9 14:12:15 CEST 2014
port directory: /usr/ports/www/mod_auth_xradius
building for: FreeBSD 93-amd64-server-srv_wb-job-02 9.3-RELEASE FreeBSD
9.3-RELEASE amd64
maintained by: mwlu...@freebsd.org
Makefile ident: $FreeBSD: ports/www/mod_auth_xradius/Makefile,v 1.7
2012/11/17 06:02:40 svnexp Exp $
Poudriere version: 3.0.17
Host OSVERSION: 1000510
Jail OSVERSION: 903000
---Begin Environment---
OSVERSION=903000
UNAME_v=FreeBSD 9.3-RELEASE
UNAME_r=9.3-RELEASE
BLOCKSIZE=K
MAIL=/var/mail/root
STATUS=1
MASTERMNT=/poudriere/data/build/93-amd64-server-srv_wb/ref
PKG_EXT=txz
FORCE_PACKAGE=yes
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin
POUDRIERE_BUILD_TYPE=bulk
PKGNG=1
PKGNAME=ap24-mod_auth_xradius-0.4.6_1
PKG_DELETE=/usr/local/sbin/pkg-static delete -y -f
PKG_ADD=/usr/local/sbin/pkg-static add
PWD=/usr/local/etc/poudriere.d
MASTERNAME=93-amd64-server-srv_wb
USER=root
HOME=/root
POUDRIERE_VERSION=3.0.17
SKIPSANITY=0
LOCALBASE=/usr/local
PACKAGE_BUILDING=yes
PKG_BIN=/usr/local/sbin/pkg-static
---End Environment---
---Begin OPTIONS List---
=== The following configuration options are available for
ap24-mod_auth_xradius-0.4.6_1:
MEMCACHE=on: Use memcache to cache radius auth
=== Use 'make config' to modify these settings
---End OPTIONS List---
--CONFIGURE_ARGS--
--prefix=/usr/local ${_LATE_CONFIGURE_ARGS}
--End CONFIGURE_ARGS--
--CONFIGURE_ENV--
XDG_DATA_HOME=/wrkdirs/usr/ports/www/mod_auth_xradius/work
XDG_CONFIG_HOME=/wrkdirs/usr/ports/www/mod_auth_xradius/work
HOME=/wrkdirs/usr/ports/www/mod_auth_xradius/work TMPDIR=/tmp
XDG_DATA_HOME=/wrkdirs/usr/ports/www/mod_auth_xradius/work
XDG_CONFIG_HOME=/wrkdirs/usr/ports/www/mod_auth_xradius/work
HOME=/wrkdirs/usr/ports/www/mod_auth_xradius/work TMPDIR=/tmp SHELL=/bin/sh
CONFIG_SHELL=/bin/sh CONFIG_SITE=/usr/ports/Templates/config.site
lt_cv_sys_max_cmd_len=262144
--End CONFIGURE_ENV--
--MAKE_ENV--
XDG_DATA_HOME=/wrkdirs/usr/ports/www/mod_auth_xradius/work
XDG_CONFIG_HOME=/wrkdirs/usr/ports/www/mod_auth_xradius/work
HOME=/wrkdirs/usr/ports/www/mod_auth_xradius/work TMPDIR=/tmp
XDG_DATA_HOME=/wrkdirs/usr/ports/www/mod_auth_xradius/work
XDG_CONFIG_HOME=/wrkdirs/usr/ports/www/mod_auth_xradius/work
HOME=/wrkdirs/usr/ports/www/mod_auth_xradius/work TMPDIR=/tmp NO_PIE=yes
SHELL=/bin/sh NO_LINT=YES PREFIX=/usr/local LOCALBASE=/usr/local
LIBDIR=/usr/lib CC=cc CFLAGS=-O2 -fno-strict-aliasing -pipe -O2
-fno-strict-aliasing -pipe -march=core2 CPP=cpp CPPFLAGS= LDFLAGS=
LIBS= CXX=c++ CXXFLAGS=-O2 -fno-strict-aliasing -pipe -O2
-fno-strict-aliasing -pipe -march=core2 -O2 -fno-strict-aliasing -pipe
MANPREFIX=/usr/local BSD_INSTALL_PROGRAM=install -s -o root -g wheel -m
555 BSD_INSTALL_LIB=install -s -o root -g wheel -m 444
BSD_INSTALL_SCRIPT=install -o root -g wheel -m 555
BSD_INSTALL_DATA=install -o root -g wheel -m 0644
BSD_INSTALL_MAN=install -o root -g wheel -m 444
--End MAKE_ENV--
--SUB_LIST--
APACHEMODDIR=libexec/apache24
APACHEETCDIR=etc/apache24
APACHE_VERSION=24
PREFIX=/usr/local
LOCALBASE=/usr/local
DATADIR=/usr/local/share/mod_auth_xradius
DOCSDIR=/usr/local/share/doc/mod_auth_xradius
EXAMPLESDIR=/usr/local/share/examples/mod_auth_xradius
WWWDIR=/usr/local/www/mod_auth_xradius
ETCDIR=/usr/local/etc/mod_auth_xradius
--End SUB_LIST--
---Begin make.conf---
USE_PACKAGE_DEPENDS=yes
BATCH=yes
WRKDIRPREFIX=/wrkdirs
PACKAGES=/packages
DISTDIR=/distfiles
/usr/local/etc/poudriere.d/make.conf
# make.conf
CFLAGS=-O2 -fno-strict-aliasing -pipe
MAKEOPTS+=-s
DEFAULT_VERSIONS = perl5=5.16 apache=2.2
/usr/local/etc/poudriere.d/srv_wb-make.conf
# srv_wb-make.conf
WITH_PKGNG=YES
WITH_BDB_VER=48
WANT_MYSQL_VER=55
#APACHE_PORT=www/apache22
CFLAGS+=-O2 -fno-strict-aliasing -pipe
CXXFLAGS+=-O2 -fno-strict-aliasing -pipe
CPUTYPE?=core2
---End make.conf---
=== Cleaning for ap24-mod_auth_xradius-0.4.6_1
===phase: check-sanity
=== Found saved configuration for ap22-mod_auth_xradius-0.4.6_1
===
===phase: pkg-depends
=== ap24-mod_auth_xradius-0.4.6_1 depends on file: /usr/local/sbin/pkg -
not found
===Verifying
Re: Can't build lang/gcc port on i386: segmentation fault
On 12.09.2014 18:49, Tijl Coosemans wrote: Can you try with NO_CPU_CFLAGS=yes It works! But CPU optimizations are gone... Then I suspect clang produces a 64 bit instruction somewhere with -march=core2. Maybe toolchain@ would be interested in debugging this further. I contact toolchain@ related to this subj, providing core file, etc. It works on -current, amd64, -march=core2 combination (on better CPU), so it either -stable or i386-specific clang bug. Alas, I don't have -current, i386 machine with this CPU. -- http://ache.vniz.net/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
shells/bash port, add a knob which symlinks to /bin/bash ?
Hi, In the last 3 jobs that I have worked at, there have been a mix of Linux machines and FreeBSD machines. When using an NIS or LDAP environment where there is a single login across multiple machines, it is useful to have a single shell setting. Since Linux and MacOS X have /bin/bash as the shell, in order to get the FreeBSD boxes to play in this environment, I have seen admins do the following on FreeBSD setups: ln -s /usr/local/bin/bash /bin/bash or ln /usr/local/bin/bash /bin/bash and then make sure that /etc/shells as: /usr/local/bin/bash /bin/bash Can we add an optional knob (turned off by default) which creates this symlink and updates /etc/shells? This would help with interoperability of FreeBSD hosts in environments mixed with Linux and MacOS X. -- Craig ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mod_auth_xradius fails with apache-2.4
On 2014-09-12 21:20, Michael W. Lucas wrote: On Tue, Sep 09, 2014 at 03:47:28PM +0200, Andreas Nilsson wrote: Hello, since they changed apache default from 2.2 to 2.4 in ports mod_auth_xradius has been failing� to build over here. Should it perhaps just have USE_APACHE=22 (and not 22+)? Best regards Andreas Nilsson Hi, Thanks for the report. Yes, you're correct. Ports team, I'm flooded at the moment. Can someone please commit the one-character fix to www/mod_auth_xradius? It should only work with Apache 2.2. Thanks, ==ml Hi Andreas, I think this should be fixed after updating the ports tree. There was an issue in Mk/bsd.apache.mk that was fixed yesterday. If there are more ports failing, please remove the apache package from the pd package directory and also packages beginning with ap22-/ap24- and start a new build. Related entries from the provided log: Building www/mod_auth_xradius build started at Tue Sep 9 14:12:15 CEST 2014 port directory: /usr/ports/www/mod_auth_xradius ---Begin Environment--- PKGNAME=ap24-mod_auth_xradius-0.4.6_1 ... ---End Environment--- ---Begin OPTIONS List--- === The following configuration options are available for ap24-mod_auth_xradius-0.4.6_1: MEMCACHE=on: Use memcache to cache radius auth ---End OPTIONS List--- --SUB_LIST-- APACHEMODDIR=libexec/apache24 APACHEETCDIR=etc/apache24 APACHE_VERSION=24 ... --End SUB_LIST-- ---Begin make.conf--- ... DEFAULT_VERSIONS = perl5=5.16 apache=2.2 apache22 is set to default and was not honored by Mk/bsd.apache.mk, this issue is fixed meanwhile. ===phase: check-sanity === Found saved configuration for ap22-mod_auth_xradius-0.4.6_1 === ===phase: pkg-depends === ap24-mod_auth_xradius-0.4.6_1 depends on file: /usr/local/sbin/pkg - not found ===Verifying install for /usr/local/sbin/pkg in /usr/ports/ports-mgmt/pkg === Installing existing package /packages/All/pkg-1.3.7.txz [93-amd64-server-srv_wb-job-02] Installing pkg-1.3.7... done ... === Patching for ap24-mod_auth_xradius-0.4.6_1 === ===phase: build-depends === ap24-mod_auth_xradius-0.4.6_1 depends on file: /usr/local/sbin/apxs - not found ===Verifying install for /usr/local/sbin/apxs in /usr/ports/www/apache24 === Installing existing package /packages/All/apache24-2.4.10_1.txz ===Verifying for apr_memcache in /usr/ports/www/apr_memcache === Installing existing package /packages/All/apr_memcache-0.7.0.txz [93-amd64-server-srv_wb-job-02] Installing apr_memcache-0.7.0... done There no www/apr_memcache port in the ports tree, try to build the original www/mod_auth_xradius port. Test build on 8.4/10 $ uname -a FreeBSD d24g 8.4-RELEASE-p14 FreeBSD 8.4-RELEASE-p14 #0: Tue Jul 8 12:41:46 UTC 2014 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 $ make ... = build OK $ uname -a FreeBSD f10 10.0-RELEASE-p7 FreeBSD 10.0-RELEASE-p7 #0: Tue Jul 8 06:37:44 UTC 2014 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 $ make ... = build OK ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: shells/bash port, add a knob which symlinks to /bin/bash ?
No (as portmgr). Ports should not be touching the base system like this. Let's NOT go backwards and add a /bin/bash. In fact the /usr/bin/perl one will be removed soon as well. If we can actually eliminate ports touching /usr and / (not including /usr/local and /var) then we gain a very large memory optimization for package building by being able to ro null-mount these to the build jails. There's no reason for bash (and perl) to be exceptions to the 24000 other ports that install to /usr/local/bin. I can think of dozens of other ports that will fall into the same arguments being made here, but it does not mean it is the right thing for FreeBSD. If you want to install the symlink on your system feel free to do it. I install a static bash to /bin/bash on mine and only because I prefer bash shell and want it in / for single-user mode. That's my personal choice though. The proper fix is to fix scripts to be portable and use #! /usr/bin/env bash rather than /bin/bash. We install all packages to PREFIX=/usr/local by default. Why should a bin symlink be an exception? There's no suggestion for symlinking includes or libraries which also hit users often. On 9/12/2014 4:12 PM, Craig Rodrigues wrote: Hi, In the last 3 jobs that I have worked at, there have been a mix of Linux machines and FreeBSD machines. When using an NIS or LDAP environment where there is a single login across multiple machines, it is useful to have a single shell setting. Since Linux and MacOS X have /bin/bash as the shell, in order to get the FreeBSD boxes to play in this environment, I have seen admins do the following on FreeBSD setups: ln -s /usr/local/bin/bash /bin/bash or ln /usr/local/bin/bash /bin/bash and then make sure that /etc/shells as: /usr/local/bin/bash /bin/bash Can we add an optional knob (turned off by default) which creates this symlink and updates /etc/shells? This would help with interoperability of FreeBSD hosts in environments mixed with Linux and MacOS X. -- Craig ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: shells/bash port, add a knob which symlinks to /bin/bash ?
On Fri, Sep 12, 2014 at 02:12:45PM -0700, Craig Rodrigues wrote: Hi, In the last 3 jobs that I have worked at, there have been a mix of Linux machines and FreeBSD machines. When using an NIS or LDAP environment where there is a single login across multiple machines, it is useful to have a single shell setting. Since Linux and MacOS X have /bin/bash as the shell, in order to get the FreeBSD boxes to play in this environment, I have seen admins do the following on FreeBSD setups: ln -s /usr/local/bin/bash /bin/bash or ln /usr/local/bin/bash /bin/bash and then make sure that /etc/shells as: /usr/local/bin/bash /bin/bash Can we add an optional knob (turned off by default) which creates this symlink and updates /etc/shells? This would help with interoperability of FreeBSD hosts in environments mixed with Linux and MacOS X. Please no, no and no! We are fighting for a very long time to prevent the ports to pollute base. We have added the shebangfix USES to be able to catch with up with cleanup this properly as well as a qa test to discover it automatically. no interpreters at all have a symlink in base but perl and this one is going to be removed. If you want interoperability just use /usr/bin/env bash as a shebang. Btw you cannot get interoprability with OS-X in there because the bash they do provide is the last GPL-2 recent bash have many incompatiblities with this old version. regards, Bapt pgp4tN48uIUNl.pgp Description: PGP signature
Re: poudriere bulk - why does it fail on single package with missing port origin?
On 9/11/2014 8:51 AM, Michael Jung wrote: Why does poudriere bulk need to bail because a single package has a missing port origin and not continue to build other packages in the package list? If I remove x11/mate from my package list poudriere rocks on building all my other ports. The missing origin is a RUN_DEPENDS in the x11/mate Makefile, but that dependency should only be for x11/mate right? I can't seem to find a good explanation in the general man pages or searching the web. Educate me please ;-) A lot of the reason is just the way poudriere handles looking up dependencies. I'm willing to explore moving this fatal error such that the port is just listed as FAILED and anything depending on it is SKIPPED. There's currently no way to do that without more logic. This sort of error hits the package build system quite often. When someone breaks INDEX they also break package building because of this error. I am more and more convinced that we should not consider these immediately fatal. However, we should also consider a threshold feature such that too many failures for bulk will cause the set to not be published. 3.1 adds a feature called atomic package repository that builds packages outside of the normal repository dir. Once the build is done the packages are synced over. I added a way to prevent publishing the set if ANYTHING fails, but it's not using a threshold yet. I'll improve that. This will have to wait until after 3.1 though. It will be releasing once I find time to focus on getting it out. --mikej Example: poudriere 3.0.17/11.0-CURRENT #1 r264318M amd64 [root@bsd11 /usr/local/poudriere/ports/default/x11/mate]# poudriere bulk -j 10stable -f /usr/local/etc/charon-list Creating the reference jail... done Mounting system devices for 10stable-default Mounting ports/packages/distfiles Mounting ccache from: /var/cache/ccache Mounting packages from: /usr/local/poudriere/data/packages/10stable-default Logs: /usr/local/poudriere/data/logs/bulk/10stable-default/2014-09-10_12h18m15s Appending to make.conf: /usr/local/etc/poudriere.d/10stable-make.conf /etc/resolv.conf - /usr/local/poudriere/data/build/10stable-default/ref/etc/resolv.conf Starting jail 10stable-default Loading MOVED Calculating ports order and dependencies MOVED: databases/db41 renamed to databases/db48 MOVED: databases/db42 renamed to databases/db48 Error: Invalid port origin 'archivers/mate-file-archiver' not found. Cleaning up Umounting file systems [root@bsd11 /usr/local/poudriere/ports/default/x11/mate]# AFTER remove x11/mate from the list charon-list [root@bsd11 /usr/local/poudriere/ports/default/x11/mate]# poudriere bulk -j 10stable -f /usr/local/etc/charon-list Creating the reference jail... done Mounting system devices for 10stable-default Mounting ports/packages/distfiles Mounting ccache from: /var/cache/ccache Mounting packages from: /usr/local/poudriere/data/packages/10stable-default Logs: /usr/local/poudriere/data/logs/bulk/10stable-default/2014-09-10_12h20m14s Appending to make.conf: /usr/local/etc/poudriere.d/10stable-make.conf /etc/resolv.conf - /usr/local/poudriere/data/build/10stable-default/ref/etc/resolv.conf Starting jail 10stable-default Loading MOVED Calculating ports order and dependencies MOVED: databases/db41 renamed to databases/db48 MOVED: databases/db42 renamed to databases/db48 Sanity checking the repository Deleting old version: liboil-0.3.17_1.txz Deleting old version: p5-DBD-Pg-3.4.0.txz Deleting old version: p5-Net-SSLeay-1.65.txz Deleting stale symlinks Deleting empty directories Cleaning the build queue Building 490 packages using 8 builders Starting/Cloning builders Hit CTRL+t at any time to see build progress and stats ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
RE: shells/bash port, add a knob which symlinks to /bin/bash ?
If you want interoperability just use /usr/bin/env bash as a shebang. That doesn't work for this use case -- the user shell coming from LDAP -- but I agree that the port shouldn't be modifying /usr/bin. It's easy enough to add the symlink manually after installing the port if you're in this situation, or there may be a way to configure the LDAP module to map /bin/bash to /usr/local/bin/bash (I haven't looked to see what is supported here). Anton ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
RE: shells/bash port, add a knob which symlinks to /bin/bash ?
On Fri, 12 Sep 2014, Rang, Anton wrote: If you want interoperability just use /usr/bin/env bash as a shebang. That doesn't work for this use case -- the user shell coming from LDAP -- but I agree that the port shouldn't be modifying /usr/bin. Here at MIT, where our Athena environment has a long history of providing a consistent experience across many different platforms, we ended up limiting the login shells a user could select, to a whitelist we provide (/bin/sh, /usr/athena/bin/bash, and /usr/athena/bin/tcsh). (The latter two are now symlinks to the normal system shells, but they used to be custom binaries.) Some people did not like being so restricted, and set their login shell to /bin/sh, with logic in their dotfiles to re-exec a different shell depending on the current runtime environment. -Ben ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: shells/bash port, add a knob which symlinks to /bin/bash ?
On Sep 12, 2014, at 14:53, Benjamin Kaduk ka...@mit.edu wrote: On Fri, 12 Sep 2014, Rang, Anton wrote: If you want interoperability just use /usr/bin/env bash as a shebang. That doesn't work for this use case -- the user shell coming from LDAP -- but I agree that the port shouldn't be modifying /usr/bin. Here at MIT, where our Athena environment has a long history of providing a consistent experience across many different platforms, we ended up limiting the login shells a user could select, to a whitelist we provide (/bin/sh, /usr/athena/bin/bash, and /usr/athena/bin/tcsh). (The latter two are now symlinks to the normal system shells, but they used to be custom binaries.) Some people did not like being so restricted, and set their login shell to /bin/sh, with logic in their dotfiles to re-exec a different shell depending on the current runtime environment. +1 user rc files (not that it would fix this particular case...): - https://github.com/yaneurabeya/scratch/blob/master/bayonetta/home/ngie/dot.bashrc - https://github.com/yaneurabeya/scratch/blob/master/bayonetta/home/ngie/dot.shrc-local Cheers, -Garrett signature.asc Description: Message signed with OpenPGP using GPGMail
RE: shells/bash port, add a knob which symlinks to /bin/bash ?
On Fri, 12 Sep 2014, Rang, Anton wrote: If you want interoperability just use /usr/bin/env bash as a shebang. That doesn't work for this use case -- the user shell coming from LDAP -- but I agree that the port shouldn't be modifying /usr/bin. It's easy enough to add the symlink manually after installing the port if you're in this situation, or there may be a way to configure the LDAP module to map /bin/bash to /usr/local/bin/bash (I haven't looked to see what is supported here). We have used LDAP on Solaris for years, and have mixed environments of Solaris, Linux, and FreeBSD. We use /usr/local/bin/bash in LDAP for shells, then either link that to the system /bin/bash or install more up-to-date bash in /usr/local/bin. This way you can always install a more up-to-date shell in /usr/local/bin without changing the base OS - you don't want base OS shell scripts to break by updating to a newer shell. -- DE ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: poudriere bulk - why does it fail on single package with missing port origin?
On 2014-09-12 17:46, Bryan Drewery wrote: On 9/11/2014 8:51 AM, Michael Jung wrote: Why does poudriere bulk need to bail because a single package has a missing port origin and not continue to build other packages in the package list? If I remove x11/mate from my package list poudriere rocks on building all my other ports. The missing origin is a RUN_DEPENDS in the x11/mate Makefile, but that dependency should only be for x11/mate right? I can't seem to find a good explanation in the general man pages or searching the web. Educate me please ;-) A lot of the reason is just the way poudriere handles looking up dependencies. I'm willing to explore moving this fatal error such that the port is just listed as FAILED and anything depending on it is SKIPPED. There's currently no way to do that without more logic. This sort of error hits the package build system quite often. When someone breaks INDEX they also break package building because of this error. I am more and more convinced that we should not consider these immediately fatal. However, we should also consider a threshold feature such that too many failures for bulk will cause the set to not be published. 3.1 adds a feature called atomic package repository that builds packages outside of the normal repository dir. Once the build is done the packages are synced over. I added a way to prevent publishing the set if ANYTHING fails, but it's not using a threshold yet. I'll improve that. This will have to wait until after 3.1 though. It will be releasing once I find time to focus on getting it out. --mikej Example: poudriere 3.0.17/11.0-CURRENT #1 r264318M amd64 [root@bsd11 /usr/local/poudriere/ports/default/x11/mate]# poudriere bulk -j 10stable -f /usr/local/etc/charon-list Creating the reference jail... done Mounting system devices for 10stable-default Mounting ports/packages/distfiles Mounting ccache from: /var/cache/ccache Mounting packages from: /usr/local/poudriere/data/packages/10stable-default Logs: /usr/local/poudriere/data/logs/bulk/10stable-default/2014-09-10_12h18m15s Appending to make.conf: /usr/local/etc/poudriere.d/10stable-make.conf /etc/resolv.conf - /usr/local/poudriere/data/build/10stable-default/ref/etc/resolv.conf Starting jail 10stable-default Loading MOVED Calculating ports order and dependencies MOVED: databases/db41 renamed to databases/db48 MOVED: databases/db42 renamed to databases/db48 Error: Invalid port origin 'archivers/mate-file-archiver' not found. Cleaning up Umounting file systems [root@bsd11 /usr/local/poudriere/ports/default/x11/mate]# AFTER remove x11/mate from the list charon-list [root@bsd11 /usr/local/poudriere/ports/default/x11/mate]# poudriere bulk -j 10stable -f /usr/local/etc/charon-list Creating the reference jail... done Mounting system devices for 10stable-default Mounting ports/packages/distfiles Mounting ccache from: /var/cache/ccache Mounting packages from: /usr/local/poudriere/data/packages/10stable-default Logs: /usr/local/poudriere/data/logs/bulk/10stable-default/2014-09-10_12h20m14s Appending to make.conf: /usr/local/etc/poudriere.d/10stable-make.conf /etc/resolv.conf - /usr/local/poudriere/data/build/10stable-default/ref/etc/resolv.conf Starting jail 10stable-default Loading MOVED Calculating ports order and dependencies MOVED: databases/db41 renamed to databases/db48 MOVED: databases/db42 renamed to databases/db48 Sanity checking the repository Deleting old version: liboil-0.3.17_1.txz Deleting old version: p5-DBD-Pg-3.4.0.txz Deleting old version: p5-Net-SSLeay-1.65.txz Deleting stale symlinks Deleting empty directories Cleaning the build queue Building 490 packages using 8 builders Starting/Cloning builders Hit CTRL+t at any time to see build progress and stats ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org Thank you for the answer. And as a user since 2.x kudo's to you, Brian and all the others working on PKG and poudriere - they have made port management and deployment nearly a non-event and I applaud everyone's effort. --mikej ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: shells/bash port, add a knob which symlinks to /bin/bash ?
On Sep 12, 2014, at 2:40 PM, Baptiste Daroussin b...@freebsd.org wrote: If you want interoperability just use /usr/bin/env bash as a shebang. Btw you cannot get interoprability with OS-X in there because the bash they do provide is the last GPL-2 recent bash have many incompatiblities with this old version. The concern is not with shell scripts, it's with the contents of the pw_shell field in 'struct passwd'. I run into this all the time, too, but with ksh. In my case I just cp a static-linked version of whatever ksh variant I happened to build into /bin/ksh and call it a day. It's not like the shell source code is changing every other week, even for bash. --lyndon signature.asc Description: Message signed with OpenPGP using GPGMail
FreeBSD Port: py27-fail2ban-0.9.0_2
Hello, I've been trying to work out why logging via syslog does not function and found that fail2ban has a hard coded socket for the syslog daemon which is not BSD compatible. Here is a patch to resolve, otherwise pass it upstream to have the project make it a configuration directive. stavros@escdev:/home/stavros# diff -a -b /usr/local/lib/python2.7/site-packages/fail2ban/server/server.py /tmp/server.py 371c371 hdlr = logging.handlers.SysLogHandler(/dev/log, facility=facility) --- hdlr = logging.handlers.SysLogHandler(/var/run/log, facility=facility) Stavros Patiniotis Managing Director Escapenet national 1300 135 235 phone 8292 5200 fax 1300 136 296 web http://www.esc.net.au/ www.esc.net.au sales mailto:sa...@staff.esc.net.au sa...@staff.esc.net.au support mailto:supp...@staff.esc.net.au supp...@staff.esc.net.au accounts mailto:accou...@staff.esc.net.au accou...@staff.esc.net.au Permitted use confidentiality terms covering the contents of this email are located at http://www.esc.net.au/terms/Email-v1.0.pdf http://www.esc.net.au/terms/Email-v1.0.pdf ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
