unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Reza Housseini <reza.housseini@gmail.com>
To: Ekaitz Zarraga <ekaitz@elenq.tech>
Cc: help-guix@gnu.org
Subject: Re: Need help packaging IUP (part 1: IM)
Date: Tue, 21 Mar 2023 17:01:30 +0100	[thread overview]
Message-ID: <e4c79b8a-4fff-f42a-08a5-f57c4515e815@gmail.com> (raw)
In-Reply-To: <uyD_spso5JxO98d1KEAVsHh8zLqPXspyNEH-aAz2oefn33HdffHaU8mkKiZPteYs4LI9MUGnReQZMF66qabD9ATLKhZsNkxV3oLQ3hUDPts=@elenq.tech>


[-- Attachment #1.1.1: Type: text/plain, Size: 972 bytes --]

On 3/21/23 16:43, Ekaitz Zarraga wrote:
>   
>>> Have you tried something like
>>>
>>> (add-before 'configure 'set-ldflags
>>> (lambda _
>>> (substitute* "tecmake.mak"
>>> (("STDLDFLAGS := -shared" all) (string-append all "
>>> -Wl,-rpath="#$output "/lib")))))
>>>
>>> not tested though.
>>
>>
>> I'll give a try to this. I didn't try it!
>> Thanks!
>>
> 
> Worked! Thank you!!

There is a confusion (which I also had) linking LDFLAGS to GCC, but 
there is no connection, see for example this stackoverflow answer: 
https://stackoverflow.com/a/16047559.
There are only a handful of environment variables affecting the GCC 
compiler (https://gcc.gnu.org/onlinedocs/gcc/Environment-Variables.html) 
and none of them is for setting rpaths. Therefore you have to provide 
them explicitly to the compiler via normal flags.

-- 
Reza Housseini

This message is signed with my GnuPG key:

     C0F3 0812 9AF2 80F4 0830 C2C1 C375 C6AF 0512 5C52


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 15557 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2023-03-21 16:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 22:44 Need help packaging IUP (part 1: IM) Ekaitz Zarraga
2023-03-20 22:59 ` Felix Lechner via
2023-03-21 12:25 ` Reza Housseini
2023-03-21 12:45   ` Ekaitz Zarraga
2023-03-21 15:43     ` Ekaitz Zarraga
2023-03-21 16:01       ` Reza Housseini [this message]

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=e4c79b8a-4fff-f42a-08a5-f57c4515e815@gmail.com \
    --to=reza.housseini@gmail.com \
    --cc=ekaitz@elenq.tech \
    --cc=help-guix@gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).