Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 650182 - dev-lang/smlnj-110.82 : * dosym: two arguments needed
Summary: dev-lang/smlnj-110.82 : * dosym: two arguments needed
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal with 3 votes (vote)
Assignee: No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-11 08:40 UTC by Toralf Förster
Modified: 2020-01-26 17:17 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge-info.txt (emerge-info.txt,15.11 KB, text/plain)
2018-03-11 08:40 UTC, Toralf Förster
Details
dev-lang:smlnj-110.82:20180311-045356.log (dev-lang:smlnj-110.82:20180311-045356.log,278.51 KB, text/plain)
2018-03-11 08:40 UTC, Toralf Förster
Details
emerge-history.txt (emerge-history.txt,40.92 KB, text/plain)
2018-03-11 08:40 UTC, Toralf Förster
Details
environment (environment,78.47 KB, text/plain)
2018-03-11 08:40 UTC, Toralf Förster
Details
etc.portage.tbz2 (etc.portage.tbz2,11.30 KB, application/x-bzip)
2018-03-11 08:41 UTC, Toralf Förster
Details
temp.tbz2 (temp.tbz2,38.02 KB, application/x-bzip)
2018-03-11 08:41 UTC, Toralf Förster
Details
patch that fixes this issue (smlnj-110.82-dosym-fix.diff,590 bytes, patch)
2019-01-28 23:14 UTC, Winston Weinert
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Toralf Förster gentoo-dev 2018-03-11 08:40:45 UTC
 * ERROR: dev-lang/smlnj-110.82::gentoo failed (install phase):
 *   dosym: two arguments needed
 * 

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

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.0-systemd_libressl_20180309-191749

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

gcc-config -l:
 [1] x86_64-pc-linux-gnu-7.3.0 *

Available Python interpreters, in order of preference:
  [1]   python3.5
  [2]   python2.7 (fallback)
Available Ruby profiles:
  [1]   ruby22 (with Rubygems)
  [2]   ruby23 (with Rubygems) *
java-config:
The following VMs are available for generation-2:
*)	IcedTea JDK 3.7.0 [icedtea-bin-8]
Available Java Virtual Machines:
  [1]   icedtea-bin-8  system-vm

emerge -qpv dev-lang/smlnj
[ebuild  N    ] dev-lang/smlnj-110.82  USE="-pax_kernel"
Comment 1 Toralf Förster gentoo-dev 2018-03-11 08:40:48 UTC
Created attachment 523430 [details]
emerge-info.txt
Comment 2 Toralf Förster gentoo-dev 2018-03-11 08:40:51 UTC
Created attachment 523432 [details]
dev-lang:smlnj-110.82:20180311-045356.log
Comment 3 Toralf Förster gentoo-dev 2018-03-11 08:40:54 UTC
Created attachment 523434 [details]
emerge-history.txt
Comment 4 Toralf Förster gentoo-dev 2018-03-11 08:40:57 UTC
Created attachment 523436 [details]
environment
Comment 5 Toralf Förster gentoo-dev 2018-03-11 08:41:00 UTC
Created attachment 523438 [details]
etc.portage.tbz2
Comment 6 Toralf Förster gentoo-dev 2018-03-11 08:41:03 UTC
Created attachment 523440 [details]
temp.tbz2
Comment 7 Thomas J. Moore 2018-04-28 18:13:37 UTC
Finally got tired of recompiling smlnj every update, so I fixed it for myself.

Just change line 123 from
  local z=$....
to
  local z=($....)
Comment 8 Luke A. Guest 2018-05-09 13:19:10 UTC
I can confirm this still is an issue.
Comment 9 Thomas J. Moore 2018-05-11 17:32:07 UTC
(In reply to Luke A. Guest from comment #8)
> I can confirm this still is an issue.

Don't worry.  Soon enough, some helpful gentoo developer will remove dev-lang/smlnj from the tree entirely, so the problem will disappear.  That's how bugs are fixed around here.  Much easier than applying a trivial fix to an ebuild.
Comment 10 Winston Weinert 2019-01-28 23:14:53 UTC
Created attachment 563150 [details, diff]
patch that fixes this issue

Here is a patch that fixes the issue.
Comment 11 David E. Narváez 2019-12-25 20:56:21 UTC
Confirmed.
Comment 12 Vicky Souza 2020-01-26 17:17:52 UTC
I can confirm that applying the bash array patch and updating the Manifest file fixes the issue.