[Bug binutils/29066] decode scaling base rather than index

[jayleblanc at roadrunner dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=29066

--- Comment #4 from jayleblanc  ---
Thanks!

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gas/29067] gas: -gsomething-not-already-a-long-option does not get a diagnostic

[hjl.tools at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=29067

--- Comment #1 from H.J. Lu  ---
This works:

diff --git a/gas/as.c b/gas/as.c
index f320bac89b5..0262a6fec98 100644
--- a/gas/as.c
+++ b/gas/as.c
@@ -836,6 +836,8 @@ This program has absolutely no warranty.\n"));
versions/sections/options.  */
 if (startswith (old_argv[optind - 1], "-gdwarf"))
   as_fatal (_("unknown DWARF option %s\n"), old_argv[optind - 1]);
+else if (old_argv[optind - 1][1] == 'g' && optarg != NULL)
+  as_fatal (_("unknown option `%s'"), old_argv[optind - 1]);

 if (md_debug_format_selector)
   debug_type = md_debug_format_selector (& use_gnu_debug_info_extensions);

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug binutils/29042] opcodes libtool regression

[toolybird at tuta dot io]

https://sourceware.org/bugzilla/show_bug.cgi?id=29042

--- Comment #4 from Toolybird  ---
This bug is a little more serious than I first thought.

Even when /usr/lib/libiberty.a does not exist, the following combination of
switches results in the wrong libiberty.a getting linked in:

--prefix=/usr
--enable-shared
--enable-install-libiberty

$ make -j2 prefix=/build/binutils/tmp/usr install

In the verbose log I see this:

attempt to open /build/binutils/tmp/usr/lib/libiberty.a succeeded

This means libopcodes is (re)linking against a non-pic libiberty. This is
definitely wrong.

Problem goes away with `make -j1 ...install'. I noticed this while
investigating issues of reproducibility.

A lot of build systems put "-j (n>1)" globally into MAKEFLAGS. What is the
common wisdom here? Always `make install' binutils with -j1 ?

Thanks

-- 
You are receiving this mail because:
You are on the CC list for the bug.