lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z-pCHdB0uXDUCki0@li-2b55cdcc-350b-11b2-a85c-a78bff51fc11.ibm.com>
Date: Mon, 31 Mar 2025 09:19:57 +0200
From: Sumanth Korikkar <sumanthk@...ux.ibm.com>
To: kernel test robot <lkp@...el.com>
Cc: oe-kbuild-all@...ts.linux.dev, linux-kernel@...r.kernel.org,
        Alexander Gordeev <agordeev@...ux.ibm.com>
Subject: Re: s390-linux-ld: Error: unable to disambiguate: -no-pie (did you
 mean --no-pie ?)

On Sat, Mar 29, 2025 at 11:11:17AM +0800, kernel test robot wrote:
> Hi Sumanth,
> 
> FYI, the error/warning still remains.
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   0c86b42439b6c11d758b3392a21117934fef00c1
> commit: 00cda11d3b2ea07295490b7d67942014f1cbc5c1 s390: Compile kernel with -fPIC and link with -no-pie
> date:   11 months ago
> config: s390-randconfig-001-20250329 (https://download.01.org/0day-ci/archive/20250329/202503291141.yTqSRdTX-lkp@intel.com/config)
> compiler: s390-linux-gcc (GCC) 8.5.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250329/202503291141.yTqSRdTX-lkp@intel.com/reproduce)
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@...el.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202503291141.yTqSRdTX-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
> >> s390-linux-ld: Error: unable to disambiguate: -no-pie (did you mean --no-pie ?)

Thanks for reporting.

I have worked on it. The fix should be available in the very near future.

Best Regards,
Sumanth

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ