From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: C D <dellicker@live.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] Forcing linker to look at right library path?
Date: Tue, 14 Mar 2023 22:07:43 +0100 [thread overview]
Message-ID: <20230314220743.21dcc880@windsurf> (raw)
In-Reply-To: <SJ0PR05MB7625BB7889E5DD3876C01E89D4BE9@SJ0PR05MB7625.namprd05.prod.outlook.com>
On Tue, 14 Mar 2023 18:43:29 +0000
C D <dellicker@live.com> wrote:
> I'm trying to build sedcli (https://github.com/sedcli/sedcli); the version
> I'm building is a slightly modified private branch (added some debugging), but
> the Makefile and configure script are basically identical. I went through
> the Makefile and added $(DESTDIR) in appropriate locations to make the files
> go where they need to, but after running a "make sedcli-reconfigure" I realized
> the configure script isn't taking any off options Buildroot is using to attempt
> to make it do the right thing, and I'm assuming this is where my problem is.
> The output I get from it is:
Could you push a Buildroot branch with your package added, and a
defconfig that allows to reproduce the problem? This will be needed to
give you some meaningful support.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-03-14 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 23:33 [Buildroot] Forcing linker to look at right library path? C D
2023-03-14 7:58 ` Thomas Petazzoni via buildroot
2023-03-14 18:43 ` C D
2023-03-14 21:07 ` Thomas Petazzoni via buildroot [this message]
2023-03-15 7:18 ` Peter Korsgaard
2023-03-15 19:59 ` C D
[not found] <mailman.10087.1678750430.50374.buildroot@buildroot.org>
2023-03-14 7:46 ` Andreas Ziegler
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=20230314220743.21dcc880@windsurf \
--to=buildroot@buildroot.org \
--cc=dellicker@live.com \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.