Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED] Problem to compile dev-go/go-md2man
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Gentoo on ARM
View previous topic :: View next topic  
Author Message
misterxx
Guru
Guru


Joined: 18 Apr 2004
Posts: 509

PostPosted: Mon Apr 15, 2024 8:48 am    Post subject: [SOLVED] Problem to compile dev-go/go-md2man Reply with quote

Hello community

I have a problem to compile dev-go/go-md2man, I am grateful for any suggestion.

Code:
>>> Emerging (3 of 23) dev-go/go-md2man-2.0.3::gentoo
 * go-md2man-2.0.3.tar.gz BLAKE2B SHA512 size ;-) ...                                                                                                                                                              [ ok ]
>>> Unpacking source...
>>> Unpacking go-md2man-2.0.3.tar.gz to /var/tmp/portage/dev-go/go-md2man-2.0.3/work
>>> Source unpacked in /var/tmp/portage/dev-go/go-md2man-2.0.3/work
>>> Preparing source in /var/tmp/portage/dev-go/go-md2man-2.0.3/work/go-md2man-2.0.3 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-go/go-md2man-2.0.3/work/go-md2man-2.0.3 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-go/go-md2man-2.0.3/work/go-md2man-2.0.3 ...
make -j8 BUILD_FLAGS=-mod=vendor build
WORK=/var/tmp/portage/dev-go/go-md2man-2.0.3/temp/go-build2854926838
-buildmode=pie requires external (cgo) linking, but cgo is not enabled
make: *** [Makefile:19: bin/go-md2man] Error 1
 * ERROR: dev-go/go-md2man-2.0.3::gentoo failed (compile phase):
 *   emake failed
 *
 * If you need support, post the output of `emerge --info '=dev-go/go-md2man-2.0.3::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-go/go-md2man-2.0.3::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/dev-go/go-md2man-2.0.3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-go/go-md2man-2.0.3/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-go/go-md2man-2.0.3/work/go-md2man-2.0.3'
 * S: '/var/tmp/portage/dev-go/go-md2man-2.0.3/work/go-md2man-2.0.3'

>>> Failed to emerge dev-go/go-md2man-2.0.3, Log file:


Code:
matrixstorage ~ # emerge --info
Portage 3.0.61 (python 3.11.8-final-0, default/linux/arm/23.0/split-usr/armv7a_hf/desktop, gcc-13, glibc-2.38-r11, 4.9.44 armv7l)
=================================================================
System uname: Linux-4.9.44-armv7l-ARMv7_Processor_rev_3_-v7l-with-glibc2.38
KiB Mem:     2041904 total,    559772 free
KiB Swap:    4189180 total,   4065624 free
Timestamp of repository gentoo: Mon, 15 Apr 2024 07:30:00 +0000
Head commit of repository gentoo: 89550f1ceb58051c2d518b0e0103300a05ea80b5
sh bash 5.1_p16-r6
ld GNU ld (Gentoo 2.41 p5) 2.41.0
app-misc/pax-utils:        1.3.7::gentoo
app-shells/bash:           5.1_p16-r6::gentoo
dev-build/autoconf:        2.13-r8::gentoo, 2.71-r6::gentoo
dev-build/automake:        1.16.5-r2::gentoo
dev-build/cmake:           3.28.3::gentoo
dev-build/libtool:         2.4.7-r4::gentoo
dev-build/make:            4.4.1-r1::gentoo
dev-build/meson:           1.3.2::gentoo
dev-java/java-config:      2.3.3-r1::gentoo
dev-lang/perl:             5.38.2-r2::gentoo
dev-lang/python:           3.10.14::gentoo, 3.11.8_p1::gentoo, 3.12.2_p1::gentoo
dev-lang/rust-bin:         1.75.0::gentoo
sys-apps/baselayout:       2.14-r2::gentoo
sys-apps/openrc:           0.54::gentoo
sys-apps/sandbox:          2.38::gentoo
sys-devel/binutils:        2.41-r5::gentoo
sys-devel/binutils-config: 5.5::gentoo
sys-devel/gcc:             13.2.1_p20240210::gentoo
sys-devel/gcc-config:      2.11::gentoo
sys-devel/llvm:            15.0.7-r3::gentoo, 17.0.6::gentoo
sys-kernel/linux-headers:  6.6-r1::gentoo (virtual/os-headers)
sys-libs/glibc:            2.38-r11::gentoo
Repositories:

gentoo
    location: /usr/portage
    sync-type: rsync
    sync-uri: rsync://rsync.gentoo.org/gentoo-portage
    priority: -1000
    volatile: True
    sync-rsync-verify-max-age: 3
    sync-rsync-extra-opts:
    sync-rsync-verify-metamanifest: yes
    sync-rsync-verify-jobs: 1

ACCEPT_KEYWORDS="arm"
ACCEPT_LICENSE="@FREE"
CBUILD="armv7a-unknown-linux-gnueabihf"
CFLAGS="-O2 -pipe -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=hard"
CHOST="armv7a-unknown-linux-gnueabihf"
CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt /var/bind"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php8.1/ext-active/ /etc/php/apache2-php8.2/ext-active/ /etc/php/cgi-php8.1/ext-active/ /etc/php/cgi-php8.2/ext-active/ /etc/php/cli-php8.1/ext-active/ /etc/php/cli-php8.2/ext-active/ /etc/php/fpm-php8.1/ext-active/ /etc/php/fpm-php8.2/ext-active/ /etc/php/phpdbg-php8.1/ext-active/ /etc/php/phpdbg-php8.2/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-O2 -pipe -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=hard"
DISTDIR="/usr/portage/distfiles"
ENV_UNSET="CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY GDK_PIXBUF_MODULE_FILE GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR XDG_STATE_HOME"
FCFLAGS="-O2 -pipe -march=armv7-a"
FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs buildpkg-live config-protect-if-modified distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync multilib-strict network-sandbox news parallel-fetch pid-sandbox pkgdir-index-trusted preserve-libs protect-owned qa-unresolved-soname-deps sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
FFLAGS="-O2 -pipe -march=armv7-a"
GENTOO_MIRRORS="http://distfiles.gentoo.org"
LANG="de_DE.UTF-8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
LEX="flex"
LINGUAS="de en"
MAKEOPTS="-j8"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/var/tmp"
SHELL="/bin/bash"
USE="X a52 aac acl airplay alsa apache2 arm bluetooth bluray branding bzip2 cairo caps cdda cdr cec crypt css cups curl dbus dri dts dvd dvdr elogind encode exif flac fpm ftp gd gdbm gif gpm gtk gui iconv icu ipv6 java jce jpeg lcms libnotify mad mng mp3 mp4 mpeg ncurses nls nsplugin ogg opengl openmp pam pango pcre pdf pdo php phython png policykit postgres ppds qt5 readline sdl seccomp server sound spell split-usr sqlite ssl startup-notification svg test-rust threads tiff truetype udev udisks unicode upower usb vorbis vulkan wxwidgets x264 xattr xcb xft xml xmlreader xmlwriter xv xvid zip zlib" ADA_TARGET="gcc_12" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_anon authn_dbm authn_file authz_dbm authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir env expires ext_filter file_cache filter headers include info log_config logio mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="karbon sheets words" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_ARM="edsp thumb thumb2 v4 v5 v6 v7 vfp" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock greis isync itrax mtk3301 ntrip navcom oceanserver oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 tsip tripmate tnt ublox" INPUT_DEVICES="evdev synaptics" KERNEL="linux" L10N="de en ru" LCD_DEVICES="bayrad cfontz glk hd44780 lb216 lcdm001 mtxorb text" LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php8-1" POSTGRES_TARGETS="postgres15" PYTHON_SINGLE_TARGET="python3_11" PYTHON_TARGETS="python3_11" RUBY_TARGETS="ruby31" VIDEO_CARDS="exynos fbdev omap dummy" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipp2p iface geoip fuzzy condition tarpit sysrq proto logmark ipmark dhcpmac delude chaos account"
Unset:  ADDR2LINE, AR, ARFLAGS, AS, ASFLAGS, CC, CCLD, CONFIG_SHELL, CPP, CPPFLAGS, CTARGET, CXX, CXXFILT, ELFEDIT, EMERGE_DEFAULT_OPTS, EXTRA_ECONF, F77FLAGS, FC, GCOV, GPROF, INSTALL_MASK, LC_ALL, LD, LFLAGS, LIBTOOL, MAKE, MAKEFLAGS, NM, OBJCOPY, OBJDUMP, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PYTHONPATH, RANLIB, READELF, RUSTFLAGS, SIZE, STRINGS, STRIP, YACC, YFLAGS


Code:
matrixstorage ~ # emerge -pqv =dev-go/go-md2man-2.0.3::gentoo
[ebuild   R   ] dev-go/go-md2man-2.


Last edited by misterxx on Mon Apr 15, 2024 2:45 pm; edited 1 time in total
Back to top
View user's profile Send private message
fedeliallalinea
Administrator
Administrator


Joined: 08 Mar 2003
Posts: 30925
Location: here

PostPosted: Mon Apr 15, 2024 9:08 am    Post subject: Reply with quote

Probably solved in 2.0.4 version, see this commit.
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
kgdrenefort
Apprentice
Apprentice


Joined: 19 Sep 2023
Posts: 186
Location: Somewhere in the 77

PostPosted: Mon Apr 15, 2024 9:08 am    Post subject: Reply with quote

Hello,

Could you please paste on bpa.st or 0x0.st the file /var/tmp/portage/dev-go/go-md2man-2.0.3/temp/build.log ?

Regards,
GASPARD DE RENEFORT Kévin
_________________
«Gentoo does not have problems, only learning opportunities.» - NeddySeagoon
«If your Gentoo installation isn't valuable to you, feel free to continue to ignore the instructions.» - figueroa
Back to top
View user's profile Send private message
misterxx
Guru
Guru


Joined: 18 Apr 2004
Posts: 509

PostPosted: Mon Apr 15, 2024 9:29 am    Post subject: Reply with quote

Code:
^[[32m * ^[[39;49;00mPackage:    dev-go/go-md2man-2.0.3:0
^[[32m * ^[[39;49;00mRepository: gentoo
^[[32m * ^[[39;49;00mMaintainer: williamh@gentoo.org
^[[32m * ^[[39;49;00mUSE:        arm elibc_glibc kernel_linux
^[[32m * ^[[39;49;00mFEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Unpacking go-md2man-2.0.3.tar.gz to /var/tmp/portage/dev-go/go-md2man-2.0.3/work
>>> Source unpacked in /var/tmp/portage/dev-go/go-md2man-2.0.3/work
>>> Preparing source in /var/tmp/portage/dev-go/go-md2man-2.0.3/work/go-md2man-2.0.3 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-go/go-md2man-2.0.3/work/go-md2man-2.0.3 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-go/go-md2man-2.0.3/work/go-md2man-2.0.3 ...
make -j8 BUILD_FLAGS=-mod=vendor build
WORK=/var/tmp/portage/dev-go/go-md2man-2.0.3/temp/go-build602114224
-buildmode=pie requires external (cgo) linking, but cgo is not enabled
make: *** [Makefile:19: bin/go-md2man] Error 1
 ^[[31;01m*^[[0m ERROR: dev-go/go-md2man-2.0.3::gentoo failed (compile phase):
 ^[[31;01m*^[[0m   emake failed
 ^[[31;01m*^[[0m
 ^[[31;01m*^[[0m If you need support, post the output of `emerge --info '=dev-go/go-md2man-2.0.3::gentoo'`,
 ^[[31;01m*^[[0m the complete build log and the output of `emerge -pqv '=dev-go/go-md2man-2.0.3::gentoo'`.
 ^[[31;01m*^[[0m The complete build log is located at '/var/tmp/portage/dev-go/go-md2man-2.0.3/temp/build.log'.
 ^[[31;01m*^[[0m The ebuild environment file is located at '/var/tmp/portage/dev-go/go-md2man-2.0.3/temp/environment'.
 ^[[31;01m*^[[0m Working directory: '/var/tmp/portage/dev-go/go-md2man-2.0.3/work/go-md2man-2.0.3'
 ^[[31;01m*^[[0m S: '/var/tmp/portage/dev-go/go-md2man-2.0.3/work/go-md2man-2.0.3'
Back to top
View user's profile Send private message
misterxx
Guru
Guru


Joined: 18 Apr 2004
Posts: 509

PostPosted: Mon Apr 15, 2024 11:52 am    Post subject: Reply with quote

does anyone have any ideas what i could try?
Back to top
View user's profile Send private message
kgdrenefort
Apprentice
Apprentice


Joined: 19 Sep 2023
Posts: 186
Location: Somewhere in the 77

PostPosted: Mon Apr 15, 2024 12:06 pm    Post subject: Reply with quote

misterxx wrote:
does anyone have any ideas what i could try?


Well:

fedeliallalinea wrote:
Probably solved in 2.0.4 version, see this commit.


Also, I can read this error:

Code:
-buildmode=pie requires external (cgo) linking, but cgo is not enabled


If fedeliallalinea is not right, that could be a good starting point.

'pie' seems to need 'cgo'. I do not see here a cgo flag, but there is some that seems related, as 'go'.

Be aware I'm just speculating from what your last output has as an error.

Regards,
GASPARD DE RENEFORT Kévin
_________________
«Gentoo does not have problems, only learning opportunities.» - NeddySeagoon
«If your Gentoo installation isn't valuable to you, feel free to continue to ignore the instructions.» - figueroa
Back to top
View user's profile Send private message
misterxx
Guru
Guru


Joined: 18 Apr 2004
Posts: 509

PostPosted: Mon Apr 15, 2024 12:10 pm    Post subject: Reply with quote

2.0.4 is still not available, https://packages.gentoo.org/packages/dev-go/go-md2man


When I try to install the previous version go-md2man-2.0.2, I get the same effect


Last edited by misterxx on Mon Apr 15, 2024 12:13 pm; edited 1 time in total
Back to top
View user's profile Send private message
kgdrenefort
Apprentice
Apprentice


Joined: 19 Sep 2023
Posts: 186
Location: Somewhere in the 77

PostPosted: Mon Apr 15, 2024 12:12 pm    Post subject: Reply with quote

misterxx wrote:
When I try to install the previous version go-md2man-2.0.2, I get the same effect


Are you reading our replies ?

Regards,
GASPARD DE RENEFORT Kévin
_________________
«Gentoo does not have problems, only learning opportunities.» - NeddySeagoon
«If your Gentoo installation isn't valuable to you, feel free to continue to ignore the instructions.» - figueroa
Back to top
View user's profile Send private message
misterxx
Guru
Guru


Joined: 18 Apr 2004
Posts: 509

PostPosted: Mon Apr 15, 2024 12:15 pm    Post subject: Reply with quote

kgdrenefort wrote:

'pie' seems to need 'cgo'. I do not see here a cgo flag, but there is some that seems related, as 'go'.


With flag USE="go" I get the same result
Back to top
View user's profile Send private message
kgdrenefort
Apprentice
Apprentice


Joined: 19 Sep 2023
Posts: 186
Location: Somewhere in the 77

PostPosted: Mon Apr 15, 2024 12:17 pm    Post subject: Reply with quote

misterxx wrote:
kgdrenefort wrote:

'pie' seems to need 'cgo'. I do not see here a cgo flag, but there is some that seems related, as 'go'.


With flag USE="go" I get the same result


It would be nice to paste it instead of stating it's the same, in my humble opinion, sometimes we think it's the same while it's not :wink:.

I can't help you more, sadly, for now.

Did you try the 2.0.4 as pointed out by Neddy ? If you can.

Regards,
GASPARD DE RENEFORT Kévin
_________________
«Gentoo does not have problems, only learning opportunities.» - NeddySeagoon
«If your Gentoo installation isn't valuable to you, feel free to continue to ignore the instructions.» - figueroa
Back to top
View user's profile Send private message
misterxx
Guru
Guru


Joined: 18 Apr 2004
Posts: 509

PostPosted: Mon Apr 15, 2024 12:26 pm    Post subject: Reply with quote

kgdrenefort wrote:

Did you try the 2.0.4 as pointed out by Neddy ? If you can.


version 2.0.4 is not available, so I can't install it either

https://packages.gentoo.org/packages/dev-go/go-md2man

Code:
matrixstorage /etc/portage # emerge =dev-go/go-md2man-2.0.4
Calculating dependencies... done!
Dependency resolution took 7.51 s (backtrack: 0/20).


emerge: there are no ebuilds to satisfy "=dev-go/go-md2man-2.0.4".
Back to top
View user's profile Send private message
kgdrenefort
Apprentice
Apprentice


Joined: 19 Sep 2023
Posts: 186
Location: Somewhere in the 77

PostPosted: Mon Apr 15, 2024 12:44 pm    Post subject: Reply with quote

misterxx wrote:
kgdrenefort wrote:

Did you try the 2.0.4 as pointed out by Neddy ? If you can.


version 2.0.4 is not available, so I can't install it either

https://packages.gentoo.org/packages/dev-go/go-md2man

Code:
matrixstorage /etc/portage # emerge =dev-go/go-md2man-2.0.4
Calculating dependencies... done!
Dependency resolution took 7.51 s (backtrack: 0/20).


emerge: there are no ebuilds to satisfy "=dev-go/go-md2man-2.0.4".


Indeed, that will be more complicated.

Then, Neddy is probably right since I can see this bug: 924632

At least, that is not your fault.

guess you can report the bug as well, it seems to be relevant, but I prefer letting you choose if that is really relevant, not really used to bug report, sorry.

Worst case is, I think, you'll have to wait a little.

Regards,
GASPARD DE RENEFORT Kévin
_________________
«Gentoo does not have problems, only learning opportunities.» - NeddySeagoon
«If your Gentoo installation isn't valuable to you, feel free to continue to ignore the instructions.» - figueroa
Back to top
View user's profile Send private message
fedeliallalinea
Administrator
Administrator


Joined: 08 Mar 2003
Posts: 30925
Location: here

PostPosted: Mon Apr 15, 2024 12:48 pm    Post subject: Reply with quote

You can try to apply this patch with /etc/portage/patches.
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
misterxx
Guru
Guru


Joined: 18 Apr 2004
Posts: 509

PostPosted: Mon Apr 15, 2024 2:43 pm    Post subject: Reply with quote

I masked the package dev-lang/go-1.22.1 and called

Code:
emerge --ask --regex-search-auto=y @golang-rebuild


7 packages dependent on dev-lang/go have been recompiled. The system is now running go-1.21.8 instead 1.22.1. And dev-go/go-md2man-2.0.3 has also been successfully installed.

Thanks to everyone involved for their suggestions
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 21650

PostPosted: Mon Apr 15, 2024 2:55 pm    Post subject: Reply with quote

misterxx wrote:
version 2.0.4 is not available, so I can't install it either
The first statement does not require the second. You are correct that version 2.0.4 is not presently available in the Gentoo Portage tree. However, that absence does not prevent you using a Portage overlay to install version 2.0.4 from an ebuild. For many packages, a minor version bump like this can be done with a simple rename.
Back to top
View user's profile Send private message
misterxx
Guru
Guru


Joined: 18 Apr 2004
Posts: 509

PostPosted: Tue Apr 16, 2024 7:47 am    Post subject: Reply with quote

Hu wrote:
However, that absence does not prevent you using a Portage overlay to install version 2.0.4 from an ebuild. For many packages, a minor version bump like this can be done with a simple rename.


Since it's simple, could you briefly explain how to do it using this example?

Thank you very much in advance!
Back to top
View user's profile Send private message
fedeliallalinea
Administrator
Administrator


Joined: 08 Mar 2003
Posts: 30925
Location: here

PostPosted: Tue Apr 16, 2024 7:53 am    Post subject: Reply with quote

misterxx wrote:
Since it's simple, could you briefly explain how to do it using this example?

Thank you very much in advance!

https://wiki.gentoo.org/wiki/Creating_an_ebuild_repository
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
misterxx
Guru
Guru


Joined: 18 Apr 2004
Posts: 509

PostPosted: Tue Apr 16, 2024 12:33 pm    Post subject: Reply with quote

fedeliallalinea wrote:
misterxx wrote:
Since it's simple, could you briefly explain how to do it using this example?

Thank you very much in advance!

https://wiki.gentoo.org/wiki/Creating_an_ebuild_repository


Thank your for instructions link.

I have followed the instructions up to the point where I need the ebuild file for go-md2man-2.0.4. Where do I get it from?
Back to top
View user's profile Send private message
fedeliallalinea
Administrator
Administrator


Joined: 08 Mar 2003
Posts: 30925
Location: here

PostPosted: Tue Apr 16, 2024 12:40 pm    Post subject: Reply with quote

misterxx wrote:
I have followed the instructions up to the point where I need the ebuild file for go-md2man-2.0.4. Where do I get it from?

Hu wrote:
For many packages, a minor version bump like this can be done with a simple rename.

You can copy go-md2man-2.0.3.ebuild and rename it to go-md2man-2.0.4.ebuild.
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
misterxx
Guru
Guru


Joined: 18 Apr 2004
Posts: 509

PostPosted: Tue Apr 16, 2024 1:17 pm    Post subject: Reply with quote

fedeliallalinea wrote:
misterxx wrote:
I have followed the instructions up to the point where I need the ebuild file for go-md2man-2.0.4. Where do I get it from?

Hu wrote:
For many packages, a minor version bump like this can be done with a simple rename.

You can copy go-md2man-2.0.3.ebuild and rename it to go-md2man-2.0.4.ebuild.


ok, I've done it.

Now I get the following.

Code:
 * Package:    dev-go/go-md2man-2.0.4:0
 * Repository: portage-ols
 * USE:        arm elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Unpacking go-md2man-2.0.4.tar.gz to /var/tmp/portage/dev-go/go-md2man-2.0.4/work
go mod verify
go: github.com/russross/blackfriday/v2@v2.1.0: Get "https://proxy.golang.org/github.com/russross/blackfriday/v2/@v/v2.1.0.mod": dial tcp: lookup proxy.golang.org on 192.168.178.1:53: dial udp 192.168.178.1:53: connect: network is unreachable
 * ERROR: dev-go/go-md2man-2.0.4::portage-ols failed (unpack phase):
 *   go mod verify failed
 *
 * Call stack:
 *     ebuild.sh, line  136:  Called src_unpack
 *   environment, line 1884:  Called go-module_src_unpack
 *   environment, line 1487:  Called ego 'mod' 'verify'
 *   environment, line  840:  Called die
 * The specific snippet of code:
 *       "$@" || die -n "${*} failed"
 *
 * If you need support, post the output of `emerge --info '=dev-go/go-md2man-2.0.4::portage-ols'`,
 * the complete build log and the output of `emerge -pqv '=dev-go/go-md2man-2.0.4::portage-ols'`.
 * The complete build log is located at '/var/tmp/portage/dev-go/go-md2man-2.0.4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-go/go-md2man-2.0.4/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-go/go-md2man-2.0.4/work/go-md2man-2.0.4'
 * S: '/var/tmp/portage/dev-go/go-md2man-2.0.4/work/go-md2man-2.0.4'


apparently it is trying to request something via UDP port 53 and my router is blocking it, is it normal?
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 21650

PostPosted: Tue Apr 16, 2024 2:52 pm    Post subject: Reply with quote

misterxx wrote:
ok, I've done it.

Now I get the following.
Code:
go mod verify
go: github.com/russross/blackfriday/v2@v2.1.0: Get "https://proxy.golang.org/github.com/russross/blackfriday/v2/@v/v2.1.0.mod": dial tcp: lookup proxy.golang.org on 192.168.178.1:53: dial udp 192.168.178.1:53: connect: network is unreachable
apparently it is trying to request something via UDP port 53 and my router is blocking it, is it normal?
That is likely the network sandbox, not your router. As to whether it is normal, the answer is complicated. It is normal for the network sandbox to block network access during most phases of package compilation. It is normal for most packages to work properly with this. It is normal for Google Golang packages to be broken with this, because the language strongly encourages developers to rig their packages to download from the Internet during the build. I had hoped that since the existing ebuild worked properly with the sandbox, that the new version would likewise succeed. That seems not to be the case. Your choices are:
  • Disable the network sandbox, allowing the build to download whatever it wants from wherever it wants on the Internet. I discourage this.
  • Create a 2.0.3-r1 ebuild that applies the specific patch identified above to the 2.0.3 sources. This might succeed where 2.0.4 fails. It might not.
  • Modify the ebuild to make the package work while offline. I cannot offer a complexity estimate on this.
  • Wait for someone who maintains this package to do the above bullet for you.
Back to top
View user's profile Send private message
misterxx
Guru
Guru


Joined: 18 Apr 2004
Posts: 509

PostPosted: Tue Apr 16, 2024 3:12 pm    Post subject: Reply with quote

Thank you!

I tried it with ebuilt 2.0.3-r1, which gives the same error as version 2.0.3. so you just don't get any network errors, you don't gain anything.


Code:
>>> Emerging (1 of 1) dev-go/go-md2man-2.0.3-r1::portage-ols
 * go-md2man-2.0.3.tar.gz BLAKE2B SHA512 size ;-) ...                                                                                                    [ ok ]
>>> Unpacking source...
>>> Unpacking go-md2man-2.0.3.tar.gz to /var/tmp/portage/dev-go/go-md2man-2.0.3-r1/work
>>> Source unpacked in /var/tmp/portage/dev-go/go-md2man-2.0.3-r1/work
>>> Preparing source in /var/tmp/portage/dev-go/go-md2man-2.0.3-r1/work/go-md2man-2.0.3 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-go/go-md2man-2.0.3-r1/work/go-md2man-2.0.3 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-go/go-md2man-2.0.3-r1/work/go-md2man-2.0.3 ...
make -j8 BUILD_FLAGS=-mod=vendor build
WORK=/var/tmp/portage/dev-go/go-md2man-2.0.3-r1/temp/go-build1042611085
-buildmode=pie requires external (cgo) linking, but cgo is not enabled
make: *** [Makefile:19: bin/go-md2man] Error 1
 * ERROR: dev-go/go-md2man-2.0.3-r1::portage-ols failed (compile phase):
 *   emake failed
 *
 * If you need support, post the output of `emerge --info '=dev-go/go-md2man-2.0.3-r1::portage-ols'`,
 * the complete build log and the output of `emerge -pqv '=dev-go/go-md2man-2.0.3-r1::portage-ols'`.
 * The complete build log is located at '/var/tmp/portage/dev-go/go-md2man-2.0.3-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-go/go-md2man-2.0.3-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-go/go-md2man-2.0.3-r1/work/go-md2man-2.0.3'
 * S: '/var/tmp/portage/dev-go/go-md2man-2.0.3-r1/work/go-md2man-2.0.3'
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 21650

PostPosted: Tue Apr 16, 2024 3:14 pm    Post subject: Reply with quote

How did you modify the 2.0.3-r1 ebuild to include the cited patch? Adding -r1 alone won't do anything. You need to make the ebuild apply the patch, too. If in doubt, show the 2.0.3-r1 ebuild you used.
Back to top
View user's profile Send private message
misterxx
Guru
Guru


Joined: 18 Apr 2004
Posts: 509

PostPosted: Tue Apr 16, 2024 4:28 pm    Post subject: Reply with quote

Hu wrote:
How did you modify the 2.0.3-r1 ebuild to include the cited patch? Adding -r1 alone won't do anything. You need to make the ebuild apply the patch, too. If in doubt, show the 2.0.3-r1 ebuild you used.


OK,

I would like to try it out. Do I have to provide the complete contents of as a patch file from https://github.com/cpuguy83/go-md2man/commit/21f901d9f38ede08f22fdf733166b0283ae4bde2.patch, or from which line?
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 21650

PostPosted: Tue Apr 16, 2024 6:16 pm    Post subject: Reply with quote

You only need to have the ebuild apply the parts that fix the build error. It is likely safe to apply the entire patch though, which would be simpler than trimming out what you do not need.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on ARM All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum