Re: Fix the breaking DMA port?
On 16/04/21 19:21, Dan Mahoney (Ports) wrote:
All,
Could we pretty please get:
a) The dma port unbroken? (https://portsfallout.com/fallout/277280/ — but the
fix seems to be here:
https://github.com/corecode/dma/commit/c3a04c866881d43a71f6d005f3a5006ba83151af)
Hello!
It was fixed in Feb by this commit:
commit 07fa21db682be2afe108f3580d9467cde3b35097
Author: Renato Botelho
Date: Thu Feb 11 14:08:44 2021 +
mail/dma: Fix compiler warning
- Make verify_server_fingerprint() static and fix compiler warning
- While here, re-generate other patches with `make makepatch`
Sponsored by: Rubicon Communications, LLC ("Netgate")
and if you’re feeling nice...
b) dma in base MFU’s (moved from upstream) to align with this?
I'm not the maintainer of dma on src. I'll take a look to see who made
last modifications on it and ping the person.
Dayjob uses it, and there’s a couple of newalias-related bugs which our puppet
install trips over. (it runs newaliases when it modifies aliases).
Thanks!
--
Renato Botelho
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Correct syntax for CFLAGS to change a -DCONFIG_FILE_PATH=...
On 30/12/20 05:31, Nuno Teixeira wrote:
Hello,
Recently upstream changed is example.c to have:
#ifndef CONFIG_FILE_PATH
#define CONFIG_FILE_PATH "./example.conf"
#endif
I found a way to change it in example port Makefile:
CFLAGS+=
-https://github.com/johnmehr/gitup/pull/17=\\\"${LOCALBASE}/etc/example.conf\\\";
It works fine.
Am I doing the correct way and correct syntax? Those "\\\" ... "\\\" make
me some confusion.
I've opened a PR [1] to improve gitup's Makefile and after it's accepted
you will be able to use:
MAKE_ENV+= CONFIG_FILE_PATH=${LOCALBASE}/etc/gitup.conf
[1] https://github.com/johnmehr/gitup/pull/17
--
Renato Botelho
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: lang/rust failing to build on aarch64
On 09/10/20 09:16, Renato Botelho wrote: Here at pfSense we follow ports tree quarterly branch. This week I merged 2020Q4 and then rust stop building on 12.x aarch64. Before the merge we had rust version 1.44.1_1 and now we got 1.46.0. We do native build on a ThunderX running 13-CURRENT from January (r357002) and poudriere jail is running stable/12 based src. When I try to build I got the following error (full log at [1]): rustc command: "LD_LIBRARY_PATH"="/wrkdirs/usr/ports/lang/rust/work/bootstrap/lib:/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/build/aarch64-unknown-freebsd/stage0-std/release/deps:/wrkdirs/usr/ports/lang/rust/work/bootstrap/lib" "/wrkdirs/usr/ports/lang/rust/work/bootstrap/bin/rustc" "--crate-name" "rustc_std_workspace_core" "--edition=2018" "src/tools/rustc-std-workspace-core/lib.rs" "--error-format=json" "--json=diagnostic-rendered-ansi,artifacts" "--crate-type" "lib" "--emit=dep-info,metadata,link" "-C" "opt-level=3" "-Cembed-bitcode=no" "-C" "debuginfo=0" "-C" "metadata=6ef567c55f0253ba" "-C" "extra-filename=-6ef567c55f0253ba" "--out-dir" "/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/build/aarch64-unknown-freebsd/stage0-std/aarch64-unknown-freebsd/release/deps" "--target" "aarch64-unknown-freebsd" "-C" "linker=cc" "-L" "dependency=/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/build/aarch64-unknown-freebsd/stage0-std/aarch64-unknown-freebsd/release/deps" "-L" "dependency=/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/build/aarch64-unknown-freebsd/stage0-std/release/deps" "--extern" "core=/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/build/aarch64-unknown-freebsd/stage0-std/aarch64-unknown-freebsd/release/deps/libcore-65643217d9192060.rmeta" "--cfg=bootstrap" "-Zmacro-backtrace" "-Clink-args=-Wl,-rpath,$ORIGIN/../lib" "-Cprefer-dynamic" "-Zbinary-dep-depinfo" "-Wrust_2018_idioms" "-Wunused_lifetimes" "-Dwarnings" "--sysroot" "/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/build/aarch64-unknown-freebsd/stage0-sysroot" "-Z" "force-unstable-if-unmarked" sysroot: "/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/build/aarch64-unknown-freebsd/stage0-sysroot" libdir: "/wrkdirs/usr/ports/lang/rust/work/bootstrap/lib" command did not execute successfully: "/wrkdirs/usr/ports/lang/rust/work/bootstrap/bin/cargo" "build" "--target" "aarch64-unknown-freebsd" "-Zbinary-dep-depinfo" "-j" "12" "-v" "--release" "--frozen" "--features" "panic-unwind backtrace compiler-builtins-c" "--manifest-path" "/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/src/libtest/Cargo.toml" "--message-format" "json-render-diagnostics" expected success, got: signal: 11 Traceback (most recent call last): File "x.py", line 11, in bootstrap.main() File "/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/src/bootstrap/bootstrap.py", line 981, in main bootstrap(help_triggered) File "/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/src/bootstrap/bootstrap.py", line 967, in bootstrap run(args, env=env, verbose=build.verbose) File "/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/src/bootstrap/bootstrap.py", line 143, in run raise RuntimeError(err) RuntimeError: failed to run: /wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/build/bootstrap/debug/bootstrap install --jobs=12 *** Error code 1 [1] https://gist.github.com/rbgarga/b2a31ffed23cd761f8dd30b8850eec68 FYI, 1.44.1_1 still builds fine. I'm downgrading it on pfSense repos for now. -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
lang/rust failing to build on aarch64
Here at pfSense we follow ports tree quarterly branch. This week I merged 2020Q4 and then rust stop building on 12.x aarch64. Before the merge we had rust version 1.44.1_1 and now we got 1.46.0. We do native build on a ThunderX running 13-CURRENT from January (r357002) and poudriere jail is running stable/12 based src. When I try to build I got the following error (full log at [1]): rustc command: "LD_LIBRARY_PATH"="/wrkdirs/usr/ports/lang/rust/work/bootstrap/lib:/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/build/aarch64-unknown-freebsd/stage0-std/release/deps:/wrkdirs/usr/ports/lang/rust/work/bootstrap/lib" "/wrkdirs/usr/ports/lang/rust/work/bootstrap/bin/rustc" "--crate-name" "rustc_std_workspace_core" "--edition=2018" "src/tools/rustc-std-workspace-core/lib.rs" "--error-format=json" "--json=diagnostic-rendered-ansi,artifacts" "--crate-type" "lib" "--emit=dep-info,metadata,link" "-C" "opt-level=3" "-Cembed-bitcode=no" "-C" "debuginfo=0" "-C" "metadata=6ef567c55f0253ba" "-C" "extra-filename=-6ef567c55f0253ba" "--out-dir" "/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/build/aarch64-unknown-freebsd/stage0-std/aarch64-unknown-freebsd/release/deps" "--target" "aarch64-unknown-freebsd" "-C" "linker=cc" "-L" "dependency=/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/build/aarch64-unknown-freebsd/stage0-std/aarch64-unknown-freebsd/release/deps" "-L" "dependency=/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/build/aarch64-unknown-freebsd/stage0-std/release/deps" "--extern" "core=/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/build/aarch64-unknown-freebsd/stage0-std/aarch64-unknown-freebsd/release/deps/libcore-65643217d9192060.rmeta" "--cfg=bootstrap" "-Zmacro-backtrace" "-Clink-args=-Wl,-rpath,$ORIGIN/../lib" "-Cprefer-dynamic" "-Zbinary-dep-depinfo" "-Wrust_2018_idioms" "-Wunused_lifetimes" "-Dwarnings" "--sysroot" "/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/build/aarch64-unknown-freebsd/stage0-sysroot" "-Z" "force-unstable-if-unmarked" sysroot: "/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/build/aarch64-unknown-freebsd/stage0-sysroot" libdir: "/wrkdirs/usr/ports/lang/rust/work/bootstrap/lib" command did not execute successfully: "/wrkdirs/usr/ports/lang/rust/work/bootstrap/bin/cargo" "build" "--target" "aarch64-unknown-freebsd" "-Zbinary-dep-depinfo" "-j" "12" "-v" "--release" "--frozen" "--features" "panic-unwind backtrace compiler-builtins-c" "--manifest-path" "/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/src/libtest/Cargo.toml" "--message-format" "json-render-diagnostics" expected success, got: signal: 11 Traceback (most recent call last): File "x.py", line 11, in bootstrap.main() File "/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/src/bootstrap/bootstrap.py", line 981, in main bootstrap(help_triggered) File "/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/src/bootstrap/bootstrap.py", line 967, in bootstrap run(args, env=env, verbose=build.verbose) File "/wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/src/bootstrap/bootstrap.py", line 143, in run raise RuntimeError(err) RuntimeError: failed to run: /wrkdirs/usr/ports/lang/rust/work/rustc-1.46.0-src/build/bootstrap/debug/bootstrap install --jobs=12 *** Error code 1 [1] https://gist.github.com/rbgarga/b2a31ffed23cd761f8dd30b8850eec68 -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Json-c, bind, and updating
On 10/06/20 03:18, Steve Kargl wrote: On Tue, Jun 09, 2020 at 11:45:28PM -0600, @lbutlr wrote: This has happened in the past, but it happened again this weekend when an update to ;ibjson-c did not update bind, rendering bind unable to load libjson-c.so.4 because it had been replaced with libjson-c.so.5. man libmap.conf This allows you to associate libjson-c.so.4 with *.5 without doing the symlink, which you'll need to remember to remove in the future. My libmap.conf currently has % cat /etc/libmap.conf includedir /usr/local/etc/libmap.d libicui18n.so.66 libicui18n.so.67 libicuuc.so.66libicuuc.so.67 libevent-2.1.so.6 libevent-2.1.so.7 libncurses.so.8 libncurses.so.9 libncursesw.so.8 libncursesw.so.9 because it seems like everything (indirectly) depends on libncurses change and the icu port. Eventually, portmaster and I catch up and libmap.conf entries are removed. For this libncurses speficific case you can just install misc/compat12x and have the old library version available. -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg / poudriere issue - wrong packagesite / meta
On 02/03/20 16:22, Renato Botelho wrote: On 02/03/20 16:02, Renato Botelho wrote: On 02/03/20 14:49, Grzegorz Junka wrote: I just finished building ports for FreeBSD 12.1. I have already upgraded base to 12.1 and now I am trying to update packages, but pkg fails with this cryptic error: # pkg update Updating desktop_nvidia repository catalogue... pkg: repository meta has wrong version 2 pkg: Repository desktop_nvidia load error: meta cannot be loaded No error: 0 Fetching meta.txz: 100% 236 B 0.2kB/s 00:01 pkg: repository meta has wrong version 2 repository desktop_nvidia has no meta file, using default settings Fetching packagesite.txz: 100% 463 KiB 474.1kB/s 00:01 pkg: repository meta has wrong version 2 pkg: Repository desktop_nvidia load error: meta cannot be loaded No error: 0 Unable to open created repository desktop_nvidia Unable to update repository desktop_nvidia Error updating repositories! There was no error in poudriere, 1067 packages have been built successfully, 1 skipped, 3 ignored. Poudriere version 3.3.2_1 The new repo has meta: # cat meta.conf version = 2; packing_format = "txz"; manifests = "packagesite.yaml"; filesite = "filesite.yaml"; manifests_archive = "packagesite"; filesite_archive = "filesite"; The old repo had meta: # cat meta version = 1; packing_format = "txz"; digest_format = "sha256_base32"; digests = "digests"; manifests = "packagesite.yaml"; filesite = "filesite.yaml"; digests_archive = "digests"; manifests_archive = "packagesite"; filesite_archive = "filesite"; So looks like the meta has changed and the old pkg, which is installed on the system, doesn't like it. How am I supposed to upgrade the pkg and/or database to the new version? I saw this problem on a personal pfSense builder. The ports tree used has old pkg and needs to have meta version 1, but it seems poudriere is using pkg-static binary from host machine (version 1.13.2) to build repository and it ends up with meta version 2. For now I moved builder machine to use quarterly repository, which contains pkg 1.12.x Ooops, quarterly also has pkg 1.13.2 now. Just to clarify, quarterly is still on 1.12 and it was a mistake I made. I'm going to have a coffee and stay away from keyboard a bit. Sorry about the noise. -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg / poudriere issue - wrong packagesite / meta
On 02/03/20 16:02, Renato Botelho wrote: On 02/03/20 14:49, Grzegorz Junka wrote: I just finished building ports for FreeBSD 12.1. I have already upgraded base to 12.1 and now I am trying to update packages, but pkg fails with this cryptic error: # pkg update Updating desktop_nvidia repository catalogue... pkg: repository meta has wrong version 2 pkg: Repository desktop_nvidia load error: meta cannot be loaded No error: 0 Fetching meta.txz: 100% 236 B 0.2kB/s 00:01 pkg: repository meta has wrong version 2 repository desktop_nvidia has no meta file, using default settings Fetching packagesite.txz: 100% 463 KiB 474.1kB/s 00:01 pkg: repository meta has wrong version 2 pkg: Repository desktop_nvidia load error: meta cannot be loaded No error: 0 Unable to open created repository desktop_nvidia Unable to update repository desktop_nvidia Error updating repositories! There was no error in poudriere, 1067 packages have been built successfully, 1 skipped, 3 ignored. Poudriere version 3.3.2_1 The new repo has meta: # cat meta.conf version = 2; packing_format = "txz"; manifests = "packagesite.yaml"; filesite = "filesite.yaml"; manifests_archive = "packagesite"; filesite_archive = "filesite"; The old repo had meta: # cat meta version = 1; packing_format = "txz"; digest_format = "sha256_base32"; digests = "digests"; manifests = "packagesite.yaml"; filesite = "filesite.yaml"; digests_archive = "digests"; manifests_archive = "packagesite"; filesite_archive = "filesite"; So looks like the meta has changed and the old pkg, which is installed on the system, doesn't like it. How am I supposed to upgrade the pkg and/or database to the new version? I saw this problem on a personal pfSense builder. The ports tree used has old pkg and needs to have meta version 1, but it seems poudriere is using pkg-static binary from host machine (version 1.13.2) to build repository and it ends up with meta version 2. For now I moved builder machine to use quarterly repository, which contains pkg 1.12.x Ooops, quarterly also has pkg 1.13.2 now. -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg / poudriere issue - wrong packagesite / meta
On 02/03/20 14:49, Grzegorz Junka wrote: I just finished building ports for FreeBSD 12.1. I have already upgraded base to 12.1 and now I am trying to update packages, but pkg fails with this cryptic error: # pkg update Updating desktop_nvidia repository catalogue... pkg: repository meta has wrong version 2 pkg: Repository desktop_nvidia load error: meta cannot be loaded No error: 0 Fetching meta.txz: 100% 236 B 0.2kB/s 00:01 pkg: repository meta has wrong version 2 repository desktop_nvidia has no meta file, using default settings Fetching packagesite.txz: 100% 463 KiB 474.1kB/s 00:01 pkg: repository meta has wrong version 2 pkg: Repository desktop_nvidia load error: meta cannot be loaded No error: 0 Unable to open created repository desktop_nvidia Unable to update repository desktop_nvidia Error updating repositories! There was no error in poudriere, 1067 packages have been built successfully, 1 skipped, 3 ignored. Poudriere version 3.3.2_1 The new repo has meta: # cat meta.conf version = 2; packing_format = "txz"; manifests = "packagesite.yaml"; filesite = "filesite.yaml"; manifests_archive = "packagesite"; filesite_archive = "filesite"; The old repo had meta: # cat meta version = 1; packing_format = "txz"; digest_format = "sha256_base32"; digests = "digests"; manifests = "packagesite.yaml"; filesite = "filesite.yaml"; digests_archive = "digests"; manifests_archive = "packagesite"; filesite_archive = "filesite"; So looks like the meta has changed and the old pkg, which is installed on the system, doesn't like it. How am I supposed to upgrade the pkg and/or database to the new version? I saw this problem on a personal pfSense builder. The ports tree used has old pkg and needs to have meta version 1, but it seems poudriere is using pkg-static binary from host machine (version 1.13.2) to build repository and it ends up with meta version 2. For now I moved builder machine to use quarterly repository, which contains pkg 1.12.x -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Retiring GNU objdump 2.17.50
On 09/01/20 12:56, Konstantin Belousov wrote: On Thu, Jan 09, 2020 at 10:31:55AM -0500, Ed Maste wrote: We currently install and use at most three tools from GNU binutils 2.17.50, depending on target architecture: 1. as - assembler 2. ld - linker 3. objdump - diagnostic / information tool I hope to retire all use of these obsolete binutils before FreeBSD 13. Here I'd like to discuss objdump. It is a diagnostic tool that provides information about object files, binaries and libraries. It's not required as a bootstrap tool (i.e., not needed to build FreeBSD world or kernel). It is required to build a limited number of ports, and is used by some developers. I have a tracking PR for GNU objdump's retirement open in PR 229046. https://bugs.freebsd.org/229046. There are two ways we can proceed with its retirement: 1. Remove it without replacement. Ports that need objdump to build will have to depend on the binutils package/port, and users who wish to use it will have to install it. Related links for this path: Ports exp-run: https://bugs.freebsd.org/212319 Patch review: https://reviews.freebsd.org/D7338 2. Install llvm-objdump in its place (perhaps via a symlink). llvm-objdump is broadly compatible in both command-line argument parsing and output format, but there are many small differences and it's not a full drop-in replacement. Related links for this path: Patch review: https://reviews.freebsd.org/D18307 I am interested in feedback on the preferred approach. Installing llvm's objdump has the advantage that for most use cases everything will "just work", but may also introduce subtle failures. IMO no. 1 is preferrable because we do not need to track differences, nor we need to explain them. Having to install binutils port is not a high cost, and if somebody needs details about binary at the level provided by objdump, including disassembler, she would need binutils port anyway. +1 -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports/arj build failing on -current
On 08/08/19 11:02, Walter Schwarzenfeld wrote:
> msgbind.c:452:50: warning: if statement has empty body [-Wempty-body]
> if(argv[6][strlen(argv[6])-1]!=PATHSEP_DEFAULT);
> ^
> msgbind.c:452:50: note: put the semicolon on a separate line to silence
> this warning
> 1 warning generated.
>
> Do what it want. Try to => put the semicolon on a separate line.
>
> (althrough it is a warning, I remember a case, this simple thing "was it").
[resending to the list with proper From]
It looks like that semicolon shouldn't be there.
Michael, can you try attached patch and let me know if it fixes the
problem? I can't reproduce so it's hard to say.
--
Renato Botelho
Index: Makefile
===
--- Makefile(revision 508386)
+++ Makefile(working copy)
@@ -3,7 +3,7 @@
PORTNAME= arj
PORTVERSION= 3.10.22
-PORTREVISION= 8
+PORTREVISION= 9
CATEGORIES=archivers
MASTER_SITES= SF/${PORTNAME}/${PORTNAME}/2.78_3.10%20build%2022:source \
DEBIAN_POOL:patch
Index: files/patch-msgbind.c
===
--- files/patch-msgbind.c (nonexistent)
+++ files/patch-msgbind.c (working copy)
@@ -0,0 +1,11 @@
+--- msgbind.c.orig 2019-08-08 14:39:25 UTC
msgbind.c
+@@ -449,7 +449,7 @@ int main(int argc, char **argv)
+ strcpyn(target_n, argv[6], sizeof(target_n)-8);
+ strcpyn(target_f, argv[6], sizeof(target_f)-8);
+ strcpyn(target_h, argv[6], sizeof(target_f)-8); /* v 1.41+ */
+- if(argv[6][strlen(argv[6])-1]!=PATHSEP_DEFAULT);
++ if(argv[6][strlen(argv[6])-1]!=PATHSEP_DEFAULT)
+ {
+strcat(target_i, pathsep);
+strcat(target_n, pathsep);
Property changes on: files/patch-msgbind.c
___
Added: fbsd:nokeywords
## -0,0 +1 ##
+yes
\ No newline at end of property
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+text/plain
\ No newline at end of property
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports/arj build failing on -current
On 07/08/19 21:42, Michael Butler wrote: > Is anyone else seeing this? > > My in-jail build fails with .. (msgbind aborts) > > gmake[3]: Entering directory '/usr/ports/archivers/arj/work/arj-3.10.22' > cc -DARJUTIL -c -Ifreebsd13.0 -I./freebsd13.0/en/rs -I. -O2 -pipe > -march=penryn -fstack-protector-strong -fno-strict-aliasing > -DLOCALE=LANG_en -DLOCALE_DESC="\"en\"" > -DPKGLIBDIR="\"/usr/local/lib/arj\"" -D_UNIX -O2 -pipe -march=penryn > -fstack-protector-strong -fno-strict-aliasing > -ofreebsd13.0/en/rs/tools/filemode.o filemode.c > cc -DARJUTIL -c -Ifreebsd13.0 -I./freebsd13.0/en/rs -I. -O2 -pipe > -march=penryn -fstack-protector-strong -fno-strict-aliasing > -DLOCALE=LANG_en -DLOCALE_DESC="\"en\"" > -DPKGLIBDIR="\"/usr/local/lib/arj\"" -D_UNIX -O2 -pipe -march=penryn > -fstack-protector-strong -fno-strict-aliasing > -ofreebsd13.0/en/rs/tools/msgbind.o msgbind.c > msgbind.c:452:50: warning: if statement has empty body [-Wempty-body] > if(argv[6][strlen(argv[6])-1]!=PATHSEP_DEFAULT); > ^ > msgbind.c:452:50: note: put the semicolon on a separate line to silence > this warning > 1 warning generated. > cc -DARJUTIL -c -Ifreebsd13.0 -I./freebsd13.0/en/rs -I. -O2 -pipe > -march=penryn -fstack-protector-strong -fno-strict-aliasing > -DLOCALE=LANG_en -DLOCALE_DESC="\"en\"" > -DPKGLIBDIR="\"/usr/local/lib/arj\"" -D_UNIX -O2 -pipe -march=penryn > -fstack-protector-strong -fno-strict-aliasing > -ofreebsd13.0/en/rs/tools/arjdata.o arjdata.c > cc -DARJUTIL -c -Ifreebsd13.0 -I./freebsd13.0/en/rs -I. -O2 -pipe > -march=penryn -fstack-protector-strong -fno-strict-aliasing > -DLOCALE=LANG_en -DLOCALE_DESC="\"en\"" > -DPKGLIBDIR="\"/usr/local/lib/arj\"" -D_UNIX -O2 -pipe -march=penryn > -fstack-protector-strong -fno-strict-aliasing > -ofreebsd13.0/en/rs/tools/crc32.o crc32.c > cc -DLOCALE=LANG_en -DLOCALE_DESC="\"en\"" > -DPKGLIBDIR="\"/usr/local/lib/arj\"" -D_UNIX -O2 -pipe -march=penryn > -fstack-protector-strong -fno-strict-aliasing -fstack-protector-strong > -s gnu/stripgcc.lnk -o freebsd13.0/en/rs/tools/msgbind > ./freebsd13.0/en/rs/tools/filemode.o ./freebsd13.0/en/rs/tools/msgbind.o > ./freebsd13.0/en/rs/tools/arjdata.o ./freebsd13.0/en/rs/tools/crc32.o > ./freebsd13.0/en/rs/tools/msgbind ./resource/resource.txt msg_crp UNIX s > en ./freebsd13.0/en/rs > gmake[3]: *** [GNUmakefile:258: freebsd13.0/en/rs/msg_crp.h] Abort trap > gmake[3]: Leaving directory '/usr/ports/archivers/arj/work/arj-3.10.22' > gmake[2]: *** [GNUmakefile:169: all] Error 2 > gmake[2]: Leaving directory '/usr/ports/archivers/arj/work/arj-3.10.22' > *** Error code 1 > There is an open PR [1] where submitter reports the same issue. I was never able to reproduce it unfortunately. [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235636 -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: arj-3.10.22_6
On 17/01/18 19:00, David Martin wrote: > Hello, > > The port is currently broken. It is attempting to fetch the file > arj_3.10.22-16.debian.tar.xz which is no longer available. It must be > updated to pull arj_3.10.22-17.debian.tar.xz. Fixed. Thanks! -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/openvpn23 tarball size mismatch
On 16/05/17 08:54, Renato Botelho wrote: > Hello Mathias, > > I was trying to get openvpn23 installed from quarterly branch and got > the following error: > > root@buildbot1:/usr/local/poudriere/ports/pfSense_v2_3/security/openvpn23 > # make checksum > ===> License GPLv2 accepted by the user > ===> openvpn23-2.3.15 depends on file: /usr/local/sbin/pkg - found > => openvpn-2.3.15.tar.xz doesn't seem to exist in > /usr/local/poudriere/ports/pfSense_v2_3/distfiles/. > => Attempting to fetch > http://swupdate.openvpn.net/community/releases/openvpn-2.3.15.tar.xz > fetch: > http://swupdate.openvpn.net/community/releases/openvpn-2.3.15.tar.xz: > size mismatch: expected 863384, actual 829240 > => Attempting to fetch > http://build.openvpn.net/downloads/releases/openvpn-2.3.15.tar.xz > fetch: > http://build.openvpn.net/downloads/releases/openvpn-2.3.15.tar.xz: size > mismatch: expected 863384, actual 829240 > => Attempting to fetch > http://distcache.FreeBSD.org/ports-distfiles/openvpn-2.3.15.tar.xz > fetch: > http://distcache.FreeBSD.org/ports-distfiles/openvpn-2.3.15.tar.xz: Not > Found > => Couldn't fetch it - please try to retrieve this > => port manually into /usr/local/poudriere/ports/pfSense_v2_3/distfiles/ > and try again. > *** Error code 1 > > Stop. > make: stopped in /usr/local/poudriere/ports/pfSense_v2_3/security/openvpn23 > Just FYI, I've downloaded current tarball from OpenVPN website and checked it using GPG and it's OK. I'm not sure why they rerolled tarball tough. -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
security/openvpn23 tarball size mismatch
Hello Mathias, I was trying to get openvpn23 installed from quarterly branch and got the following error: root@buildbot1:/usr/local/poudriere/ports/pfSense_v2_3/security/openvpn23 # make checksum ===> License GPLv2 accepted by the user ===> openvpn23-2.3.15 depends on file: /usr/local/sbin/pkg - found => openvpn-2.3.15.tar.xz doesn't seem to exist in /usr/local/poudriere/ports/pfSense_v2_3/distfiles/. => Attempting to fetch http://swupdate.openvpn.net/community/releases/openvpn-2.3.15.tar.xz fetch: http://swupdate.openvpn.net/community/releases/openvpn-2.3.15.tar.xz: size mismatch: expected 863384, actual 829240 => Attempting to fetch http://build.openvpn.net/downloads/releases/openvpn-2.3.15.tar.xz fetch: http://build.openvpn.net/downloads/releases/openvpn-2.3.15.tar.xz: size mismatch: expected 863384, actual 829240 => Attempting to fetch http://distcache.FreeBSD.org/ports-distfiles/openvpn-2.3.15.tar.xz fetch: http://distcache.FreeBSD.org/ports-distfiles/openvpn-2.3.15.tar.xz: Not Found => Couldn't fetch it - please try to retrieve this => port manually into /usr/local/poudriere/ports/pfSense_v2_3/distfiles/ and try again. *** Error code 1 Stop. make: stopped in /usr/local/poudriere/ports/pfSense_v2_3/security/openvpn23 -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: manpath change for ports ?
On 07/03/17 12:24, Diane Bruce wrote: > On Tue, Mar 07, 2017 at 06:29:19AM +, Jan Beich wrote: >> Baptiste Daroussin writes: >> >>> Hi all, >>> >>> I would like to propose a change in the localbase hier for ports >>> >>> I think we should add /usr/local/share/man in the manpath along with at >>> first >>> and maybe instead of in long term. >>> >>> The reason is: >>> - /usr/local/share/man seems more consistent to me with base which have: >>> /usr/share/man >>> - It will remove lots of patches from the ports tree where were we need to >>> patch >>> upstream build system to install in a non usual path. >> Can you also move /usr/local/info to /usr/local/share/info? texinfo is >> gone since 11.0-RELEASE (or r276551) but hier(7) and BSD.usr.dist still >> try to encroach on GNU defaults. > A big yes from me for both of these proposals. > +1 -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Problems are a Curl upgrade on 12.0 current of Sun Oct 2
> On 5 Dec 2016, at 17:21, Ed Schouten wrote: > > Basename@FBSD_1.5 is the new symbol. Did you by any chance downgrade your > system? t happened to me as well. I didn’t downgrade the system but I’ve installed curl package, that was built on a more recent version. After upgrade world to recent -CURRENT it was fixed -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: make makepatch
> On 27 Oct 2016, at 04:20, Kurt Jaeger wrote: > > Hi! > >> # portlint >> WARN: /usr/home/joneum/dev/ports/net/wpa_gui/files/patch-wpa_ctrl.c: >> patch was not generated using ``make makepatch''. It is recommended to >> use ``make makepatch'' when you need to [re-]generate a patch to ensure >> proper patch format. >> 0 fatal errors and 1 warning found. >> >> okay, i use "make makepatch", and copy the files from >> "work/.makepatch-tmp/archived-patches" to the "/files" folder, and start >> portlint. But, the same. >> >> what am i doing wrong? > > make makepatch places the corrected files into files/ and > the prevision version to work/.makepatch-tmp/archived-patches. > > So, I'd suggest: > > make patch > make makepatch > mv work work.old > portlint -AC > > and if portlint is silent, and all the necessary patches are in files/, > you're done. I only suggest to replace ‘make patch’ by: # make extract do-patch There are several ports that changes files using REINPLACE_CMD in post-patch: target, this way you will not run post-patch: and will not risky to end up converting REINPLACE_CMD into static patches. -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Clamd core dumps
Thanks! Please go ahead and commit it. Em 09/08/2016 23:23, "Dima Panov" escreveu: > 10.08.16 0:20, Kubilay Kocak пишет: > > On 9/08/2016 11:07 AM, Dima Panov wrote: > >> 09.08.16 10:05, Doug Hardie пишет: > >>> I just upgraded a mail server from 9.3 to 11.0-BETA4. clamav worked > fine on 9.3. However, after upgrading it and reinstalling the package > clamd core dumps just after reading all the signatures. Ktrace shows > nothing other than the sig 11. I then built clamav from ports so I would > have source. The bt from the core dump shows: > >>> > >>> #0 0x000800f94b09 in cli_printcxxver () from > /usr/local/lib/libclamav.so.7 > >>> #1 0x0008010e7d2b in cli_printcxxver () from > /usr/local/lib/libclamav.so.7 > >>> #2 0x000800d3eee9 in cli_printcxxver () from > /usr/local/lib/libclamav.so.7 > >>> #3 0x000800d5ebd3 in cli_printcxxver () from > /usr/local/lib/libclamav.so.7 > >>> #4 0x000800d5e256 in cli_printcxxver () from > /usr/local/lib/libclamav.so.7 > >>> #5 0x000800d5df16 in cli_printcxxver () from > /usr/local/lib/libclamav.so.7 > >>> #6 0x000800d03283 in cli_printcxxver () from > /usr/local/lib/libclamav.so.7 > >>> #7 0x000800d034a4 in cli_printcxxver () from > /usr/local/lib/libclamav.so.7 > >>> #8 0x000800c118d0 in cli_pcre_scanbuf () from > /usr/local/lib/libclamav.so.7 > >>> #9 0x000800b675e8 in cli_bytecode_prepare2 () from > /usr/local/lib/libclamav.so.7 > >>> #10 0x000800aba3b9 in cl_engine_compile () from > /usr/local/lib/libclamav.so.7 > >>> #11 0x00408fec in main () > >>> > >>> I am going to try rebuilding with symbols. > >>> > >>> Any ideas what is causing this or how to get around it? > >>> > >>> pkg is clamav-milter-0.99.2 > >>> > >> > >> Let me guess. ClamAV was built with LLVM/Jit support? It's broken for > >> now as Clamav can use only LLVM <3.7 and base system provide llvm 3.8. > >> > >> Try to rebuild without LLVM/Jit, this solved crashdumps for me. > >> > >> > > > > Dima, > > > > Should we set BROKEN on OSVERSION > X with that option? > > > > Nope. Right solution is use a proper LLVM from ports instead of bundled > (very limited) to build Jit engine. > > Found it yesterday and filled a PR: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211683 > > Solution is works for me at two mailservers under 11.0-BETA4 and 10.3-REL. > > > CC'ed to: garga@ (maintainer) > > -- > Dima Panov (flu...@freebsd.org) > (X11, KDE, Office)@FreeBSD team > > Facebook: http://www.facebook.com/fluffy.khv > twitter: fluffy_khv | skype: dima.panov | telegram: @dima_panov > IRC: fluffy@EFNet, fluffykhv@FreeNode > > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Drop Maintainership, need help
On Jun 12, 2014, at 17:23, Dennis Herrmann wrote: > > Ahoi, > > I'am very busy since the few month. Unfortunately this will > not be better in the next month. This is the reason why I > can't maintain my ports :(. > > Now I'm looking for some people which take some of my ports > and my open PR explicated Stage PR's. I hope anyone can help > me. > > Current I take the maintainership of this ports: > > astro/libnova > audio/cmus-post.fm > audio/cripple > audio/cutmp3 > audio/last-cmus > audio/mp3burn > audio/ncmpcpp > audio/p5-Audio > audio/p5-Audio-Mixer > audio/snd > audio/solfege > audio/vitunes > audio/xpi-musicpm > comms/ncid > comms/picocom > comms/viewfax > devel/etl > devel/libdsp > devel/nasm > devel/p5-Data-Table > devel/p5-Data-TreeDumper > devel/p5-Date-Simple > devel/p5-Devel-Events > devel/p5-Module-Loaded > devel/rubygem-lockfile > devel/rubygem-trollop > devel/skalibs > devel/synfig > devel/trio > editors/poedit > ftp/ftpsync > ftp/scythia > games/doom-freedoom > games/rubix > games/vitetris > games/zoom > graphics/fotofix > graphics/gocr > graphics/silgraphite > graphics/synfigstudio > irc/anope > irc/miau > irc/py-supybot > irc/py-supybot-plugins > irc/simpleirc > lang/mmix > mail/elmo > mail/elmo-devel > mail/p5-Mail-Ezmlm > math/fxt > misc/hello > net/GeoIP > net/libosip > net/p5-Net-ARP > net/p5-Net-Libdnet > net/p5-XML-Fast > net/radvd > net/rubygem-rubytter > net/vnstat > net/wire > net/wired > net/wired-tracker > net-im/mcabber > net-im/rubygem-termtter > net-im/tkabbur > net-mgmt/cowpatty > net-mgmt/rrdbot > science/clhep > sysutils/fusefs-curlftpfs > sysutils/fusefs-gstfs > sysutils/logtool > sysutils/rubygem-teamocil > sysutils/ttyload > textproc/p5-Tk-XMLViewer > textproc/p5-XML-Parser-Lite-Tree > textproc/rss2html > textproc/rubygem-termcolor > textproc/smu > www/multisort > www/p5-HTML-Template-Associate > www/p5-WWW-FreeProxy > www/p5-WWW-TinySong > www/zerowait-httpd > x11/i3lock > x11/lsw > x11-fm/gentoo > x11-fonts/montecarlo_fonts > x11-toolkits/p5-Tk-FontDialog > x11-wm/antiwm > x11-wm/musca > x11-wm/ratpoison > x11-wm/wmfs > > Thanks > > Regards, > Dennis 'dhn' Herrmann I can take radvd. -- Renato Botelho http://people.freebsd.org/~garga/pubkey.asc signature.asc Description: Message signed with OpenPGP using GPGMail
Re: clamav-0.98.3_2: LibClamAV Warning: Cannot dlopen libclamunrar_iface...
On Thursday, May 15, 2014 04:23:28 PM Shawn Webb wrote: > On Thu, May 15, 2014 at 3:59 PM, Dr. Peter Voigt wrote: > > After the upgrade to clamav-0.98.3_2 I am obtaining following error on > > every start of ClamAV: > > > > # service clamav-clamd start > > Starting clamav_clamd. > > LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - > > unrar support unavailable > > > > ClamAV, however, seems to work correctly. Is this a known issue? > > > > I am on 10.0-RELEASE-p3 amd64. > > > > Regards, > > Peter > > Hey Peter, > > This can be fixed by applying this patch: > https://github.com/vrtadmin/clamav-devel/commit/d17ee49f75e23b43fadf745c27dc > 4dd16ee372e5 > > CC'd on this email is the ports maintainer for ClamAV. Fixed. Thanks! -- Renato Botelho GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc ___ 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: Unable to update to clamav 0.98.3
On Tuesday, May 13, 2014 05:55:04 AM Jerry wrote:
> On Mon, 12 May 2014 11:03:50 -0300, Renato Botelho stated:
> > On Thursday, May 08, 2014 04:35:11 PM Jerry wrote:
> > > FreeBSD 10.0-RELEASE
> > >
> > > I am unable to update to "clamav-0.98.3". It terminates with the
> > > following error message:
> > >
> > > clamd.c:335:59: warning: format specifies type 'unsigned int' but the
> > > argument has type 'off_t' (aka 'long') [-Wformat] logg("#Log file size
> > > limited to %u bytes.\n", logg_size); ~~^ %ld
> > > 1 warning generated.
> > >
> > > CC tcpserver.o
> > > CC localserver.o
> > > CC session.o
> > > CC thrmgr.o
> > > CC server-th.o
> > > CC scanner.o
> > >
> > > scanner.c:105:25: warning: passing 'const unsigned char *' to parameter
> > > of type 'const char *' converts between pointers to integer types with
> > > different sign [-Wpointer-sign]
> > >
> > > strncpy(c->virhash, md5, 32);
> > >
> > > ^~~
> > >
> > > /usr/include/string.h:101:57: note: passing argument to parameter here
> > > char*strncpy(char * __restrict, const char * __restrict, size_t);
> > >
> > >^
> > >
> > > 1 warning generated.
> > >
> > > CC others.o
> > > CC fan.o
> > > CCLD clamd
> > >
> > > gmake[3]: Leaving directory
> > > `/usr/ports/security/clamav/work/clamav-0.98.3/clamd' Making all in
> > > clamdscan
> > > gmake[3]: Entering directory
> > > `/usr/ports/security/clamav/work/clamav-0.98.3/clamdscan' CC
> > > output.o CC optparser.o
> > >
> > > CC misc.o
> > > CC getopt.o
> > > CC actions.o
> > > CC clamdcom.o
> > >
> > > ../shared/clamdcom.c:42:13: warning: implicit declaration of function
> > > 'send' is invalid in C99 [-Wimplicit-function-declaration] int sent =
> > > send(sockd, line, len, 0);
> > >
> > >^
> > >
> > > ../shared/clamdcom.c:75:13: warning: implicit declaration of function
> > > 'recv' is invalid in C99 [-Wimplicit-function-declaration] s->r =
> > > recv(s->sockd, s->cur, sizeof(s->buf) - (s->cur - s->buf), 0); ^
> > > 2 warnings generated.
> > >
> > > CC clamdscan.o
> > > CC proto.o
> > > CC client.o
> > > CCLD clamdscan
> > >
> > > gmake[3]: Leaving directory
> > > `/usr/ports/security/clamav/work/clamav-0.98.3/clamdscan' Making all in
> > > freshclam
> > > gmake[3]: Entering directory
> > > `/usr/ports/security/clamav/work/clamav-0.98.3/freshclam' CC
> > > output.o CC optparser.o
> > >
> > > CC getopt.o
> > > CC misc.o
> > > CC cdiff.o
> > > CC tar.o
> > > CC clamdcom.o
> > >
> > > ../shared/clamdcom.c:42:13: warning: implicit declaration of function
> > > 'send' is invalid in C99 [-Wimplicit-function-declaration] int sent =
> > > send(sockd, line, len, 0);
> > >
> > >^
> > >
> > > ../shared/clamdcom.c:75:13: warning: implicit declaration of function
> > > 'recv' is invalid in C99 [-Wimplicit-function-declaration] s->r =
> > > recv(s->sockd, s->cur, sizeof(s->buf) - (s->cur - s->buf), 0); ^
> > > 2 warnings generated.
> > >
> > > CC freshclam.o
> > >
> > > In file included from freshclam.c:57:
> > > In file included from ../libclamav/others.h:21:
> > > In file included from ../libclamav/matcher.h:28:
> > > ../libclamav/others.h:154:5: error: unknown type name 'stats_section_t'
> > >
> > > stats_section_t *sections;
> > > ^
> > >
> > > ../libclamav/others.h:323:5: error: unknown type name
> > > 'clcb_stats_add_sample' clcb_stats_add_sample cb_stats_add_sample;
> > >
> > > ^
> > >
> > > ../libclamav/others.h:324:5: error: unknown type name
> > > 'clcb_stats_remove_sample' clcb_stats_remove_sample
> > > cb_stats_remove_sam
Re: Unable to update to clamav 0.98.3
lcb_stats_decrement_count > cb_stats_decrement_count; > ^ > ../libclamav/others.h:383:5: error: unknown type name 'clcb_stats_submit' > clcb_stats_submit cb_stats_submit; > ^ > ../libclamav/others.h:384:5: error: unknown type name 'clcb_stats_flush' > clcb_stats_flush cb_stats_flush; > ^ > ../libclamav/others.h:385:5: error: unknown type name 'clcb_stats_get_num' > clcb_stats_get_num cb_stats_get_num; > ^ > ../libclamav/others.h:386:5: error: unknown type name 'clcb_stats_get_size' > clcb_stats_get_size cb_stats_get_size; > ^ > ../libclamav/others.h:387:5: error: unknown type name > 'clcb_stats_get_hostid' clcb_stats_get_hostid cb_stats_get_hostid; > ^ > freshclam.c:762:5: warning: implicit declaration of function > 'cl_engine_stats_enable' is invalid in C99 > [-Wimplicit-function-declaration] > cl_engine_stats_enable(engine); > ^ > freshclam.c:781:9: warning: implicit declaration of function > 'cl_engine_set_clcb_stats_get_hostid' is invalid in C99 > [-Wimplicit-function-declaration] > cl_engine_set_clcb_stats_get_hostid(engine, NULL); > ^ > freshclam.c:786:35: error: use of undeclared identifier > 'CL_ENGINE_STATS_TIMEOUT'; did you mean 'CL_ENGINE_BYTECODE_TIMEOUT'? > cl_engine_set_num(engine, CL_ENGINE_STATS_TIMEOUT, optget(opts, > "StatsTimeout")->numarg); ^~~ > CL_ENGINE_BYTECODE_TIMEOUT > /usr/local/include/clamav.h:192:5: note: 'CL_ENGINE_BYTECODE_TIMEOUT' > declared here CL_ENGINE_BYTECODE_TIMEOUT, /* uint32_t */ > ^ > 2 warnings and 18 errors generated. > gmake[3]: *** [freshclam.o] Error 1 > gmake[3]: Leaving directory > `/usr/ports/security/clamav/work/clamav-0.98.3/freshclam' gmake[2]: *** > [all-recursive] Error 1 > gmake[2]: Leaving directory `/usr/ports/security/clamav/work/clamav-0.98.3' > gmake[1]: *** [all] Error 2 > gmake[1]: Leaving directory `/usr/ports/security/clamav/work/clamav-0.98.3' > *** Error code 1 > > Stop. > make: stopped in /usr/ports/security/clamav > > The full build log is available here: > http://www/seibercom.net/logs/clamav.txt Hello, I was not able to reproduce the issue, but, I restored a patch that I accidentally removed during the update process. Could you please try 0.98.3_1 and check if it helps? Regards -- Renato Botelho GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc ___ 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: libiconv problem on dansguardian-(devel)
On 17-10-2013 10:02, Boris Samorodov wrote:
> 17.10.2013 16:56, Renato Botelho пишет:
>> On 17-10-2013 09:38, Boris Samorodov wrote:
>>> 17.10.2013 15:19, Marko Cupać пишет:
>>>
>>>> I cannot compile either of the two with NTLM option enabled:
>>>> www/dansguardian
>>>> www/dansguardian-devel
>>>>
>>>> This is on 9.2-RELEASE i386.
>>>>
>>>> Both fail with the same error message:
>>>>
>>>> error message
>>>> checking for NTLM support... yes
>>>> checking for iconv... no
>>>> no
>>>> checking for iconv in -liconv... no
>>>> no
>>>> checking for libiconv in -liconv... no
>>>> configure: error: no native or standard library iconv function found!
>>>> (needed by NTLM plugin - try again with "--with-libiconv"?)
>>>> ===> Script "configure" failed unexpectedly.
>>>> error message
>>>>
>>>> Any idea how to fix this?
>>>
>>> I think that the right way is to include iconv to Uses unconditionally
>>> (keeping in mind that --with-libiconv=${LOCALBASE} also was used
>>> unconditionally before switching to Uses/iconv.mk). The same for
>>> www/dansguardian-devel.
>>>
>>> The proposed patch attached.
>>
>> Thanks Boris, feel free to commit it please.
>
> Ok, I have a question though. Should a PORTREVISION be bumped?
> The package for 11-x and 10-x won't change, however for 9.x and 8.x
> would. I assume that to be on a safe side it's better to bump it.
> What do you think? Thanks!
I agree with bumping, sounds more safe.
--
Renato Botelho
GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc
signature.asc
Description: OpenPGP digital signature
Re: libiconv problem on dansguardian-(devel)
On 17-10-2013 09:38, Boris Samorodov wrote:
> 17.10.2013 15:19, Marko Cupać пишет:
>
>> I cannot compile either of the two with NTLM option enabled:
>> www/dansguardian
>> www/dansguardian-devel
>>
>> This is on 9.2-RELEASE i386.
>>
>> Both fail with the same error message:
>>
>> error message
>> checking for NTLM support... yes
>> checking for iconv... no
>> no
>> checking for iconv in -liconv... no
>> no
>> checking for libiconv in -liconv... no
>> configure: error: no native or standard library iconv function found!
>> (needed by NTLM plugin - try again with "--with-libiconv"?)
>> ===> Script "configure" failed unexpectedly.
>> error message
>>
>> Any idea how to fix this?
>
> I think that the right way is to include iconv to Uses unconditionally
> (keeping in mind that --with-libiconv=${LOCALBASE} also was used
> unconditionally before switching to Uses/iconv.mk). The same for
> www/dansguardian-devel.
>
> The proposed patch attached.
Thanks Boris, feel free to commit it please.
--
Renato Botelho
GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc
signature.asc
Description: OpenPGP digital signature
Re: devel/lua-sysctl broken with clang (patch)
On Wed, Jan 23, 2013 at 12:12:00PM +, Matt Burke wrote: > ===> Building for lua-sysctl-0.2 > install -m 755 -d sysctl > cc -shared -soname lua_sysctl -O2 -pipe -fno-omit-frame-pointer > -fno-strict-aliasing -fno-omit-frame-pointer -Wall -Wextra -fPIC > `pkg-config --cflags lua-5.1` -o sysctl/core.so src/lua_sysctl.c > cc: error: no such file or directory: 'lua_sysctl' > *** [sysctl/core.so] Error code 1 > > Stop in /usr/ports/devel/lua-sysctl/work/lua-syscl-0.2. > *** [do-build] Error code 1 Committed. Thanks! -- Renato Botelho GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc ___ 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: Error building pcre on 9.0
On Wed, Aug 15, 2012 at 5:36 PM, Matthias Andree wrote: > Am 15.08.2012 22:18, schrieb Renato Botelho: >> I was updating a 9.0-RELEASE-p3 i386 system's ports and got the >> following error when building pcre 8.31: >> >> CXXpcrecpp.lo >> In file included from /usr/include/c++/4.2/bits/c++allocator.h:39, >> from /usr/include/c++/4.2/bits/allocator.h:53, >> from /usr/include/c++/4.2/memory:54, >> from /usr/include/c++/4.2/string:48, >> from pcrecpp.cc:43: >> /usr/include/c++/4.2/ext/new_allocator.h:37:15: error: new: No such >> file or directory >> In file included from /usr/include/c++/4.2/string:48, >> from pcrecpp.cc:43: >> /usr/include/c++/4.2/memory: In function 'std::pair<_Tp*, int> >> std::__get_temporary_buffer(ptrdiff_t, _Tp*)': >> /usr/include/c++/4.2/memory:83: error: 'nothrow' was not declared in this >> scope >> /usr/include/c++/4.2/memory: In function 'void >> std::return_temporary_buffer(_Tp*)': >> /usr/include/c++/4.2/memory:123: error: 'nothrow' was not declared in this >> scope >> *** Error code 1 > > Renato, > > works for me. > > Your system appears to have a broken gcc installation. > It lacks /usr/include/c++/4.2/new, an include file dated Dec 4 2011 and > sized 4041 bytes on my 9.0-RELEASE-p3 i386 system, which would also > explain the nothrow-related errors. > > Anything in [/usr]/lost+found by chance? Thanks for pointing that out. I copied this file from other server and now i'm building world to be sure everything is in place. -- Renato Botelho ___ 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"
Error building pcre on 9.0
I was updating a 9.0-RELEASE-p3 i386 system's ports and got the following error when building pcre 8.31: CXXpcrecpp.lo In file included from /usr/include/c++/4.2/bits/c++allocator.h:39, from /usr/include/c++/4.2/bits/allocator.h:53, from /usr/include/c++/4.2/memory:54, from /usr/include/c++/4.2/string:48, from pcrecpp.cc:43: /usr/include/c++/4.2/ext/new_allocator.h:37:15: error: new: No such file or directory In file included from /usr/include/c++/4.2/string:48, from pcrecpp.cc:43: /usr/include/c++/4.2/memory: In function 'std::pair<_Tp*, int> std::__get_temporary_buffer(ptrdiff_t, _Tp*)': /usr/include/c++/4.2/memory:83: error: 'nothrow' was not declared in this scope /usr/include/c++/4.2/memory: In function 'void std::return_temporary_buffer(_Tp*)': /usr/include/c++/4.2/memory:123: error: 'nothrow' was not declared in this scope *** Error code 1 Stop in /usr/ports/devel/pcre/work/pcre-8.31. *** Error code 1 Stop in /usr/ports/devel/pcre/work/pcre-8.31. *** Error code 1 Stop in /usr/ports/devel/pcre. *** Error code 1 Stop in /usr/ports/devel/pcre. Any thoughts? Best regards -- Renato Botelho ___ 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: [HEADSUP][CFT] pkgng beta1^6 is out
from pkg_manifest.c:5: /usr/include/xlocale/_ctype.h:109: warning: no previous prototype for 'isalnum_l' /usr/include/xlocale/_ctype.h:110: warning: no previous prototype for 'isalpha_l' /usr/include/xlocale/_ctype.h:111: warning: no previous prototype for 'isblank_l' /usr/include/xlocale/_ctype.h:112: warning: no previous prototype for 'iscntrl_l' /usr/include/xlocale/_ctype.h:113: warning: no previous prototype for 'isdigit_l' /usr/include/xlocale/_ctype.h:114: warning: no previous prototype for 'isgraph_l' /usr/include/xlocale/_ctype.h:115: warning: no previous prototype for 'ishexnumber_l' /usr/include/xlocale/_ctype.h:116: warning: no previous prototype for 'isideogram_l' /usr/include/xlocale/_ctype.h:117: warning: no previous prototype for 'islower_l' /usr/include/xlocale/_ctype.h:118: warning: no previous prototype for 'isnumber_l' /usr/include/xlocale/_ctype.h:119: warning: no previous prototype for 'isphonogram_l' /usr/include/xlocale/_ctype.h:120: warning: no previous prototype for 'isprint_l' /usr/include/xlocale/_ctype.h:121: warning: no previous prototype for 'ispunct_l' /usr/include/xlocale/_ctype.h:122: warning: no previous prototype for 'isrune_l' /usr/include/xlocale/_ctype.h:123: warning: no previous prototype for 'isspace_l' /usr/include/xlocale/_ctype.h:124: warning: no previous prototype for 'isspecial_l' /usr/include/xlocale/_ctype.h:125: warning: no previous prototype for 'isupper_l' /usr/include/xlocale/_ctype.h:126: warning: no previous prototype for 'isxdigit_l' /usr/include/xlocale/_ctype.h:164: warning: no previous prototype for 'digittoint_l' /usr/include/xlocale/_ctype.h:167: warning: no previous prototype for 'tolower_l' /usr/include/xlocale/_ctype.h:174: warning: no previous prototype for 'toupper_l' In file included from /usr/include/wctype.h:93, from pkg_manifest.c:6: /usr/include/xlocale/_ctype.h:48: warning: redundant redeclaration of '___runetype_l' /usr/include/xlocale/_ctype.h:48: warning: previous declaration of '___runetype_l' was here /usr/include/xlocale/_ctype.h:49: warning: redundant redeclaration of '___tolower_l' /usr/include/xlocale/_ctype.h:49: warning: previous declaration of '___tolower_l' was here /usr/include/xlocale/_ctype.h:50: warning: redundant redeclaration of '___toupper_l' /usr/include/xlocale/_ctype.h:50: warning: previous declaration of '___toupper_l' was here /usr/include/xlocale/_ctype.h:51: warning: redundant redeclaration of '__runes_for_locale' /usr/include/xlocale/_ctype.h:51: warning: previous declaration of '__runes_for_locale' was here /usr/include/xlocale/_ctype.h:109: warning: no previous prototype for 'iswalnum_l' /usr/include/xlocale/_ctype.h:110: warning: no previous prototype for 'iswalpha_l' /usr/include/xlocale/_ctype.h:111: warning: no previous prototype for 'iswblank_l' /usr/include/xlocale/_ctype.h:112: warning: no previous prototype for 'iswcntrl_l' /usr/include/xlocale/_ctype.h:113: warning: no previous prototype for 'iswdigit_l' /usr/include/xlocale/_ctype.h:114: warning: no previous prototype for 'iswgraph_l' /usr/include/xlocale/_ctype.h:115: warning: no previous prototype for 'iswhexnumber_l' /usr/include/xlocale/_ctype.h:116: warning: no previous prototype for 'iswideogram_l' /usr/include/xlocale/_ctype.h:117: warning: no previous prototype for 'iswlower_l' /usr/include/xlocale/_ctype.h:118: warning: no previous prototype for 'iswnumber_l' /usr/include/xlocale/_ctype.h:119: warning: no previous prototype for 'iswphonogram_l' /usr/include/xlocale/_ctype.h:120: warning: no previous prototype for 'iswprint_l' /usr/include/xlocale/_ctype.h:121: warning: no previous prototype for 'iswpunct_l' /usr/include/xlocale/_ctype.h:122: warning: no previous prototype for 'iswrune_l' /usr/include/xlocale/_ctype.h:123: warning: no previous prototype for 'iswspace_l' /usr/include/xlocale/_ctype.h:124: warning: no previous prototype for 'iswspecial_l' /usr/include/xlocale/_ctype.h:125: warning: no previous prototype for 'iswupper_l' /usr/include/xlocale/_ctype.h:126: warning: no previous prototype for 'iswxdigit_l' /usr/include/xlocale/_ctype.h:131: warning: no previous prototype for 'towlower_l' /usr/include/xlocale/_ctype.h:138: warning: no previous prototype for 'towupper_l' /usr/include/xlocale/_ctype.h:146: warning: no previous prototype for '__wcwidth_l' *** [pkg_manifest.o] Error code 1 Stop in /usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta6/libpkg. *** [all] Error code 1 Stop in /usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta6. *** [do-build] Error code 1 Stop in /usr/ports/ports-mgmt/pkg. [1]97410 exit 1 make -C /usr/ports/ports-mgmt/pkg install clean make -C /usr/ports/ports-mgmt/pkg install clean 33.86s user 1.48s system 61% cpu 57.212 total -- Renato Botelho ___ 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: [HEADSUP][CFT] pkgng beta1^6 is out
FreeBSD murphys.ramenzoni.com.br 10.0-CURRENT FreeBSD 10.0-CURRENT #4 r231691: Tue Feb 14 15:51:35 BRST 2012 r...@murphys.ramenzoni.com.br:/usr/obj/usr/src/sys/MURPHYS i386 On Wed, Feb 15, 2012 at 8:57 PM, Baptiste Daroussin wrote: > On Wed, Feb 15, 2012 at 08:53:42PM -0200, Renato Botelho wrote: >> On Wed, Feb 15, 2012 at 3:50 PM, Baptiste Daroussin wrote: >> > beta6 is now out with the following changes: >> > >> > * pkg register: now run inside a transaction, this speeds up things a lot >> > (thanks avg) >> > * pkg version: -v now print name-version to match behaviour of legacy >> > pkg_version >> > * pkg register: fix flatsize calculation >> > * new pkg-updating(1) man page (thanks beat) >> > >> > if you are upgrading from previous version you migh discover the weird >> > value the >> > the disk space saved or required for some operation, this is just because >> > a bug >> > in previous version was always calculating each package flatsize as 0 B, >> > this is >> > now fixed. >> >> Hello Bapt, >> >> I tried to build it on a recent current and got these errors: >> >> FreeBSD murphys.ramenzoni.com.br 10.0-CURRENT FreeBSD 10.0-CURRENT #4 >> r231691: Tue Feb 14 15:51:35 BRST 2012 >> r...@murphys.ramenzoni.com.br:/usr/obj/usr/src/sys/MURPHYS i386 >> >> root@murphys:/root# make -C /usr/ports/ports-mgmt/pkg install clean >> ===> License BSD accepted by the user >> => pkg-1.0-beta6.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/. >> => Attempting to fetch >> ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/portmgr/pkg-1.0-beta6.tar.bz2 >> pkg-1.0-beta6.tar.bz2 100% of 1434 kB 108 kBps >> 00m00s >> ===> Extracting for pkg-1.0.b6 >> => SHA256 Checksum OK for pkg-1.0-beta6.tar.bz2. >> ===> Patching for pkg-1.0.b6 >> ===> Configuring for pkg-1.0.b6 >> ===> FreeBSD 10 autotools fix applied to >> /usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta6/external/libyaml/aclocal.m4 >> ===> FreeBSD 10 autotools fix applied to >> /usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta6/external/libyaml/configure >> ===> Building for pkg-1.0.b6 >> ===> external (all) >> ===> external/sqlite (all) >> Warning: Object directory not changed from original >> /usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta6/external/sqlite >> cc -O2 -pipe -fno-strict-aliasing -fPIC -DSQLITE_OMIT_AUTOVACUUM >> -DSQLITE_OMIT_BLOB_LITERAL -DSQLITE_OMIT_COMPLETE >> -DSQLITE_OMIT_DECLTYPE -DSQLITE_OMIT_DEPRECATED >> -DSQLITE_OMIT_EXPLAIN -DSQLITE_OMIT_GET_TABLE >> -DSQLITE_OMIT_LOAD_EXTENSION -DSQLITE_OMIT_PROGRESS_CALLBACK >> -DSQLITE_OMIT_TCL_VARIABLE -DSQLITE_OMIT_UTF16 -DSQLITE_OMIT_CAT >> -DSQLITE_OMIT_CHECK -DSQLITE_OMIT_AUTOINIT >> -DSQLITE_OMIT_COMPILEOPTION_DIAGS -DSQLITE_OMIT_INTEGRITY_CHECK >> -DSQLITE_OMIT_BUILTIN_TEST -DSQLITE_OMIT_SHARED_CACHE -DUSE_PREAD >> -DSQLITE_THREADSAFE=1 -DSQLITE_TEMP_STORE=3 -DNDEBUG -std=gnu99 >> -fstack-protector -Wsystem-headers -Werror -Wno-pointer-sign >> -Wformat=2 -Wno-format-extra-args -Werror -c sqlite3.c -o sqlite3.o >> building static sqlite3 library >> ranlib libsqlite3.a >> ===> external/libyaml (all) >> Warning: Object directory not changed from original >> /usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta6/external/libyaml >> cc -O2 -pipe -fno-strict-aliasing -fPIC >> -I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta6/external/libyaml/include >> -I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta6/external/libyaml >> -DHAVE_CONFIG_H -std=gnu99 -fstack-protector -Wsystem-headers -Werror >> -Wno-pointer-sign -c >> /usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta6/external/libyaml/src/api.c >> -o api.o >> cc -O2 -pipe -fno-strict-aliasing -fPIC >> -I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta6/external/libyaml/include >> -I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta6/external/libyaml >> -DHAVE_CONFIG_H -std=gnu99 -fstack-protector -Wsystem-headers -Werror >> -Wno-pointer-sign -c >> /usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta6/external/libyaml/src/dumper.c >> -o dumper.o >> cc -O2 -pipe -fno-strict-aliasing -fPIC >> -I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta6/external/libyaml/include >> -I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta6/external/libyaml >> -DHAVE_CONFIG_H -std=gnu99 -fstack-protector -Wsystem-headers -Werror >> -Wno-pointer-sign -c >> /usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta6/external/libyaml/src/emitter.c >> -o emitter.o >> cc -O2 -pipe -fno-str
Re: clamav size mismatch: expected 45793424, actual 45793398
On Tue, Oct 18, 2011 at 11:35:21PM -0700, Doug Barton wrote: > Any ideas? :) Updated, take a look at commit message. Thanks for reporting -- Renato Botelho GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc "Get back to your stations!" "We're beaming down to the planet, sir." -- Kirk and Mr. Leslie, "This Side of Paradise", stardate 3417.3 pgpgJ67HDmSWU.pgp Description: PGP signature
Re: Fwd: FreeBSD ports you maintain which are out of date
-+-+ > > www/mhonarc | 2.6.16 | 2.6.18 > > +-+ > > www/middleman | 1.9.1 | 2.0.1 > > +-+ > > www/openvrml| 0.18.6 | 0.18.8 > > +-+ > > www/phpwiki | 1.2.10 | 1.2.11 > > +-+ > > www/plugger | 5.1.3 | 5.1.5 > > +-+ > > www/py-webhelpers | 1.2 | 1.3 > > +-+ > > www/resin3 | 3.1.9 | 3.2.1 > > +-+ > > www/rt36| 3.6.7 | 3.6.11 > > +-+ > > www/screem | 0.16.1 | 0.17.1 > > +-+ > > www/srg | 1.1 | 1.3.6 > > +-+ > > www/tikiwiki| 3.1 | 4.3 > > +-+ > > www/twiki | 4.2.4 | 5.0.2 > > +-+ > > www/twiki-TopicVarsPlugin | 0.0.16417b | > > 0.0.16417 > > +-+ > > www/udmsearch | 3.1.5 | 3.1.7 > > +-+ > > www/wacko | 4 | 4.2 > > +-+ > > www/wiliki | 0.6.1 | 0.6.2 > > +-+ > > www/xist| 3.17.3 | 3.23 > > +-+ > > www/zope-zmysqlda | 2.0.8 | 3.1.1 > > +-+ > > x11/libsynaptics| 0.14.6b | 0.14.6c > > +-+ > > x11/trayer | 1.0 | 1.1.1 > > +-+ > > x11-clocks/gdesklets-clock | 0.32| 0.50 > > +-+ > > x11-fm/dolphin | 0.8.2 | 0.8.5 > > +-+ > > x11-fm/filerunner | 10.12.28.23 | > > 11.2.20.13 > > +-----+-------- > > x11-fm/krusader | 1.90.0 | 2.0.0 > > +-+ > > x11-themes/kde-style-polyester | 1.0.4 | 2.0.0 > > --
Re: [CFT] cpu stresser^W libreoffice 3.3.0 final
On Wed, Feb 2, 2011 at 8:20 AM, Baptiste Daroussin wrote: > 2011/2/2 Sam Fourman Jr. : >> >>> nice thank you very much for the tests now it is in the ports tree. >>> >> >> >> >> I am using FreeBSD 9-CURRENT amd64 and a fresh ports tree >> my build is failing, what can i do? >> >> >> >> >> >> >> sw deliver >> Module 'sw' delivered successfully. 0 files copied, 281 files unchanged >> >> --- >> Oh dear - something failed during the build - sorry ! >> For more help with debugging build errors, please see the section in: >> http://wiki.documentfoundation.org/Development >> >> internal build errors: >> >> ERROR: error 65280 occurred while making >> /usr/ports/editors/libreoffice/work/libreoffice-build-3.3.0.4/build/libreoffice/sdext/source/presenter >> ERROR: error 65280 occurred while making >> /usr/ports/editors/libreoffice/work/libreoffice-build-3.3.0.4/build/libreoffice/lingucomponent/source/languageguessing >> >> it seems you are using a threaded build, which means that the >> actual compile error is probably hidden far above, and could be >> inside any of these other modules: >> lingucomponent >> please re-run build inside each one to isolate the problem. >> --- >> >> /usr/local/bin/bash >> cd >> /usr/ports/editors/libreoffice/work/libreoffice-build-3.3.0.4/build/libreoffice >> source ./FreeBSDAMDEnv.Set.sh >> cd sdext >> build >> >> when the problem is isolated and fixed exit and re-run 'make' from the >> top-level >> sometimes (sadly) it is necessary to rm -Rf unxfbsdx.pro in a module. >> gmake: *** [all] Error 1 >> Sam# >> >> -- >> >> Sam Fourman Jr. >> Fourman Networks >> http://www.fourmannetworks.com >> > your built is failing because you ran it twice. > > make can't be run twice you should make clean before > build/libreoffice/sdext/unxfbsdx.pro needs to be deleted before a > second run We could hack this removing this diredctory (if it exists) during pre-build. I know it's not beaultiful, but at least it works. -- Renato Botelho ___ 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: x11-wm/awesome fail to start
On Tue, Feb 1, 2011 at 11:11 PM, Joseph Olatt wrote: > Hi, > > I'm having trouble getting x11-wm/awesome (3.4.9) to start up. I'm > getting the following error on start up. > > W: awesome: image_new_from_file:288: cannot load image > /usr/local/share/awesome/icons/awesome16.png: unknown error, that's > really bad > /usr/local/share/awesome/lib/awful/menu.lua:221: attempt to compare > number with nil > W: awesome: image_new_from_file:288: cannot load image > /usr/local/share/awesome/icons/awesome16.png: unknown error, that's > really bad > /usr/local/share/awesome/lib/awful/menu.lua:221: attempt to compare > number with nil > E: awesome: main:505: couldn't find any rc file > > > > I have the rc.lua files at: > > joji@mint> ls -l ~/.config/awesome/rc.lua > -rw-r--r-- 1 joji joji 13802 Feb 1 18:19 /home/joji/.config/awesome/rc.lua > > > [~] > joji@mint> ls -l /usr/local/etc/xdg/awesome/rc.lua > -rw-r--r-- 1 root wheel 13802 Feb 1 18:54 > /usr/local/etc/xdg/awesome/rc.lua > > > > Anybody else have these problems. I have another machine running awesome > 3.4.8 and that is running fine. Have you tried to rename ~/.config/awesome and start it with default configuration? -- Renato Botelho ___ 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: clamav makefile patch
On Fri, Jan 07, 2011 at 01:59:25PM +, Anton Shterenlikht wrote:
> clamav fails configure on ia64 portscluster because
> LLVM is included in default options:
>
> from
> http://pointyhat.freebsd.org/errorlogs/ia64-errorlogs/e.8.20101230091827/clamav-0.96.5_1.log
>
> configure: error: Failed to configure LLVM, and LLVM was explicitly requested
>
> With this patch it builds fine on my ia64 box.
>
>
> --- Makefile 2010-12-16 17:43:46.0 +
> +++ Makefile.new 2011-01-07 13:52:26.0 +
> @@ -140,7 +140,7 @@
> CONFIGURE_ARGS+=--without-iconv
> .endif
>
> -.if defined(WITH_LLVM) && ${ARCH} != "sparc64"
> +.if defined(WITH_LLVM) && ${ARCH} != "sparc64" && ${ARCH} != "ia64"
> CONFIGURE_ARGS+=--enable-llvm
> USE_GMAKE= yes
> . if defined(WITH_TESTS)
>
>
> However, LLVM probably doesn't build on PPC either, so
> it might be better to use something like
>
> .if defined(WITH_LLVM) && ${ARCH} == "i386" | ${ARCH} == "amd64"
I've committed this change, thanks!
--
Renato Botelho
GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc
This fortune intentionally not included.
pgpj7oma5TfTR.pgp
Description: PGP signature
Re: comms/spandsp compile failure on upgrade
On Tue, Aug 31, 2010 at 7:13 PM, David Southwell wrote: > > Hi > > On amd64 freebsd 7.1 Strange, i tested it on 7.2-RELEASE amd64 and it built without any problem. All your other ports are up-to-date? -- Renato Botelho ___ 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"
[CFT]: Compat7x 7.3
It's better later than never. After a long time i found time to update compat7x port to 7.3-RELEASE. I would like to ask you to test it and let me know if you find any problems. Thanks -- Renato Botelho compat7x-7.3.diff Description: Binary data ___ 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: pure-ftpd 1.0.29: add support for various unofficial macros
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jul 12, 2010 at 11:25:41AM +0700, Edho P Arief wrote: > Please add support for unofficial macros (but exists in official > source) available in pure-ftpd. At least the macros included in > following patch enable operations commonly allowed in other ftp > daemons (resume, delete and rename support for anonymous user). There > are some more macros but I think these three are the most useful. Committed. Thanks! - -- Renato Botelho GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc A strong conviction that something must be done is the parent of many bad measures. -- Daniel Webster -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.15 (FreeBSD) iEYEARECAAYFAkw69kgACgkQ6CRbiSJE7anXWgCgrWa86kzgsUkeULx51q9QHFaK aDgAn1pKai8r3J9m8TP/7TRaT1OWOx4H =4mYM -END PGP SIGNATURE- ___ 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: Give freeze a chance
On Mon, May 17, 2010 at 5:29 PM, Thomas Abthorpe wrote: > The next wave of the challenge, fear, there is one more already > composed to be released with 8.1! > > -- > > Give Freeze a chance > with apologies to John Lennon et al > > Ev'rybody's talkin' 'bout > portism, srcism, docism, cvsism, svnism, tagism > This-ism, that-ism, ism ism ism > All we are saying is give freeze a chance > All we are saying is give freeze a chance > > C'mon > Ev'rybody's talkin' 'bout > re@, core@, doceng@, donations@, secteam@, > marketing@, portmgr@, vendor-relations@ > All we are saying is give freeze a chance > All we are saying is give freeze a chance > > Let me tell you now > Ev'rybody's talkin' 'bout > Revolution, evolution, i18n, l10n, documentation, > Integration, administration, applications, congratulations > All we are saying is give freeze a chance > All we are saying is give freeze a chance > > Ev'rybody's talkin' 'bout > Erwin Lansing, Mark Linimon, Martin Wilke, > Pav Lucistnik, Florent Thoumie, Ion-Mihai Tetcu, > Kris Kennaway, Joe Marcus Clarke, Thomas Abthorpe too > All we are saying is give freeze a chance > All we are saying is give freeze a chance Nice, it makes me remember the old "Breaking the Ports" song... http://www.mail-archive.com/freebsd-ports@freebsd.org/msg02907.html -- Renato Botelho ___ 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: update compat7x to 7.3 libs
On Tue, May 11, 2010 at 6:58 AM, pluknet wrote: > Hi. > > Is there todo to update misc/compat7x port to 7.3 libraries? > Usually update comes in several days/weeks after release. ccing the list now My fault, i completely forgot about this update, i'll start to work on this ASAP -- Renato Botelho ___ 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: FreeBSD Port: clamav-0.95.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Apr 05, 2010 at 01:09:18PM +0300, admin wrote: > Hi > Please update ports clamav > Local version: 0.95.3 Recommended version: 0.96 > --- Clamav 0.96 has API/ABI changes, and because of it i need to test all dependant ports before commit. I'm working on it. - -- Renato Botelho GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc Laetrile is the pits. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAku5xRkACgkQ6CRbiSJE7akcOQCfcBQqu1qeW6JjYivS5apkXrto 07YAnAwaW1JH13hpVvrtnI3MeRNSOo5l =SgDb -END PGP SIGNATURE- ___ 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: New portmgr secretary: Thomas Abthorpe
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Mar 18, 2010 at 05:02:01PM +0100, Erwin Lansing wrote: > On behalf of portmgr, I am pleased to announce that portmgr has found > a new secretary: Thomas Abthorpe. Thomas has been a FreeBSD ports committer > since 2007 and has made more than 1000 commits since. He has previously > served on the ports-security team and is currently a member of the KDE > and donation teams. He has also mentored several new ports committers > over the years. > > In his role as portmgr secretary, Thomas will help portmgr keep track of > ongoing issues, keeps the portmgr, and other bookkeeping work like > organizing votes and stay in touch with other FreeBSD teams. > > Please welcome him onboard! Congratulations Thomas and Thanks Erwin for all the work in last years. - -- Renato Botelho GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc To be is to be related. -- C. J. Keyser -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkuiVCUACgkQ6CRbiSJE7anr5wCeLS9YAMIV+SE4YEso5S5K3UhA 6hYAoI5qwV5tihC6UxVPkzSDUesy1DgE =sp/n -END PGP SIGNATURE- ___ 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: FreeBSD Port: clamav-0.95.3
On Sat, Jan 9, 2010 at 1:56 AM, Stewart MacLund wrote: > hi there. > > this port appears to be broken for 6.3 release (which i realize is old, > but regardless) by > --enable-gethostbyname_r > in the Makefile. changing this to > --disable-gethostbyname_r > allows the port to build fine. Clamav port had a hack like this for FreeBSD <= 6.1, it was removed since 6.1 is no longer supported. gethostbyname_r is supposed to work fine on 6.3. -- Renato Botelho ___ 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: ion windows manager on FreeBSD
On Fri, Oct 2, 2009 at 10:32 AM, Dmitry Marakasov wrote: > * Mark Linimon (lini...@lonesome.com) wrote: > >> The author orginally contacted us with a legal threat because we were >> not in compliance with the 28-day clause. A long, acrimonious disucssion >> ensued. In that discussion, the author was asked "if we agree to meet >> that condition going forward, would you guarantee that this would remove >> any further legal threat?" and he said yes ... >> >> for now. >> >> But that he reserved the right to change his mind later. >> >> *depending* on what we did or did not do in the future -- not just in >> adhering to the *existing clauses* like the "significant" clause or >> "renamed" clause -- both of which he mentioned would be part of any >> lawsuit. >> >> Legally indefensible? Of course. Would that prevent a lawsuit being >> filed? No. Anyone can sue anyone for anything. > > Well, if you insist I of course won't commit it. But the whole thing > disappoints me greately, cause I was pretty sure at least FreeBSD > developers won't be affected by a mere FUD. Do you honestly think > the probability of Tuomo suing us is higher of, say, me suing, well, > us? And that anything will change by us not providing a port we > have absolutely totally utterly 100% right to provide? That is > just silly. > > The port from now on is available here (removed from people.freebsd.org): > http://mirror.amdmi3.ru/ports/ion3-20090110.port.tar You can start a fork of it, change its name, its license, and keep it as a separate project... people will use the same software with another name. Everybody will be happy and we won't have a Tuomo's software inside ports collection again. -- Renato Botelho ___ 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: net-im/ayttm: I'd like to take the maintainership
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Jun 28, 2009 at 10:59:58AM -0300, Carlos A. M. dos Santos wrote: > Hello, > > I just sent a PR regarding net-im/ayttm > (http://www.freebsd.org/cgi/query-pr.cgi?pr=136117) but noticed that > the port does not have a maintainer. This is a real shame! Could you > please give me the usual punishment for those who complain about > unmaintained ports? > > Thanks in advance. Olá Carlos, Please, send a new patch changing MAINTAINER line to your email address as a Follow-up to the PR and the port will be assigned to you. Até mais - -- Renato Botelho GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc You have an ambitious nature and may make a name for yourself. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkpHgNIACgkQ6CRbiSJE7alcDwCgn5nfd2Zd4Sxk+92OoUJ6w6vr PcYAn0nHI3RqZHf1Z/Ukl8nksTFuDHc3 =EMeB -END PGP SIGNATURE- ___ 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: portmgr reorganization
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Jun 04, 2009 at 10:35:55AM +0200, Erwin Lansing wrote: > Portmgr is happy to announce that two new members will join the team. > > Martin Wilke has been one of our active committers since receiving > his commit bit today 3 years ago. He has been working in a number > of subgroups including python, ports-security and the KDE team. > > Ion-Mihai Tetcu has been interested in regression testing and qualitiy > assurance, creeating QAT automated tinderbox testing of all port > commits on a per-commit basis, and adding on-the-fly feedback to the > snapshot builds from the pointyhat package cluster. > > Unfortunately, we will also be saying goodbye to Kririll Ponomarew, who > hasn't had much time to spend on FreeBSD and will be stepping down from > portmgr. > > We thank Kirill for all his contributions in the past and wish Martin > and Ion-Mihai the best of luck with the new tasks bestowed upon them. Thank you krion for all the good work done in the past. Welcom miwi and itetcu, you deserve this, good lucky!!! - -- Renato Botelho GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc Fashions have done more harm than revolutions. -- Victor Hugo -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkonuzcACgkQ6CRbiSJE7alShACfVi3QBgaYdfLra/xfb6z4Ncy2 MMUAoLKffvKJe+6RHfWjUuO7HhaaAhHJ =MNLc -END PGP SIGNATURE- ___ 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: [Call For Testing] VirtualBox for FreeBSD!
On Thu, May 14, 2009 at 4:12 PM, Martin Wilke wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > Howdy Guys, > > After the announcement from Alexander Eichner about > Virtualbox on FreeBSD, we started the work on a port > for FreeBSD. Now we think that we solved the most > problems and are ready for the first Call for Testing. > > Some notes before you can test the port: > Make sure you are using RELENG_7 or higher. You have > to use a fresh portstree with uptodate ports!! Please > read carefully the pkg-messages. > > Some known issues / Troubleshooting: > Sometimes the kernel on HEAD coredumps when loading > or unloading the kernel module. A small workaround > to prevent the crash is to not start X, mount proc, > then load the kernel module and start X from the > console. That helped me and some testers, maybe you > too. :P AMD64 should be work in general, it builds > and start. But not right tested at the moment. We > want here also some feedback. > > Some Thanks: > First of all we'd like to say many thanks to _ALL_ > vbox developers. Next people are Bernhard Froehlich > (aka decke), Beat Gaetzi (beat@), Dennis Herrmann > (dhn@), Pietro Cerutti (gahr@), myself (*gg*), > and _ALL_ who helped and provided feedback. > > Happy Testing :-) > > Download: > > http://people.freebsd.org/~miwi/vbox/vboxport.tgz > > Wiki Page: > http://wiki.freebsd.org/VirtualBox Hello Martin I've built it on i386/CURRENT r191522, but I couldn't load the module, when i try, i got: KLD vboxdrv.ko: depends on kernel - not available kldload: can't load vboxdrv: File exists It says file exists, but the module is not loaded r...@botelhor:/home/garga# kldstat Id Refs AddressSize Name 1 18 0xc040 b584bc kernel 21 0xc0f59000 809c snd_via8233.ko 32 0xc0f62000 4a438sound.ko 41 0xc46af000 8000 linprocfs.ko 51 0xc46c8000 24000linux.ko Any idea? -- Renato Botelho ___ 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: Why so many ports still depend on firefox-2.X.X.X ?
On Sun, Apr 26, 2009 at 6:09 AM, Yuri wrote: > I see that ImageMagick, gimp, gimp-apps, inkscape, gnucash, etc depend on > firefox-2. > Why they aren't switched to firefox-3? You can change gecko engine with WITH_GECKO, if you want to use libxul, the one firefox3 uses, just use: WITH_GECKO=libxul -- Renato Botelho ___ 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: mail/p5-Mail-ClamAV
2009/3/30 Sergei Vyshenski : > Hi, > > After updating of ClamAV to ver. 0.95, got problems with compiling > of mail/p5-Mail-ClamAV-0.20_5 (please see listing below). > > Thanks in advance for any comment. I apologize for this inconvenience, I made a mistake and don't test this port correctly before commit 0.95 version to the ports tree. Now I've marked it as BROKEN and contacted author and maintainer, I hope to have it fixed soon. -- Renato Botelho ___ 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: mail/p5-Mail-ClamAV
On Mon, Mar 30, 2009 at 9:04 AM, matt donovan wrote: > 2009/3/30 Sergei Vyshenski > >> Hi, >> >> After updating of ClamAV to ver. 0.95, got problems with compiling >> of mail/p5-Mail-ClamAV-0.20_5 (please see listing below). >> >> > > > Port needs updated to 0.22nb1 to work correctly I do believe with later > version of clamav. I don't know 0.22nb1, but 0.22 version doesn't build with new clamav, I've already contacter author and maintainer, but got no answer. -- Renato Botelho ___ 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: Dead projects in ports tree
On Mon, Mar 2, 2009 at 7:36 PM, David E. Thiel wrote: > On Sat, Feb 28, 2009 at 04:05:56PM -0800, Garrett Cooper wrote: >> > multimedia/openquicktime - no movement in CVS / SVN for 1+ years; no >> > releases in the past 3 years >> > >> > I'll continue posting more items to this thread as I find them... >> > Thanks, >> > -Garrett >> >> xmms looks completely dead now. Can someone confirm or deny this fact? > > While I'm in favor of removing useless ports, there are several projects > which are simply "done", and lack of development doesn't mean they're > obsolete or useless. The logic above would seem to suggest we should > remove qmail too. I would like to hear what people feel the best method > for getting rid of unused and irrelevant ports, though -- bump > portrevision and mark BROKEN for a few months? Qmail doesn't have a new version for a long time, i know, but new version of patch collection are released, like you can see las spamcontrol 2.5.x, and author is working on 2.6.x with a lot of new features, so, i don't consider qmail a dead project at all. And, there are a good number of qmail users, i don't think it's a good idea remove this port, i'm maintaining it for some years and i can still maintain and keep it working on ports infrastructure. -- Renato Botelho ___ 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: Call for potential ports maintainers
On Sat, Feb 14, 2009 at 3:23 AM, Dylan Leigh wrote: > On Thu, Feb 12, 2009 at 12:32:13PM -0500, Thomas Abthorpe wrote: >> At any given time, approximately 20 - 25% of all ports are >> unmaintained. Not all unmaintained ports need updating, but some do. >> That is where you folks come in. >> >> There are a bunch of you out there who are subscribers to this list >> (and other FreeBSD related lists too, I am sure), you have FreeBSD >> installed and likely have quite an array of ports installed on this >> system of yours. You are subscribed as a means of keeping up with >> the world of FreeBSD. > > > Is there an easy way to get a list of all the unmaintained ports one > currently has installed? cd /usr/ports make search maint=po...@freebsd.org -- Renato Botelho ___ 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: FreeBSD Port: clamav-0.94_1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Sep 19, 2008 at 12:40:35PM +0800, Snopy Land wrote: > Hi, > > My server version is freebsd6.2 amd64. I have installed clamav to scan my > incoming mail. Everything works smoothly for several years. > Recently, I need to upgrade clamav version from 0.92 to 0.94 (latest > version). > > There is no error message found in the whole process, however, I cannot find > the file of "clamd", "clamscan" & "freshclam". > The previous version of these file can be found in /usr/local/sbin and > /usr/local/bin > > I have posted my problem in the mailling list of freebsd-ports, however, I > cannot get any hints. > > After redo the upgrade process, I find there are some files under > /usr/local/bin and /usr/local/sbin but the file name is differenet. > > ls -ltr /usr/local/bin > -r-xr-xr-x 1 root wheel80624 Sep 19 11:07 > amd64-portbld-freebsd6.2-sigtool > -r-xr-xr-x 1 root wheel87944 Sep 19 11:07 > amd64-portbld-freebsd6.2-freshclam > -r-xr-xr-x 1 root wheel51968 Sep 19 11:07 > amd64-portbld-freebsd6.2-clamscan > -r-xr-xr-x 1 root wheel52592 Sep 19 11:07 > amd64-portbld-freebsd6.2-clamdscan > -r-xr-xr-x 1 root wheel28272 Sep 19 11:07 > amd64-portbld-freebsd6.2-clamconf > -r-xr-xr-x 1 root wheel 1103 Sep 19 11:07 > amd64-portbld-freebsd6.2-clamav-config > > ls -ltr /usr/local/sbin > -r-xr-xr-x 1 root wheel67536 Sep 19 11:07 > amd64-portbld-freebsd6.2-clamd > Are these files are the same as the file of "clamd", "freshclam" and > "clamscan". If yes, can I create symbolic link for these file so that I can > keep my old setting? (i.e run "/usr/local/sbin/clamd -c > /usr/local/etc/clamd.conf", and run "/usr/local/bin/freshclam --quiet" in > the cronjob). How many configuration files location should I change ? > > Thanks. This same problem happened with another user, and the cause was his ports tree and autotools ports are not up-to-date. Please, update your ports tree, update all autotools ports (automake, autoconf, libtool) and rebuild clamav. Thanks - -- Renato Botelho GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc The one good thing about repeating your mistakes is that you know when to cringe. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkjTjnEACgkQ6CRbiSJE7amXzwCePlC+uU715DPcmIlIxYfW5nJM XloAoLGXwcWWYPniW2VIXlv5fQU9JJns =VOj/ -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: clamav-0.93.1_2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Jun 30, 2008 at 01:35:59PM +0200, Pieter Sybesma wrote:
> Hi,
>
> I'm getting this on compiling clamav:
>
> > cc -O -pipe -march=pentium4 -o .libs/clamscan output.o getopt.o cfgparser.o
> > misc.o options.o clamscan.o others.o manager.o treewalk.o -L/usr/local/lib
> > ../libclamav/.libs/libclamav.so
> > /usr/ports/security/clamav/work/clamav-0.93.1/libclamunrar_iface/.libs/libclamunrar_iface.so
> >
> > /usr/ports/security/clamav/work/clamav-0.93.1/libclamunrar/.libs/libclamunrar.so
> > -lbz2 /usr/local/lib/libgmp.so -lz -lthr -Wl,--rpath -Wl,/usr/local/lib
> > ../libclamav/.libs/libclamav.so: undefined reference to `gethostbyname_r'
> > *** Error code 1
> >
> > Stop in /usr/ports/security/clamav/work/clamav-0.93.1/clamscan.
> > *** Error code 1
> >
> > Stop in /usr/ports/security/clamav/work/clamav-0.93.1.
> > *** Error code 1
> >
> > Stop in /usr/ports/security/clamav/work/clamav-0.93.1.
> > *** Error code 1
> >
> > Stop in /usr/ports/security/clamav.
> > *** Error code 1
> >
> > Stop in /usr/ports/security/clamav.
> > ** Command failed [exit code 1]: /usr/bin/script -qa
> > /tmp/portupgrade.33714.0 env UPGRADE_TOOL=portupgrade
> > UPGRADE_PORT=clamav-0.93_1 UPGRADE_PORT_VER=0.93_1 make
> > ** Fix the problem and try again.
> > ** Listing the failed packages (-:ignored / *:skipped / !:failed)
> > ! security/clamav (clamav-0.93_1) (linker error)
>
> It seems it's a problem since you removed the following from the
> Makefile last in version 1.112 2008/06/09 16:13:25:
>
> > .if ${OSVERSION} < 601103
> > CONFIGURE_ARGS+=--disable-gethostbyname_r
> > .else
> > CONFIGURE_ARGS+=--enable-gethostbyname_r
> > .endif
>
> I'm running the following version:
>
> > qmailin# uname -a
> > FreeBSD qmailin.gicom.nl 5.3-RELEASE-p37 FreeBSD 5.3-RELEASE-p37 #1: Mon
> > Mar 12 12:47:07 CET 2007 [EMAIL
> > PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL i386
Yes, the problem occours because i removed that lines. I removed them
because since Last May 31, any FreeBSD < 6.2 is no longer supported anymore.
This was announced one year before. Now, all "hackerisms" that made ports
build and work fine on these version will be removed from the tree.
FreeBSD project people strongly recommend to upgrade at least to 6.3.
Thanks
- --
Renato Botelho
GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc
PAIN:
Falling out of a twenty story building,
and snagging your eyelid on a nail.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)
iEYEARECAAYFAkho1hYACgkQ6CRbiSJE7amZkwCaAtVbC7hrk3JL7hEAWIs52TR4
0J4An3GxRPvGms38NkDooo/e8Xtf7hou
=LHv+
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: clamav-0.93
On Sun, May 18, 2008 at 11:44:26AM +1000, Adrian Thearle wrote: > Hi > > I have made a change to the clamav-milter startup script that helps with > permissions on the socket. > I use postfix, not sure of sendmails requirements, but the socket needs to > be writeable by the postfix user. The attached patch adds three variables > that can be used to change the permissions and owner of the socket. I > checked for this functionality within clam itself, but could not find an > option. Hi, Clamav has 2 options that you can set on your /etc/make.conf: CLAMAVUSER CLAMAVGROUP You can safely set this to postfix user and group, and after this, socket and all other things needed will have the correct permissions. I will commit part of the change you proposed to clamav's port, the mode option, that is already present in clamav-devel port. After this commit, if you don't want to install clamav with postfix user, you can install with clamav user and group, change socket mode to group writeable and add postfix user to clamav's group. Regards -- Renato Botelho GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc 186,000 miles per second: It isn't just a good idea, it's the law! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: New portmgr member: Pav Lucistnik
On 11/23/06, Erwin Lansing <[EMAIL PROTECTED]> wrote: Portmgr is pleased to announce that Pav Lucistnik has accepted the challenge of being a portmgr member. Pav has been with the project for a long time and is one of our most active committers and bug busters. He has been working on the ports infrastructure and will now be working with the other portmgr members on integrating infrastructure patches and quality assurance in addition to other portmgr tasks. Wish him luck! Congratulations Pav!!! \o/ One more for approvals during freeze time ;-) -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: pure-ftpd-1.0.21_1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: > Tried to install the latest version from ports.. > > MySQL support in Pure-FTPD seems to be broken with the latest mysql50-server > and client.. (mysql-client-5.0.24a) > > When trying to make with support it errors out on sqlconnect.. > > Sorry for not being able to supply the actual error as I've already gone > back to mysql-41-server and client.. Fixed. Thanks! - -- Renato Botelho GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFBX406CRbiSJE7akRAqW+AJoC1xS1PWwnz+lhbS36+ZMxEpD+PgCgnyU0 /dMIamYlpspq5ZkQfHlHhkc= =iW76 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [Samba] authenticating using winbindd against NT4 domain fail s
On 9/6/06, Doug Sampson <[EMAIL PROTECTED]> wrote: > There is portdowngrade, but i never tested. I do it: > > # setenv CVSROOT [EMAIL PROTECTED]:/home/ncvs > # cvs co -D"Apr 10 2006" samba3 > # cd samba3 > # make > # make deinstall > # make install > [EMAIL PROTECTED]:/usr/ports/net/samba3# make ===> samba-3.0.22,1 has known vulnerabilities: => samba -- memory exhaustion DoS in smbd. Reference: <http://www.FreeBSD.org/ports/portaudit/b168ddea-105a-11db-ac96-000c6ec775d9 .html> => Please update your ports tree and try again. *** Error code 1 Stop in /usr/ports/net/samba3. [EMAIL PROTECTED]:/usr/ports/net/samba3# Seems it cannot find the older port. Where can I locate it? Teh problem is that it has a vulnerability, so, make -DDISABLE_VULNERABILITIES will disable the vuxml check -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [Samba] authenticating using winbindd against NT4 domain fail s
On 9/6/06, Doug Sampson <[EMAIL PROTECTED]> wrote: > > I understand that the winbind behavior has changed in > 3.0.23x (or 3.0.22?) > > but it was my impression that nothing had changed in the > way a Samba member > > server authenticates against a NT4 PDC using winbindd. What > might I be doing > > wrong here? > > I'm having the same problems here, the only version that works really > fine is 3.0.22. :-( > How does one downgrade back to version 3.0.22? There is portdowngrade, but i never tested. I do it: # setenv CVSROOT [EMAIL PROTECTED]:/home/ncvs # cvs co -D"Apr 10 2006" samba3 # cd samba3 # make # make deinstall # make install -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [Samba] authenticating using winbindd against NT4 domain fails
On 9/6/06, Doug Sampson <[EMAIL PROTECTED]> wrote: Since version 3.0.23b, I have been having trouble getting Windows & OSX users to access an NT domain member server running FreeBSD 5.4. It is now at 3.0.23c (installed this morning the 5th). [cut] I understand that the winbind behavior has changed in 3.0.23x (or 3.0.22?) but it was my impression that nothing had changed in the way a Samba member server authenticates against a NT4 PDC using winbindd. What might I be doing wrong here? I'm having the same problems here, the only version that works really fine is 3.0.22. :-( -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports/102937: Update port: archivers/epkg Fix for compiling on ia64 systems
Synopsis: Update port: archivers/epkg Fix for compiling on ia64 systems State-Changed-From-To: open->closed State-Changed-By: garga State-Changed-When: Wed Sep 6 15:28:50 UTC 2006 State-Changed-Why: Committed. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=102937 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS-UP: DESTDIR support committed to Mk/
On 8/4/06, Gábor Kövesdán <[EMAIL PROTECTED]> wrote: Hi, I am pleased to announce, that portmgr committed my patch for ports infrastructure DESTDIR support today. Note that this support is only for the infrastructure, ports may or may not respect the DESTDIR macro, so you should use this with care. Also note, that we only tested this patchset without the DESTDIR macro set, but will do an another one with DESTDIR set to something and check how many ports respect DESTDIR and how many left to fix, but port maintainers can start checking their ports and fixing them if necessary. Unfortunately, testing ports for DESTDIR is pretty difficult, since we don't have support for this in tinderbox. I used a chroot jail installed into an another chroot jail to ensure I won't make my filesystem dirty. I chrooted into the first jail and run make install for the given port with DESTDIR set to the another chroot jail, checked if everything went fine and did make deinstall and checked if everything is still good. I know it's a bit complicated, but we don't have better yet. I've also written a Wiki page for DESTDIR with some guidelines what to care about when writing DESTDIR-respective ports. You can find it here: http://wikitest.freebsd.org/DESTDIR I also suggest to read the CHANGES entry, if you haven't done this yet: http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/CHANGES?rev=1.57&content-type=text/plain Documentation update for porters-handbook will also come soon. If you have questions, please feel free to contact me. Great news. Congratulations and thanks for the great work! -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: UPDATING? - terminus font installation directory changed
On 7/13/06, Andriy Gapon <[EMAIL PROTECTED]> wrote: I accidentally noticed that I started to have troubles with terminus font (x11-fonts/terminus-font) after recent update to version 4.20. No wonder, it seems that the port now installs font files into a separate directory lib/X11/fonts/terminus-font instead of previous lib/X11/fonts/local. I think that such a change warrants a note in UPDATING, so that people know to add the new path to their font paths. I forgot to do it before, done now. Sorry! -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
