[no subject]
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- On Thursday, November 26, 2020, 6:29:00 AM GMT-3, Rosen Penev wrote: > On Thu, Nov 26, 2020 at 12:26 AM, Petr Štetiar wrote: >> Rosen Penev [2020-11-24 02:04:24]: Hi, >>> It seems the Makefile wrongly picks up dist CC and matches on a clang >>>path. Fixes: mips-openwrt-linux-musl-gcc: error: unrecognized command-line >>>option '-Qunused-arguments' >> then the fix seems wrong. You should make sure, that proper CC is used. > Yeah. I CC'd cotequeiroz to get his comment on this. No dice so far. Sorry. I've been busy lately, but I'll take a look at it over the weekend. I agree with ynezz, we should ensure the right CC is used. Cheers, Eneas --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] cryptodev-linux: move from packages feed
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- On Sat, 24 Nov 2018, Hauke Mehrtens wrote: > On 11/9/18 6:06 PM, Eneas U de Queiroz wrote: >> This is actually a build dependency for /dev/crypto support in openssl. >> Since it is a kernel module, it belongs here anyway. >> >> Acked-by: Ansuel Smith >> Signed-off-by: Eneas U de Queiroz >> >> diff --git a/package/kernel/cryptodev-linux/Makefile >> b/package/kernel/cryptodev-linux/Makefile >> new file mode 100644 >> index 00..8e9c7ed8b0 >> --- /dev/null >> +++ b/package/kernel/cryptodev-linux/Makefile >> @@ -0,0 +1,74 @@ >> +# >> +# Copyright (C) 2014 OpenWrt.org >> +# >> +# This is free software, licensed under the GNU General Public License v2. >> +# See /LICENSE for more information. >> +# >> +# $Id$ >> + >> +include $(TOPDIR)/rules.mk >> +include $(INCLUDE_DIR)/kernel.mk >> + >> +PKG_NAME:=cryptodev-linux >> +PKG_VERSION:=1.9.git-2018-11-02 >> +PKG_RELEASE:=1 >> + >> +PKG_SOURCE_URL:=https://github.com/cryptodev-linux/cryptodev-linux >> +PKG_SOURCE_PROTO:=git >> +PKG_SOURCE_VERSION:=f1a693000d116718379f8b53ed7bc6b9c0f7de27 >> +PKG_MIRROR_HASH:=340d314e2a88bf2449ccee906b141e085d376f6e2a94a64e36254e8376323169 >> +PKG_LICENSE:=GPL-2.0 >> +PKG_LICENSE_FILES:=COPYING >> + >> +PKG_MAINTAINER:=Ansuel Smith >> + >> +PKG_BUILD_DIR:=$(KERNEL_BUILD_DIR)/$(PKG_NAME)-$(PKG_VERSION) >> + >> +include $(INCLUDE_DIR)/package.mk >> + >> +CRYPTODEV_AUTOLOAD:= \ >> + cryptodev > > Please inline this, this extra variable is unneeded. > >> + >> +define KernelPackage/cryptodev >> + SUBMENU:=Cryptographic API modules >> + DEFAULT:=m if ALL >> + TITLE:=Driver for cryptographic acceleration >> + URL:=http://cryptodev-linux.org/ >> + MAINTAINER:=Nikos Mavrogiannopoulos > > Why are there two different maintainers in this file? > >> + VERSION:=$(LINUX_VERSION)+$(PKG_VERSION)-$(BOARD)-$(PKG_RELEASE) >> + DEPENDS:=+kmod-crypto-authenc +kmod-crypto-hash >> + FILES:= \ >> + $(PKG_BUILD_DIR)/cryptodev.$(LINUX_KMOD_SUFFIX) >> + AUTOLOAD:=$(call AutoLoad,50,$(CRYPTODEV_AUTOLOAD)) >> + MODPARAMS.cryptodev:= cryptodev_verbosity=-1 >> +endef >> + >> +define KernelPackage/cryptodev/description >> + This is a driver for that allows to use the Linux kernel supported >> + hardware ciphers by user-space applications. >> +endef >> + >> +CRYPTODEV_MAKEOPTS= -C $(PKG_BUILD_DIR) \ >> + PATH="$(TARGET_PATH)" \ >> + ARCH="$(LINUX_KARCH)" \ >> + CROSS_COMPILE="$(TARGET_CROSS)" \ >> + TOOLPREFIX="$(KERNEL_CROSS)" \ >> + TOOLPATH="$(KERNEL_CROSS)" \ >> + KERNEL_DIR="$(LINUX_DIR)" \ >> + LDOPTS=" " \ >> + DOMULTI=1 > > Most of these options are already defined in KERNEL_MAKE_FLAGS, please > use that as a base. > >> + >> +define Build/Compile/cryptodev >> + $(MAKE) $(CRYPTODEV_MAKEOPTS) >> +endef > > Why is Build/Compile/cryptodev needed? > >> + >> +define Build/Compile >> + $(call Build/Compile/cryptodev) >> +endef >> + >> +define Build/InstallDev >> + $(INSTALL_DIR) $(STAGING_DIR)/usr/include/crypto >> + $(CP) $(PKG_BUILD_DIR)/crypto/cryptodev.h >> $(STAGING_DIR)/usr/include/crypto/ >> +endef >> + >> +$(eval $(call KernelPackage,cryptodev)) >> > > > I had shipped the Makefile as it was. I have streamlined it, but still I need to sort out the maintainers. Then I'll resend. Thanks for the review. Eneas --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] libpcap: patch to add limits.h to pcap-usb-linux.c
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- I will repost the patch with a cover letter explaining all this, and with a better commit message. I made the wrong assumption that the commit id on top of the patch would be enough to identify its origin. I'm still learning, and shall do it right next time. The reason why the buildservers don't fail is that they're probably not setting CONFIG_PCAP_HAS_USB (default is OFF), so the patched file does not get compiled. I will add that info in the cover letter. Cheers, Eneas Em quarta-feira, 1 de agosto de 2018 06:01:58 BRT, John Crispin escreveu: none of the buildservers seem to break without this patch. please repost explaining how the build breaks without this patch. also reference the place where you copied the patch from John --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2 1/4] openssl: Upgrade to 1.1.0h
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Sorry about the typos and spacing changes. This should have never happened.
Thank you for pointing them out. I have corrected them in the PR I've opened
on github. Since I'm new to the mailing list and don't know what the best way
to proceed, please advise me. I have 4 patches all related to the openssl
upgrade. John asked me earlier to send the whole bundle, so that people
wouldn't need to search for them all over the list. Now I have to change just
one of them. Should I repost all 4, or is it OK to do a V3 for just the
openssl patch?
Since it's only the text I'm changing, I don't feel the need to do it right
away--I still have plenty of pull requests to send to the packages feed. I
will change the PR I've opened in github right away, but I feel like I'm
polluting the mailing list if I do it just for some typos in the text. If
there are nothing else to change, my intent is to repost the patch after I'm
finished with the packages feed.
By the way, here's the progress with the packages that depend on openssl
(packages that were added or removed after I posted the patch are not tallied):
Global Progress
---
Total packages 152 100,00%
Packages that worked right away 109 71,71%
Packages working now 122 80,26%
Packages that still need changes 30 19,74%
PR Progress
---
Total packages that needed changes 43 100,00%
PRs created 32 74,42%
Merged PRs 13 30,23%
Open PRs 19 44,19%
PRs to open 11 25,58%
As for the comment about dropping the engines: I'm removing the patch that
dropped the engines, and adding some options to control their installation, not
ditching the engines.
Cheers,
Eneas
Em domingo, 3 de junho de 2018 14:58:42 BRT, Philip Prindeville
escreveu:
Inline… but generally, please spellcheck yourself.
> On May 30, 2018, at 8:35 PM, Eneas U de Queiroz via openwrt-devel
> wrote:
>
> From: Eneas U de Queiroz
> Subject: [PATCH v2 1/4] openssl: Upgrade to 1.1.0h
> Date: May 30, 2018 at 8:18:34 PM MDT
> To: openwrt-devel@lists.openwrt.org
> Cc: Eneas U de Queiroz
>
>
> This version brings major changes to the API, so many packages will need
> adjustments or version bumps.
> Separated the individual engines in place of the generic "hardware
> support" option.
>
> Signed-off-by: Eneas U de Queiroz
> ---
> package/libs/openssl/Config.in | 45 ++---
> package/libs/openssl/Makefile | 80 -
> .../patches/100-Configure-afalg-support.patch | 13 ++
> .../libs/openssl/patches/110-openwrt_targets.patch | 26 +++
> .../openssl/patches/110-optimize-for-size.patch | 16 --
> ..._segfault.patch => 120-fix_link_segfault.patch} | 16 +-
> package/libs/openssl/patches/130-perl-path.patch | 64 ---
> .../libs/openssl/patches/140-makefile-dirs.patch | 11 --
> package/libs/openssl/patches/150-no_engines.patch | 81 -
> .../openssl/patches/160-disable_doc_tests.patch | 58 ---
> package/libs/openssl/patches/170-bash_path.patch | 8 -
> .../patches/190-remove_timestamp_check.patch | 23 ---
> .../libs/openssl/patches/200-parallel_build.patch | 184 -
> 13 files changed, 107 insertions(+), 518 deletions(-)
> create mode 100644
> package/libs/openssl/patches/100-Configure-afalg-support.patch
> create mode 100644 package/libs/openssl/patches/110-openwrt_targets.patch
> delete mode 100644 package/libs/openssl/patches/110-optimize-for-size.patch
> rename package/libs/openssl/patches/{180-fix_link_segfault.patch =>
> 120-fix_link_segfault.patch} (52%)
> delete mode 100644 package/libs/openssl/patches/130-perl-path.patch
> delete mode 100644 package/libs/openssl/patches/140-makefile-dirs.patch
> delete mode 100644 package/libs/openssl/patches/150-no_engines.patch
> delete mode 100644 package/libs/openssl/patches/160-disable_doc_tests.patch
> delete mode 100644 package/libs/openssl/patches/170-bash_path.patch
> delete mode 100644
> package/libs/openssl/patches/190-remove_timestamp_check.patch
> delete mode 100644 package/libs/openssl/patches/200-parallel_build.patch
>
> diff --git a/package/libs/openssl/Config.in b/package/libs/openssl/Config.in
> index 96d3ba3e9d..a705aa741c 100644
> --- a/package/libs/openssl/Config.in
> +++ b/package/libs/openssl/Config.in
> @@ -10,11 +10,6 @@ config OPENSSL_WITH_EC2M
> depends on OPENSSL_WITH_EC
> prompt "Enable ec2m support"
>
> -config OPENSSL_WITH_SSL3
> - bool
> - default n
> - prompt "Enable sslv3 support"
> -
> config OPENSSL_WITH_DEPRECATED
> bool
>
[OpenWrt-Devel] wolfssl: no maintainer to take a look at PR
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- While testing ustream-ssl security options with different ssl libraries, I stumbled upon some problems with wolfssl configuration options. I've opened a PR https://github.com/openwrt/openwrt/pull/1008 to address these problems. To summarize, there are build options that can't be turned off and should not be in openwrt Config.in, and the POLY_1305 option is clearly mishandled. However, Alexandru Ardelean stepped down as maintainer, and I would like for someone to take a look at this. Thanks, Eneas --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
