Hi
Nothing happend, it dropped me right to the shell - no clue. ;)
No error output, nothing else - an error code maybe... I didnt check (I
can try tomorrow again).
Am 29.09.2017 um 23:34 schrieb Jason Bacon:
>
> What happened after this?
>
> If pkgsrc is bootstrapped to use the GCC compiler collection,
> it will look for gfortran in the PATH when building certain packages.
> ============================================================================
>
>
> Did you let it continue? Did it terminate with an error?
>
> It should find your native CC and try to bootstrap with that. GCC 4.2.3
> is too old to be very useful with the current pkgsrc collection.
>
> The reason I suggested auto-pkgsrc-setup is that it scrubs the
> environment before boostrapping, so it's a good litmus test for
> pollution that might trip up the bootstrap process.
>
> If you send me all of the auto-pkgsrc-setup output, I might be able to
> identify something relevant.
>
> Regards,
>
> JB
>
> On 09/29/17 10:58, Georg Bege wrote:
>> Hi
>>
>> Yes Im not sure myself, I dont have much HP-UX experience - for years
>> I've been tinkering with SGI Irix.
>> However I got my hands on this box and pkgsrc would be great. ;)
>> I've added /bin to the PATH though, but it doesnt seem to make a lot
>> change.
>>
>> I've tried that script you mentioned, never heard of it before.
>> But it doesnt want to continue either.
>>
>> After setting my prefix and answering the scripted dialog:
>> ============================================================================
>>
>>
>> Press Enter to continue...
>>
>> ============================================================================
>>
>> You will need at least a C compiler and a C++ compiler to build most
>> pkgsrc packages. Many packages also require a Fortran compiler. On
>> many systems, such as NetBSD, pkgsrc can build its own Fortran compilers.
>> On RHEL/CentOS, using the gfortran compiler provided via Yum works well.
>>
>> If pkgsrc is bootstrapped to use the GCC compiler collection,
>> it will look for gfortran in the PATH when building certain packages.
>> ============================================================================
>>
>> # gcc --version
>> gcc (GCC) 4.2.3
>> Copyright (C) 2007 Free Software Foundation, Inc.
>> This is free software; see the source for copying conditions. There
>> is NO
>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
>> PURPOSE.
>>
>> # which gcc
>> /usr/local/bin/gcc
>>
>> -----------------------------------------------------------------------------
>>
>> How am I supposed to use this thing?
>>
>> regards,
>> Georg
>>
>> Am 29.09.2017 um 16:11 schrieb Jason Bacon:
>>> Is it normal not to have /bin in PATH on HP-UX? I could imagine
>>> bootstrap needing some basic Unix tools from there.
>>>
>>> Just for curiosity's sake could you try auto-pkgsrc-setup?
>>>
>>> http://acadix.biz/pkgsrc.php
>>>
>>> On 09/29/17 04:53, Georg Bege wrote:
>>>> Hi
>>>>
>>>> No sadly not...
>>>>
>>>> bmake: stopped in /opt/pkgsrc/pkgtools/bootstrap-mk-files
>>>> ===> exited with status 1
>>>> aborted.
>>>> # which bmake
>>>> no bmake in /usr/bin /usr/sbin /sbin
>>>> # bmake
>>>> bash: bmake: command not found
>>>>
>>>> ... just tried bash here in order to see if it makes any difference -
>>>> but well shouldnt be the case.
>>>>
>>>> Am 29.09.2017 um 10:13 schrieb David Brownlee:
>>>>> Just checking, do you have any other bmake binaries in your path?
>>>>>
>>>>> On 29 Sep 2017 08:27, "Georg Bege" <georg@bege.email> wrote:
>>>>>
>>>>> Hello guys,
>>>>>
>>>>> Im having problem with bootstrapping pkgsrc on HP-UX.
>>>>> Basically the bootstrap-mk-files make is failing, it spills a
>>>>> lot of
>>>>> "bmake: unexpected regex error" prior to this.
>>>>>
>>>>> Then all I get is:
>>>>> -------------------------snip-------------------------
>>>>> *** Failed target: barrier
>>>>> *** Failed command: set -e; if test -n "" &&
>>>>> /opt/pkgsrc/bootstrap/work/sbin/pkg_info -K /usr/pkg/pkgdb -qe
>>>>> bootstrap-mk-files-20170802; then /usr/bin/echo ===\> "Skipping
>>>>> installation of already handled package"; else cd
>>>>> /opt/pkgsrc/pkgtools/bootstrap-mk-files && /usr/bin/env
>>>>> MAKECONF=/opt/pkgsrc/bootstrap/work/mk.conf
>>>>>
>>>>> PATH=/opt/pkgsrc/bootstrap/work/wrk//work/.wrapper/bin:/opt/pkgsrc/bootstrap/work/wrk//work/.buildlink/bin:/opt/pkgsrc/bootstrap/work/wrk//work/.tools/bin:/usr/pkg/bin:/usr/bin:/usr/sbin:/sbin
>>>>>
>>>>>
>>>>> /opt/pkgsrc/bootstrap/work/bin/bmake
>>>>> _MAKE=/opt/pkgsrc/bootstrap/work/bin/bmake OPSYS=HPUX
>>>>> OS_VERSION=11.11
>>>>> LOWER_OPSYS=hpux _PKGSRCDIR=/opt/pkgsrc
>>>>> PKGTOOLS_VERSION=20170419
>>>>> _CC=/usr/bin/cc _PATH_ORIG=/usr/bin:/usr/sbin:/sbin
>>>>> _PKGSRC_BARRIER=yes
>>>>> ALLOW_VULNERABLE_PACKAGES= install || { exitcode="$?";
>>>>> /usr/bin/env
>>>>> MAKECONF=/opt/pkgsrc/bootstrap/work/mk.conf
>>>>>
>>>>> PATH=/opt/pkgsrc/bootstrap/work/wrk//work/.wrapper/bin:/opt/pkgsrc/bootstrap/work/wrk//work/.buildlink/bin:/opt/pkgsrc/bootstrap/work/wrk//work/.tools/bin:/usr/pkg/bin:/usr/bin:/usr/sbin:/sbin
>>>>>
>>>>>
>>>>> /opt/pkgsrc/bootstrap/work/bin/bmake
>>>>> _MAKE=/opt/pkgsrc/bootstrap/work/bin/bmake OPSYS=HPUX
>>>>> OS_VERSION=11.11
>>>>> LOWER_OPSYS=hpux _PKGSRCDIR=/opt/pkgsrc
>>>>> PKGTOOLS_VERSION=20170419
>>>>> _CC=/usr/bin/cc _PATH_ORIG=/usr/bin:/usr/sbin:/sbin
>>>>> _PKGSRC_BARRIER=yes
>>>>> barrier-error-check; exit "$exitcode"; }; fi
>>>>> *** Error code 2
>>>>> -------------------------snip-------------------------
>>>>>
>>>>> The system is a fresh install of HP-UX 11.11 with a couple of
>>>>> patches
>>>>> like GOLDPKG.
>>>>>
>>>>> I'll attach the bootstrap log and a *very noisy* output of bmake
>>>>> with
>>>>> all debugging enabled!
>>>>> Of course the latter will be XZ compressed.
>>>>>
>>>>> regards,
>>>>> Georg
>>>>>
>>>>> --
>>>>> Georg Bege
>>>>> Mail: georg@bege.email
>>>>> XMPP: therion%ninth-art.de@localhost <mailto:therion%ninth-art.de@localhost>
>>>>> IRC: megaTherion @ Freenode
>>>>>
>
--
Georg Bege
Mail: georg@bege.email
XMPP: therion%ninth-art.de@localhost
IRC: megaTherion @ Freenode
Attachment:
signature.asc
Description: OpenPGP digital signature