[Bug build/16704] New: toolchain building for x86_64 x32 fails on Debian 7

[Bug build/16704] New: toolchain building for x86_64 x32 fails on Debian 7

[wbx at openadk dot org]

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

            Bug ID: 16704
           Summary: toolchain building for x86_64 x32 fails on Debian 7
           Product: glibc
           Version: 2.19
            Status: NEW
          Severity: minor
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: wbx at openadk dot org
                CC: carlos at redhat dot com

Hi Developers,

while creating a cross-compiler for x86_64 with x32 ABI I encountered a small
issue regarding the usage of echo.

In sysdeps/unix/make-syscalls.sh following line is used:
296          echo 'asm (\".globl __GI_${strong}\\n\"'; \\

----
$ dash -c "echo '\\n'"


$ bash -c "echo '\\n'"
\n
$ mksh -c "echo '\\n'"


____

Debian uses a symlink /bin/sh -> /bin/dash. After changing it to
/bin/sh -> /bin/bash the toolchain build completes without errors.

I am not sure how to make it portable. Should printf be used?
The \n for echo seems not standardized.
http://pubs.opengroup.org/onlinepubs/009695399/utilities/echo.html
"It is not possible to use echo portably across all POSIX systems unless both
-n (as the first argument) and escape sequences are omitted."

thanks
 Waldemar

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

[Bug build/16704] toolchain building for x86_64 x32 fails on Debian 7

[carlos at redhat dot com]

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

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING

--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to wbx from comment #0)
> Debian uses a symlink /bin/sh -> /bin/dash. After changing it to
> /bin/sh -> /bin/bash the toolchain build completes without errors.

We are moving towards being able to build the library with dash as the system
shell e.g. specifying bash explicitly where required and cleaning up otherwise.
However, I do not think this work is yet done to the point where you can
compile with dash as the system shell.

I suggest two courses of action:
* Ask on libc-alpha about compiling with your system shell as dash.
* Leave this issue open and retitle "Support compiling glibc with system shell
set to dash".

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

[Bug build/16704] Support compiling glibc with system shell set to dash

[wbx at openadk dot org]

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

wbx at openadk dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
            Summary|toolchain building for      |Support compiling glibc
                   |x86_64 x32 fails on Debian  |with system shell set to
                   |7                           |dash

--- Comment #2 from wbx at openadk dot org ---
Hi,

would be nice if the build can be done setting something like SHELL to point to
bash as environment or make option. This does not work at the moment.

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

[Bug build/16704] Support compiling glibc with system shell set to dash

[fweimer at redhat dot com]

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

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |security-

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

[Bug build/16704] Support compiling glibc with system shell set to dash

[cvs-commit at gcc dot gnu.org]

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

--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, master has been updated
       via  b2fb25240813266e4f62f2dd039573f1a042ea2f (commit)
      from  0e9be4db8f655d3dc006c5b101f15a5912a5846f (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b2fb25240813266e4f62f2dd039573f1a042ea2f

commit b2fb25240813266e4f62f2dd039573f1a042ea2f
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Fri May 15 08:49:12 2015 -0300

    Add BZ #16704 as fixed

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog |    1 +
 NEWS      |   16 ++++++++--------
 2 files changed, 9 insertions(+), 8 deletions(-)

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

[Bug build/16704] Support compiling glibc with system shell set to dash

[adhemerval.zanella at linaro dot org]

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

Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |adhemerval.zanella at linaro dot o
                   |                            |rg
         Resolution|---                         |FIXED

--- Comment #4 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
Fixed upstream by 95b07fbcc702a83b421cb5d0488ba2817d3123c1

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