mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released
Date: Tue, 13 Feb 2018 15:44:09 +0100	[thread overview]
Message-ID: <20180213144409.alamndyjbuhu2uvn@pengutronix.de> (raw)
In-Reply-To: <2512815.1UNvg0mjz2@ada>

On Tue, Feb 13, 2018 at 03:05:17PM +0100, Alexander Dahl wrote:
> Am Dienstag, 13. Februar 2018, 14:30:38 CET schrieb Michael Olbrich:
> > > Host is on Debian 9 (stretch), amd64, using icecc:
> 
> ^^
> 
> > Hmm, generating Debian packages is not widely tested outside my local
> > setup, but it should work. Can you add 'set -x' at the beginning of the
> > main() function in scripts/make_deb.sh and send the output?
> 
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
> target: oselas.toolchain-2018.02.0-dirty-arm-v5te-linux-gnueabi-gcc-7.3.1-
> glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-
> dirty-0ptx1~bpo9+1_amd64.deb
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
> 
> + getopts d:s: opt
> + case "${opt}" in
> + local deb=/mnt/data_2/adahl/src/OSELAS.Toolchain/dist/
> oselas.toolchain-2018.02.0-dirty-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-
> binutils-2.30-kernel-4.15-sanitized_2018.02.0-dirty-0ptx1~bpo9+1_amd64.deb
> + getopts d:s: opt
> + case "${opt}" in
> + local src=/mnt/data_2/adahl/src/OSELAS.Toolchain/inst/opt/
> OSELAS.Toolchain-2018.02.0/arm-v5te-linux-gnueabi/gcc-7.3.1-glibc-2.27-
> binutils-2.30-kernel-4.15-sanitized
> + getopts d:s: opt
> + '[' -z /mnt/data_2/adahl/src/OSELAS.Toolchain/dist/
> oselas.toolchain-2018.02.0-dirty-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-
> binutils-2.30-kernel-4.15-sanitized_2018.02.0-dirty-0ptx1~bpo9+1_amd64.deb -o 
> -z /mnt/data_2/adahl/src/OSELAS.Toolchain/inst/opt/OSELAS.Toolchain-2018.02.0/
> arm-v5te-linux-gnueabi/gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-
> sanitized ']'
> + local 'ifs_orig=
> '
> + IFS=_
> + set -- /mnt/data 2/adahl/src/OSELAS.Toolchain/dist/
> oselas.toolchain-2018.02.0-dirty-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-
> binutils-2.30-kernel-4.15-sanitized 2018.02.0-dirty-0ptx1~bpo9+1 amd64.deb
> + IFS='
> '
> + local package=data
> + local inst=/mnt/
> + local version=2/adahl/src/OSELAS.Toolchain/dist/oselas.toolchain-2018.02.0-
> dirty-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-
> sanitized
> + local arch=2018.02.0-dirty-0ptx1~bpo9+1
> + local prefix=opt/OSELAS.Toolchain-2018.02.0/arm-v5te-linux-gnueabi/
> gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized
> + local destdir=/mnt/data_2/adahl/src/OSELAS.Toolchain/inst/
> + local debian_tmp=/mnt//data-temp
> + '[' -e /mnt//data-temp ']'
> + mkdir -p /mnt//data-temp/tmp /mnt//data-temp/debian
> mkdir: cannot create directory '/mnt//data-temp': Permission denied
> mkdir: cannot create directory '/mnt//data-temp': Permission denied
> 
> ----
> 
> The problem is probably the '_' in the path of my working directory?

Indeed. We do some magic with '_' to split the version and arch and this
breaks in your case.

> > This is a bug in gcc on your build host. What distribution (and version)
> > are you using and what is the output of 'gcc --version'?
> 
> Debian GNU/Linux 9 (stretch) on amd64.
> 
> % gcc --version
> gcc (Debian 6.3.0-18) 6.3.0 20170516
> 
> The build without icecc seemed to succeed, if I start it from a (symlinked) 
> directory without '_' anywhere in the path. I get some warnings on the *.deb 
> stage, but it succeeds.

Strange, I've used exactly the same compiler to built at least one
toolchain with icecc enabled.
I'm currently building the Debian packages for buster. stretch is next, so
I'll see if I get any similar errors.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2018-02-13 14:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 15:51 Michael Olbrich
2018-02-13 10:00 ` Roland Hieber
2018-02-13 10:04   ` Michael Olbrich
2018-02-13 12:41 ` Alexander Dahl
2018-02-13 13:30   ` Michael Olbrich
2018-02-13 13:59     ` Denis OSTERLAND
2018-02-13 14:37       ` Michael Olbrich
2018-02-19  9:38         ` Michael Olbrich
2018-02-13 14:05     ` Alexander Dahl
2018-02-13 14:44       ` Michael Olbrich [this message]
2018-02-18 20:00 ` Jon Ringle
2018-02-19  8:11   ` Alexander Dahl
2018-02-19  9:34     ` Michael Olbrich
2018-09-29 15:57 ` [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released - host-m4 build error on Ubuntu 18.10 Andreas Pretzsch
2019-01-18  9:07   ` Roland Hieber
2019-01-18 10:34     ` Michael Olbrich
2019-01-18 13:23       ` Roland Hieber
2019-01-18 14:06         ` Michael Olbrich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180213144409.alamndyjbuhu2uvn@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox